terminal-code
VS Code in the terminal
What is it?
What it is
A CLI tool that renders the VS Code editor directly in the terminal using the kitty graphics protocol, combining code-server and terminal-browser to bring the full VS Code experience to terminal environments.
Why it exists
To enable developers to use VS Code in terminal-only environments, provide lightweight remote development via SSH with near-instant interaction, and offer a seamless code editor alternative without requiring a graphical display.
Who should use it
Developers, system administrators, and power users who want to run VS Code in a terminal environment, especially those comfortable with command-line tools and remote development.\n\n" ,
Who should avoid it
Teams that need a fully managed SaaS with enterprise SLAs out of the box.
Stars over time
+22 stars in the last 1 day
How it works
A quick walkthrough in plain English
How terminal-code works
Step 1 of 3
You interact with it
Open terminal-code, send a request, or connect it to your stack.
Features
Advantages
- Full VS Code experience directly in the terminal
- SSH optimization reduces network latency by running only the backend remotely
- Interactive shortcut setup prevents conflicts with the host terminal
- Cross-platform support including macOS, Linux, and Windows via WSL
- Built-in extension management
- Flexible split pane and window customization
- Theme and settings import/export capabilities
Disadvantages
- No official Windows build; requires WSL for Windows users
- Depends on kitty graphics protocol, limiting terminal compatibility
- Default SSH without --ssh sends all frames and input over network, causing latency
- May have default shortcut conflicts with the underlying terminal
- Requires a modern terminal supporting graphics protocol features
Installation
native
curl -fsSL https://tode.sh/install | bash
FAQ
How do I install terminal-code on macOS and Linux?
Run the installation script: `curl -fsSL https://tode.sh/install | bash`.
What are the basic ways to use `tode`?
`tode` opens the current folder, a specified folder, or file. You can add options like `--goto <f:l:c>` to jump to a line/column, `--new-window` for a new pane, `--split <direction>` to open in a new split, and many other commands listed in the help.
How can I resolve shortcut conflicts between terminal-code and my terminal?
Run `tode --shortcut-setup`. This launches an interactive wizard that lets you adjust shortcuts so they no longer clash.
What is the recommended way to use terminal-code over SSH?
Use `tode --ssh <user@host>` on your local machine. This runs only the VS Code backend remotely while keeping the frontend locally, giving near‑instant interaction and proxying network requests over the SSH connection.
Is there an official Windows build of terminal-code?
No. terminal-code relies on the kitty graphics protocol, which few Windows terminals support. You can run the Linux version inside WSL, or try a compatible terminal like winterm‑ghostty, but official Windows support is not yet available.
Featured in Videos
YouTube tutorials and walkthroughs for terminal-code
Alternatives
Similar projects ranked by category, topics, and text overlap.
