zenbu-labs/terminal-code
VS Code in the terminal. Contribute to zenbu-labs/terminal-code development by creating an account on GitHub.
486 stars · 17 forks
README
terminal-code VS Code inside your terminal
todemp4.mp4
Install (macOS & Linux): curl -fsSl https://tode.sh/install | bash Usage Usage: tode [path...] [options] tode --<command>
tode Open the folder in the current working directory tode <folder> Open the specified folder tode <file> Open the specified file
Options: -g, --goto <f:l:c> Open a file at a line and column -a, --add <folder> Add a folder to the active workspace -n, --new-window Open a new pane even for a file -w, --wait Wait until the file is closed again -d, --diff <a> <b> Compare two files -r, --reuse-window Open folder in this window rather than a new pane --install-extension Install an extension by id or vsix path --uninstall-extension Remove an extension --list-extensions List installed extensions --split <direction> Open in a new pane: right, left, down, up --size <fraction> The % a new split will take up (0.2 to 0.95) --timing Report how long each stage of this open took --review Open on the source control panel
Commands, each as the first argument: --shortcut-setup Resolve shortcut conflicts between terminal-code and the current terminal --timing Profile terminal-code launch --import [editor] Bring settings, keybindings, snippets and extensions over from vscode compatible editors --theme [file] Set editor theme --skill An agent skill to assist with modifying terminal-code --upgrade [--check] Upgrade terminal-code to the latest version --shutdown Stop all terminal-code activities --uninstall [--yes] Remove all terminal-code data from this machine
Shortcuts Your terminal and terminal-code will likely conflict on important shortcuts, meaning sometimes terminal-code will never even receive your key press. To resolve shortcut conflicts you can run tode --shortcut-setup, and you will be placed into an interactive wizard that lets you change terminal or terminal-code shortcuts so they no longer conflict How does it work? terminal-code combines terminal-browser (a browser in the terminal) and code-server (VS Code in the browser) to bring VS Code to the terminal. You should look into these projects for more details! Windows terminal-code depends on a modern terminal feature (the kitty graphics protocol) that not many terminals on Windows support. There are projects attempting to bring this capability to terminals on Windows that you can try at your own risk:
https://github.com/ibuildthecloud/winterm-ghostty
Even with a compatible terminal, terminal-code does not have an official windows build. But, it's possible to install the linux version of terminal-code inside WSL, which is the final piece needed to run terminal-code on Windows. Please file an issue if you are eager for a more official solution