Guides
Terminal & Code Editor
Using the browser-based VS Code editor and web terminal in your CrabGlamp agent.
Terminal & Code Editor
Every agent comes with two browser-based tools: a code editor (VS Code via code-server) and a web terminal (ttyd). Both are accessed through the dashboard — no local installs needed.
Code editor
The editor is a full VS Code instance running in your browser. Extensions, themes, keybindings, and settings all work as expected.
What works:
- Install extensions from the Open VSX marketplace
- Customize themes and keybindings
- Use the integrated terminal
- Multi-file editing, search, git integration
- All standard VS Code features
What doesn’t work:
- Connecting from desktop VS Code (no SSH or remote tunnel support)
- Extensions that require a desktop environment
- JetBrains or other desktop IDEs
Your editor settings and extensions persist across restarts — they’re stored on the agent’s persistent volume.
Web terminal
The terminal is a full zsh shell with passwordless sudo. Use it like any Linux terminal.
- Default shell: zsh
- Home directory:
/home/coder/ - Shell config:
~/.zshrc(persists across restarts) - Full sudo access — install anything with
sudo apt-get install
Authentication
Access is managed automatically. When you open the terminal or editor from the dashboard, CrabGlamp generates a short-lived token (60 seconds) and sets a session cookie (24 hours). You don’t need to enter passwords or manage credentials.
If your session expires, refresh the page from the dashboard.
Tips
- Install additional tools with
sudo apt-get install <package>. Packages persist across restarts thanks to the overlay filesystem. - Customize your shell by editing
~/.zshrc. Changes take effect on the next terminal session. - Browser keyboard shortcuts can conflict with editor shortcuts. Use the editor’s keybinding settings to remap if needed.
- Long-running processes stay alive as long as the agent is running, even if you close the browser tab. They stop when the agent is stopped.