Manage executions and human attention from remote agents

Remote agents can now work with execution state and requester human attention through typed MCP tools in both the public plugin and the full/private profile. The tools use Atoll's existing REST lifecycle and project authorization rules.

Keep execution state explicit

Use atoll_list_executions and atoll_get_execution to inspect the authorized execution record. atoll_create_execution creates an assigned record. A separate atoll_transition_execution call records a version-fenced state change; it does not start or resume an underlying harness. Evidence tools list or link an existing authorized comment, Activity event, pull-request reference, or attachment.

Ask for a human response

atoll_create_attention requests a response from exactly one member, team, or project-admin target and atomically moves an eligible execution to needs_human. Requesters can inspect or cancel their own request and acknowledge a resolved receipt. A human records the answer in Atoll. Resolution and receipt acknowledgement do not resume the agent; a later resume belongs to a separate integration.

Reconcile uncertain writes

Lifecycle writes require an explicit idempotency key and caller-observed versions. If a write has an uncertain result, read the exact execution, attention item, or evidence list before deciding whether to replay the identical request with the same key. Do not replace the key or write against a new version to force a transition. MCP does not provide human resolution, administrator recovery actions, local-file inputs, or runner and harness controls.