Scanner Refresh

Analyze recent changes in GitHub Copilot repositories and update the scanner.py parsing logic for new CLI event types, VS Code response kinds, session metadata, and data formats.

Working directory

Use temp_export/ (gitignored) as the working directory for any intermediate markdown files such as gap analysis reports, research notes, or comparison summaries. This keeps the repo clean while preserving artifacts for review.

# Ensure working directory exists
New-Item -ItemType Directory -Path "temp_export" -Force | Out-Null

Quick start

When triggered, follow this workflow:

1. •Research recent changes in source repositories
2. •Analyze local session files for actual event types in use
3. •Compare against current scanner.py handlers
4. •Check for structural/metadata changes (session types, locations, storage formats)
5. •Write gap analysis and findings to temp_export/ as markdown
6. •Implement missing handlers and add tests

Instructions

Step 0: Determine search window

Restrict research to changes since the last scanner update to avoid redundant work.

# Get the date of the last commit that touched scanner.py or the SKILL.md
$lastScannerChange = git --no-pager log --format="%ai" -1 -- `
  src/copilot_session_tools/scanner/ `
  .claude/skills/scanner-refresh/SKILL.md
Write-Output "Search window: since $lastScannerChange"

Use this date as the --since filter for all github-mcp-server-list_commits calls and as the since: qualifier for github-mcp-server-search_pull_requests. If no date is available, fall back to "past 2 weeks".

Step 1: Research source repositories

Check recent commits and PRs (since last scanner update) in these repositories:

Use GitHub MCP tools:

github-mcp-server-list_commits (past 2 weeks)
github-mcp-server-search_pull_requests (merged PRs)

Key files to monitor for structural changes in microsoft/vscode:

Also consult DeepWiki/Context7 for documentation on event schemas.

Mining past Copilot sessions for format examples:

Use copilot-session-tools search to find past sessions that discussed formats, parsing, or scanner changes:

uv run copilot-session-tools search "vscode session type background" --full --limit 20
uv run copilot-session-tools search '"copy all"' --full --limit 20

Do NOT use copilot --share for format comparison. CLI --share only exports the current turn (post-compaction), not the full session history. Our tool parses the raw events.jsonl which contains the complete history — strictly more comprehensive. Use our own uv run copilot-session-tools export <sessionId> for markdown export instead.

Step 2: Analyze local session files

CLI sessions are stored in:

• •~/.copilot/session-state/*/events.jsonl

Extract unique event types:

Get-ChildItem -Path "$env:USERPROFILE\.copilot\session-state" -Recurse -Filter "events.jsonl" |
  ForEach-Object { Get-Content $_.FullName } |
  ForEach-Object { ($_ | ConvertFrom-Json).type } |
  Sort-Object -Unique

VS Code sessions come in three formats (see sample_files/README.md):

1. •JSON (structured export / state.vscdb) — full metadata + response item kinds
   • •~/.config/Code/User/workspaceStorage/*/state.vscdb (SQLite, key-value in ItemTable)
   • •Or exported .json files
2. •HTML (DOM snapshot from VS Code Inspector) — rendered panel output
3. •Markdown ("Copy All" right-click) — lossy stringifyItem() output, just username: response.toString()

Extract unique response kinds from VS Code JSON:

# From exported JSON
Get-Content session.json | ConvertFrom-Json |
  Select-Object -ExpandProperty requests |
  Select-Object -ExpandProperty response |
  Select-Object -ExpandProperty value |
  ForEach-Object { $_.kind } |
  Sort-Object -Unique

Check initialLocation values across sessions to see which session types are in use:

# From exported JSON files
Get-ChildItem -Path "sample_files" -Filter "*.json" |
  ForEach-Object { (Get-Content $_.FullName | ConvertFrom-Json).initialLocation } |
  Sort-Object -Unique

VS Code session types (from ChatAgentLocation in constants.ts):

Background/cloud sessions are marked with isExternal: true in IChatSessionEntryMetadata and may be stored via chatSessionWorktreeServiceImpl.ts in vscode-copilot-chat.

Cross-referencing formats using sample files:

The sample_files/ directory contains the same sessions in all three formats (JSON, HTML, MD) with matching UUID filenames. Use these to compare what information each format preserves:

