
The example's README
The full guide: setup, credentials, the port check and clean up. Start there.
How it works
- Two machines. MongoDB, the Argon console and
host.pyrun on a data machine. The agent’s code runs on a second machine thathost.pycreates for each run withisolatedand theargon-examplenetwork. It reaches the data machine at<data-machine>.boxd:27017and no other machine you own. - No internet for the agent’s code. The agent machine installs PyMongo first. Then
host.pysets its egress allowlist tonone, so the code can reach MongoDB and nothing else. SSH is off. - A database user per run. The agent never gets Argon’s connection string.
host.pycreates a MongoDB user withreadWriteon the sandbox’s database only, passes it on the command’s stdin, and drops it when the run ends. - Review first. A default run prints the diff and discards the sandbox, so your main branch stays as it was.
--applymerges the diff of its own run.
Run it
1
Create the data machine and an API key
npm install -g argonctl) and start argon console. The README has the exact commands.2
Check port 27017
The README’s check pings MongoDB from an isolated machine on
argon-example and from one outside it. Only the first may answer:3
Run the example
On the data machine:The run took about 17 seconds, the agent machine included.
host.py deletes the agent machine at the end.4
Merge after review
--apply merges the diff of its own run.agent.py stands in for code an agent would write, so no LLM account is needed. Replace it with your agent’s code and keep the rest.
Clean up
The data machine and the API key stay until you remove them:Read more
- The example’s README: every command, credentials and options like
--keep-machine - Argon on GitHub
- Networks and egress allowlists on boxd
- Sandboxes on boxd