Agents (the place)
The place in Caura Prism that shows who writes to your memory and from where — every agent, your OpenClaw fleets, the rules each agent's sessions loaded, and the broker machines — and who sees each tab.
Agents in the sidebar answers one question: who writes to your memory, and from where? That is also its line under the title. (This page is about the place in the app. To teach an agent to use Caura, see the Caura skill.)
Agents shows the tenant chosen in the switcher at the top of the sidebar. With no tenant chosen, a tab says so and offers Choose a tenant.
Who sees what
| Tab | Who sees it |
|---|---|
| Agents | everyone in the tenant |
| OpenClaw fleets | everyone in the tenant |
| Rules and receipts | people with the View the audit log permission, when governance is on for your organization |
| Machines | when Broker Fleet is switched on for your organization, and your role can view the fleet, manage the organization's credentials or manage governance |
Agents
Every agent in this tenant in one table, across fleets: Agent, Fleet, Memories, Recalls, Last write and Trust. A dot beside each name shows whether it was active in the last 24 hours. The line above the table counts the agents and fleets, and how many agents wrote or recalled in the last 24 hours.
- Filter by fleet with the buttons at the top, or Find an agent by name.
- Click a fleet to open it in OpenClaw fleets.
- Click a memory count to see that agent's memories in Memory.
- Organization admins can change an agent's trust level in the Trust column; everyone else sees the level. See Trust levels.
With no agents yet, the table links to Connect to connect one.
OpenClaw fleets
Your OpenClaw fleets and the nodes in each.
- Connect New Fleet (organization admins): give it a Fleet ID and, if you like, a description.
- Pick a fleet to see its OpenClaw nodes: hostname, OpenClaw and plugin versions, when it joined, the agents it reported and their registered tools. When a fleet has more than one node, filter its nodes by name, hostname or IP and sort them by status, name or last heartbeat.
- Paste a Caura API Key (from Connect › Keys) at the top of a fleet to get a ready-to-run command that connects a node to it. The key is kept only until you reload the page.
- On a node, get the command to Install on another node. Organization
admins can also send it a command, send its agents a prompt that explains
what Caura can do for them (written to their
HEARTBEAT.md), or Update Plugin. - Delete fleet (organization admins) removes the fleet with its nodes and pending commands, after you type its name. Memories written by the fleet are kept.
See OpenClaw and Multi-agent fleet.
Rules and receipts
Which rules each agent's sessions loaded. At the top: sessions on the current rules version, stale agents (on an older version) and agents by tool. Below: the current rules, which you can unfold, and every enrolled agent with the rules its last session loaded. Open a session to see what was delivered, what the session did, and any of its writes being held for review, each a click from Review › Held writes. A receipt proves the rules were delivered, not that the model followed them.
Under it, How rules were kept: each tenant rule can carry one check that the Caura broker runs on the machine against every tool call of a session given that rule. It records only the verdict, and in block mode refuses the call. Rules without a check read "delivered only". People whose role can manage governance can Add check or Edit check. See Rule checks.
The tab needs governance, which is on for every organization unless it was
turned off for yours. Where it is off, the tab is hidden, and a direct link
says "Rules and receipts aren't switched on for this organization", with
Ask us to turn it on. See Governance. Every
read on it also needs the View the audit log permission (org.audit.view;
organization admins have it), so the tab is hidden without it, and a direct
link says you don't have access.
Machines
The machines your Caura brokers run on. The feature is called Broker Fleet; the tab is named for what it lists. It has its own tabs, each shown to the people who may use it:
| Tab | What it is | Who sees it |
|---|---|---|
| Brokers | every broker install and its status | roles that can view the fleet |
| Agents on machines | the agents the brokers report, in every tenant | roles that can view the fleet |
| Onboard | connect a new broker | roles that can manage the organization's credentials |
| Manage | installs, fleet join tokens, Mint a registration key and fleet policy | roles that can manage governance |
Machines opens on the first of these you may use.
Broker Fleet is switched on per organization. Without it the tab is hidden, and a direct link says "Broker Fleet isn't switched on for this organization", with Ask us to turn it on. See The Broker Fleet screen, Onboarding and Monitoring.
Review
The place in Caura Prism for decisions waiting on a person — conflicting memories, skills to approve, near-duplicates and held writes — what each tab lets you decide, and who sees it.
Insights
The place in Caura Prism that says what happened and how safe it is — the activity report, per-agent summaries, the security scan and what memory was worth — and who sees each tab.