# Compare a session across all three formats
$id = "7add4c61-3ac2-42db-b672-cf461938cdfb"
# JSON — structured response items with kind, tool invocations, metadata
Get-Content "sample_files/$id.json" | ConvertFrom-Json | Select-Object initialLocation, version
# HTML — rendered DOM, shows what the VS Code panel actually displays (classes, data attributes)
# MD — "Copy All" output, shows what users get when they right-click > Copy All

When identifying rendering gaps, compare how the same content appears in:

1. •The JSON response items (ground truth)
2. •The HTML rendered panel (what users see in VS Code)
3. •The MD copy-all output (what users paste elsewhere)
4. •The web viewer output from this tool (what we render)

Any content visible in HTML/MD but missing from our web viewer parsing = a gap to fix.

Step 3: Compare with current scanner.py

The scanner is at: src/copilot_session_tools/scanner/

CLI event handlers are in _parse_cli_jsonl_events() method (~line 1950+):

• •Look for elif event_type == "..." patterns
• •Current handlers include: user.message, assistant.message, tool.use, tool.result, session.model_change, assistant.reasoning, skill.invoked, session.compaction_complete
• •CLI events for tool lifecycle: tool.execution_start / tool.execution_complete (paired by toolCallId)
• •MCP tools appear as tool.execution_start with mcpServerName and mcpToolName fields

Tool pretty-formatting is in _build_tool_invocation() (~line 1735):

• •Known tools get user-friendly invocation_message values (e.g., edit → "Edited filename")
• •Unknown tools fall back to description argument, then bare tool_name
• •When adding new MCP tools, add a pretty handler here — bare tool names like "web_search" are unhelpful in the viewer
• •Current pretty-formatted tools: view, edit, create, str_replace_editor, grep, glob, web_search, web_fetch, task, store_memory, task_complete, sql, update_todo
• •Pattern for adding new tool formatters:

elif tool_name == "new_tool":
    key_arg = arguments.get("key_param", "")
    invocation_message = f"🔧 Description: {key_arg}" if key_arg else "🔧 Description"

VS Code kind handlers are in _process_vscode_response_item() method (~line 1100+):

• •Look for if kind == "..." patterns
• •Current handlers include: markdownContent, codeBlockContent, inlineReference, progressMessage, treeData, thinkingContent, toolInvocation, toolMessage, confirmationWidget, buttonPresentation, progressTaskSerialized

VS Code session parsing uses two entry points:

• •_parse_chat_session_file() — parses exported .json files
• •_parse_vscdb_file() → _extract_session_from_dict() — parses state.vscdb SQLite databases

Both use the same response-item processing logic, looking for requests (or messages/exchanges) arrays.

Session metadata extraction status:

• •✅ session.start context (cwd, gitRoot, repository) — extracted for workspace/repo URL detection
• •❌ initialLocation (panel/terminal/notebook/editor) — not read from VS Code JSON
• •❌ isExternal (background/cloud sessions) — not read
• •❌ version (serialization format version 1/2/3) — not read
• •❌ ChatModeKind (ask/edit/agent mode) — not read
• •❌ Session timing data (IChatSessionTiming) — not read

"Copy All" markdown format — the scanner does not handle .md files from "Copy All". This format is lossy: stringifyItem() calls item.response.toString() which flattens all response items (tool invocations, thinking blocks, inline references) into plain markdown text. The format is just:

username: message text

username: response markdown

Step 4: Identify gaps

Create a gap analysis and save it to temp_export/scanner-gap-analysis.md:

• •List event types found in local files but not handled in scanner
• •List structural/metadata fields present in source repos but not extracted
• •Categorize by priority:
  • •HIGH: Contains user-visible content that would be lost
  • •MEDIUM: Contains metadata that aids understanding (e.g., session type, mode)
  • •LOW: Internal/transient events with no content

Structural gaps to always check:

