Running a cycle
Who should read this: agent authors and Loop Runner owners.
Tools (catalogue)
| Tool | Purpose |
|---|---|
loop_workspace_register | Create/idempotent-update a company workspace |
loop_agent_register | Create/idempotent-update an agent in a workspace |
loop_run_start | Open a leased run; return continuity + shared inbox |
loop_run_heartbeat | Extend lease (fencing token required) |
loop_run_complete | Commit private_state, notes, checkpoints, acks |
loop_run_fail | Controlled failure with failure_id |
loop_shared_publish_now | Urgent note visible before complete |
loop_shared_read_more | Page more unacked deliveries |
loop_agent_inspect | Read pair-scoped continuity metadata |
Minimal start payload
{ "workspace_name": "chrilan", "agent_name": "hos-whatsapp-overview", "schedule_key": "hos-whatsapp-overview:5min", "trigger_id": "manual-2026-08-14T10:00:00Z" }
Complete payload essentials
run_id,fencing_token,completion_id(idempotency)result_summaryprivate_state.objectiveandprivate_state.summary_for_next_run(required)- Optional:
shared_notes,ack_delivery_ids,checkpoint_updates,metrics
Isolation rules
- Wrong pair on another agent's run →
FORBIDDEN(owner not disclosed) - Stale fencing token → rejected
- Duplicate
trigger_id/completion_id/failure_id/dedupe_key→ idempotent replay