Agent Escalation: Create Tickets for MCP/Workflow Issues

Tinker

Home Epics Agent Escalation: Create Tickets for MCP/Workflow IssuesEdit

Cancel

Title *

Project *

Description

## Problem

Agents encounter issues but don't have a clear path to escalate them:
- Tinker MCP tools don't work as expected
- Workflow restrictions don't make sense for a task
- API responses are too large (token limits)
- Tools are missing or misconfigured
- Permissions block necessary actions

Currently, agents either:
- Give up and fail the task
- Work around it silently
- Leave comments that get ignored

## Solution

Add escalation workflow to all agent banners:

### When to Escalate

Agents should create a ticket when:

1. **MCP Tool Issues**
   - Tool is missing from mcp-bridge but exists in mcp_controller
   - Tool has wrong parameters or schema
   - Tool returns errors that block work
   - Permission denied for a necessary tool

2. **Workflow Problems**
   - Role restriction prevents completing assigned task
   - Need to do something outside defined boundaries
   - Workflow step is unclear or contradictory
   - Ticket requirements are impossible as stated

3. **Token/Response Size**
   - API response > 10k tokens (excessive)
   - Tool returns massive data that should be paginated
   - Context window flooded by single response

### How to Escalate

Add to agent banners:

```markdown
## ESCALATION

If you encounter problems that block your work:

1. **Create a ticket** using `create_ticket()`
2. **Title format**: "Escalation: [brief description]"
3. **Priority**: high or critical
4. **Include context**:
   - What you were trying to do
   - What went wrong (error, missing tool, etc.)
   - Ticket ID if related to existing work
   - Suggested fix if you have one

Examples:
- "Escalation: search_memory tool not in mcp-bridge"
- "Escalation: Cannot create PR - worker role blocked from git operations"
- "Escalation: get_ticket returns 50k tokens, need pagination"
```

### Acceptance Criteria

1. All agent banners include escalation section
2. Clear examples of when to create tickets
3. Title format and priority guidance
4. Agents test escalation workflow (create actual tickets when issues found)