Stopping and resuming

Stop a run when you want to pause its work and continue later. Stopping snapshots its sandbox and shuts it down. Resuming creates a new sandbox from that snapshot, so the agent can continue with its saved conversation, files, and tools.

Stop a run

Call run.stop() and wait for it to finish:

await run.stop();

The run saves a snapshot of its sandbox before shutting it down. Vulnerabilities and evidence already saved remain available in the platform and through the SDK.

Resume a run

Call run.resume() to create a sandbox from the saved snapshot and continue:

await run.resume();

for await (const event of run) {
  console.log(event.type, event.summary);
}

The run keeps its ID and continues with its saved agent configuration and context. Progress and results remain associated with the same run.

Retrieve a run later

Save the run ID if you want to continue from another script or application session:

console.log(run.id);

Retrieve it through the SDK, then resume:

import Antigen from "@antigen/sdk";

const antigen = new Antigen(process.env.ANTIGEN_API_KEY);
const run = await antigen.runs.get("run_abc123");

await run.resume();

Provide additional context

After resuming, use steering to share new information or adjust the agent’s focus:

await run.resume();

await run.steer(
  "The application now uses a separate identity provider for admin accounts.",
);

To change skills or guardrails for future runs, update the registered agent. Existing runs retain the configuration they started with, including when resumed.

Getting started

Asset Map

Runs

Vulnerability Lifecycle

Team Workflows

SDK

CLI

Integrations

Stop a run

Resume a run

Retrieve a run later

Provide additional context

​Stop a run

​Resume a run

​Retrieve a run later

​Provide additional context

Stop a run

Resume a run

Retrieve a run later

Provide additional context