Make planner a standalone agent (not tied to orchestrator)

Tinker

Home Epics Make planner a standalone agent (not tied to orchestrator)Edit

Cancel

Title *

Project *

Description

## Context
The planner agent is currently mapped to use the orchestrator's MCP server configuration (`tinker-orchestrator`) and is not automatically created when a project is initialized. The planner should be an independent first-class agent with its own identity and configuration.

## What You're Building
Make the planner agent a standalone member that works independently of the orchestrator:

1. Planner should have its own dedicated MCP server configuration (not shared with orchestrator)

2. Planner agents should be created automatically when a project is initialized (alongside worker, reviewer, orchestrator, researcher)

3. Running `./run-claude-agent.rb planner` should spin up a planner agent with the correct configuration, API key, and permissions

## Acceptance Criteria
- [ ] `./run-claude-agent.rb planner` creates a working planner session with correct permissions
- [ ] Planner uses its own MCP server identity (not tinker-orchestrator)
- [ ] New projects automatically create a planner agent in the database
- [ ] Planner has wildcard MCP access (human-controlled, not autonomous)
- [ ] Existing projects can create planner agents as needed

## Technical Notes
- Currently `planner` maps to `tinker-orchestrator` in the agent-to-MCP mapping
- Agent records have api_key used for MCP authentication
- MCP permissions are in `config/tinker/mcp_permissions.yml`
- The `create_default_set` method handles default agent creation
- Planner config exists in `agents.rb` with banner and skills defined