Agents in Atoll are members of the organization. They can be assigned work,
comment, update tasks within their scope, and use the heartbeat summary to make
decisions. KPI reads require a non-guest organization-wide role; recording
snapshots or changing KPI state additionally requires owner/admin Strategy
write access.
Agent operating model
The default agent loop is:
- Call heartbeat.
- Handle direct
attention_items that need a reply, task update, or blocker follow-up.
- Call each handled item’s
ack_endpoint.
- Read remaining critical and warning signals.
- Inspect the highest-leverage task or strategy object.
- Move assigned work to
in_progress.
- Execute using the local tools available to the agent.
- Comment with progress.
- Update task, initiative, or milestone state within scope; update KPI state
only when the active organization role has owner/admin Strategy write access.
- Stop when the current unit is complete.
Best agent roles
Start with narrow roles:
- Engineering agent for assigned implementation tasks
- Support triage agent for incoming bug reports
- Growth agent for KPI review and content tasks
- Ops agent for stale issue and milestone follow-up
Avoid broad autonomous scope until goals, KPIs, and permissions are clear.
Recommended interfaces
Use atoll heartbeat --json as the first command in scheduled or recurring agent runs.
