Home
The dashboard's first screen — how many agents worked and on what, whether memory is being used and what it was worth, how safe it is, where agents reached and which rules they kept. What each panel counts, what its sentence means, and who sees what.
Home is the first screen after you sign in, for everyone: a new account, a new tenant, an accepted invite and a domain join all land here too. It answers a few questions about your agents, one panel each, for the last 24 hours or the last 7 days (the switch at the top right). The line above the title names what Home covers: the date, the tenant's name (or all tenants), and the period.
- A tenant with no memories yet shows one line above the panels pointing to Connect › Get started, where the setup checklist lives.
- With no tenant selected, Home says "No tenant selected" and offers Choose a tenant, which opens the switcher.
- Until 17 November 2026, a line at the top links to What moved where. Dismiss it with ×; the browser remembers.
Each panel has one number, a little evidence, and a sentence saying what the number means. The sentences are written from the numbers by fixed rules, not by a model, so the same numbers always read the same way.
Who sees what
- People who can view the organization's audit log (org admins, auditors) also see the security, broker and rules panels, and a This tenant / All tenants switch beside the period switch. It sets what Agents at work and Memory recall cover. It starts on This tenant each time Home opens.
- Everyone else sees their own tenant, without those panels or the switch.
- What memory was worth is for organization admins; Caura doesn't give members its numbers.
- Waiting for you counts skills to approve only for organization admins, and held writes and security findings only for people whose role can manage governance.
Every panel says which tenants it covers, next to its title:
| Panel | Covers |
|---|---|
| Agents at work, Memory recall | what the switch says (always this tenant without it) |
| What they're working on, What memory was worth | this tenant |
| Security | the scan and flagged agents: this tenant; rule checks and the audit trail: all tenants (shown as two groups) |
| What they reached, Rules kept | all tenants |
Agents at work, Memory recall and What memory was worth show even when their numbers are zero. What they're working on, Security and Rules kept are left out when they have nothing to show. The broker panel always says where the organization stands with the broker (see What they reached below).
When Agents at work, Memory recall or What memory was worth can't load its numbers, it stays on the page and says so, with Try again. A panel you aren't allowed to see is left out.
The panels
Waiting for you. At the top: what needs a person (conflicting memories, skills to review, writes held for review, risky memories, duplicates), with links straight to each.
Agents at work. How many agents wrote to memory in the period (an agent that only recalled is not counted), how many durable memories they wrote and, with All tenants, how many tenants the report covers (each one counts, whether or not its agents wrote). The sentence names the two agents that wrote the most; an agent known only by a UUID is shown by the first eight characters of it.
What they're working on. The largest topics in this tenant's memory, from the memory map (Memory › Map). Each topic is named from the entities its memories mention. The panel needs the memory map, which Caura turns on per organization, and memories that enrichment has named. Until two distinct topics exist, it stays hidden.
Memory recall. The share of all durable memories that were recalled at
least once during the period, whenever they were written ("Recalled this
period"). Memories marked outdated (superseded, expired or retracted) aren't
counted, because search doesn't return them. Under the number, the funnel for
the period's new memories: everything
written, what was kept as durable memory, and how many of those have been
recalled. The sentence states what the numbers show:
| Recalled this period | Reading |
|---|---|
| 60% or more | most memories were recalled this period |
| 50–59% | half or more of the memories were recalled this period |
| 30–49% | some memories were recalled this period; most were not |
| under 30% | most memories weren't recalled this period |
| none | no memory was recalled this period |
| no durable memories yet (the number shows —) | no durable memories yet |
A share that rounds to 0% while some memories were recalled shows as "<1%". The most-recalled of the new memories is named below.
With an older Caura engine that doesn't report recall over the whole corpus, the number is the share of the period's new memories recalled so far, and it is labelled that way. That share reads low on any busy fleet (a memory written an hour ago has had an hour to be recalled), so the panel gives it none of the readings above. It says when none of the new memories has been recalled yet, and, when there are more than six new memories and six of them drew a fifth or more of their recalls, it says so.
Recalls are counted for searches that carry an agent identity, so agentless searches don't show here.
What memory was worth. For this tenant: the share of agent sessions that started with work another session had already done, the agent time that reuse saved, and the share of reuse that came from a different agent. The same numbers in full are on Insights › Value.
Security. For this tenant: the last security scan's score and open findings (org admins), and agents flagged on their receipts. For all tenants: whether checked rules were kept, and whether the brokers' audit trail is uploading continuously.
What they reached. The hosts and services, programs and sensitive files your agents' tool calls reached, across the organization. Recorded by the broker; see Where agents reach. What the panel shows depends on where you are with the broker:
| Where you are | The panel shows |
|---|---|
| Broker Fleet not on for your organization | what the broker would record, and a way to ask us to turn Broker Fleet on |
| No broker connected | what the broker would record and what never leaves the machine, with a link to connect one |
| Brokers connected, recording turned off | that recording is off, with a link to Settings › Agent monitoring |
| Brokers connected, no calls in the period | how many brokers are connected, and that none reported a call |
| Brokers reporting | where the calls reached |
While brokers are connected and no rule has a check, a line under the panel links to Agents › Rules and receipts to attach one.
Rules kept. Of the calls a rule check looked at, the share that kept the rule, with how many broke one and how many the broker blocked before they ran. Shown where Broker Fleet is on, once a broker has checked a call against a rule with a check during the period; see Rule checks.
When a number looks wrong
- Low recall with memories written: few memories were found by the searches agents ran this period. The number can't say why: agents may not search, or may search for things memory doesn't hold. Check that they run the Caura skill: it tells them to recall before they work.
- Agents at work and Memory recall don't change with the tenant: the switch is on All tenants.
- No topics: the memory map is off unless Caura turns it on for your organization (ask us), or enrichment hasn't yet named enough memories for two distinct topics.
- No rules panel: it needs Broker Fleet on for your organization, and a call that a broker checked against a rule with a check during the period. Checks are attached in Agents › Rules and receipts, which needs governance (on unless it was turned off for your organization).
- "Broker Fleet isn't switched on for this organization": Broker Fleet is switched on per organization; ask us from the panel.
- "No broker is connected": reach and rule checks need brokers in fleet mode. See onboarding.
Enterprise — SaaS
The hosted Caura Enterprise deployment at caura.ai. Caura runs the database, API, and worker for you.
Memory
The place in Caura Prism that holds everything your agents remember — the memory table, the map or graph, documents and the audit trail, what each tab lets you do, and who sees what.