claude-ide-bridge 2.11.3 → 2.11.21

package/README.md

@@ -74,12 +74,12 @@ This appends the bridge section to your existing `CLAUDE.md` and writes `.claude
 
 ## Slim Mode vs Full Mode
 
-By default, the bridge starts in **slim mode** — 38 IDE-exclusive tools that Claude can't replicate with its built-in `Read`/`Write`/`Bash` tools: LSP intelligence, debugger, editor decorations, diagnostics, refactoring, and editor state. This is the right default for most workflows because Claude already has file editing and shell access built in.
+By default, the bridge starts in **slim mode** — 48 IDE-exclusive tools that Claude can't replicate with its built-in `Read`/`Write`/`Bash` tools: LSP intelligence, debugger, editor decorations, diagnostics, refactoring, impact analysis, and editor state. This is the right default for most workflows because Claude already has file editing and shell access built in.
 
 If you need Claude to use the bridge's **git, terminal, file ops, HTTP client, or GitHub** tools instead of its built-in equivalents, start in full mode:
 
 ```bash
-claude-ide-bridge --watch --full   # all ~95 tools
+claude-ide-bridge --watch --full   # all ~130 tools
 ```
 
 Or set it permanently in your config file (`claude-ide-bridge.config.json`):
@@ -169,7 +169,7 @@ See [docs/multi-ide-review.md](docs/multi-ide-review.md) for the staged review w
 
 | Doc | What it covers |
 |-----|----------------|
-| **[Platform Docs](documents/platform-docs.md)** | Complete tool reference (95+ tools), parameters, examples |
+| **[Platform Docs](documents/platform-docs.md)** | Complete tool reference (130+ tools), parameters, examples |
 | **[Data Reference](documents/data-reference.md)** | Data flows, state management, protocol details |
 | **[Plugin Authoring](documents/plugin-authoring.md)** | Writing custom plugins — manifest schema, entrypoint API |
 | **[Use Cases](documents/use-cases.md)** | Real-world workflows and scenarios |
@@ -278,15 +278,16 @@ claude --plugin-dir ./claude-ide-bridge-plugin
 
 The bridge exposes tools in two modes:
 
-- **Slim mode (default)** — 38 IDE-exclusive tools. Only tools that require a live VS Code extension and have no native Claude equivalent. This is what you get with `claude-ide-bridge --watch`.
-- **Full mode (`--full`)** — all ~95 tools, adding git, terminal, file ops, HTTP, and GitHub. Use this for large projects or workflows that rely on those integrations.
+- **Slim mode (default)** — 48 IDE-exclusive tools. Only tools that require a live VS Code extension and have no native Claude equivalent. This is what you get with `claude-ide-bridge --watch`.
+- **Full mode (`--full`)** — all ~130 tools, adding git, terminal, file ops, HTTP, and GitHub. Use this for large projects or workflows that rely on those integrations.
 
-### Slim mode — 38 IDE tools (default)
+### Slim mode — 48 IDE tools (default)
 
 | Category | Tools |
 |----------|-------|
-| LSP / Code Intelligence | `getDiagnostics` · `watchDiagnostics` · `goToDefinition` · `findReferences` · `getHover` · `getCodeActions` · `applyCodeAction` · `renameSymbol` · `searchWorkspaceSymbols` · `getDocumentSymbols` · `getCallHierarchy` |
-| Refactor & Navigation | `refactorAnalyze` · `refactorPreview` · `refactorExtractFunction` · `renameSymbol` · `prepareRename` · `selectionRanges` · `foldingRanges` · `signatureHelp` · `explainSymbol` · `getImportTree` |
+| LSP / Code Intelligence | `getDiagnostics` · `watchDiagnostics` · `goToDefinition` · `findReferences` · `getHover` · `getCodeActions` · `applyCodeAction` · `renameSymbol` · `searchWorkspaceSymbols` · `getDocumentSymbols` · `getCallHierarchy` · `getSemanticTokens` · `getCodeLens` · `getDocumentLinks` · `batchGetHover` · `batchGoToDefinition` |
+| Impact Analysis | `getChangeImpact` · `getImportedSignatures` |
+| Refactor & Navigation | `refactorAnalyze` · `refactorPreview` · `refactorExtractFunction` · `prepareRename` · `selectionRanges` · `foldingRanges` · `signatureHelp` · `explainSymbol` · `getImportTree` |
 | Editor Decorations | `setEditorDecorations` · `clearEditorDecorations` |
 | Debugger | `startDebugging` · `stopDebugging` · `setDebugBreakpoints` · `evaluateInDebugger` · `getDebugState` |
 | Editor State | `getOpenEditors` · `getCurrentSelection` · `getLatestSelection` · `checkDocumentDirty` · `saveDocument` · `openFile` · `closeTab` · `captureScreenshot` |
@@ -422,6 +423,17 @@ claude-ide-bridge --workspace /path/to/project \
     "prompt": "Review the saved file: {{file}}",
     "cooldownMs": 10000
   },
+  "onFileChanged": {
+    "enabled": true,
+    "patterns": ["**/*.ts"],
+    "prompt": "A file was edited: {{file}}. Run getDiagnostics to check for new errors.",
+    "cooldownMs": 15000
+  },
+  "onCwdChanged": {
+    "enabled": true,
+    "prompt": "Working directory changed to {{cwd}}. Call getBridgeStatus and getOpenEditors to orient.",
+    "cooldownMs": 10000
+  },
   "onPostCompact": {
     "enabled": true,
     "prompt": "Context was compacted. Call getOpenEditors and getDiagnostics to rebuild your understanding of the current state.",
@@ -430,20 +442,29 @@ claude-ide-bridge --workspace /path/to/project \
   "onInstructionsLoaded": {
     "enabled": true,
     "prompt": "Call getToolCapabilities to confirm the bridge is connected and note which tools are available for this session."
+  },
+  "onTestRun": {
+    "enabled": true,
+    "onFailureOnly": true,
+    "prompt": "Tests failed ({{failed}}/{{total}}). Fix the failures:\n{{failures}}",
+    "cooldownMs": 15000
   }
 }
 ```
 
