jy1655/tabcli

한국어 follows this README; this one is the reference when they differ.
Use tabcli to launch the Codex, Claude Code, Agy, and Pi CLIs you already have installed and
signed in to, in terminal tabs or windows you can watch. Read the result, send follow-up work to the
same conversation, and explicitly close the session when you finish. TAB runs on macOS and native
Windows; Linux, including Linux processes in WSL, is unsupported, and Warp support is limited.
Try a session
After installing tabcli and signing in to Codex 0.149.0 or newer, run this from your
project directory. Scripts and other agents can use tabcli while you watch the CLI's conversation
and tool activity. Each CLI keeps its own UI and settings.
The example uses provider defaults. The ids and results below are illustrative; use your own ids.
ask waits for the result. The session stays open so you can continue the same conversation:
Use tabcli hold SESSION to refuse further follow-ups until tabcli hold SESSION --release.
The current turn continues.
Close the session when you finish; its recorded results remain available.
If close fails, inspect the reported session and run tabcli doctor SESSION before retrying;
follow the close recovery instructions.
A timeout while waiting for a result does not cancel work already delivered. A startup timeout can
prevent launch. Inspect the original request before retrying; follow the
request recovery instructions.
If launch fails, run tabcli doctor --provider codex --probe. For an existing session, run
tabcli doctor SESSION and tabcli inspect SESSION --timeline, replacing SESSION with its id;
see diagnostics.
Support
These tables summarize selected historical runs. The linked records identify the tested versions,
settings, and limitations. These are not checks of every combination on the current version.
| Platform / terminal | Status | Recorded live evidence |
| --- | --- | --- |
| macOS / iTerm2 | Implemented | Codex, 2026-10-07 |
| macOS / Terminal.app | Implemented | Codex, 2026-10-07 |
| macOS / Ghostty | Implemented | Codex, 2026-10-07 |
| macOS / WezTerm | Implemented | Codex/Claude/Agy, 2026-10-07 |
| macOS / Warp | Limited | Not verified |
| Native Windows | Implemented | All four providers, 2026-10-02 |
| Windows Terminal tab | Preferred surface | Tab creation/follow-up/close, 2026-10-01 |
| Windows console window | Fallback | Initial prompt/close, 2026-10-01 |
| Linux, including a Linux process in WSL | Unsupported | No session transport |
macOS detects the invoking terminal and uses Terminal.app when it cannot identify the host.
Terminal.app always opens a new window. Windows prefers a tab in a dedicated Windows Terminal
window and uses a console window when a tab cannot be created. See
terminal selection and settings, including
settings macos-open-mode and settings windows-tab-window.
By default, ask, reopen, and self-test refuse to launch any provider in the Codex memory
workspace ($CODEX_HOME/memories, default ~/.codex/memories) or a directory inside it, before
any session or terminal exists. Codex's background memory consolidation started Bridge sessions
there that nobody closed. The refusal also applies to a launch you start there yourself;
tabcli settings codex-memory-workspace allow permits it. See ask.
Warp requires an authorized official Control endpoint and the relevant creation features.
It cannot submit terminal input, so Agy and Pi follow-ups are unsupported there. Its authenticated
round trip and close are not verified. Choose another terminal for those providers.
| Provider CLI | Minimum launch version |
| --- | --- |
| Codex (codex) | 0.147.0 |
| Claude Code (claude) | 2.1.234 |
| Agy (agy) | 1.1.12 |
| Pi (pi) | 0.84.1 |
Codex follow-ups require 0.149.0 or newer; no shared daemon is required. Claude needs working
cross-session messaging in its installed backend and configuration, not only a recent version.