Continue Team Run

Team storage and identity

Use the database-backed example Team server. Keep the Team run's returned run_id and session_id; a nested member run is not interchangeable with the Team run. Stored run, checkpoint and session operations require the configured database.

JWT user isolation is opt-in; non-admin service-account PAT callers always self-scope. Scoped callers need their own matching Team session and run, while configured resource authorization also applies. Run and checkpoint lookups return 404 for inaccessible or mismatched records. For factories, retain any factory_input needed by endpoints that reconstruct the Team.

Resolve a paused Team

Start with an actual PAUSED run, such as the Team approval example. That example configures both leader and member approval tools and shows how to resolve any persistent approval record before continuing.

Save the returned requirements array to requirements.json. Preserve its IDs, tool-call IDs and member context. After a human approves a confirmation requirement, set its confirmation to true; provide the appropriate user-input or external-execution result for other requirement types. Resend the issued array with only those decisions changed.

TEAM_ID="leader-approval-team"
RUN_ID="returned-paused-run-id"
SESSION_ID="returned-session-id"
curl --fail-with-body "http://127.0.0.1:7777/teams/$TEAM_ID/runs/$RUN_ID/continue" \
  -H "Authorization: Bearer $OS_SECURITY_KEY" \
  -F "session_id=$SESSION_ID" -F 'stream=false' \
  -F 'requirements=<requirements.json'

The linked approval server can use the same OS_SECURITY_KEY configured in the example Team server. Local Teams require session_id, including unscoped callers. Team continuation binds decisions to stored requirements by identity; the field is requirements, not the Agent API's tools field. Conflicting or duplicate identities cannot select a different member's operation.

Inspect the returned status: continuation can pause again. Continuing a completed Team run with follow-up input creates a new run ID; retain the returned ID. Explicit fork and regenerate are separate controls for branching or replacing a run.

Background continuation

An eligible paused durable ticket can resume through the queue and return 202 for non-streaming acceptance. Without that path, background=true, stream=false currently executes inline and waits for output. Background streaming uses a detached process task unless queued; it can survive a client disconnect but not a process restart. Streaming events retain their Team-prefixed names.

curl --request POST 'https://example.com/teams/string/runs/string/continue'

null

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}