Durable runs and output
Inspect accepted commands, follow byte-exact output, cancel one generation, and recover safely after interruption.
Every accepted command has a durable run ID. Keep and reuse that ID instead of submitting another command when a network connection drops.
Inspect and follow
amics runs get RUN_ID
amics runs logs RUN_ID --followOutput cursors are opaque. To resume from the last acknowledged position:
amics runs logs RUN_ID --cursor OPAQUE_CURSOR --followUse --jsonl on runs logs for structured frames.
Run states
queued, acquiring, syncing, starting, running, succeeded, failed,
cancelling, cancelled, and unknown.
unknown means Amics cannot prove the command outcome. The command may have
executed. Inspect the run and its output before deciding whether another
submission is safe.
Cancel
amics runs cancel RUN_IDCancellation targets the current run generation. Supply an exact generation when coordinating with another caller:
amics runs cancel RUN_ID --generation GENERATIONAdd --stop-compute only when the compute resource should stop too. A cancelled
remote process returns exit status 130.
Interrupting the local CLI
During an attached run, the first Ctrl-C requests cancellation of the current generation. A second Ctrl-C detaches the local CLI while the server state remains inspectable.
Stop retained compute
amics compute stop COMPUTE_IDUse the exact compute ID returned by the run. This is required for user-supplied compute and useful when ending an approved warm reuse window early.