Your favorite agent harness, personalized by you.
An open-source, terminal-first dev desk for AI coding agents. Run Muse Code, Claude Code, Codex or Hermes on your own machines, and reach your desk from your laptop, phone or iPad over your tailnet.
Watch the demo · Website · Quick start · Docs
▶ Click to watch the 3 minute demo on YouTube
We each have a favorite coding agent, ticket board, calendar and news feed, so one-size-fits-all tools never quite fit. And the day is spent hopping between windows, terminals and devices to keep up with the agents doing the work.
Devcules, named after Hercules, is a strong skeleton you tune to fit you:
- A personal harness, unique to each dev. Your agents, your providers, your panels, your theme. Your own agent can even reshape Devcules itself.
- Any device, including a real terminal on your phone. The same desk and the same live tmux sessions follow you from laptop to phone to iPad.
- A dev sandbox per terminal. Every terminal opens in a project on the machine you pick: this computer, a second box, or a container.
- Less context and screen switching. Calendar, tickets, approvals, agent feed and terminals sit on one desk, and the risky steps come to you.
Pick one, or ask the assistant to make one for you.
One command on your computer:
go install github.com/devcules/devcules/cmd/devcules@latest
devculesThat runs serve and its own host runner in one process, on http://127.0.0.1:7659. It sets no environment variable and asks nothing: the Projects picker sees your own folders, named host (this computer), and the first start prints a bootstrap admin password.
In the first two minutes you have: the web desk on the loopback, a Projects tree of the machine's folders, a Terminals tab to run an agent in one, and an Assistant tab that chats with the setup helper (it asks before it changes anything; your phone answers). The three-line walkthrough:
- Open http://127.0.0.1:7659 and sign in (the bootstrap password the first start printed; you add a passkey once, and the phone's Touch ID / Face ID is the sign-in after).
- In Providers save your Meta key; set
META_API_KEYonce and it is in the vault forever (you can unset the variable). - Ask the Assistant "which providers do I have and which runner is live". It reads the live setup through the same MCP tools agents use, and any change it proposes waits for your approval first.
Prefer the sandbox over the host? The full stack (serve, a runner
rooted at your ~/code, the vault all in one volume) is one compose
up:
docker compose -f deploy/compose.yaml up -d --waitThe phone reaches the desk over your tailnet, never a public port:
echo "TS_AUTHKEY=tskey-auth-…" > .env
docker compose -f deploy/compose.yaml --profile tailscale up -d --wait
# the desk is https://devcules.<your-tailnet>.ts.netA sandbox or a second machine is a machine you add from the GUI: Machines → Add a computer. The compose stack is the container option, and it shows up as container (…) so the desk never confuses it for your own filesystem. See docs/deploy.md for environment, hardening and limits.
| Topic | |
|---|---|
| Architecture | docs/architecture.md |
| Deploy, hardening and limits | docs/deploy.md |
| Machines and runners | docs/machines.md |
| Terminals | docs/terminals.md |
| Agents and assistants | docs/agents.md, docs/assistants.md |
| Model providers | docs/providers.md |
| MCP and extensions | docs/mcp.md |
| Approvals | docs/approvals.md |
| Security, auth, vault and redaction | docs/security.md, docs/auth.md, docs/vault.md, docs/redact.md |
| The full plan | PLAN.md |
Issues, ideas and pull requests are all welcome. Devcules is built one
module per pull request, each with tests, go vet and a dated
CHANGELOG.md entry. See CONTRIBUTING.md and the
CI setup in docs/ci.md.
If Devcules fits the way you work, a ⭐ helps others find it.
Apache-2.0. See LICENSE, NOTICE and THIRD_PARTY_NOTICES.md.
Built with Muse Code; planning and review with other AI tools.







