Owner fit
Who owns this host?
alice@company.com
known owner
developer_machine
expected environment
Endpoints detail story
alice-mbp.local should read as a stable but consequential host: trusted identity anchor, sensitive repo adjacency, and a useful containment boundary.
A host story page should help the operator reason about trust and containment quickly, not just list OS fields and IP addresses.
This host anchors the important work
Why is this host story valuable even though the host is known?
Sessions
6
Most meaningful recent developer work
Sensitive files
12
Several are high consequence
Primary user
NaN
Stable owner anchor
Environment
NaN
Expected but consequential
c6 detail reference
alice-mbp.local
Significance
Owner binding incomplete
This host is active in AI usage but still lacks a clear person or environment owner.
Hostname :
10.0.1.44
IP Address :
10.0.1.44
Environment :
unknown
OS :
macOS
Runtime :
node
Endpoint ID :
endp_01Y7w...
Users On This Endpoint
c6 starts with attribution around the host.
User | Primary agent | Sessions | Last seen |
|---|---|---|---|
| unknown | Claude Code | 1 | 22 min ago |
Recent Sessions
The raw page then shows the work actually happening there.
User | Agent | Model | Cost | Status |
|---|---|---|---|---|
| unknown | Claude Code | claude-sonnet-4-6 | $0.61 | active |
| sandbox-evals | Cursor | claude-opus-4-6 | $1.94 | ended |
Key findings
What this representative item changes in the story
3 findings
Finding | Body | Operator note |
|---|---|---|
This host gives the story a stable anchor | Owner, environment, and work pattern align, making interpretation stronger than on weaker endpoints. | That is why the page matters even without an obvious anomaly. |
Company consequence is high here | Sensitive file and repo context are concentrated on this machine. | The consequence is about the work, not the OS metadata. |
Containment is unusually clear | If the surrounding session story turns concerning, this host is a clean place to act. | That operational clarity is valuable to surface. |
Immediate actions
Point to action before deeper raw inspection
3 actions
Use the host as the containment anchor :
If the surrounding session or key story escalates, this endpoint gives security a clear boundary for action.
Compare against the unresolved host :
Use this page as the baseline for what a strong endpoint story looks like.
Trace the file-to-network sequence :
Open the attached session and file stories to confirm how company context moved from the host outward.
Endpoint trust map
A host story should connect owner clarity, company context, and containment value in one read.
endpoint
Use the map to show why a known host can still be the most consequential endpoint in inventory.
Focus
alice-mbp.local
Stable developer machine behind several high-signal stories.
trusted anchor
Execution lane
What runs here?
Claude Code
primary agent
shared org key
adjacent caveat
Company context
What lives here?
api-refactor
auth repo path
.env + config files
sensitive file cluster
Containment value
Why does the host matter?
clean host boundary
good containment anchor
boundary-linked sessions
important review lane
owner trust
high
company consequence
high
containment
clear
next drill
session detail
Evidence bundles
Bundle the story instead of reconstructing it from rows
4 bundles
Bundle | Body | Why it matters |
|---|---|---|
Identity bundle | alice-mbp.local aligns with Alice’s account and expected developer environment. | Strong host trust baseline. |
Context bundle | Auth-related repos and sensitive files sit on this endpoint. | That is what makes the host consequential. |
Execution bundle | Claude Code and a shared key appear repeatedly on the host. | The host is central to the broader inventory story. |
Boundary bundle | High-signal sessions on the host lead into provider and secondary outbound paths. | Host meaning sharpens boundary interpretation. |