Add real-time session event monitoring to execution screen by Copilot · Pull Request #12 · colindembovsky/planeteer

Copilot · 2026-02-13T01:06:09Z

Implementation Plan: Real-Time Session Event Monitoring

✅ All tasks completed!

Extend copilot.ts to support session event callbacks
Update executor.ts to propagate session events
Enhance execute.tsx to display real-time events
Add unit tests for event handling
Update documentation in README
Code review and refinements
Fix React key issue: Added unique id field to DisplayEvent
Improved event ID generation for better uniqueness guarantee
Enhanced test coverage for event callbacks and forwarding

Recent Changes

Improved copilot.test.ts with comprehensive StreamCallbacks testing
Enhanced executor.test.ts with event forwarding and lifecycle validation
Added tests for:
- Event callback structure and type validation
- Multiple sequential events through callbacks
- Event data preservation when forwarding
- TaskId context enrichment in executor layer
- Error event handling with taskId context
- Complete task lifecycle with events
All 17 tests passing ✅

Original prompt

This section details on the original issue you should resolve

<issue_title>[enhancement] Add Real-Time Session Event Monitoring for Task Execution Feedback</issue_title>
<issue_description>## Background

Recent changes in the Copilot SDK (v0.1.24-preview.0) include:

Event naming improvements: The SDK renamed tool.execution_end to tool.execution_complete for clarity (PR colindembovsky/planeteer#385 by Andrew Yoon, merged Feb 6, 2026)

Session event handling: Enhanced session event subscription mechanisms with better reliability (PR colindembovsky/planeteer#24 by nathfavour)

Forward compatibility tests: New tests verify handling of unknown session event types (PR colindembovsky/planeteer#35)

CLI update: @github/copilot upgraded to 0.0.405 (PR colindembovsky/planeteer#396 by Devraj Mehta, merged Feb 7, 2026)

Commit reference: 439e0f0

Proposal

Implement real-time session event monitoring in src/services/executor.ts to provide users with granular feedback during task execution. The SDK's session event API allows subscriptions to events like:

tool.execution_complete (formerly tool.execution_end)

Progress updates from Copilot agents

Token usage and performance metrics

Implementation approach:

Add event listeners in the Copilot SDK wrapper (src/services/copilot.ts)

Stream events to the execution screen component (src/screens/execute.tsx)

Display real-time progress indicators for each task (e.g., "Installing dependencies...", "Running tests...", "Generating code...")

Show estimated completion percentages based on event data

Benefit

Better UX: Users see what Copilot is actively doing instead of staring at a blank "In Progress" spinner

Debugging: When tasks fail, users can see exactly where execution stopped

Transparency: Token usage and performance data help users understand costs

Trust: Real-time feedback builds confidence that the system is working

Acceptance Criteria

Session event subscription implemented in src/services/copilot.ts using SDK's event API

Event stream plumbed to src/screens/execute.tsx (via React state or context)

Execution screen displays at least 3 types of events: task start, progress updates, and tool.execution_complete

Event log is scrollable and shows timestamps

Error events are highlighted in red and include actionable messages

Unit tests verify event handlers properly parse SDK event payloads

Documentation updated to explain the event monitoring feature

AI generated by Weekly Enhancement Suggestions

Comments on the Issue (you are @copilot in this section)

Fixes [enhancement] Add Real-Time Session Event Monitoring for Task Execution Feedback #9

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

…ts, document event subscription Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Copilot

Pull request overview

This PR adds real-time session event monitoring to provide users with granular visibility into Copilot SDK agent behavior during task execution. The implementation subscribes to SDK session events (tool executions, progress updates, token usage, errors) and displays them in a toggleable event log panel accessible via the e keyboard shortcut.

Changes:

Added session event subscription infrastructure in copilot.ts with SessionEventData interface and callback plumbing through sendPrompt and sendPromptSync
Extended executor callbacks to forward events with task context (onSessionEvent receives taskId + event data)
Implemented event log UI in execute screen with bounded 100-event memory, showing last 8 events with timestamps and color-coded error highlighting
Added documentation for the new feature in README with usage instructions

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/services/copilot.ts	Added SessionEventData interface, onSessionEvent callback to StreamCallbacks, and session.on() subscription to capture all SDK events
src/services/copilot.test.ts	Added type structure tests for SessionEventData covering tool execution, usage, and error events
src/services/executor.ts	Extended ExecutionCallbacks with optional onSessionEvent, forwarding events from copilot.ts with taskId context for both regular and init tasks
src/services/executor.test.ts	Added tests verifying onSessionEvent callback signature and multi-task event handling
src/screens/execute.tsx	Implemented event log UI with DisplayEvent interface, formatSessionEvent helper, toggle functionality (e key), bounded 100-event buffer, and last-8 display panel
README.md	Added keyboard shortcut table entries and "Real-Time Session Event Monitoring" feature section with usage instructions

Copilot · 2026-02-18T17:08:07Z

src/screens/execute.tsx

+                {visible.map((evt, i) => (
+                  <Box key={i}>
+                    <Text color="gray">[{evt.timestamp}] </Text>
+                    <Text color="cyan">{evt.taskId}: </Text>
+                    <Text color={evt.isError ? 'red' : 'white'}>{evt.message}</Text>
+                  </Box>
+                ))}


Using array index as React key can cause rendering issues when the event log is updated. Since events are bounded to the last 100 and displayed items are sliced from the end, the same index could refer to different events after updates. Consider adding a unique identifier to DisplayEvent (like a counter or timestamp+taskId combination) and use that as the key instead of the array index.

@copilot apply changes based on this feedback

Fixed in d9709b9. Added a unique id field to DisplayEvent using a counter-based approach (taskId-timestamp-counter), and updated the map to use evt.id as the React key instead of the array index.

Copilot · 2026-02-18T17:08:08Z

src/services/copilot.test.ts

+import { describe, it, expect, vi } from 'vitest';
+import type { SessionEventData } from './copilot.js';
+
+describe('SessionEventData', () => {
+  it('should have correct type structure', () => {
+    const mockEvent: SessionEventData = {
+      type: 'tool.execution_start',
+      timestamp: new Date().toISOString(),
+      data: { toolName: 'test-tool' },
+    };
+
+    expect(mockEvent.type).toBe('tool.execution_start');
+    expect(mockEvent.timestamp).toBeDefined();
+    expect(mockEvent.data).toBeDefined();
+  });
+
+  it('should handle tool.execution_complete events', () => {
+    const mockEvent: SessionEventData = {
+      type: 'tool.execution_complete',
+      timestamp: new Date().toISOString(),
+      data: {
+        toolCallId: 'test-123',
+        success: true,
+        result: { content: 'Task completed' },
+      },
+    };
+
+    expect(mockEvent.type).toBe('tool.execution_complete');
+    expect(mockEvent.data).toHaveProperty('success');
+  });
+
+  it('should handle session.error events', () => {
+    const mockEvent: SessionEventData = {
+      type: 'session.error',
+      timestamp: new Date().toISOString(),
+      data: {
+        errorType: 'timeout',
+        message: 'Request timed out',
+      },
+    };
+
+    expect(mockEvent.type).toBe('session.error');
+    expect((mockEvent.data as { message: string }).message).toBe('Request timed out');
+  });
+
+  it('should handle assistant.usage events', () => {
+    const mockEvent: SessionEventData = {
+      type: 'assistant.usage',
+      timestamp: new Date().toISOString(),
+      data: {
+        model: 'claude-sonnet-4',
+        inputTokens: 100,
+        outputTokens: 50,
+      },
+    };
+
+    expect(mockEvent.type).toBe('assistant.usage');
+    expect((mockEvent.data as { inputTokens: number }).inputTokens).toBe(100);
+  });
+});


The tests in this file only verify the interface type structure and don't test actual SDK integration or event callback behavior. Consider adding integration tests that mock the SDK's session.on() method to verify that events are properly captured and forwarded through the callback chain.

@copilot apply changes based on this feedback

Enhanced in 81acab6. Added comprehensive tests for StreamCallbacks including:

Event callback structure validation

Multiple sequential event handling

Event data preservation when forwarding

Tests verify callbacks properly handle tool.execution_start, tool.execution_progress, tool.execution_complete, session.error, and assistant.usage events

Copilot · 2026-02-18T17:08:08Z

src/services/executor.test.ts

+import { describe, it, expect, vi } from 'vitest';
+import type { ExecutionCallbacks } from './executor.js';
+import type { SessionEventData } from './copilot.js';
+
+describe('ExecutionCallbacks with session events', () => {
+  it('should define onSessionEvent callback', () => {
+    const mockCallback: ExecutionCallbacks = {
+      onTaskStart: vi.fn(),
+      onTaskDelta: vi.fn(),
+      onTaskDone: vi.fn(),
+      onTaskFailed: vi.fn(),
+      onBatchComplete: vi.fn(),
+      onAllDone: vi.fn(),
+      onSessionEvent: vi.fn(),
+    };
+
+    expect(mockCallback.onSessionEvent).toBeDefined();
+    expect(typeof mockCallback.onSessionEvent).toBe('function');
+  });
+
+  it('should call onSessionEvent with taskId and event data', () => {
+    const onSessionEvent = vi.fn();
+
+    const mockEvent: SessionEventData = {
+      type: 'tool.execution_start',
+      timestamp: new Date().toISOString(),
+      data: { toolName: 'bash' },
+    };
+
+    onSessionEvent('task-1', mockEvent);
+
+    expect(onSessionEvent).toHaveBeenCalledWith('task-1', mockEvent);
+    expect(onSessionEvent).toHaveBeenCalledTimes(1);
+  });
+
+  it('should handle multiple session events for different tasks', () => {
+    const onSessionEvent = vi.fn();
+
+    const event1: SessionEventData = {
+      type: 'tool.execution_start',
+      timestamp: new Date().toISOString(),
+      data: { toolName: 'bash' },
+    };
+
+    const event2: SessionEventData = {
+      type: 'tool.execution_complete',
+      timestamp: new Date().toISOString(),
+      data: { success: true },
+    };
+
+    onSessionEvent('task-1', event1);
+    onSessionEvent('task-2', event2);
+
+    expect(onSessionEvent).toHaveBeenCalledTimes(2);
+    expect(onSessionEvent).toHaveBeenNthCalledWith(1, 'task-1', event1);
+    expect(onSessionEvent).toHaveBeenNthCalledWith(2, 'task-2', event2);
+  });
+});


The tests only verify that callbacks can be called with the correct signature, but don't test the actual event forwarding behavior in the executor. Consider adding tests that verify the executor correctly forwards events from sendPromptSync through the onSessionEvent callback with the appropriate taskId context.

@copilot apply changes based on this feedback

Enhanced in 81acab6. Added tests that verify:

Event forwarding with taskId context enrichment

Complete task lifecycle with event flow

Multiple tasks with correct taskId assignment

Error event handling with taskId context

Event data structure preservation through the forwarding chain

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

…g validation Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Copilot · 2026-02-20T20:56:22Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

https://api.github.com/user
- Triggering command: /home/REDACTED/work/planeteer/planeteer/node_modules/@github/copilot-linux-x64/copilot /home/REDACTED/work/planeteer/planeteer/node_modules/@github/copilot-linux-x64/copilot --headless --log-level debug --stdio (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Initial plan

8365e39

Copilot AI assigned Copilot and colindembovsky Feb 13, 2026

Copilot started work on behalf of colindembovsky February 13, 2026 01:06 View session

Copilot AI and others added 4 commits February 13, 2026 01:10

Add session event monitoring infrastructure

3bb7177

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Add unit tests for session event monitoring

366c947

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Update README with session event monitoring documentation

cb93901

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Address code review feedback: fix variable naming, add event log limi…

c53ee55

…ts, document event subscription Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add real-time session event monitoring for task execution feedback~~ Add real-time session event monitoring to execution screen Feb 13, 2026

Copilot AI requested a review from colindembovsky February 13, 2026 01:14

Copilot finished work on behalf of colindembovsky February 13, 2026 01:14

colindembovsky requested a review from Copilot February 18, 2026 17:03

Copilot started reviewing on behalf of colindembovsky February 18, 2026 17:04 View session

Copilot AI reviewed Feb 18, 2026

View reviewed changes

Copilot started work on behalf of colindembovsky February 20, 2026 20:44 View session

Copilot AI and others added 2 commits February 20, 2026 20:46

Fix React key issue: use unique event ID instead of array index

d9709b9

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Improve event ID generation for better uniqueness guarantee

a91c422

Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Copilot finished work on behalf of colindembovsky February 20, 2026 20:49

Copilot started work on behalf of colindembovsky February 20, 2026 20:49 View session

Enhance tests with better event callback coverage and event forwardin…

81acab6

…g validation Co-authored-by: colindembovsky <1932561+colindembovsky@users.noreply.github.com>

Copilot finished work on behalf of colindembovsky February 20, 2026 20:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Add real-time session event monitoring to execution screen#12

Add real-time session event monitoring to execution screen#12
Copilot wants to merge 8 commits intomainfrom
copilot/add-realtime-session-monitoring

Copilot AI commented Feb 13, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 18, 2026

Uh oh!

colindembovsky Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 18, 2026

Uh oh!

colindembovsky Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 18, 2026

Uh oh!

colindembovsky Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI commented Feb 20, 2026

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Comments

Conversation

Copilot AI commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Implementation Plan: Real-Time Session Event Monitoring

Recent Changes

Proposal

Benefit

Acceptance Criteria

Comments on the Issue (you are @copilot in this section)

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

colindembovsky Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

colindembovsky Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

colindembovsky Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Feb 20, 2026

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Feb 13, 2026 •

edited

Loading