Four verbs control a clone after it’s been spun. All take a clone id and fail
with CLONE_NOT_FOUND if it doesn’t exist.
reset
Returns a clone to a clean, seeded state without a rebuild — the fastest way
to start the next trial from identical input.
It drops the database (terminating live connections), recreates it, re-runs all
migrations, restarts the backend to rebind its connection pool, waits for health
(90s), and re-applies the clone’s last seed if it had one.
start
Starts a previously stopped clone. Runs docker compose up -d with the
clone’s saved ports and marks it running. Silent on success.
stop
Stops a running clone without destroying its data. Runs docker compose stop
(volumes preserved) and marks it stopped. Silent on success. Bring it back with
start.
destroy
Tears a clone down completely: docker compose down -v (containers + volumes),
drops the database, frees its ports, and removes it from the registry.
destroy is irreversible. The database and all seeded data are dropped. Use
stop if you only want to pause a clone.
How they relate