Hey HN. Like many others, I'm running my coding agents almost exclusively on my VPS. But I got tired of the terminal as the interface: I tried Termius on my phone but it was quite painful the moment I tried to paste screenshots or record voice notes. The best thing I found was Claude's remote-control feature, but it locks me to one coding agent / LLM provider, and therefore I'm stuck as soon as I hit my usage limit.
This is why I built ShellTeam, an open-source cockpit to steer the coding agents on your VPS. It puts your existing coding agents (Claude Code, Codex, Antigravity, OpenCode) behind one mobile-friendly web app: start a task with a voice note, paste screenshots, and every file an agent writes gets a URL only you can open, every port it serves gets a subdomain.
The clip shows the part I like most: a chart is pasted, Opus reads it, then the thread is switched to GPT-5.6 by the user with a dropdown and it answers using the previous turns with Opus. ShellTeam translates the session into each CLI's native session-file format, so the target agent resumes it as its own. Actually, this GIF, as well as most of ShellTeam, was built through ShellTeam.
I know that many of you probably already have a setup for your coding agents, so I tried to make ShellTeam strictly additive. It does not touch ~/.claude.json or ~/.codex/config.toml (a CI test asserts your own claude/codex stay byte-identical), and with the "minimal" (default) install, spawns your CLIs with zero additions. An optional layer adds skills, a headless browser, and a nightly knowledge pass, but they are passed as launch flags, not written to your dotfiles.
Other small but important facts about ShellTeam:
* It is private by default: everything binds 127.0.0.1, and you reach it over Tailscale, or you can wire it to your own domain.
* There's no telemetry. The only way data can flow to me is if you submit a bug to the product.
* The agents are not sandboxed, on purpose: the VPS on which you install it is the boundary. So install it only on a machine where you'd let your coding agents run anyway. ./install.sh --plan prints every change it would make to that machine (units, sudoers, ports, files) and exits without touching anything.
* License is AGPL-3.0. I also offer a VPS with ShellTeam preinstalled (--full version) at $19/month for people who want an easy path to start using coding agents. Anything you build with it stays yours.
I've been using it for months now and can't imagine going back to SSH + terminal, but this is the first time I'm putting it in front of others: I'd love a few people to try it on their own box and tell me how it goes (or ask your agent to). It is hopefully easy and safe to try: the install is additive, uninstall.sh removes everything, and if your setup lives on your laptop, a one-command mirror (in beta) imports it onto your box.
Hey HN. Like many others, I'm running my coding agents almost exclusively on my VPS. But I got tired of the terminal as the interface: I tried Termius on my phone but it was quite painful the moment I tried to paste screenshots or record voice notes. The best thing I found was Claude's remote-control feature, but it locks me to one coding agent / LLM provider, and therefore I'm stuck as soon as I hit my usage limit.
This is why I built ShellTeam, an open-source cockpit to steer the coding agents on your VPS. It puts your existing coding agents (Claude Code, Codex, Antigravity, OpenCode) behind one mobile-friendly web app: start a task with a voice note, paste screenshots, and every file an agent writes gets a URL only you can open, every port it serves gets a subdomain.
15-second demo: https://github.com/sebderhy/shellteam/raw/main/docs/assets/d...
The clip shows the part I like most: a chart is pasted, Opus reads it, then the thread is switched to GPT-5.6 by the user with a dropdown and it answers using the previous turns with Opus. ShellTeam translates the session into each CLI's native session-file format, so the target agent resumes it as its own. Actually, this GIF, as well as most of ShellTeam, was built through ShellTeam.
I know that many of you probably already have a setup for your coding agents, so I tried to make ShellTeam strictly additive. It does not touch ~/.claude.json or ~/.codex/config.toml (a CI test asserts your own claude/codex stay byte-identical), and with the "minimal" (default) install, spawns your CLIs with zero additions. An optional layer adds skills, a headless browser, and a nightly knowledge pass, but they are passed as launch flags, not written to your dotfiles.
Other small but important facts about ShellTeam: * It is private by default: everything binds 127.0.0.1, and you reach it over Tailscale, or you can wire it to your own domain. * There's no telemetry. The only way data can flow to me is if you submit a bug to the product. * The agents are not sandboxed, on purpose: the VPS on which you install it is the boundary. So install it only on a machine where you'd let your coding agents run anyway. ./install.sh --plan prints every change it would make to that machine (units, sudoers, ports, files) and exits without touching anything. * License is AGPL-3.0. I also offer a VPS with ShellTeam preinstalled (--full version) at $19/month for people who want an easy path to start using coding agents. Anything you build with it stays yours.
I've been using it for months now and can't imagine going back to SSH + terminal, but this is the first time I'm putting it in front of others: I'd love a few people to try it on their own box and tell me how it goes (or ask your agent to). It is hopefully easy and safe to try: the install is additive, uninstall.sh removes everything, and if your setup lives on your laptop, a one-command mirror (in beta) imports it onto your box.