Branch a Live MongoDB Database and Write Reviewed Changes Back Argon Labs released Argon 2.8.0, which lets teams write a reviewed change back to a live MongoDB database in a single transaction, building on Argon 2.7.0's ability to import a MongoDB database while it is still being written and keep following it. In a walkthrough on two MongoDB 7.0.45 one-member replica sets, an online import of the 50,000-order, 200-customer `shop` database copied 50.3K documents in 868.05 ms while the simulated application made 144 writes, publishing the source at cluster time Timestamp(1795093601, 130) with LSN 50348. Argon Labs said the source must be a replica set — a sharded cluster behind mongos is refused — and that indexes, validators and collection options are not copied. Branch a Live MongoDB Database and Write Reviewed Changes Back Import a MongoDB database while it is being written, follow it, let an agent work in a sandbox, review the diff, and write the approved change back in one transaction. A full run on Argon 2.8.0, with its limits. Argon Labs https://argonlabs.tech/about 10 min read Current capability notes: checkout materializes a physical database; native actor attribution is per branch/run; undo needs complete images and retained history. CLI sandboxes require watch and scheduled sweep. Read the capability matrix https://argonlabs.tech/features capabilities . Argon gives AI agents and developers MongoDB sandboxes: a copy of your data to work in, a diff to read, and a merge you approve. Until now the copy started from an import that needed your writers paused, and the approved merge landed in Argon, not in your database. Two releases changed that. From Argon 2.7.0 you can import a MongoDB database while it is being written and keep following it. From Argon 2.8.0 you can write a reviewed change back to that database. This post runs the whole path on a database that never stops taking writes, shows what is refused, and lists the limits. It is for teams that already run MongoDB and want a safe place for an agent or a developer to try a change against current data. running MongoDB ──online import──▶ main ──fork──▶ sandbox ──▶ diff ──▶ reviewed plan ▲ follows the source │ └──────────────── write-back, one transaction, with approval ──────────┘ What we ran - Argon 2.8.0 , the binary that npm install -g argonctl@2.8.0 installs. - Two MongoDB 7.0.45 deployments, each a one-member replica set without access control, in containers on one laptop. One holds the source database shop . The other holds Argon's metadata and its sandboxes. - The source has 50,000 orders and 200 customers. A thread plays the application for the whole run: it inserts a new order or updates an existing one, sleeps 5 ms, and repeats. It made 2,498 writes in all. We paused it twice, only to compare the source with a sandbox while the source stood still. This is a walkthrough with a transcript, not a benchmark. The few timings below are single observations. Every command and its output is in the transcript https://github.com/argon-lab/benchmarks/blob/main/reports/2026-11-19-v2.8.0-live-source-walkthrough/transcript.txt , and the report https://github.com/argon-lab/benchmarks/tree/main/reports/2026-11-19-v2.8.0-live-source-walkthrough has the script that produced it. Step 1: import while the application writes export ARGON SOURCE URI="mongodb://…" used per command, never stored argon import database --database shop --project shop --online --yes Documents Imported: 50.3K Duration: 868.050209ms Consistent: LSN 50348 is the source at cluster time Timestamp 1795093601, 130 LSNs below 50348 are the copy in progress, not states the source was in. main follows database 'shop'; keep it current with: argon source follow -p