crewship checkpoint
Create, inspect, restore (advisory), fork, and delete mission checkpoints. A checkpoint pins a journal cursor to a human-readable label so you can return to it later. See the Cartographer guide for semantics.Subcommands
| Command | Description |
|---|---|
list | List checkpoints for a mission. |
create | Create a checkpoint at the current journal cursor. |
restore <id> | Show divergence since a checkpoint (advisory). |
fork <id> | Spawn a new mission from a checkpoint. |
delete <id> | Delete a checkpoint. |
crewship checkpoint list
| Flag | Type | Required | Description |
|---|---|---|---|
--mission | string | Yes | Mission ID to list checkpoints for. |
crewship checkpoint create
| Flag | Type | Required | Description |
|---|---|---|---|
--mission | string | Yes | Mission ID. |
--label | string | Optional human-readable label. |
| Exit | Meaning |
|---|---|
| 409 | Mission has no journal entries to anchor a checkpoint. Run some agent work first. |
crewship checkpoint restore <id>
Advisory only. The server returns the checkpoint cursor and any journal entries that diverged since the checkpoint was made. Mission state is not mutated — use fork when you need a concrete branch.
crewship checkpoint fork <id>
Creates a new mission anchored at the checkpoint’s cursor and a matching new checkpoint in it.
| Flag | Type | Description |
|---|---|---|
--label | string | Optional label for the forked mission’s initial checkpoint. |
crewship checkpoint delete <id>
| Flag | Type | Description |
|---|---|---|
--yes | bool | Skip confirmation prompt. |
fork_of are orphaned (their reference is set to NULL). The forked missions themselves are not deleted.