Open-Source Claude IDE Bridge Connects Dispatch, Desktop App, and Claude Code

How the Claude IDE Bridge Works

The claude-ide-bridge serves as a shared nervous system connecting three components: Dispatch, the Claude desktop app, and Claude Code. Without it, each surface is isolated; with it, they function as one continuous system across different screens.

Practical Workflow Example

Here's a real loop showing how all three pieces work together:

• A user sends a task from their phone via Dispatch: "Start on register and login."
• The Claude desktop app on a Mac receives it and hands it to Claude Code.
• Claude Code reads the API contract and security rules from the repository, writes the routes, and runs tests.
• The bridge enables Claude Code to interact with the actual IDE throughout this process.
• When tests fail, the bridge catches live diagnostics.
• Claude Code fixes the issues and commits the changes.
• Result: Register and login endpoints were written, 8 tests were passing, and the feat/auth-routes commit was ready.
• When opening Windsurf, the bridge highlights new files in amber with live annotations directly in the editor.
• The user updates .claude-plan.md to mark register and login as complete (✓).
• Every surface reading the plan now knows those tasks are done.

Component Breakdown

• Dispatch — Sends tasks from your phone to the desktop app
• Claude desktop app — The persistent session on your Mac that stays in context
• claude-ide-bridge — Gives Claude Code real IDE access: LSP, debugger, terminals, git, GitHub (124 tools total)

Technical Details

The bridge is an open-source MCP (Model Context Protocol) bridge that connects Claude Code to your IDE. It's available under the MIT license at github.com/Oolab-labs/claude-ide-bridge.