-When automation is active, VS Code save events and diagnostic errors automatically enqueue Claude tasks. Output streams to the "Claude IDE Bridge" output channel in real time.
+When automation is active, VS Code save/change events, diagnostic errors, and Claude Code hook events automatically enqueue Claude tasks. Output streams to the "Claude IDE Bridge" output channel in real time.
 
 **Policy triggers:**
 
 | Trigger | When it fires | Key fields |
 |---------|--------------|------------|
 | `onDiagnosticsError` | VS Code reports new errors/warnings for a file | `enabled`, `minSeverity` (`error`/`warning`), `prompt` (supports `{{file}}` and `{{diagnostics}}`), `cooldownMs` |
-| `onFileSave` | A file matching `patterns` is saved | `enabled`, `patterns` (minimatch globs), `prompt` (supports `{{file}}`), `cooldownMs` |
+| `onFileSave` | A file matching `patterns` is explicitly saved (Ctrl+S) | `enabled`, `patterns` (minimatch globs), `prompt` (supports `{{file}}`), `cooldownMs` |
+| `onFileChanged` | Any buffer edit on a matching file (unsaved changes, external writes) — CC 2.1.83+ | `enabled`, `patterns` (minimatch globs), `prompt` (supports `{{file}}`), `cooldownMs` |
+| `onCwdChanged` | Claude Code's working directory changes — CC 2.1.83+; call via `notifyCwdChanged` tool from a CC `CwdChanged` hook | `enabled`, `prompt` (supports `{{cwd}}`), `cooldownMs` |
 | `onPostCompact` | Claude compacts its context (Claude Code 2.1.76+) | `enabled`, `prompt`, `cooldownMs` |
 | `onInstructionsLoaded` | Claude loads CLAUDE.md at session start (Claude Code 2.1.76+) | `enabled`, `prompt` |
+| `onTestRun` | `runTests` completes | `enabled`, `onFailureOnly` (bool, default `true`), `prompt` (supports `{{runner}}`, `{{failed}}`, `{{passed}}`, `{{total}}`, `{{failures}}`), `cooldownMs` |
 
 > **Cloud sessions**: If `CLAUDE_CODE_REMOTE=true` (Claude Code on the web), automation tasks will still enqueue but the bridge itself runs locally — those tasks will not execute. Guard policy prompts or the `onInstructionsLoaded` hook with an environment check if needed.
 
@@ -638,7 +659,7 @@ bash scripts/gen-claude-desktop-config.sh --write
 
 Then restart Claude Desktop once to load the new config. After that, the bridge's **stdio shim** handles everything automatically — it discovers the running bridge via lock files, buffers requests until connected, and reconnects transparently when the bridge restarts. No port or token needs to be hard-coded, and no further Desktop restarts are needed when the bridge restarts.
 
