vscode-ext-dev

VS Code Extension Development Workflow

When to Use

• Adding a new feature or command to the extension
• Fixing a bug in tracking, UI, or detection logic
• Running or writing tests
• Debugging the extension in the Extension Development Host
• Packaging the extension for distribution
• Modifying package.json contributions (commands, configuration, activation)

Project Architecture

Module	Responsibility
src/extension.ts	Activation, command registration, event wiring, disposal
src/codeTracker.ts	AI vs manual detection heuristics, stats persistence via workspaceState
src/statusBar.ts	Status bar item with 2-second polling updates
src/statsView.ts	Webview panel with per-file and workspace-wide statistics
src/test/extension.test.ts	Mocha test suite (run via @vscode/test-cli)

Key Interfaces

// in codeTracker.ts
interface CodeStats { totalChars: number; agentChars: number; manualChars: number; percentage: number; }
interface FileStats { [filePath: string]: CodeStats; }

Dependency Flow

extension.ts → creates CodeTracker
             → passes CodeTracker to StatusBarManager
             → passes CodeTracker to StatsViewProvider

All disposables are pushed to context.subscriptions for cleanup.

Procedure

1. Understand the Change

• Identify which module(s) the change touches (see Architecture table)
• If adding a command: update both src/extension.ts (registration) and package.json (contributes.commands)
• If adding a config setting: update package.json (contributes.configuration) and consume it via vscode.workspace.getConfiguration('agentCodeTracker')

2. Implement

• Follow existing patterns:
  • Classes: PascalCase with descriptive suffixes (Manager, Provider)
  • Methods: camelCase
  • Interfaces: PascalCase, exported
  • Strict mode: All type annotations explicit
  • Semicolons: Required (enforced by ESLint)
• Webview HTML must use VS Code CSS variables (--vscode-foreground, --vscode-editor-background, etc.)
• Webview communication uses panel.webview.postMessage() and panel.webview.onDidReceiveMessage()
• All resources (intervals, event listeners, status bar items) must implement disposal