15 Commits

Author	SHA1	Message	Date
freemo	ce396d2b43	build: reordered agent perms	2026-05-02 14:33:45 -04:00
freemo	bdcc44cb09	build: read and write permissions set seperate edit since read seems to be getting denied as does write	2026-05-01 17:58:29 -04:00
freemo	3a6d42ee79	build: fixed some bad permissions and no longer require prompt to be written to a file for supervisors	2026-05-01 17:45:27 -04:00
freemo	1885990081	build: auto opencode agents rewritten	2026-04-27 12:49:08 -04:00
freemo	435e409df9	build: moved all sonnet agents to haiku	2026-04-18 12:33:27 -04:00
CleverAgents Build Agent	5a57eb9a07	Build: doom loops are detected and killed	2026-04-14 14:50:01 -04:00
CleverAgents Build Agent	acb901abf1	Build: Refined some of the wording in the supervisors to get more reliable performance out of them. Made permissions stricter so we will get less circumvention of intended permissions	2026-04-14 14:15:43 -04:00
CleverAgents Build Agent	38bcd41338	Build: Better protection against agents editing the main working directory	2026-04-13 23:36:46 -04:00
CleverAgents Build Agent	ad069c2012	Build: Fixed forgejo tool permissions in the agents and fixed the label manager so it reliably works with org level labels	2026-04-13 19:45:22 -04:00
clever-agent	5a9aaa79ed	Build: Reinforced label enforcement, and ensure implementation workers dont continue work on a mergable PR.	2026-04-13 13:54:43 -04:00
clever-agent	8692bb46e5	build: Refactored agent definitions to be simpler and less contention	2026-04-12 19:24:50 -04:00
CleverAgents Build Agent	fc9c730670	build: Fixed some model settings	2026-04-09 16:42:44 -04:00
clever-agent	5c584c1cab	feat(agents): Harden label creation restrictions ... - 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.	2026-04-09 16:53:48 +00:00
freemo	db7e044b18	refactor: complete tier selector architecture migration for all agents ... BREAKING CHANGE: Removed all tier-specific agents in favor of model-agnostic versions Key changes: - Create model-agnostic agents: - behave-tester.md (replaces 4 tier-specific versions) - robot-tester.md (replaces 4 tier-specific versions) - coverage-improver.md (replaces coverage-checker with escalation) - Convert existing agents to support escalation: - lint-fixer.md (now model-agnostic) - test-fixer.md (now model-agnostic) - integration-test-runner.md (now model-agnostic) - Update tier selectors to support all new agents - Update quality-gate-escalator to handle all quality fixers - Update subtask-loop to use quality-gate-escalator for all quality gates - Empty redundant tier-specific agents for deletion: - All implementer-{tier}.md files - All behave-tester-{tier}.md files - All robot-tester-{tier}.md files - coverage-checker.md (replaced by coverage-improver.md) Benefits: - Eliminates ~90% code duplication - All agents now support full 4-tier escalation (haiku→codex→sonnet→opus) - Consistent escalation behavior across all agent types - Single source of truth for each agent's logic - Significant cost savings by defaulting to haiku for all quality gates The system now uses tier selectors (tier-haiku, tier-codex, tier-sonnet, tier-opus) that set the model and invoke model-agnostic worker agents, eliminating the need for separate implementations per model tier.	2026-04-06 17:52:33 -04:00
freemo	4aa236b7df	feat: implement tier selector architecture for escalation without redundancy ... 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.	2026-04-06 21:26:20 +00:00