Remote Development

Remote development toolkit

A dev workspace is an ordinary workspace with env=dev, direct SSH into the user, and a dev image launched via toolbx/distrobox with a shared home directory.

Tool	Purpose	Notes
Neovim (+ LSP, tree-sitter)	Primary console editor	Config lives in the user's home and survives image rebuilds
tmux or zellij	Persistent sessions: a dropped laptop interrupts nothing	Agents and builds run inside the session
Claude Code (and other CLI agents)	Agentic development in the terminal	Connects to Maurice MCP; plan-only rights for prod
code-server (VS Code in the browser)	Browse and edit from the browser, file/line links from the agent	Runs as a dev-workspace service behind Caddy or a tunnel; token access. For desktop VS Code: vscode://vscode-remote/ssh-remote+host/path:line. Exact code-server line-link format to be verified during implementation
Language toolchains	Rust, Go, Node (pnpm), Python	Versions pinned in the dev image Dockerfile; mise or asdf for switching
Podman inside the dev user	Local Postgres, ClickHouse, Dragonfly for development	Same service catalogue as prod
cloudflared	External access to dev services (webhooks, mobile tests)	Via the panel tool, see Beta scope
git + gh/glab, lazygit	Repositories and PRs	Git keys stored as panel secrets
Entire CLI	Capture agent sessions into git	See Agent Memory
Common utilities	ripgrep, fd, fzf, jq, yq, httpie, direnv	Standard set for agents and humans

Coder (coder.com) and DevPod are worth studying as references: environment templates, dev machines on a button, code-server integration. Commercial and heavy, but the "template → workspace" model transfers one to one.