• •New ChatAgentLocation values (new session locations)
• •New ChatModeKind values (new interaction modes)
• •New SerializedChatResponsePart types (new response content types)
• •Changes to ISerializableChatData version (currently v3)
• •New IChatSessionEntryMetadata fields
• •Changes to stringifyItem() format (affects "Copy All" markdown parsing)
• •New VS Code JSONL append-log format (chatSessionOperationLog.ts, used >=1.109)
• •New MCP tools without pretty-format handlers — check _build_tool_invocation() for any tool names that fall through to bare name display

Step 5: Implement handlers

For each HIGH/MEDIUM priority gap:

CLI event handler pattern:

elif event_type == "new.event.type":
    content = data.get("content") or data.get("text", "")
    if content:
        content_block = ContentBlock(
            kind="appropriate_kind",  # text, thinking, status, skill, etc.
            content=content
        )
        message.content_blocks.append(content_block)

VS Code kind handler pattern:

elif kind == "newKindType":
    content_value = item.get("content", {}).get("value", "")
    if content_value:
        content_block = ContentBlock(
            kind="appropriate_kind",
            content=content_value
        )
        blocks.append(content_block)

Step 6: Add tests

Add tests in tests/test_scanner.py:

class TestNewEventTypes:
    def test_new_cli_event(self):
        """Test handling of new.event.type CLI events."""
        event = {
            "type": "new.event.type",
            "data": {"content": "test content"}
        }
        # ... test implementation

Step 7: Validate

Run the full test suite:

uv run pytest tests/ --ignore=tests/test_webapp_e2e.py -v
uv run ruff check .
uv run ruff format .
uv run ty check

Content block kinds reference

VS Code session data model reference

Serialization format (ISerializableChatData v3 in chatModel.ts):

{
  version: 3,
  sessionId: string,
  creationDate: number,
  initialLocation: "panel" | "terminal" | "notebook" | "editor" | undefined,
  responderUsername: string,
  customTitle: string | undefined,
  requests: ISerializableChatRequestData[],
  // v3 additions: hasPendingEdits, pendingRequestQueue, inputState
}

Response parts (SerializedChatResponsePart union type):

• •IMarkdownString — markdown text content
• •IChatResponseProgressFileTreeData — file tree data
• •IChatContentInlineReference — inline file/symbol references
• •IChatAgentMarkdownContentWithVulnerability — markdown with vulnerability info
• •IChatThinkingPart — thinking/reasoning content
• •IChatProgressResponseContentSerialized — progress content
• •IChatQuestionCarousel — question carousel UI

Session metadata (IChatSessionEntryMetadata in chatSessionStore.ts):

• •sessionId, title, lastMessageDate
• •initialLocation?: ChatAgentLocation — where chat was started
• •isExternal?: boolean — background/cloud sessions
• •hasPendingEdits?: boolean
• •isEmpty?: boolean
• •timing: IChatSessionTiming — created, lastRequestStarted, lastRequestEnded
• •stats?: IChatSessionStats
• •lastResponseState: ResponseModelState

"Copy All" format (from chatActions.ts stringifyItem()):

username: user message text

username: flattened response markdown (response.toString())

This is lossy — tool invocations, thinking blocks, inline references, and structured content are all flattened into plain markdown. No metadata is preserved.

Best practices

• •Only implement handlers for events with meaningful content
• •Skip internal/transient events (add to skip list with comment)
• •Preserve original formatting where possible
• •Add tests for each new handler
• •Update _merge_content_blocks() if new kinds should stay standalone
• •When adding metadata extraction (e.g., initialLocation), store it on ChatSession and propagate through to the database schema
• •Consider whether new session types (terminal, notebook, editor) need different parsing logic than panel sessions
• •Monitor the VS Code JSONL append-log format for structural changes separate from the flat JSON format
• •Always add pretty-format handlers for new MCP/tool names in _build_tool_invocation() — bare tool names are unhelpful in the web viewer and markdown export
• •When adding new tools, extract the most informative argument (e.g., query for search tools, path for file tools) into the invocation_message

Export parity notes

Our markdown export (markdown_exporter.py) is strictly more comprehensive than CLI --share:

CLI --share cosmetic features (emoji role markers 👤💬, <details> for tool args, <sub>⏱️</sub> timing) are NOT worth adopting — they add noise without adding content.

Do not use copilot --share for comparison or research — it only exports the active turn after compaction. Use our own copilot-session-tools export for full session markdown.