- Block REST API endpoints for label creation at the bash level for all agents.
- Restrict `forgejo_create_label` and related MCP tools for all agents.
- Restrict `forgejo_add_issue_labels` to only the `forgejo-label-manager`.
- Ensure all label operations are centralized through the `forgejo-label-manager`.
- Update agent definitions to use the label manager instead of direct API calls or MCP tools for adding labels.
This prevents agents from creating new project-level labels and enforces the use of organization-level labels, resolving the issue of duplicate labels being created.
Add explicit clone isolation protocols and warnings to prevent agents
from manipulating the local repository in /app. This ensures:
- Agents use isolated /tmp/ clones for all source code operations
- No interference between parallel agents
- No disruption to developer's local work environment
- No conflicts from branch changes or file modifications
Updated agents:
- Core implementation agents (implementer, build, plan)
- Quality gate agents (lint-fixer, typecheck-fixer, test-fixer, etc.)
- Test writing agents (behave-tester, unit-test-runner, coverage-improver)
- Analysis agents (difficulty-evaluator, fix-pr)
- Special cases (build-opencode with .opencode/ exception)
Each agent now includes prominent warnings and proper isolation protocols
with detailed explanations of why clone isolation is critical for
system stability.
BREAKING CHANGE: New escalation architecture eliminates duplicate agent code
Key changes:
- Add tier selector agents (tier-haiku, tier-codex, tier-sonnet, tier-opus)
that set the model and invoke worker agents
- Create model-agnostic implementer.md that inherits model from caller
- Update unit-test-runner and typecheck-fixer to support escalation
- Add quality-gate-escalator to manage escalation for quality fixers
- Create subtask-loop-v2.md demonstrating the new architecture
- Document the new architecture in escalation-architecture-proposal.md
Benefits:
- Eliminates 90% code duplication across tier-specific agents
- Single source of truth for implementation logic
- Easy to add new tiers or modify escalation paths
- Consistent behavior across all model tiers
- Quality gate fixers now support full escalation starting from haiku
The architecture leverages the fact that agents without a model specification
inherit the model from their caller, allowing thin tier selectors to control
which model executes the actual work.