-> **Tool availability:** Without the VS Code extension connected, ~38 tools (debugger, LSP intelligence, editor state, decorations, refactoring) are unavailable. Claude Desktop works best alongside the running extension. You can verify connectivity by asking *"What tools do you have available?"* — the response will list what's active.
+> **Tool availability:** Without the VS Code extension connected, ~48 tools (debugger, LSP intelligence, editor state, decorations, refactoring) are unavailable. Claude Desktop works best alongside the running extension. You can verify connectivity by asking *"What tools do you have available?"* — the response will list what's active.
 
 > **Debugging the shim:** If the connection seems stuck, the shim logs to stderr. In Claude Desktop, check **Settings → Developer → MCP Logs** to see shim output. Common cause: bridge not running — start it with `claude-ide-bridge --watch` first.
 
@@ -746,7 +767,7 @@ Team Lead (Claude Code)
     └── Teammate C ──► Bridge Session 3 ──► IDE
 ```
 
-All teammates share the same IDE and workspace. Each gets full access to all 95+ bridge tools.
+All teammates share the same IDE and workspace. Each gets full access to all 130+ bridge tools.
 
 ### Setup
 
@@ -897,7 +918,7 @@ claude-ide-bridge \
 
 > The bridge token is entered once during authorization. After that, claude.ai holds a short-lived OAuth access token that it refreshes automatically — you don't need to update the connector URL when the bridge restarts.
 
-> **Tool availability:** All 95+ tools are available in full mode. VS Code extension-dependent tools (LSP, debugger, editor state) require the extension to be connected on the remote machine. Without the extension, ~57 CLI-backed tools still work (file ops, git, terminal, search, HTTP client). In slim mode (default), only the 38 IDE-exclusive tools are exposed.
+> **Tool availability:** All 130+ tools are available in full mode. VS Code extension-dependent tools (LSP, debugger, editor state) require the extension to be connected on the remote machine. Without the extension, ~57 CLI-backed tools still work (file ops, git, terminal, search, HTTP client). In slim mode (default), only the 48 IDE-exclusive tools are exposed.
 
 ### Alternatives
 
@@ -993,7 +1014,7 @@ claude-ide-bridge gen-claude-md [--write] [--workspace <path>]
 --automation-policy <path> Path to JSON automation policy file
 --plugin <path>           Load a plugin directory (repeatable)
 --plugin-watch            Watch plugin directories and hot-reload on change
---full                    Register all ~95 tools (default: slim mode with 38 IDE-exclusive tools)
+--full                    Register all ~130 tools (default: slim mode with 48 IDE-exclusive tools)
 --verbose                 Enable debug logging
 --version, -v             Print version and exit
 --analytics <on|off>      Enable or disable anonymous usage analytics
@@ -1012,8 +1033,8 @@ claude-ide-bridge/
     config.ts         CLI args & config
     claudeDriver.ts   IClaudeDriver interface + SubprocessDriver
     claudeOrchestrator.ts Task queue (MAX_CONCURRENT=10, MAX_QUEUE=20)
-    automation.ts     AutomationHooks — onDiagnosticsError / onFileSave / onPostCompact / onInstructionsLoaded policies
-    tools/            95+ MCP tool implementations
+    automation.ts     AutomationHooks — onDiagnosticsError / onFileSave / onFileChanged / onTestRun / onPostCompact / onInstructionsLoaded policies
+    tools/            130+ MCP tool implementations
   vscode-extension/
     src/extension.ts  VS Code extension
     src/connection.ts WebSocket connection management
@@ -1116,7 +1137,7 @@ npm test             # Run 394 extension tests
 
 ### Claude says a tool doesn't exist or tool count seems low
 
-When the VS Code extension is disconnected, 38 tools that require extension access return an error with reconnect instructions (they remain visible but non-functional). These include LSP, debugger, editor state, and refactoring tools. In slim mode (default), all tools need the extension; in full mode, ~57 CLI-backed tools (git, terminal, file ops, HTTP, GitHub) still work. Check the "Claude IDE Bridge" output channel in VS Code — if you see a disconnection event, use `Claude IDE Bridge: Reconnect` from the command palette, or reload the window.
+When the VS Code extension is disconnected, 48 tools that require extension access return an error with reconnect instructions (they remain visible but non-functional). These include LSP, debugger, editor state, and refactoring tools. In slim mode (default), all tools need the extension; in full mode, ~57 CLI-backed tools (git, terminal, file ops, HTTP, GitHub) still work. Check the "Claude IDE Bridge" output channel in VS Code — if you see a disconnection event, use `Claude IDE Bridge: Reconnect` from the command palette, or reload the window.
 
 ### Bridge and extension version mismatch
 

package/dist/automation.d.ts

@@ -15,6 +15,14 @@ export interface OnFileSavePolicy {
     prompt: string;
     cooldownMs: number;
 }
+export interface OnFileChangedPolicy {
+    enabled: boolean;
+    /** Minimatch glob patterns, e.g. ["**\/*.ts", "!node_modules/**"] */
+    patterns: string[];
+    /** Placeholders: {{file}} */
+    prompt: string;
+    cooldownMs: number;
+}
 export interface OnPostCompactPolicy {
     enabled: boolean;
     /**
@@ -35,13 +43,137 @@ export interface OnInstructionsLoadedPolicy {
      */
     prompt: string;
 }
+export interface OnCwdChangedPolicy {
+    enabled: boolean;
+    /**
+     * Prompt to enqueue when Claude Code's working directory changes (Claude Code 2.1.83+).
+     * Useful for re-initialising workspace context when CC switches projects.
+     * Placeholder: {{cwd}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+export interface OnTestRunPolicy {
+    enabled: boolean;
+    /**
+     * Only trigger when there are test failures or errors.
+     * Set to false to trigger after every test run regardless of outcome.
+     * Default: true.
+     */
+    onFailureOnly: boolean;
+    /**
+     * Prompt to enqueue after a test run.
+     * Placeholders: {{runner}}, {{failed}}, {{passed}}, {{total}}, {{failures}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+/** Minimal test run result passed to handleTestRun — avoids importing TestResult from tool files. */
+export interface TestRunResult {
+    runners: string[];
+    summary: {
+        total: number;
+        passed: number;
+        failed: number;
+        skipped: number;
+        errored: number;
+    };
+    failures: Array<{
+        name: string;
+        file: string;
+        message: string;
+    }>;
+}
+export interface OnGitCommitPolicy {
+    enabled: boolean;
+    /**
+     * Prompt to enqueue after a successful git commit.
+     * Placeholders: {{hash}}, {{branch}}, {{message}}, {{files}}, {{count}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+/** Minimal commit result passed to handleGitCommit — avoids importing from gitWrite. */
+export interface GitCommitResult {
+    hash: string;
+    branch: string;
+    message: string;
+    files: string[];
+    count: number;
+}
+export interface OnGitPushPolicy {
+    enabled: boolean;
+    /**
+     * Prompt to enqueue after a successful git push.
+     * Placeholders: {{remote}}, {{branch}}, {{hash}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+/** Minimal push result passed to handleGitPush — avoids importing from gitWrite. */
+export interface GitPushResult {
+    remote: string;
+    branch: string;
+    hash: string;
+}
+export interface OnBranchCheckoutPolicy {
+    enabled: boolean;
+    /**
+     * Prompt to enqueue after a successful git checkout (branch switch or creation).
+     * Placeholders: {{branch}}, {{previousBranch}}, {{created}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+/** Minimal checkout result passed to handleBranchCheckout — avoids importing from gitWrite. */
+export interface BranchCheckoutResult {
+    branch: string;
+    previousBranch: string | null;
+    created: boolean;
+}
+export interface OnPullRequestPolicy {
+    enabled: boolean;
+    /**
+     * Prompt to enqueue after a GitHub PR is successfully created.
+     * Placeholders: {{url}}, {{number}}, {{title}}, {{branch}}
+     */
+    prompt: string;
+    /** Minimum ms between triggers. Enforced minimum: 5000. */
+    cooldownMs: number;
+}
+/** Minimal PR result passed to handlePullRequest — avoids importing from github/pr. */
+export interface PullRequestResult {
+    url: string;
+    number: number | null;
+    title: string;
+    branch: string;
+}
 export interface AutomationPolicy {
     onDiagnosticsError?: OnDiagnosticsErrorPolicy;
     onFileSave?: OnFileSavePolicy;
+    /** Fired by Claude Code 2.1.83+ FileChanged hook — reacts to any file edit, not just explicit saves. */
+    onFileChanged?: OnFileChangedPolicy;
+    /** Fired by Claude Code 2.1.83+ CwdChanged hook — fires when CC's working directory changes. */
+    onCwdChanged?: OnCwdChangedPolicy;
     /** Fired by Claude Code 2.1.76+ PostCompact hook — re-injects IDE context after compaction. */
     onPostCompact?: OnPostCompactPolicy;
     /** Fired by Claude Code 2.1.76+ InstructionsLoaded hook — injects bridge status at session start. */
     onInstructionsLoaded?: OnInstructionsLoadedPolicy;
+    /** Fired after every runTests call (or only on failures, depending on onFailureOnly). */
+    onTestRun?: OnTestRunPolicy;
+    /** Fired after every successful gitCommit call. */
+    onGitCommit?: OnGitCommitPolicy;
+    /** Fired after every successful gitPush call. */
+    onGitPush?: OnGitPushPolicy;
+    /** Fired after every successful gitCheckout call (branch switch or creation). */
+    onBranchCheckout?: OnBranchCheckoutPolicy;
+    /** Fired after every successful githubCreatePR call. */
+    onPullRequest?: OnPullRequestPolicy;
 }
 export interface Diagnostic {
     message: string;
@@ -64,10 +196,27 @@ export declare class AutomationHooks {
     private activeDiagnosticsTasks;
     /** Active task IDs per file for the file-saved handler. */
     private activeSaveTasks;
+    /** Active task IDs per file for the file-changed handler. */
+    private activeFileChangedTasks;
+    /** Active task ID for the test-run handler (workspace-global). */
+    private activeTestRunTaskId;
+    /** Active task ID for the git-commit handler (workspace-global). */
+    private activeGitCommitTaskId;
+    /** Active task ID for the git-push handler (workspace-global). */
+    private activeGitPushTaskId;
+    /** Active task ID for the branch-checkout handler (workspace-global). */
+    private activeBranchCheckoutTaskId;
+    /** Active task ID for the pull-request handler (workspace-global). */
+    private activePullRequestTaskId;
     constructor(policy: AutomationPolicy, orchestrator: ClaudeOrchestrator, log: (msg: string) => void);
     handleDiagnosticsChanged(file: string, diagnostics: Diagnostic[]): void;
     /** Prune lastTrigger entries older than LAST_TRIGGER_MAX_AGE_MS to prevent unbounded growth. */
     private _pruneLastTrigger;
+    /**
+     * Called when Claude Code fires a CwdChanged hook (Claude Code 2.1.83+).
+     * Fires when CC's working directory changes — useful for re-snapshotting workspace context.
+     */
+    handleCwdChanged(newCwd: string): void;
     /**
      * Called when Claude Code fires a PostCompact hook (Claude Code 2.1.76+).
      * Re-enqueues the configured prompt so Claude can re-snapshot IDE state after losing context.
@@ -79,6 +228,36 @@ export declare class AutomationHooks {
      */
     handleInstructionsLoaded(): void;
     handleFileSaved(_id: string, type: string, file: string): void;
+    /**
+     * Called when the VS Code extension reports a file-changed event (type === "change").
+     * Distinct from handleFileSaved — reacts to any editor buffer change, not just explicit saves.
+     * Useful for triggering tasks on unsaved edits (e.g. lint-as-you-type workflows).
+     */
+    handleFileChanged(_id: string, type: string, file: string): void;
+    /**
+     * Called after every runTests tool invocation completes.
+     * Triggers an automation task when tests fail (or on every run if onFailureOnly is false).
+     */
+    handleTestRun(result: TestRunResult): void;
+    /**
+     * Called after a successful gitCommit tool call.
+     * Fires the onGitCommit automation hook if configured.
+     */
+    handleGitCommit(result: GitCommitResult): void;
+    /**
+     * Called after a successful gitPush tool call.
+     * Fires the onGitPush automation hook if configured.
+     */
+    handleGitPush(result: GitPushResult): void;
+    /**
+     * Called after a successful gitCheckout tool call.
+     * Fires the onBranchCheckout automation hook if configured.
+     */
+    handleBranchCheckout(result: BranchCheckoutResult): void;
+    /**
+     * Fires the onPullRequest automation hook if configured.
+     */
+    handlePullRequest(result: PullRequestResult): void;
     /** Summary of automation policy for getBridgeStatus. */
     getStatus(): {
         onPostCompact: {
@@ -92,5 +271,34 @@ export declare class AutomationHooks {
             enabled: boolean;
             patternCount: number;
         } | null;
+        onFileChanged: {
+            enabled: boolean;
+            patternCount: number;
+        } | null;
+        onCwdChanged: {
+            enabled: boolean;
+            cooldownMs: number;
+        } | null;
+        onTestRun: {
+            enabled: boolean;
+            onFailureOnly: boolean;
+            cooldownMs: number;
+        } | null;
+        onGitCommit: {
+            enabled: boolean;
+            cooldownMs: number;
+        } | null;
+        onGitPush: {
+            enabled: boolean;
+            cooldownMs: number;
+        } | null;
+        onBranchCheckout: {
+            enabled: boolean;
+            cooldownMs: number;
+        } | null;
+        onPullRequest: {
+            enabled: boolean;
+            cooldownMs: number;
+        } | null;
     };
 }