Support

Terminal Champion is a macOS application that wraps your terminal sessions with identity, context, memory, and orchestration. It's built for developers running multiple AI coding agents alongside shells, containers, and SSH sessions.

No. Terminal Champion spawns real shells using your existing configuration (zsh, bash, fish — whatever your $SHELL is). Your aliases, prompts, plugins, and tools behave exactly as they always have.

macOS 14.0 (Sonoma) or later. Apple Silicon and Intel Macs are both supported.

No. Terminal Champion has zero telemetry and no external servers. All state lives locally. See the Privacy Policy for the full breakdown.

Click the + button in the tab bar, or press ⌘T. Click the caret next to it to pick a Pinned or Recent connection instead of a local shell.

Right-click a tab → Add to group → pick an existing group or create a new one. Grouped tabs render with a colored bar above them and can be acted on together (broadcast, briefing, etc.).

Right-click the tab → Split view → choose 2–5 columns. Press Esc to collapse.

Click the tab's color dot or long-press the tab; a label editor appears. Once a label is set, it takes priority over the auto-name.

Any that run in a terminal. First-class auto-detection (with a colored tab gradient and an agent badge in the identity bar) covers six: Claude Code, Codex CLI, Gemini CLI, Aider, Kimi Code CLI, and Qwen Code CLI — including model-name recognition where the agent exposes it. Kimi and Qwen also light up from Chinese-language banners (通义千问, 通義千問, 月之暗面). Other CLI-based agents still work — you just won't get the colored badge.

Type @tab: in any terminal to open a picker listing other tabs. Select one and Terminal Champion injects a formatted context block — identity, recent output, activity — into your current prompt. @group: does the same for whole groups.

In any agent tab, type /fork. Terminal Champion captures the resume token, creates a paired child tab, and resumes the same conversation in both — they share the same starting point and diverge from there. Claude uses a switcheroo flow; Codex, Gemini, Kimi, and Qwen use a right-side fork that renames the parent Original and opens a new Fork N tab to its right. If your tab has a friendly display name (e.g. "Dev Box"), the fork inherits it.

Yes. Terminal Champion forces the fork in this case — we capture the resume command directly and start a parallel tab regardless of Claude's in-TUI check.

A lightweight session daemon keeps your PTYs alive in the background, so running processes continue. Relaunching Terminal Champion restores every tab exactly where you left it.

If Settings → Terminal → Keep shell on tab close is on, closing a tab detaches it rather than killing it. Click the caret next to the + button to see detached sessions and reattach.

Force-quit Terminal Champion (⌘⌥Esc → Terminal Champion → Force Quit) and relaunch. The daemon preserves your PTYs, so your tabs and running agents will come back. If the blank-screen issue repeats, open View → Toggle Developer Tools and send us what's in the Console.

Click the caret next to the + button → Recent tab → hover a row → click the pin icon. Pinned entries never evict from the list.

Only if you save them. In the Connect dialog, save a password (or the passphrase for a private key) and Terminal Champion stores it in your platform's native credential store — macOS Keychain on Mac, Credential Manager on Windows, kernel keyring on Linux. You can audit and revoke entries any time in Keychain Access.app by searching for com.terminalchampion.app. Credentials never leave your device.

Yes. Copy an image, switch to the target tab, press ⌘V. Terminal Champion writes it to a temp file and routes it: LOCAL tabs get the local path; DOCKER tabs get a docker cp into the container; managed-SSH tabs (those opened from the Connect dialog with saved credentials) stream the bytes through the russh exec channel — no scp or sftp setup needed.

Yes — but only into managed-SSH tabs (saved Connect-dialog hosts using the russh transport) and LOCAL tabs. The file uploads to /tmp/tc-files/<name> on the remote and the path is pasted at the prompt. 100 MB cap per file. DOCKER and OpenSSH-binary tabs aren't supported drop targets.

Open a managed-SSH tab, then click the Network icon in the identity bar. The Port Forwards dialog lets you add local-to-remote (-L) or remote-to-local (-R) forwards on the fly. Forwards live as long as the tab does.

Open the right panel → Appearance → Visual Mode / Border Decoration. Settings are per-tab by default; use groups to apply to several at once.

The Jarvismaxxing border is paired with the Jarvismaxxing visual mode. Switch to a different visual mode and the border changes with it. Or turn off Force mode borders in Settings → Appearance to decouple mode and border.

Yes — it's purely cosmetic. All functionality is identical. Turn it on via Settings → Appearance → Skin.

~/Library/Application Support/TerminalChampion/ (session database, scrollback, persisted state) and ~/Library/Preferences/ (app settings). Nothing leaves your Mac.

Quit the App, then delete the directories in the previous answer. See the Privacy Policy, Section 7, for the full step-by-step.