Connecting Signal Browser Extension to VS Code

Streamlining Your Debugging Workflow

Signal's VS Code integration allows you to bridge the gap between where a bug happens (the browser) and where you fix it (your editor). By mapping a domain to your local source code, Signal can automatically connect your browser session context directly to VS Code.

Here is the step-by-step process to get everything connected.

1. Install the VS Code Extension

Before connecting the browser to your editor, you need the Signal VS Code extension.

1. Open VS Code.
2. Navigate to the Extensions view (Ctrl+Shift+X or Cmd+Shift+X).
3. Search for "Signal" and click Install.
4. Once installed, the extension will start a local Model Context Protocol (MCP) server that communicates with the browser extension.

2. Create a Workspace in Signal

Workspaces in Signal allow you to group settings, domain mappings, and integrations for specific projects.

1. Open the Signal Chrome Extension popup.
2. Click on the Workspace Builder (or settings/configuration).
3. Create a new workspace for your project and give it a descriptive name.

3. Configure Domain to Local Path Mapping

This is the crucial step. You need to tell Signal which local directory corresponds to the domain you are debugging.

1. In your newly created workspace, navigate to the mapping configuration.
2. Add the URL you are debugging (e.g., localhost:3000 or staging.myapp.com).
3. Set the Local Path to the absolute path of your source code on your machine (e.g., /Users/dev/my-web-app or C:\dev\my-web-app).
4. Save the workspace configuration.

4. Experience Zero-Friction Handoff

With the connection established, you're ready to debug.

1. Navigate to the mapped domain in your browser.
2. Open the Signal extension popup or capture a bug session.
3. You will now see an Open in VS Code button appear.
4. Click it to automatically push the captured bug context directly to your AI agent within VS Code-no copy-pasting required!

By connecting your browser extension directly to your editor, you eliminate the tedious steps of manually moving logs, session state, and context, allowing you to focus immediately on fixing the issue.