An open-source workspace for coding agents, running on your own machine.
Run Claude Code, Codex, Cursor and Gemini side by side, each on its own git worktree.
They keep working when you close the browser. Nothing lands until you read the diff.
More work. Less AI waste. Same subscriptions.
You hand out tasks, agents plan and work in parallel, and you review the result. All of it runs in a sandbox on a machine you control.
-
Sign in with Google. No card, no forms.
-
Paste one command on the laptop, desktop or server that will host your sandbox. The setup page shows it with your code filled in, and the command offers to install Docker if it is missing.
curl -fsSL https://intentic.dev/connect | sh -s -- <SETUP_CODE>
On Windows, use PowerShell or the desktop app for Windows and Linux. The tunnel dials out, so no ports need opening.
-
Connect an AI account and give an agent its first task.
To try it before installing anything, open the live demo: the real app on a recorded workspace. The quickstart covers the desktop app, Docker Compose and scripted installs.
One board shows every agent, sorted by who needs you. Each card shows the model, the branch, the diff size and the cost. Every agent works on its own git worktree, so ten agents never edit the same checkout.
Agents read the code, write a plan and wait. Approve it, or reply to keep planning. Permission modes range from plan-only to fully automatic, per turn.
Finished work waits on its branch with the agent's own report. Read it file by file, then land it or discard it.
The sandbox is a daemon on your machine, not a browser tab. Terminals stay open and turns finish without you. Any browser reopens the same board, phone included.
Agents run on your own Claude, ChatGPT, Cursor, Google, Grok, Kimi or Z.ai account, or on a local model. intentic never meters tokens or adds a markup. Connect several accounts and see every plan's limits in one place.
Connect GitHub, PostgreSQL, Sentry, Stripe, Discord, SSH, a VPN or any MCP server. Each card shows what a connection adds before you save it. Credentials stay inside your sandbox.
Wake an agent on a schedule, a push, a failed pipeline, a Sentry alert, a payment, an email or a Discord message. An optional check command decides whether each run starts. Every run shows up on your board.
- The sandbox is a Docker container on your laptop, desktop or server. Put it on an always-on machine and work continues while your laptop sleeps.
- The platform stores your sign-in and your sandbox's address. It never receives your files, prompts or credentials.
- The sandbox, CLI, workspace and platform are all MIT-licensed, in this repository. Read what runs on your hardware before you run it.
| If you use | Examples | intentic is |
|---|---|---|
| Coding agents and CLIs | Claude Code, Codex, OpenCode, Gemini CLI, Kimi Code | where you run them: one worktree each, a shared workspace, review before landing |
| AI code editors | Cursor, GitHub Copilot, Zed, JetBrains AI | a companion: keep your editor for inline work |
| Multi-agent workspaces | Conductor, Superset, T3 Code, Synara, Nimbalyst | the closest alternative: MIT, any browser or phone, any Docker host |
| Cloud coding agents | Devin, Jules, Codex cloud, Claude Code on the web | the self-hosted option: your always-on machine, your accounts |
| Self-hosted assistants | OpenClaw, Hermes Agent | focused on repositories, branches and review |
Each comparison page includes the case for picking the other product.
Is it free?
Yes. Every sandbox, capability, automation and shared workspace is free, with no tiers or card. You pay your AI provider directly. An optional hosted sandbox exists for people who would rather not run a machine.
Which agents and models can I use?
Claude Code (Opus, Sonnet, Haiku), Codex, Cursor, Gemini, Grok, Kimi Code, GLM and Meta's models, picked per conversation. Any ACP agent, such as OpenCode, connects as a capability, and local models run through llama.cpp or any OpenAI-compatible endpoint.
Where does my code live?
On your machine, as plain git. Your browser reaches the sandbox over a private tunnel. The platform never receives your files, and secret files such as .env never pass through the connection.
What do I need to run a sandbox?
A computer with Docker and a Google account. No public IP, open ports or Cloudflare account. If Docker is missing, the installer offers to install it.
Can an agent break my stuff?
It can make mistakes, so it proposes a plan first and works on its own branch. You read every diff before it lands, environment changes need your approval, and permissions are adjustable per turn.
Is it production-ready?
It is a working product, and it is new. Start with low-risk work and review the results. The changelog lists every release.
Questions go to Discord, bugs to Issues. A star helps other developers find the project.
CONTRIBUTING.md covers setup, builds and checks, and ARCHITECTURE.md explains how the parts connect. Coding agents working in this repository start at AGENTS.md.
| Area | What lives there |
|---|---|
| _editor | The web app you look at, plus desktop and mobile shells and the UI kit |
| _sandbox | The daemon that owns a project's sandbox, and the CLIs agents use inside it |
| _platform | The hosted plane: sign-in, sandbox registry, tunnels, database |
| _extensions | Bundled extensions: agents, connectors, automations, viewers |
| _shared | Contracts and SDKs more than one part is written against |
| _search | iq and lsp: how agents find code |
| _devices | What runs on your own machines: device agent, browser extension |
| _deploy | The deployment tool: intent to running servers |
| _site | intentic.dev and the interactive demo |
| _tools | Shared config, checks, test harnesses, maintainer scripts |
The pictures in this README are drawn from the demo build by _site/site/scripts/readme. Run pnpm -C _site/site readme to redraw them.
MIT. Report security issues as described in SECURITY.md.