Not a clone in someone else's sandbox
Cloud agents work on a copy in their VM and hand back a branch or a pull request. Whatever you had not committed stays behind.
Early · remote dev host for coding agents
The agent never sleeps.
Your code stays on your disk.
Coding agents need a machine that never sleeps. You need the code on the computer in front of you. Corami gives you both: the agent runs on an always-on Linux server, and every computer keeps a real copy of the project folder, synced both ways.
Corami is the host, not the agent. Install OpenCode, Claude Code, Codex or any other harness on the server.
Works withOpenCodeClaude CodeCodexAny harness
Why Corami
The agent runs there. The code is here.
Corami is not another cloud sandbox. It is the host for the agent you already use, with the project staying a real folder on your disk.
A real folder, on your disk
Every machine keeps the full project. Editor, tests and Xcode run at local speed while the agent writes on the server. Conflicts that cannot be solved without losing data are held and reported, never overwritten.
Your own machine
Nothing is on the public internet. The server, the agent and the previews are reachable only through your Tailscale network.
Workflow
A day with Corami
Close the lid at any point. Nothing needs committing, and the agent keeps working on the server.
At your desk
You give the agent a task. Its edits show up in the project folder on your Mac as it saves them. You follow them in your editor, and tests and Xcode run at local speed, with no remote filesystem.
Time to leave
Close the lid: no commit needed. Your last saves are already on the server, and the agent keeps working there.
On the train
Open the preview on your phone and keep talking to the agent. The dev server runs on the server, and corami serve 3000 gives it a stable HTTPS address, so it can stay in your bookmarks.
Back at your desk
Open the lid: what the agent did while you were away syncs to the Mac by itself.
On another computer
corami project add ~/dev/myapp --from-server --name myapp brings the same files, uncommitted work included.
Try it
From zero to a synced project.
A Linux server, a free Tailscale account and a laptop are enough. The server becomes the source of truth; the folder stays on your machine.
# on the server, as root curl -fsSL https://github.com/tapeo/corami/releases/latest/download/install.sh | sh # on the laptop, signed in to the same Tailscale account curl -fsSL https://github.com/tapeo/corami/releases/latest/download/install.sh | sh # copies the project to the server, which becomes the source of truth: # the folder stays here, in sync with the copies on your other machines corami project add ~/dev/myapp
The quickstart goes through it step by step, then adds your agent and a preview you open from the phone.
How it works
One binary, one folder, two directions.
Corami is the host. It stays out of your toolchain and keeps the code aligned.
One binary
corami is the CLI on every machine and the daemon on the server. Every command takes --json, the default without a terminal, so agents can drive it too.
Sync
Files travel with Mutagen over Tailscale SSH. Dependencies and build outputs (node_modules, build, Pods...) stay out; each machine regenerates them.
Never silent
A conflict that cannot be solved without losing data is held and reported, never overwritten. Keys and env files travel as part of the folder unless you keep them out.
Private
Nothing is on the public internet. The server, the agent and the previews are reachable only through your Tailscale network.
Previews
corami serve 3000 gives a dev server a stable HTTPS address. If the port changes, corami serve <new-port> keeps the same URL.
Your tools
Corami installs no toolchain and runs no build. Node, pnpm, Flutter, Xcode and the rest run where you put them, on the server or on a client over SSH.
Documentation
Everything, documented.
From the first install to the invariants the code relies on.
Quick startFrom nothing to an agent and a preview on your phoneSecurityWhat to keep in place, in order of weightCLI referenceEvery command, flag and JSON outputPreviewsA dev server with a stable HTTPS addressBuildsOn the server, or on a client over SSHBackupWhat to save and howArchitectureHow it is builtInternalsInvariants the code relies onDevelopmentBuild Corami and run it locallyIdeas for v2What comes after v1
Get started
Give your agent a machine that never sleeps.
Keep the code on every disk, the agent on the server, and the commit for when you actually want one.
Early It works end to end on a real VPS with a macOS client. Binaries and updates come from GitHub releases, and corami update keeps every machine current.