Attach a terminal to a run: ant sessions connect vs Sume jobs

Claude platform release notes for September 10, 2026 say ant CLI 1.32.0 adds ant beta:sessions connect, which attaches your terminal to a Claude Managed Agents session. Sume has no session to attach to; it has jobs. To watch one from a terminal, run sume jobs watch <job_id>, or call jobs_wait over MCP.

The Anthropic side

The release notes read on 2026-10-03 state that the new command attaches to a Managed Agents session and that --web serves the Console session viewer locally. That is an agent-session feature. It does not apply to Sume jobs.

Watching a Sume job from the terminal

Generation endpoints create durable jobs. Store the job id from the submit response, then use the CLI job commands. These work for Avatar CLI submits and for Image, Video and Music jobs created through the Developer API.

sume jobs status <job_id> --agent --json
sume jobs events <job_id> --agent --json
sume jobs watch <job_id>
sume jobs result <job_id> --agent --json
sume jobs download <job_id> --output-dir ./out

jobs watch polls until the job is terminal or a timeout is reached. jobs events prints the public timeline, such as job.queued, job.started and job.completed. The events endpoint is a pull snapshot, not a stream; there is no SSE or WebSocket transport on the Developer API.

Waiting from an agent over MCP

On hosted MCP, jobs_wait accepts one job_id or a job_ids list of 1 to 20. A call holds at most 55 seconds, with 50 as the default, so a ten-minute render is a loop of waits rather than one long one. On wait_slice_expired, call jobs_wait again with the same ids. A 524 on jobs_wait is a transport failure, never a job outcome.

The rule that matters

Do not resubmit a paid request because your terminal or process went away. A client-side timeout does not cancel the job, which keeps running and billing. If you must retry the submit itself, reuse the same Idempotency-Key so the retry returns the original job. Cancellation only succeeds before generation starts; after that the API answers 409 job_generation_already_started.