terminal-code CLI
The tode command opens a VS Code interface inside the terminal for reviewing files and changes alongside agent work.
- 2,240 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The editor modifies actual project files and can load extensions with user-level access.
Install
Manual install
curl -fsSL https://tode.sh/install | bashFirst Install block for macOS and Linux. Inspect the downloaded installer before running it.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The editor modifies actual project files and can load extensions with user-level access.
This is third-party code. Review the repository files before installing.
What it does
terminal-code combines code-server and terminal-browser to display an editor inside the terminal. The tode command opens folders, files or a line and compares two files. An agent can prepare navigation while the user inspects edits. Workspaces support multiple folders, split panes and source-control review. SSH mode keeps the interface local with a remote backend. Editor extensions are installed separately.
Who it is for. Developers working with terminal agents who want an adjacent, familiar file-editing interface.
Good fit when
- An agent identified an error line that needs opening in the editor.
- Two files need visual comparison before accepting an edit.
- You want to browse an authorized SSH project through a local interface.
- Several folders should be viewed in one workspace.
Not a fit when
- The terminal lacks the required graphics protocol.
- An official native Windows build is required.
- The editor must not access the selected folder or extensions.
Example request
Open the affected file at the relevant line through tode so I can inspect the proposed edit.Limitations
The terminal must support the kitty graphics protocol; a plain text-only terminal is insufficient. The official installer targets macOS and Linux; Windows needs a compatible terminal and the Linux version through WSL. Editor shortcuts can conflict with terminal bindings, so use the setup wizard first. The editor and extensions work with real files and user permissions; verify the project and extension sources before enabling them.
How to disable. Close the editor and use terminal-code shutdown if needed. Saved edits and installed extensions remain until separately removed.
FAQ
How do I open the current folder?
Run `tode` without a path.
How do I jump to a line and column?
Use `--goto` with a `file:line:column` argument. Check the path before opening it.
How do I compare files?
Use `--diff` with two paths.
What if shortcuts conflict?
Run `tode --shortcut-setup` to resolve editor and terminal conflicts.
How do I stop all tool activity?
Use `tode --shutdown`.
Discussion
No questions or reviews yet.
Related
CLI toolsA VS Code extension that runs a local MCP server so an agent can search symbols, edit files and run commands in the terminal
A CLI opens diffs and documents in a terminal so a person can annotate lines and pass feedback to a coding agent
A terminal coding agent tuned for the deepseek-v4 model: deep thinking, reasoning effort control, Agent Skills and MCP
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
nnn manages files in a terminal with selection, batch renaming, disk analysis, bookmarks and optional plugin extensions.
An open-source TypeScript terminal coding agent tuned for DeepSeek models and cheap caching
README in short
Settings and extensions can be imported from compatible editors. SSH mode moves the backend remotely while retaining the local interface.