extension-dev

name	extension-dev
description	Build / F5 / debug the cc-connect VSCode extension. Use when you're iterating on src/ or webview/ in this directory and need to know which command to run, how to inspect runtime state, or how to debug specific subsystems (webview rendering, Claude SDK driver, daemon spawn, log tail, IPC over chat.sock).

cc-connect extension dev — operational skill

When to use this

Invoke whenever the task involves:

• editing src/ (extension host TS) or webview/ (React TS) and needing to compile + reload the dev host
• diagnosing why a change didn't appear (build cache vs dev-host reload vs JS bundle staleness)
• understanding which subsystem owns which behavior (sidebar tree, panel webview, Claude runner, log tail, chat.sock client, daemon orchestrator)
• debugging the Claude Agent SDK plumbing without burning subscription quota

For architecture / design rationale, read ../CLAUDE.md and ../docs/vscode-extension-design.md first — this skill is the operational layer.

The dev loop

# From vscode-extension/
bun install              # one-time
bun run compile          # build host TS + webview bundle
bun run watch            # tsc --watch (host only — webview needs manual rebuild)

F5 in VSCode launches the dev host. The bundled launch config (vscode-extension/.vscode/launch.json) auto-runs bun run compile as a pre-launch task and disables user-installed extensions in the dev host (--disable-extensions flag).

Three layers of "did my change land?" — when something looks stale, check in this order:

1. Host TS ( → ): F5 always rebuilds via the pre-launch task, but reload inside dev host does NOT. Close + reopen the dev host window after host changes.