Keyboard first
Work in a real TTY without switching to a graphical client.
Checking sign-in status
01TERMINAL / TUI 03
Keep moving real coding tasks forward from the terminal
Cocode TUI brings the same session to your keyboard, SSH connection, and remote machine without requiring a graphical environment.
Capabilities and limits follow the current release
02Direct answer
Start with what it is.
Cocode TUI is a terminal AI coding agent for real TTYs, SSH, and headless environments. It connects to the Cocode Host and Session so developers can read repositories, run commands, edit code, and continue desktop tasks on remote machines.
- Runtime
- A real TTY with interactive input
- Remote use
- SSH with a pseudo-terminal allocated
- Task continuity
- Same Host, Profile, and Session as GUI
- Startup check
- Run `cocode doctor`, then `cocode`
SSH friendly
Designed for remote machines, servers, and headless workspaces.
Shared sessions
Connect to the same Host, profile, and session data as the GUI.
02Why it matters
Built for remote and keyboard-first work
Run `cocode doctor` to check the Host, then run `cocode` to start a task. A real terminal preserves scrolling, shortcuts, and interactive state.
Not an isolated second client
The GUI and TUI connect to the same Host. Review a diff on your desktop, run tests over SSH, and return to the GUI when you need visual context.
↗
Clear boundaries make real development work easier to trust.
Permissions, models, and sessions stay visible
The terminal surface shows the active model, workspace, activity, and permission boundaries so remote work is not a black-box command stream.
↗
Clear boundaries make real development work easier to trust.
05Working flow
Move from setup to verification with a clear result at every step.
This is an executable, reviewable path through a real repository—not an abstract feature list.
- 01
Confirm terminal support
Use a shell with TTY, color, and interactive input; allocate a pseudo-terminal for SSH.
- 02
Run environment diagnostics
Use `cocode doctor` to inspect the Host, configuration, and model connection before fixing explicit errors.
- 03
Start the TUI
Run `cocode`, choose a workspace and Session, then begin the task.
- 04
Continue across GUI and TUI
Return to desktop for visual diff review, or keep using the same Host and Session for remote execution.
06Use cases
Decide by the work you actually need to finish.
Remote development over SSH
Inspect logs, change services, and run tests on cloud or development machines.
Headless servers
Keep a complete agent workflow where no graphical environment is available.
Container diagnosis
Enter a development container or temporary environment to inspect dependencies, builds, and runtime failures.
CI repair
Reproduce a failing command, change configuration or tests, and rerun the same gate.
07Before you start
Runtime requirements and compatibility boundaries
- A real interactive TTY; a non-interactive pipe is not a TUI
- SSH `-t` or an equivalent pseudo-terminal setting
- Sufficient user permissions for the workspace and requested commands
- Stable session management for long tasks and explicit handling of disconnects
08Try it
Terminal quick start
Enter the target repository, inspect the environment, then launch TUI.
cocode://workspaceREADY
cd /path/to/repository
cocode doctor
cocode09Facts and boundaries
Terminal workflow capabilities and limits.
TUI sits close to the real command environment. That makes remote work efficient and makes permission boundaries more important.
| Capability | Status | Conditions and evidence scope |
|---|---|---|
| SSH / headless | Supported | SSH needs a pseudo-terminal; a graphical environment is not required. |
| Interactive TTY | Required | A non-interactive pipe or incomplete terminal is not a substitute for TUI. |
| Session continuity | Same-scope support | Use the same Host, Profile, DSH Home, and Session data. |
| Disconnect recovery | State-dependent | Use stable session tooling for long work and inspect pending actions after reconnecting. |
10Cocode perspective
The terminal should preserve context, not hide impact.
Cocode TUI keeps the same task available over SSH and keyboard workflows, but commands, databases, credentials, and deployments still affect real systems. Speed belongs with exit-code, output, and permission checks.
- Maintained by
- Cocode Agency
- Last reviewed
- 2026-08-25
- Scope
- Cocode TUI, TTY, SSH, and cross-client Session continuity
- Verification
- Maintained against the current terminal startup path, Host connection, and permission boundaries
06FAQ
Before you start, make the boundaries clear.
Does Cocode TUI need a real terminal?
Yes. TUI is a terminal client and should run in a shell with TTY support.
Can I use it over SSH?
Yes. TUI is designed for keyboard-first and remote work and does not require a graphical environment.
Can Cocode TUI run in a non-interactive shell?
TUI needs a real interactive terminal. Automation should use an interface designed for non-interactive execution instead of treating TUI as a pipeline command.
Will an SSH disconnect always recover without losing state?
There is no unconditional guarantee. Recovery depends on Host, Session, and action state, so inspect running or pending work after reconnecting.