Executive Summary

Use Case: Accelerate bug investigation and resolution using Factory.ai's Droid CLI with CoreStory's code intelligence, creating a specialized bug-resolver subagent.

Value Proposition: Custom Droids enable you to encode the complete CoreStory bug resolution workflow as a reusable subagent with strict tooling policies and context isolation.

Factory-Specific Advantage: Droid's custom subagent system allows you to create a dedicated bug-resolver that can be invoked with a single command, maintaining the six-phase workflow consistently across all bug investigations.

Get the custom subagent below:

CoreStory + Factory.ai Custom Bug Resolver Droid

Prerequisites & Setup

Required: CoreStory MCP Server Integration

Factory.ai Droid accesses CoreStory via the Model Context Protocol (MCP). This enables Droid to query your codebase intelligence, project documentation, and conversation history directly.

What you need:

1. CoreStory MCP Token

<aside> 💡

MCP Docs: CoreStory MCP Server Setup & Usage Guide

</aside>

1. CoreStory Project Ingested
   • Codebase ingested into CoreStory
   • Project status: "completed"
   • Note project name/ID
2. Factory.ai Droid with MCP Configured
   • Droid must have CoreStory MCP server connected
   • Configuration allows access to CoreStory tools

Step 1: Configure CoreStory MCP in Factory.ai

Add CoreStory MCP server to Droid:

droid mcp add corestory <https://api.corestory.ai/mcp> --type http \\
  --header "Authorization: Bearer mcp_YOUR_TOKEN_HERE"

Verify connection:

*# Open MCP management UI*
droid
*# Type: /mcp
# Confirm CoreStory appears with available tools
# Or test directly:*
droid exec "List my CoreStory projects"