Coding Agent Security · Workstation Sensor

Coding-agent session evidence and workstation monitoring.

Investigate agent sessions, credential exposure and changes to local agent configuration. Follow a finding to the workstation and the recorded activity behind it.

WORKSTATION → HEELEREvidence collection
forumAgent sessionsPrompts · tools · responses
settingsLocal configurationSkills · hooks · MCP
↓
laptop_macWorkstation SensorCollect changes · upload evidence
↓
DetectionsRisk and supporting events
InvestigationSessions and workstations
Session investigation

Session findings linked to recorded activity.

Inspect prompts, tool calls and responses in sequence. Trace credential exposure through recorded session evidence instead of investigating an isolated alert.

SESSION INVESTIGATION
PROMPT“Debug the payment client.”
TOOL READRead services/payments/.env
TOOL OUTPUTCredential appears in output
DETECTIONReview the exposure
Open the supporting event and trace where the credential appeared.
Agent configuration

Agent configuration changes and risk assessments.

Compare workstation snapshots to find new or modified skills, hooks and MCP configuration. Open the file assessment to understand the risk.

WORKSTATION CHANGE
PREVIOUS SNAPSHOTMCP serversgithub · heeler
CURRENT SNAPSHOT+ release-helperNew server configuration
↓
Review the agent fileSafety score · findings · referenced hosts
Configuration shows what is installed. Session evidence shows observed activity.
Collection coverage

Session and configuration collection coverage.

Session sources include Claude Code, Codex, OpenCode and supported Cursor and VS Code chat sources. Configuration inventory covers agents, skills, hooks, MCP servers and editor extensions separately.

forumSession evidencePrompts · responses · tool activity · Observed commits · delegated sessions
settingsConfiguration inventoryInstalled tools · agent files · Snapshots · file assessments
Fleet visibility

Workstation reporting status and collection gaps.

Review reporting state, sensor versions and collection health. Identify stale or missing evidence before relying on a fleet-wide assessment.

WORKSTATIONS
DeviceReporting
mac-0142Current
win-0087Current
mac-0206Stale
Last heartbeatSensor versionCollection status
Stale evidence is a coverage gap, not a clean result.
Evidence controls

Raw-evidence access and retention.

Set raw-evidence access separately from indexed session metadata. Raw transcripts and collected files can contain sensitive data; inventory redaction does not sanitize those artifacts.

EVIDENCE RETENTIONSeparate controls
Raw evidence7 / 30 / 90 days
Transcripts · snapshots · collected files
Derived analysis30 / 90 days
Cached findings
Raw-access permissionsRetention policy
Indexed metadata can remain after raw evidence expires.
Prevention and investigation

Agent enforcement and session investigation in one platform.

Use Agent Hooks for guidance and supported enforcement inside the coding agent. Use the Sensor for session and workstation evidence.

blockAgent HooksGuide and check supported actions
searchWorkstation SensorCollect evidence of observed activity
↓
Coding Agent SecurityReview detections, sessions and workstation configuration
Deployment

Deployment through device management.

Deploy to macOS and Windows workstations. Enroll each machine with a deployment credential, then use its machine identity for subsequent uploads.

FLEET ROLLOUTmacOS · Windows
admin_panel_settingsYour device managementDistribute the sensor
↓
laptop_macmacOS
computerWindows
↓
Enroll each workstationMachine identity → signed uploads

Investigate agent behavior using recorded evidence.

Connect workstation configuration, session activity and repository context in Coding Agent Security.