Deebo is an agentic debugging copilot that works alongside your AI coding agent to accelerate debugging by 10x. It introduces "multi-threaded" capabilities to your development workflow by launching automated investigations into software errors, helping you identify and fix issues more efficiently.
You can quickly install Deebo using the npm package manager:
npx deebo-setup@latest
This automated setup will guide you through the installation process.
If you prefer to configure Deebo manually after running the setup, you'll need to create a configuration file at the location specified by your coding agent. The configuration should include both the guide server and the main Deebo server:
{
"servers": {
"deebo-guide": {
"command": "node",
"args": [
"--experimental-specifier-resolution=node",
"--experimental-modules",
"/Users/[your-name]/.deebo/guide-server.js"
],
"env": {},
"transportType": "stdio"
},
"deebo": {
"command": "node",
"args": [
"--experimental-specifier-resolution=node",
"--experimental-modules",
"--max-old-space-size=4096",
"/Users/[your-name]/.deebo/build/index.js"
],
"env": {
"NODE_ENV": "development",
"USE_MEMORY_BANK": "true",
"MOTHER_HOST": "openrouter",
"MOTHER_MODEL": "anthropic/claude-3.5-sonnet",
"SCENARIO_HOST": "openrouter",
"SCENARIO_MODEL": "deepseek/deepseek-chat",
"OPENROUTER_API_KEY": "your-openrouter-api-key"
}
}
}
}
Be sure to replace [your-name] with your actual username and add your OpenRouter API key. Deebo is compatible with OpenAI-compatible SDKs, Anthropic, Gemini, and OpenRouter.
When you encounter a difficult bug, ask your AI agent to delegate the debugging task to Deebo:
Example request to your agent:
This error is happening in /path/to/repo, possibly related to auth logic. I already checked the session token parser. Can you delegate this to Deebo?
Your agent will initiate a Deebo session and provide you with a session ID (e.g., session-1745...). Make note of this ID.
After approximately 30 seconds, ask your agent to check the status of your Deebo session using the session ID. You'll receive a "session pulse" that includes:
If you notice something important or want to guide Deebo's investigation in a specific direction, you can ask your agent to pass an observation to Deebo:
Let Deebo know that the file size warnings might be a red herring — the issue is probably with the CI env vars.
If you've resolved the issue or no longer need the investigation, you can tell your agent to cancel the Deebo session.
When asked to check debug session progress, agents can look in:
~/.deebo/memory-bank/[project-hash]/sessions/[session-id]/logs/
The project hash is a unique identifier for each repository, and session IDs are provided when starting a debug session.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "deebo" '{"autoApprove":[],"disabled":false,"timeout":30,"command":"node","args":["--experimental-specifier-resolution=node","--experimental-modules","--max-old-space-size=4096","/absolute/path/to/deebo/build/index.js"],"env":{"NODE_ENV":"development","USE_MEMORY_BANK":"true","MOTHER_HOST":"openrouter","MOTHER_MODEL":"anthropic/claude-3.5-sonnet","SCENARIO_HOST":"openrouter","SCENARIO_MODEL":"anthropic/claude-3.5-sonnet","OPENROUTER_API_KEY":"sk-or-v1-..."},"transportType":"stdio"}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"deebo": {
"autoApprove": [],
"disabled": false,
"timeout": 30,
"command": "node",
"args": [
"--experimental-specifier-resolution=node",
"--experimental-modules",
"--max-old-space-size=4096",
"/absolute/path/to/deebo/build/index.js"
],
"env": {
"NODE_ENV": "development",
"USE_MEMORY_BANK": "true",
"MOTHER_HOST": "openrouter",
"MOTHER_MODEL": "anthropic/claude-3.5-sonnet",
"SCENARIO_HOST": "openrouter",
"SCENARIO_MODEL": "anthropic/claude-3.5-sonnet",
"OPENROUTER_API_KEY": "sk-or-v1-..."
},
"transportType": "stdio"
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"deebo": {
"autoApprove": [],
"disabled": false,
"timeout": 30,
"command": "node",
"args": [
"--experimental-specifier-resolution=node",
"--experimental-modules",
"--max-old-space-size=4096",
"/absolute/path/to/deebo/build/index.js"
],
"env": {
"NODE_ENV": "development",
"USE_MEMORY_BANK": "true",
"MOTHER_HOST": "openrouter",
"MOTHER_MODEL": "anthropic/claude-3.5-sonnet",
"SCENARIO_HOST": "openrouter",
"SCENARIO_MODEL": "anthropic/claude-3.5-sonnet",
"OPENROUTER_API_KEY": "sk-or-v1-..."
},
"transportType": "stdio"
}
}
}3. Restart Claude Desktop for the changes to take effect