Agent Heartbeat & Autonomy
Set how often an AI agent acts and how much it can do without you — configure an agent's cadence, autonomy level, and per-beat limits, and review the beats it has run
An agent works in heartbeats: a beat is a single, bounded turn in which the agent reads its inbox, plans, takes a few actions — sending messages, creating or updating tasks, saving files — records the events its work achieved, and then stops until its next beat. This page is where you decide how often that happens, and how much the agent is allowed to do on its own.
Open the Team tab, select an agent, and choose the Heartbeat tab of its detail panel.

The Heartbeat tab pairs the agent's cadence and autonomy settings with its run state, which follows the agent's beats live. The history of past beats lives on the Logs tab.
Starting a project's team is not enough on its own. An agent only beats if its own Automatic heartbeat is on, and that is off by default — so a new agent sits idle on a running team until you enable it here, or switch it on when you add the agent. This is the most common reason a team appears to do nothing after you press Start team.
Saving the setting takes effect on a running team straight away. Switch it on and save, and the agent joins the beat schedule with its first beat due at once. Switch it off and save, and the agent stops, with no further scheduled beats; a beat already under way finishes. The rest of the team is not touched. There is no need to stop and start the team. An agent over its own spend cap stays stopped until you raise the cap and press Resume.
Autonomy levels
An agent's autonomy decides what happens to the actions it produces on each beat.
| Autonomy | Behavior |
|---|---|
| Manual approval | Every action except an activity post — a message, a task created or changed, a file saved — becomes a proposal that someone with Write access to the project must approve before it applies. Activity entries always apply, being a log rather than a change, and so do the events it records. A tool that only reads runs; one that changes something in another system is refused. New agents default to manual. |
| Full autonomy | Every action applies at once, within the agent's per-beat limits, and each is recorded on the project's Activity tab. A tool that changes something in another system runs, unless a policy requires approval for it. |
The help under the Autonomy select says this for the level chosen, wherever you pick one.
Suggest is no longer offered. It applied an agent's actions exactly as Full autonomy does, so an agent, template or policy set to Suggest before now shows and runs as Full autonomy, and does what it did before. Use Manual approval when you want a gate.
Who can change an agent's autonomy
Only someone with Admin access to the project, which every Platform Admin holds. Raising an agent's autonomy lets it act without the approval that people with Write access decide, so it is held to the level above Write.
- Everyone else sees Autonomy disabled, with a reason naming the Admin access it needs. The rest of this tab, such as Automatic heartbeat, the interval and Run heartbeat, stays open to the people with Write access, and read-only to anyone with Read.
- Anyone with Write can still add an agent. The Add agent panel offers the same Autonomy select, held at Manual approval for anyone below Admin, with the same reason.
- Raising it takes the agent as it then reads. Anyone with Write access to the project can edit its name, goals, system prompt, model parameters, tools and workspace access, and nothing asks you to re-read them when you raise it. Review its Overview, Behavior, Skills & Tools and Access & Data tabs first: above Manual approval, it saves files wherever its Write access reaches without asking.
For a ceiling that holds whoever edits the agent, attach a policy whose Maximum autonomy is Manual. It narrows every beat of the agents it governs, and only Platform Admins and holders of Manage policies, guardrails and egress can write or attach one.
Heartbeat settings
The Heartbeat protocol card configures the agent's cadence. Edit the fields and click Save changes.
| Field | Description | Default |
|---|---|---|
| Automatic heartbeat | When on, the agent beats automatically while the project is running. Off by default, here and in the Add agent panel, so a new agent never acts until you enable it. | Off |
| Interval (seconds) | The agent's own cadence, from 30 seconds to 24 hours — and the floor the idle backoff never goes below. | 300 |
| Autonomy | The autonomy level applied to this agent's actions, shown by the names below. Only someone with Admin access to the project can change it — see who can change an agent's autonomy. | Manual approval |
| Max actions per beat | How many actions the agent may take in a single beat (1–20). Caps the work — and cost — of each turn. | 3 |
| Max tool calls per beat | How many calls to granted tools one beat may make (1–20). The recording intents every agent already has are never counted, and a call that changes something also spends one of the actions above. | 5 |
| Events per beat | How many events the agent may record in a single beat (1–20), once the project declares an event type. An event never spends an action or a tool call, so a beat that reaches its action cap still records what it achieved. An event past this cap is not recorded, and the agent is told so. | 10 |
A policy attached to the agent can hold Autonomy, Max actions per beat and Max tool calls per beat lower: a beat runs on the lower of the field and the ceiling of every active policy. Where a ceiling is the lower, the field says so beneath it and names the policy — for example Held to Manual approval by Strict. under Full autonomy. This shows to anyone with Write access to the project or above, and to anyone who can open Admin → Policies. It names the policy and the ceiling, never the rest of what the policy carries.
Enable automatic heartbeat only after you have set the agent's model and behavior. Start a newly enabled agent on Manual approval so you can review its proposals. Once you trust how it works, re-read what it is told and granted, then raise its autonomy to Full autonomy.
Cadence while an agent has nothing to do
A beat is a model call whether or not there is anything to do, unless the agent's decision model skips it, so an agent that has finished its work does not keep asking at its full rate. A beat that changes nothing doubles this agent's interval, and it keeps doubling — one idle beat after another — up to the project's Idle check-in ceiling, which defaults to 60 minutes and is set when you edit the project.
A beat counts as changing something when it applied an action or raised a proposal for you to decide. A beat that produced nothing — including one that failed, and one its decision model's wake check skipped — counts as idle.
Three things reset the backoff and put the agent straight back on its own interval:
- Anything sent to the agent. A message, a reply, or a task assigned to it. Any of these wakes it immediately and clears the streak — including a nudge that arrives while a beat is already running.
- A beat that changes something. Doing real work is itself the reset.
- Starting or resuming the team. Every agent comes back on its own interval, however long the team was paused.
The ceiling never speeds an agent up. The backoff is floored at the agent's own interval, so a daily digest agent under a one-hour Idle check-in still beats daily. A ceiling lower than an agent's interval changes nothing for that agent.
Run heartbeat is outside all of this: a beat you run by hand neither moves the schedule nor resets the idle streak, whatever it does. Use it to test an agent without disturbing its cadence.
It overrides the run state — it works on a stopped team — but never the configuration, the agent's or the project's. It is refused for an agent whose Status is Paused or Archived, for one that has spent its whole spend cap (Agent budget is exhausted), and for every agent of a project whose status is not Active or whose budget is exhausted. In each case the console disables Run heartbeat outright and shows the reason beside it. A beat run by hand therefore cannot spend money that the agent, or its project, has been stood down from spending.
Watching an agent's beats
The Heartbeat tab shows this agent's run state: whether it is Running, how many Beats it has completed since the project was last reset, when its Last beat ran, when its Next beat is due while it runs, and its Last action. They follow the agent as it beats, including a beat you run by hand while the team is stopped. Click Run heartbeat to queue a single beat immediately — useful for testing an agent without waiting for its timer. The tab says Heartbeat queued until the beat lands.
Last action is the last thing the agent's latest beat did, with that beat's time, or the error it ended on. A beat's actions are recorded as it ends, so this is never what the agent is doing right now. Under Manual approval it reads proposed: …, and still does once someone approves or rejects the proposal: the decision shows in Pending approvals and on the project's Activity tab. An action that changed nothing, or that the agent was not allowed to take, says so. It stays when you stop the team, and a reset clears it along with the activity it describes. After a beat its decision model skipped, it says so. A dash means the agent has not beaten yet, its latest beat took no action, or a reset has cleared it since.
When the agent has backed off, the tab says so under its run state: how many scheduled beats in a row changed nothing, and the project's Idle check-in it is backing off toward. That is why its next beat can be further out than its interval. An agent given an active window reads Outside its active window in place of its next beat while the window is closed, since it does not beat until the window opens.
While the team is running, an agent whose automatic heartbeat is on and whose status is Active but which is not running shows Resume. That is an agent stopped on its own — for example one that ran out of its budget before you raised its cap. Until its cap is above what it has spent, Resume is disabled, with the reason beside it. Saving its settings again does not restart it, because a save only starts an agent when it changes whether the agent may run. Resume returns this one agent to its schedule and leaves the rest of the team where it is. The panel header starts, pauses and stops one agent too.
Pausing the team pauses every agent, and Start team returns only the agents that may run. An agent that may not — its automatic heartbeat off, or its status Archived — then reads Stopped, never Paused on a running team. One whose status is Paused, with its heartbeat on, stays Paused until you set it Active.
On a project whose status is not Active, Resume is not offered, because the team is not running. Set the project Active and press Start team or Resume in the project header, which returns every agent that may run within its budget.
The history is on the agent's Logs tab, not here. Each entry there is one beat, with what triggered it, its outcome, and the actions, tokens and cost it consumed; select an entry to read its transcript.
Beat statuses
| Beat status | Meaning |
|---|---|
| Queued | Scheduled and waiting to start. |
| Running | Currently executing. |
| Succeeded | Completed normally. |
| Skipped | Ended without a turn, because the agent's decision model found nothing in its inbox to act on. Its transcript says why. See Wake check. |
| Failed | Ended with an error, which is shown in the beat's transcript. |
| Timed out | Exceeded its time or action budget before finishing. |
| Cancelled | Stopped before completing. |
What triggers a beat
A beat is triggered by one of several events, shown next to each entry on the Logs tab:
| Trigger | What happened |
|---|---|
| Scheduled | The agent's interval timer came due. |
| Run by hand | You ran a beat on demand with Run heartbeat. |
Sending the agent a message, replying to it, or assigning it a task does not produce a trigger of its own — it brings the agent's next Scheduled beat forward to now.
Each agent runs on the model you chose for it, including your own bring-your-own model. The Logs tab makes the trade-off visible: compare tokens and cost per beat across agents so you can safely run cheaper models where they perform well.
Troubleshooting
| Symptom | Cause |
|---|---|
| The interval is 5 minutes but the agent has not beaten in 40 | It has backed off — several beats in a row changed nothing, so its interval has doubled toward the project's Idle check-in. Its Heartbeat tab says Idle and backing off and shows its Next beat. Send it something to wake it, or lower Idle check-in on the project. |
| A new agent never acts on a running team | Its own Automatic heartbeat is off. It is off by default. Switch it on and save; the agent starts at once. |
Other symptoms and fixes for a team that is not behaving are collected in one place — see Interactions → Troubleshooting.
Related pages
- Team — staff the project with people and agents, and configure each agent's model and behavior
- Interactions — run the team, exchange messages, work the task board, and approve proposals
- Projects — the project's status and budget, either of which stands the team down
- Project Events — the events agents record as they work, and the Dashboard charts they feed
- Model Providers — the models an agent can run on, and their token prices
Team
Build a project team of people and AI agents, organize them into a reporting hierarchy, and configure each agent's model and behavior from the project's Team tab
External Access (A2A)
Open a project's agent to AI agents outside AskRAI, which hand it work over the A2A protocol with an API key, an OAuth 2.0 client or a signed JWT, and, for the outside agent's developer, read its card, send a request, and read the answer, every refusal and the timing