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.
Developer preview · capabilities and limits follow the current release
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.
03Why it matters
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.
04Why it matters
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.
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.