AI Terminal Deck
Launch supported AI command-line tools in Windows Terminal with process-local tool discovery and read-only readiness checks that never persist PATH changes.
The problem it solves
AI Terminal Deck AI Terminal Deck detects Codex CLI, Claude Code, and Kimi Code, offers consent-based guided installation for anything missing, and opens the available tools together in one maximized Windows Terminal window. It is a single, reviewable batch file for people who want independent access to multiple AI coding agents without installing another dashboard or orchestration service.
Who AI Terminal Deck is for
- Developers and maintainers who need reviewable evidence before changing or releasing software.
- Users working with AI coding, guided setup, terminal who want the documented v1.0.5 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Launch supported AI command-line tools in Windows Terminal with process-local tool discovery and read-only readiness checks that never persist PATH changes.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.0.5
Capabilities below come from the current project README and release documentation.
AI Terminal Deck detects Codex CLI, Claude Code, and Kimi Code, offers consent-based guided installation for anything missing, and opens the available tools together in one maximized Windows Terminal window. It is a single, reviewable batch file for people who want independent access to multiple AI coding agents without installing another dashboard or orchestration service.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Verified release evidence
This project does not currently publish a screenshot or dedicated example folder. The current README, tests, changelog, tagged release, and source repository remain the verified examples of its behavior.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
Built with
- Batch
- PowerShell
- Windows Terminal
Changelog
Release notes from the canonical v1.0.5 source tag.
All notable changes are documented here. The project follows Semantic Versioning.
Official install-folder discovery now changes only the launcher's process PATH. Readiness checks never persist user or machine environment settings, prompt, install, or launch tools, including missing-tool and invalid-directory paths. Persistent PATH repair has been removed; users can configure their environment separately if they want a permanent change. Synthetic Windows fixtures intercept every PowerShell environment/installer/launch operation and use fake official install folders.
- Recognize Claude Code at its official Windows location,
%USERPROFILE%\.local\bin\claude.exe, even when the upstream installer does not updatePATH. - Activate known official Codex, Claude, and Kimi install folders before every detection pass.
- Add Claude's verified official install folder to the user
PATHso new terminals can invokeclaudedirectly.
- Clarify provider-specific login behavior and that AI Terminal Deck never shares credentials.
- Clarify that the selected working directory is a starting folder, not a filesystem sandbox.
- Collect all missing-tool installation choices before executing any installer.
- Run the official Codex installer with its supported
CODEX_NON_INTERACTIVE=1mode so its internal “Start Codex now?” question cannot launch Codex and block Claude or Kimi setup. - Recheck all tools after the complete setup phase and require a final confirmation before opening the detected panes.
- Remove a batch escape character that was passed literally into PowerShell and caused every consented Codex, Claude, and Kimi installer to fail with
A positional parameter cannot be found that accepts argument '^'. - Add regression coverage for the exact installer command parsing failure.
- Keep dependency, working-directory, and Windows Terminal startup errors visible when the launcher is opened by double-click.
- Add a clear keypress prompt before closing after startup failures.
- Preserve non-interactive test execution through the internal
AI_TERMINAL_DECK_NO_PAUSEtest seam.
- Detect each supported AI CLI independently and offer a separate, consent-gated official installer for every missing tool.
- Recheck the active
PATHafter installation attempts and immediately continue into the terminal layout when possible. - Automatically open one, two, or three panes based on the CLIs actually available; two-pane and three-pane layouts divide the window evenly.
- Offer Windows Terminal installation through its Microsoft
wingetpackage when the required terminal host is missing. - Keep
--checkstrictly read-only with no installation prompts or launches.
Quick start
The shortest documented path into the current release.
Open the current release, follow the repository README for AI Terminal Deck, and use only the documented inputs and commands for v1.0.5.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
- Windows only; the launcher depends on
wt.exeand Windows batch scripting. - It arranges one to three independent interfaces. It does not coordinate agents or merge their answers.
- It can launch official installers only after individual confirmation. It does not silently install, update, uninstall, or authenticate any AI tool.
- It does not install Git for Windows, which Kimi Code expects for normal use.
- It does not manage subscriptions, usage limits, model selection, or login sessions.
- If an AI process exits, its pane remains at PowerShell so an error message can still be read.
- Very narrow displays may be more comfortable with one or two panes or separate tabs.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
- The launcher contains no analytics, telemetry, API keys, or credential storage.
- Network access occurs only after explicit consent to run one of the displayed official installers.
- Authentication is handled independently by each installed AI CLI.
- The launcher checks every supported command, offers guided setup for missing ones, refreshes its process
PATH, and checks again before opening Windows Terminal. - An invalid working directory stops with an explanation instead of silently falling back elsewhere.
- Startup and dependency errors remain visible until you press a key, including when the launcher is opened by double-click.
- AI Terminal Deck does not relay prompts, responses, credentials, or files between agents.
All three agents receive the same starting directory. They can safely discuss or inspect that directory independently, but simultaneous edits to one Git checkout can conflict. Use separate Git worktrees or give write access to only one agent at a time.
License and release
AI Terminal Deck is published under MIT. The current cataloged release is v1.0.5, published 2026-10-16.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
AI Terminal Deck v1.0.5
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: d31fdc21aed4c9ad.