sub-agent-continue

razyone/sub-agent-continue

3.1

If you are the rightful owner of sub-agent-continue and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

Sub Agent Continue MCP is a server that ensures seamless context continuity for sub-agents in Claude Code workflows.

Tools
2
Resources
0
Prompts
0

Sub Agent Continue MCP

npm version License: MIT Node.js Version

An MCP server that provides Claude Code sub-agents with conversation context, solving the "blank slate" problem where sub-agents start with zero knowledge of previous discussions.

⚠️ Important: For Sub-Agents Only

This MCP server provides tools that are only useful for sub-agents. The main Claude Code instance doesn't need these tools since it already has full conversation context.

When these tools are useful:

  • ✅ Sub-agents that need access to conversation history
  • ❌ Main Claude Code instance (it already has full context)

How It Works

Sub-agents pull conversation history from Claude Code logs (.claude/projects/) using two tools:

  • getCurrentConversation: Full conversation context
  • getCurrentConversationUpto: Context up to a specific user message

Key Benefits:

  • Context Inheritance: Sub-agents understand previous discussions and gathered information instantly
  • Cost & Time Savings: No need to re-gather context within sub-agents
  • Clean Context Management: Keep main agent's context window focused

Example Use Cases:

  • After making changes: Create a lint-agent that fixes issues without polluting main context
  • Planning phase: Use getCurrentConversationUpto for a planning-agent that only sees requirements/analysis, then generates execution summaries
  • Side tasks: Any specialized work that would waste valuable main context space

Perfect workflow: Gather information → Create specialized agents that inherit context → Execute focused tasks.

Sample Sub-Agent Creation Prompt

Create a [specialized task] agent.

Use sub-agent-continue MCP server's getCurrentConversation tool to pull our 
full conversation history from Claude Code logs. 
This will give you complete context about what we've 
discussed and accomplished so far.

[Specific task instructions...]

Installation

Requirements

  • Node.js 18 or higher
git clone https://github.com/razyone/sub-agent-continue.git
cd sub-agent-continue
npm install && npm run build

Add to your Claude configuration:

{
  "mcpServers": {
    "sub-agent-continue": {
      "command": "node",
      "args": ["/absolute/path/to/sub-agent-continue/dist/index.js"],
      "transport": "stdio"
    }
  }
}

For detailed configuration instructions, see Installing MCP Servers.

Tools

getCurrentConversation

Get current conversation history (excludes the last user message to avoid sub-agents seeing their trigger).

Parameters:

  • projectPath (optional): Project path, defaults to current directory
  • filterPreset (optional): Filter level - none, light, or heavy (default)

Best for: Sub-agents continuing ongoing work like linting, fixing, refactoring.

getCurrentConversationUpto

Get conversation history up to a specific user message.

Parameters:

  • userMessageIndex (required): User message number (1-indexed)
  • projectPath (optional): Project path, defaults to current directory
  • filterPreset (optional): Filter level - none, light, or heavy (default)

Best for: Development phases (planning, testing, reviewing) or debugging conversation flow.

Filter Presets

  • none - Complete conversation history
  • light - Remove reasoning blocks (<thinking>)
  • heavy (default) - Remove reasoning blocks and sub-agent interactions for cost efficiency

Usage Example

{
  "tool": "getCurrentConversation",
  "parameters": {
    "projectPath": "/path/to/project",
    "filterPreset": "heavy"
  }
}

Development

npm test        # Run tests
npm run lint    # Lint code  
npm run build   # Build for production

License

MIT