Users
Who rides this lane?
alice@company.com
high-signal work
bob@company.com
normal baseline
Agents meaning layer
Agent inventory should explain which agent families shape company consequence and execution reach, not just which binaries are present.
Security cares about the execution lane each agent opens: how broadly it is deployed, what tools it can reach, and what kinds of work it normalizes.
1 agent family dominates
Which agent family matters most to the current security story?
Agent families
3
One matters far more than the others
Dominant lane
NaN
Most sensitive work routes here
Sensitive repo use
NaN
Common in auth and infra paths
Low-signal families
2
Mostly background or CI work
Meaning anchors
Why agents matter before the raw catalog
3 anchors
Anchor | Summary | Operator note |
|---|---|---|
Agent inventory explains execution lanes | A shared agent family is really a shared behavioral surface across users and machines. | This is more important than a simple install count. |
Common can still be consequential | The most widely deployed agent often matters most because it touches the most context and credentials. | A meaning page should make that concentration obvious. |
Agent detail should connect capability to consequence | The story is about what the lane can reach and normalize, not only version metadata. | This turns a technical detail page into an operational one. |
Priority queue
Fastest drill paths for this entity type
Significance
Story | Summary | Why it matters |
|---|---|---|
Claude Code v1.2.0 | Shared across several endpoints and tied to the most consequential session lane. | It concentrates tool power and sensitive repo access. |
Automation runner family | High volume but narrower consequence. | Useful baseline against the dominant human-operated lane. |
Legacy agent version | Low volume but important for compatibility drift. | Good follow-up after the main execution lane is understood. |
c6 reference
Raw Agent Inventory
2 js/node · 1 python
Languages
NaN
Agents observed
3
Dominant lane
NaN
Last seen
NaN
Agent | Version | SDK language | Sessions | Users |
|---|---|---|---|---|
| Claude Code | v1.2.0 | js / node | 31 | 12 |
| Cursor | v0.42.0 | js / node | 8 | 4 |
| LangChain | v0.3.1 | python | 4 | 1 |
Representative detail
claude-code@1.2.0
Claude Code should be shown as a shared execution lane with broad reach into files, tools, and model traffic, not just as the most common agent row.
Agent :
Claude Code
claude-code@1.2.0
Version :
v1.2.0
SDK Language :
js / node
SDK Runtime :
node
SDK Version :
0.38.0
Agent ID :
claude-code@1.2.0
Agent execution map
The dominant agent family should be shown as a shared lane, not an isolated binary.
agent
Use the map to connect one agent version to the users, tools, files, and destinations that make it consequential.
Focus
claude-code@1.2.0
Dominant execution lane across recent developer work.
shared lane
Endpoints
Where does it run?
alice-mbp.local
sensitive repo context
bob-thinkpad.local
normal lane
Capabilities
What does it unlock?
bash
broad execution power
filesystem
sensitive file adjacency
External paths
Where can it send context?
api.anthropic.com
expected provider
secondary calls
review this path
users on lane
5
shared reach
high
boundary importance
elevated
next drill
agent detail