argon
Git for MongoDB — branch, time-travel, and undo your data. Built for AI agents.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/argon-lab/argon with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/argon-lab/argon'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/argon-lab--argon)HTML
<a href="/listings/argon-lab--argon"><img src="/api/listings/argon-lab--argon/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
For npm, use Node.js 24 LTS with npm 11.16 or newer. The package-scoped approval allows the installer to download Argon's binary on npm 12.
brew install argon-lab/tap/argonctl # macOS
npm install -g argonctl --allow-scripts=argonctl # cross-platform
# MongoDB must run as a replica set (one-node is fine):
docker run -d --name argon-mongo -p 127.0.0.1:27017:27017 mongo:7 --replSet rs0
docker exec argon-mongo mongosh --quiet --eval 'rs.initiate({_id:"rs0",members:[{_id:0,host:"localhost:27017"}]})'
argon doctorUse a current supported MongoDB patch release in production. Source builds use Go 1.26.9 or newer, as declared in `go.mod`. Use a patched toolchain: Go 1.27.0–1.27.1 also contain the October 2026 standard-library vulnerabilities.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 284 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # Argon — MongoDB sandboxes for AI agents
- <p align="center">
- <a href="https://argonlabs.tech">
- <img src=".github/assets/hero.png" alt="Argon — MongoDB sandboxes for AI agents. Git for MongoDB underneath: branch, diff, merge, undo." width="100%">
- </a>
- </p>
- [](https://github.com/argon-lab/argon/actions/workflows/ci.yml)
- [](https://goreportcard.com/report/github.com/argon-lab/argon)
- [](https://opensource.org/licenses/MIT)
- [](https://github.com/argon-lab/homebrew-tap)
- [](https://www.npmjs.com/package/argonctl)
- [](https://pypi.org/project/argon-agents/)
- [](https://mcp.market/server/argon-lab-argon)
- **Give every agent run its own real MongoDB database, forked from your data.
- Review what it changed, merge what you want, discard the rest. Git for MongoDB
- underneath: branch, diff, merge, time travel and undo. Any driver, real mongod.**
- Three ideas, thirty seconds:
- 1. **A sandbox is a real MongoDB database** — forked from a branch or a pinned
- dataset, checked out and given a TTL in one command. pymongo, mongoose,
- mongosh, indexes, aggregation, transactions: all real.
- 2. **What the agent wrote is a diff** — supported document writes become
- history while capture is healthy, so a run can be reviewed, merged as a data
- pull request, undone or thrown away. Your source data is untouched until you
- merge.
- 3. **Underneath, it is Git for MongoDB** — a branch is a pointer created with a
- metadata write; checkout separately materializes the data. Diff, merge, undo
- and pins work within the configured retention and capture guarantees. The
- commands are [side by side with Git](#git-for-mongodb) below.
- ## Install
- For npm, use Node.js 24 LTS with npm 11.16 or newer. The package-scoped
- approval allows the installer to download Argon's binary on npm 12.
- ```bash
- brew install argon-lab/tap/argonctl # macOS or Linux, builds from source
- npm install -g argonctl --allow-scripts=argonctl # cross-platform
- # MongoDB must run as a replica set (one-node is fine):
- docker run -d --name argon-mongo -p 127.0.0.1:27017:27017 mongo:7 --replSet rs0
- docker exec argon-mongo mongosh --quiet --eval 'rs.initiate({_id:"rs0",members:[{_id:0,host:"localhost:27017"}]})'
- argon doctor
- ```
- Use a current supported MongoDB patch release in production. Source builds use
- Go 1.26.11 or newer, as declared in `go.mod`. Use a patched toolchain: on the
- Go 1.27 line that means 1.27.4 or newer, which carry the same standard-library fixes.
- ## The flow
- ```
- your data ──sandbox──▶ mongodb://… ← the agent, any driver
- │
- argon diff ──────┤ what the run changed
- ▼ ▼
- merge (a data PR) or discard / undo
- ```
- ```bash
- # 0 · Bring your data in once, from a database nobody is writing to — or: argon projects create myapp
- # (a database that is in use: see "A database that is in use" below)
- argon import database --uri mongodb://localhost:27017 --database myapp --project myapp --source-quiesced
- # 1 · In terminal A, a sandbox: fork + checkout + TTL + capture in one command.
- # Prints its name and a connection string, then keeps capturing until Ctrl-C
- argon sandbox create -p myapp --ttl 1h --watch --actor agent:run-1
- # In terminal B, point the agent at the printed URI. Then:
- # 2 · Review, then adopt the run — a data pull request
- argon diff -p myapp -b <sandbox>
- argon merge preview -p myapp -b <sandbox>
- argon merge apply <plan-id>
- # …or throw the run away
- argon sandbox discard -p myapp -b <sandbox>
- ```
- Through the MCP server or `argon console`, capture and expiry are managed for
- you: nothing stays in the foreground, and expired sandboxes are swept every
- minute. `--watch` needs 2.3.0 or newer; on older versions run
- `argon watch -p myapp -b <sandbox> --actor agent:run-1` after creating the sandbox.
- Long-lived branches work the same way with `argon branches create` and
- `argon checkout`, and `argon restore reset` rewinds a branch to an earlier time.
- ### A database that is in use
- Online import, the `argon source` commands, and write-back are experimental
- and off by default. They have known open issues. Set
- `ARGON_EXPERIMENTAL_SOURCE=1` to enable them after reading
- [the operations guide](docs/OPERATIONS.md#following-a-source-database).
- Releases after 2.5.0 can import a replica-set database without stopping its
- writers, keep the project's `main` following it, and write a reviewed plan
- back to it:
- ```bash
- export ARGON_EXPERIMENTAL_SOURCE=1
- export ARGON_SOURCE_URI="mongodb://…" # read per command, never stored
- argon import preview --database myapp --online
- argon import database --database myapp --project myapp --online
- argon source follow -p myapp # main tracks the source; leave it running
- argon sandbox create -p myapp --ttl 1h --watch --actor agent:run-1
- argon merge preview -p myapp -b <sandbox>
- argon merge apply <plan-id> --write-back # one transaction on the source
- ```
- The import copies ordinary collections at one cluster time, which it prints.
- Add `--dry-run` to the import command to check the source and its change stream
- and see the estimated copy without writing anything.
- Following ignores changes to views. `--write-back`
- checks every document against the plan's before-image and aborts the
- transaction if one has changed. Write-back and `--enable-source-images`
- require importing with a user allowed to run `replSetGetConfig`, such as one
- with the `clusterMonitor` role. Use `argon source status` to see which identity
- check applies. The MCP server and REST API do not offer write-back. Argon
- never drops, renames or rewrites a source database. See
- [the operations guide](docs/OPERATIONS.md#following-a-source-database).
- If a plan stays `writing_back`, check the affected documents on the source,
- let following catch up, and run `argon merge preview` again for the sandbox.
- Each project can run one follower or resync at a time. `argon source status`
- shows the lease owner's host, process ID and last heartbeat. Run
- `argon source follow --auto-resync` to complete an unfinished resync or
- repair a gap in the source stream before continuing to follow.
- If an older Argon process checked out a followed `main`, status reports
- it as degraded. Upgrade the older processes, stop writes to the checkout,
- release it with `argon release -p myapp -b main`, then run
- `argon source resync -p myapp`.
- When requested, `source follow --enable-source-images` alters existing
- source collections after the saved position is followable. An error after
- the change lists the affected collections.
- Prefer clicking? `argon console` serves a local web console (UI + REST API),
- supervises capture, reaps expired sandboxes every minute, and opens your browser.
- The console's MIT-licensed source is in [web/](web/README.md); see the
- [rebuild instructions](CONTRIBUTING.md#console-source-and-reproducible-assets).
- For a complete managed workflow, run [the two-agent pinned dataset example](examples/pinned_agents.py).
- ## For AI agents
- ```bash
- claude mcp add argon -- argon mcp # 13 tools: sandbox, diff, merge, undo, pins
- # Install the published Python SDK and LangGraph adapter.
- python3 -m pip install 'argon-agents[langgraph]==0.2.0'
- ```
- Start `argon console --no-browser` in another terminal, then:
- ```python
- from argon_agents import ArgonClient, ArgonCheckpointSaver
- argon = ArgonClient("http://127.0.0.1:1818")
- argon.get_or_create_project("myapp")
- saver = ArgonCheckpointSaver.from_sandbox(argon, "myapp")
- # Compile and run your LangGraph graph with checkpointer=saver, then review:
- plan = argon.merge_preview("myapp", saver.sandbox.branch)
- print(plan)
- # After reviewing this exact plan, apply it explicitly:
- # argon.merge_apply(plan["id"])
- # Or reject the run: saver.discard()
- argon.create_pin("myapp", "eval-v1") # pin the dataset once
- run = argon.sandbox_from_pin("myapp", "eval-v1") # identical state, every eval run
- ```
- `saver.merge()` is a convenience call that previews and applies immediately;
- use the separate calls above when approval is required. Pins protect captured
- document state while they exist; keep independent backups.
- To keep a person in the loop, withhold tools from the MCP server:
- `argon mcp --disable-tools argon_merge_apply` leaves applying a merge plan to
- `argon merge apply <plan-id>`, and `argon mcp --read-only` offers only the
- tools that inspect state.
- The full agent workflow: [docs/AGENTS.md](docs/AGENTS.md).
- ## Git for MongoDB
- Underneath the sandbox, Argon does for MongoDB documents what Git does for
- files. Side by side:
- | In Git | In Argon | What it does to your data |
- |---|---|---|
- | `git branch` | `argon branches create` | adds a pointer into shared history; no documents are copied |
- | `git worktree add` | `argon sandbox create` | gives a new branch its own working copy: a real MongoDB database, with a TTL |
- | `git diff` | `argon diff` | lists the documents a branch would add, change or remove |
- | `git merge` | `argon merge preview`, then `argon merge apply` | saves the change as a plan to review, then applies exactly that plan |
- | `git checkout <commit>` | `argon time-travel query` | reads the data as it was at an earlier position in retained history |
- | `git revert` | `argon undo` | reverses earlier writes with a new change; history is not rewritten |
- | `git tag` | `argon pin create` | names one fixed state and protects its history while the pin exists |
- Where it differs from Git: there is no commit step, because a running capture
- process records each document change. A merge goes from a branch into its
- parent and compares whole documents. Checking out a branch copies its data, so
- it takes time and storage that depend on the dataset. Documents are versioned;
- indexes and collection options are not. History older than the retention
- window can be reclaimed unless a pin protects it.
- ## What you get
- | | Command | In one line |
- |---|---|---|
- | **Sandboxes** | `argon sandbox create --ttl 1h` | fork + checkout + TTL in one step — disposable agent workspaces |
- | **Dataset pins** | `argon pin create` / `pin sandbox` | named captured states protected from GC and resets while the pin exists |
- | **Data PRs** | `argon merge preview/apply` | three-way merges as reviewable plans; conflicts never silent |
- | **Undo** | `argon undo --actor <a>` | revert a range or actor label; append-only, conflict-aware |
- | **Real databases** | `argon checkout` / `argon proxy` | any driver, real mongod; proxy serves stable `mongodb://host/<project>~<branch>` URIs |
- | **Write capture** | `argon watch` | exact change-stream images → history, one actor label per branch |
- | **Branching** | `argon branches create` | a metadata write — instant, zero copy |
- | **Time travel** | `argon time-travel query` | query captured document states at retained LSNs; restore/pin also accept timestamps |
- | **Restore** | `argon restore preview/reset/branch` | rewind a released branch or fork retained history |
- | **Web console** | `argon console` | local UI + REST API in one command |
- Data history covers document inserts, updates, replacements and deletes. Collection
- drop/rename produces degraded capture; indexes and collection options are not
- versioned. Native writes are asynchronous; control operations drain capture.
- Stop writers before release. Existing pins protect their referenced states, while GC can expire audit
- and undo history. See [operations](docs/OPERATIONS.md) for recovery and credentials.
- Two things to know before handing a sandbox to an agent. A collection the agent
- creates is captured exactly while capture is running, or when it is next
- synchronized within MongoDB's snapshot history (five minutes by default); the
- one exception is a document that is updated and then changed again inside one
- transaction on a collection created moments earlier. Before 2.3.1 such a collection needed
- `argon collections prepare` first. And a sandbox is a full physical copy with
- capture ready, so creating one takes longer as the data grows: the
- [benchmarks](https://github.com/argon-lab/benchmarks) measure it as
- `sandbox_capture_ready_ms`.
- Storage retention uses snapshots + retention-window GC to keep state plus a
- window of history, not every write forever. Details and the consistency
- model, stated honestly: [ARCHITECTURE.md](docs/ARCHITECTURE.md).
- ## Documentation
- | | |
- |---|---|
- | [Quick start](docs/QUICK_START.md) | install → first merge, step by step |
- | [CLI reference](docs/CLI.md) | every command |
- | [Agents](docs/AGENTS.md) | sandboxes, pins, MCP, REST API, argon-agents, proxy |
- | [Architecture](docs/ARCHITECTURE.md) | how it works and what it guarantees |
- | [Operations](docs/OPERATIONS.md) | deployment, chunk stores (S3/FS), GC, v1→v2 migration |
- | [Performance](docs/PERFORMANCE.md) | every number lives in the [reproducible benchmarks](https://github.com/argon-lab/benchmarks) — none here, by policy |
- ## Community
- [Issues](https://github.com/argon-lab/argon/issues) ·
- [Discussions](https://github.com/argon-lab/argon/discussions) ·
- [Contributing](CONTRIBUTING.md) ·
- [argonlabs.tech](https://argonlabs.tech) · [Blog](https://argonlabs.tech/blog)
- ## Contributors
- Thank you to everyone who has made Argon better.
- <a href="https://argonlabs.tech/about#contributors">
- <img src="https://argonlabs.tech/contributors.svg" alt="Argon contributors" height="64">
- </a>
- What each person shipped, and the release it shipped in, is listed at
- [argonlabs.tech/about#contributors](https://argonlabs.tech/about#contributors).
- Every release also names its new contributors in the
- [release notes](https://github.com/argon-lab/argon/releases).
- New here? Start with a
- [good first issue](https://github.com/argon-lab/argon/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
- and the [first-contribution guide](CONTRIBUTING.md#your-first-contribution).
- ---
- <div align="center">
- **Give your MongoDB a time machine. Branch without fear.** ⭐
- </div>
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.