Inventory AI tools
AI tools
An AI tool is a program on a machine that talks to a model: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI and others. The agent finds each one by its own config folder and reports it as an AI artifact of category AI tool. This page is AI artifacts narrowed to those tools, with a page for each one.
Who can use it
Reading the list and a tool's page needs machines:read, which every role holds. Unlock needs policies:write: Owner, Admin and Policy author.
Read the list
- Open Inventory › AI Tools.
- The list opens folded by tool name and version, so you see which tools run at which release. Fold by Name, Account, Machine or Source instead, or turn the fold off for one row per machine.
- Search with Search tool or location.
- Select a row. The tool opens beside the list with its tabs, and the full page is one click away.
A row can show Signed in as, Machine, Location, State and Tags. A row names its state only when it is not Present. The end of a row shows the worst open issue, named when a setting caused it, and a lock when one is held.
A tool can state some things about itself and not others. When it cannot state its version, last use or account, the console says so. That is different from a tool that would have told us and there is nothing.
A tool's page
The tabs a tool shows depend on what the agent reported for it.
| Tab | What it holds |
|---|---|
| Overview | Identity (account, plan, install location, hooks), Needs attention, Live sessions, Settings files read, Governed by, a Timeline, and a Sessions · last 7 days chart. |
| Sessions | The tool's recent sessions. Only for tools whose own history the agent reads. |
| Permissions | The tool's own settings: what is allowed, asked and denied, and extra directories. |
| Extensions | MCP servers, Plugins, Marketplaces, Skills, Agents and commands. |
| Memory | The memory or instruction files recorded for the tool on that machine. |
| Hooks | Ours, the coverage the agent has on this tool, and Other hooks. |
| Issues | Open issues about the tool. |
Sessions
The tab shows sessions for 1 day, 7 days or 30 days, filtered by Project and Oversight. The columns are Project and first prompt, Started, Length, Prompts, Tool calls, Oversight and Saved rules. A running session carries Live.
Oversight is how much the tool asks before it acts: Ask, Allow list only, Auto edits, Auto, Plan or Bypass.
The agent reads the tool's own history every five minutes. Until the first sessions arrive the tab says "Waiting for the first sessions".
Session locks
A policy can lock one session, or a whole tool on one machine. While the lock holds, the tool's calls are refused. A lock is shown on the row it locks. There is no list of locks.
- Find the lock icon on a session row in Sessions, or at the end of the tool's row in the list.
- Hover it. The tooltip shows Policy, Matched, Locked, Lifts and Refused since. Lifts reads "When someone unlocks it" when the lock has no end.
- Click the icon to open the decision that locked it. A lock set by a Session-log policy opens in Governance › Runs. A lock set by a Hook policy opens the hook call in Activity › Interactions.
- Choose Unlock.
The row then reads Unlock sent, and a message tells you which machine the unlock reaches at its next check-in. The lock stays until the machine checks in. Pressing Unlock a second time changes nothing. Each unlock is written to the audit log.
When it goes wrong
| You see | It means |
|---|---|
| No AI tools found yet, "Agents report what they find on each scan." | No enrolled machine has reported a tool. |
| "Could not load AI tools" | The list could not be read. |
| "Could not load this tool." with Try again | The tool you opened could not be read. |
| "This tool’s sessions could not be read." | The Sessions tab failed. |
| "No session matches. Clear the Project or Oversight facet to see more." | Your Sessions filters match nothing. |
| "No sessions received from this machine yet" | The agent has not sent any sessions for this tool. |
| "Nothing on this tool needs attention." | The tool has no open issue. |
| "Live sessions could not be read." | The Overview card failed. |
| "Could not unlock" or "Could not unlock this session", then the reason | The unlock was refused. |
| "unlocking a session requires policies:write in this workspace" | Your role does not hold policies:write. |
With the API
Tools, their sessions and the Unlock request are in the Inventory reference. An API key needs machines:read to read and policies:write to unlock.