Setup and quick reference
Windows Terminal AI Workspace Setup
Create a predictable Windows Terminal workspace for local AI tools while keeping shells, paths, profiles, and credentials explicit.
- Format
- How To
- Level
- Beginner
- Audience
- Learner, Developer, Operator
- Owner
- Project42 Editorial
- Review cadence
- Every 90 days
- Prerequisites
- Windows Terminal installed through a Microsoft-supported channel; At least one supported shell; A version-controlled workspace
Choose one shell and path boundary per task
Windows Terminal hosts command-line profiles; it does not make PowerShell, Command Prompt, and WSL path or environment semantics interchangeable. Record the selected profile, executable, starting directory, repository root, and whether the task runs against Windows or Linux files before invoking an AI tool.
Use the publisher's current profile and startup-setting documentation. Dynamic profiles can be generated by installed tools, so verify the profile source and command line instead of assuming every visible profile was manually configured.
Configure the smallest predictable workspace
Set an intentional default profile or launch a named profile explicitly. Use a stable starting directory, keep project credentials outside the profile definition, and avoid copying settings files between machines without reviewing paths and installed shells.
When an AI tool needs a runtime such as Node.js or Python, verify it inside the same profile that will run the tool. A successful version check in PowerShell does not prove that the runtime is available inside WSL, or the reverse.
Task: [TOOL OR REPOSITORY OUTCOME]
Scope: [WINDOWS OR WSL, PROFILE, STARTING DIRECTORY, AND REPOSITORY]
Permissions: [FILESYSTEM, PROCESS, NETWORK, AND ELEVATION LIMITS]
Profile evidence: [PROFILE NAME, SOURCE, COMMAND LINE, AND SHELL VERSION]
Runtime evidence: [GIT, NODE/PYTHON, AND AGENT VERSION CHECKS IN THIS PROFILE]
Path boundary: [WINDOWS PATH OR LINUX PATH; DO NOT MIX SILENTLY]
Stop conditions: [UNEXPECTED ELEVATION, WRONG ROOT, MISSING RUNTIME, OR PROFILE DRIFT]
Verification: [OPEN FRESH TAB, CONFIRM SHELL/PATH, RUN READ-ONLY REPOSITORY CHECK]
Recovery: [RESTORE BACKED-UP SETTINGS OR REMOVE ONLY THE NEW PROFILE, THEN REOPEN]Expected result and verification
Expected evidence is a fresh terminal tab that opens the intended shell and directory, resolves the expected Git and runtime executables, identifies the repository root, and performs a read-only status check without elevation. Keep a backup or version-controlled copy of the settings change without credentials.
If Terminal stops loading a profile or opens the wrong environment, use the documented settings interface or backed-up settings to reverse only the last change. Reopen Terminal and repeat the shell, path, executable, and repository checks before allowing an agent to edit files.