Inventory gives you a complete picture of every managed endpoint — the AI agents installed, their versions, the operating system, and hardware specs. It’s the fleet register for your AI deployment.
What Inventory shows
For each endpoint in scope, Inventory captures:
- Which AI agents are installed and their versions
- Operating system and hardware profile
- Last-seen timestamp and agent heartbeat status
- Whether the endpoint has an active metadata snapshot
Step 1: Navigate to Inventory
Click INVENTORY in the Views section of the left panel. The center panel switches to the Inventory view.
Step 2: Review the scope summary
The Inventory header shows:
Step 3: Explore Fleet Composition
The Inventory Surface shows a Fleet Composition view by default. This shows:
- AI agents tab — a horizontal bar chart showing all AI agents detected across the fleet, color-coded by agent. The chart shows both count and relative proportion. Hover over any bar segment to see the exact count for that agent.
- Operating systems tab — same breakdown by OS (macOS, Windows, etc.)
The Fleet Composition chart is one of the best answers to the question “what AI tools are my employees actually using?” — including shadow AI tools that weren’t officially approved or deployed.
Step 4: Drill into individual endpoints
Scroll down past the Fleet Composition chart to see the endpoint list. Each row shows:
- Endpoint identifier (hostname or device ID)
- Active AI agents on that endpoint
- OS version and hardware summary
- Last seen / last inventoried timestamp
Click any row to open the endpoint detail view, which shows the full installed agent inventory, OS details, and activity history for that specific machine.
Step 5: Filter and search
Use the scope controls in the left panel to narrow the inventory view:
- Filter by agent to see only endpoints running a specific AI tool
- Filter by OS to see macOS vs Windows breakdowns
- Use the search box to find a specific endpoint by name
Understanding inventory gaps
If an endpoint shows as “No snapshot,” the Origin agent has been seen on that machine but hasn’t yet completed a full inventory scan. This can happen on first install, after a long offline period, or if the agent was temporarily blocked from reporting. The next agent heartbeat will resolve the snapshot.