Agent Status

VS Code extension for reporting observable agent-tool behaviors and runtime snapshots to dashboard.

Important limitation

This extension does not read private internal state from another extension. It only uses observable editor/window/tab/document signals exposed by VS Code APIs.

The extension reports data in two channels:

• events -> dashboard /api/events
• statuses -> dashboard /api/status

Protocol version:

• schemaVersion = 2.0
• each event/status includes source, user, machine, workspace, instanceId, sessionId, phase

Dimension identity block (in detail.identity):

• targetDimension: instance | human | agent
• instance: { id, vscodeSessionId, vscodeMachineId }
• human: { id, user, machine }
• agent: { id, sessionId, toolExtensionId }

Runtime status identity fields:

• instanceId: extension-generated VS Code instance identifier.
• vscodeSessionId: current VS Code environment session id (when available).
• vscodeMachineId: VS Code machine-level identifier.

Status payload fields used by dashboard:

• isWorking
• detail.reason
• detail.identity
• detail.runtimeStatus
• detail.behaviorSummary.recentAgentEvents
• detail.behaviorSummary.recentAgentDirectingEvents

Event Types Reported By Plugin

Current extension emits the following event.type values:

• agent.extension_state
• agent.prompt_buffer_changed
• agent.interaction_ended
• agent.interaction_signal_lost
• agent.interaction_started
• agent.panel_closed
• agent.panel_opened
• agent.panel_tabs_changed
• agent.panel_visibility_changed
• editor.file_changed
• editor.file_changed_with_agent_context
• editor.focus_changed
• editor.focus_changed_to_agent
• editor.selection_changed
• editor.selection_changed_with_agent_context
• heartbeat.agent_present
• heartbeat.tick
• lifecycle.session_ended
• lifecycle.session_started
• window.focus_changed
• window.focus_changed_with_agent

Configuration

Open VS Code settings and configure:

• agentStatus.enabled
• agentStatus.endpoint
• agentStatus.apiKey
• agentStatus.heartbeatIntervalSeconds
• agentStatus.debugLogging

Endpoint recommendation:

• Prefer http://localhost:8787/api/events (or your server /api/events URL).
• Host-only endpoint like http://localhost:8787 is also supported; extension auto-resolves to /api/events and /api/status.

Commands

• Agent Status: Show Current Status
• Agent Status: Show Log
• Agent Status: Open Sidebar
• Agent Status: Flush Queue Now

Run locally

1. npm install
2. npm run compile
3. Press F5 in VS Code to launch Extension Development Host