For solo founders and their agents
Your dev environment, replicated in the cloud
Your code, tools and logins sit on a machine of its own, where agents run with full permissions and nobody approves commands one by one. Snapshot it as you go, and you can put a wrecked machine back in minutes.
curl -fsSL https://repose.herakraft.co/install.sh | sh
Your laptop holds your repo and your private things: SSH keys, cat.jpg and a tax return. Your cloud machine runs the app’s Postgres database (3,532 rows of job listings) and node v24.20.0, and has a nightly snapshot from 03:00. repose run copies only the repo to it. There Claude Code, in bypass permissions mode, edits .env.example and poller.ts and writes a test, and you take a snapshot with repose snapshots create at 21:25. Then the agent pulls in a malicious skill from the internet and turns rogue: its uncommitted edits are discarded, the database is emptied to 0 rows and node is no longer found. The skill’s attempt to reach your laptop stops at the machine’s wall. The machine is stopped, which takes one more snapshot, and restored from the 21:25 one: the edits, all 3,532 rows and node are back, and the agent starts again.
01 Setup
Your laptop's setup, in one command
You spend an hour setting up a cloud machine: install the CLIs, log in to GitHub, paste the .env files. repose run copies all of it from your laptop.
Two source control panels side by side, your laptop and your cloud machine. On the laptop, branch fetch-timeout has 2 new commits, 2 modified files (.env.example and poller.ts), an untracked timeout.test.ts and a gitignored .env; its node_modules folder is struck out and stays behind. After repose run, ready in 16 seconds, the cloud machine shows the same branch, the same commits, the same two modified files and untracked test, and the same .env. An agent on the machine then commits "Retry fetchBoard once", and git fetch repose brings that commit to the laptop as repose/fetch-timeout.
02 Machine
Work on the machine as you would on your laptop
Each project gets a machine of its own, and you reach it from the tools already on your laptop.
Your cloud machine holds more than the repo: 578 tracked files in apps and packages, 3 files of uncommitted edits, 3,532 job listings in Postgres, pnpm 10.30.3, a PATH of 28 directories, and gh and Codex logged in. It has a nightly snapshot from 03:00, and at 21:25 you take another. The agent wrecks the machine: the files, the edits and the listings drop to zero, pnpm is not found, PATH is broken and the logins are gone. git brings back only the 578 tracked files. Restoring the 21:25 snapshot brings back everything else: the uncommitted edits, all 3,532 listings, pnpm, PATH and the logins.
your cloud machine- apps/ packages/ 578 files
- uncommitted edits 3 files
- job listings 3,532 rows
- pnpm 10.30.3
- PATH 28 dirs
- gh, codex logged in
snapshots03:0021:252.1 Snapshots
Restore the whole disk
A snapshot holds the checkout, the installed tools and the logins made on the machine. A restore puts it back on the stopped machine, or on a new one with
--as.repose snapshots restore
2.2 Ports
Use its ports on your localhost
Ports your servers listen on, from 1024 up, appear on your localhost while you're attached, so cookies and OAuth redirects behave as they do locally.
repose attach
The agent opens the app's feedback page, types a bug report into the text box, reads the console (0 errors, 0 warnings) and clicks Bug; each Playwright call in the log changes the page above it. Then repose browser shows the same browser on your laptop, and your pointer clicks into the text box and adds a sentence.
2.3 Browser
Watch the agent's browser, and take over
The agents' browser runs on the machine. Open it on your laptop to watch, or to do a login or a captcha for them.
repose browser
- your cloud machine
2.4 Editor
Open it in your editor
Each machine is an SSH host. Neovim runs on it, and VS Code, Cursor and Zed open it from your laptop.
ssh your-project.repose
03 Agents
The agents you use, and the tools they need, on first boot
Install the CLI
curl -fsSL https:/
/ repose.herakraft.co/ install.sh | sh Sign in
repose login
Run in any checkout
repose run
Solo
$49$39 a monthFirst 12 months, first 30 subscribers
8 GB running at once
100 GB disk · 250 GB egress
Plus
$89 a month
16 GB running at once
250 GB disk · 500 GB egress
Pro
$169 a month
32 GB running at once
500 GB disk · 1 TB egress
Why not skip permissions on my laptop?
There the agent can read whatever you can, from your SSH keys to the sessions in your browser. On repose it gets a machine holding one project and the logins you chose to copy. The machine can't open a connection to your laptop, and your other projects are separate machines it can't reach.
Can I close my laptop while the agent works?
Yes. Detach and close it; the agent keeps working on the machine, and you attach again to see where it got to.
How long are snapshots kept?
Seven days, and the newest one always. repose takes one each night the machine runs and at
every stop, and repose snapshots create takes one before something risky.
Can three agents try three approaches at once?
repose fork your-project -n 3 copies the machine's disk, uncommitted changes
and installed dependencies included, into three new machines, and --prompt starts an agent in each. Fetch the copy that won with git, and remove
the rest.
Why not rent a server and set it up myself?
You can, and you redo that setup for each project. The nightly snapshots and the port forwards are then yours to build as well.