- 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.
- Add proper frontmatter to all emptied tier-specific agents
- Mark them as hidden subagents with deprecation notice
- Ensures they cannot be accessed as primary agents
- Completes the tier selector architecture migration
All deprecated agents now have:
mode: subagent
hidden: true
description: "This subagent should only be called manually by the user."
This prevents accidental usage of the deprecated agents while maintaining
the clean tier selector architecture where only 6 primary agents are
accessible to users.