cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

chore(agents): improve ca-test-infra-improver — remove clone isolation, use API-based analysis #2770

Closed
freemo wants to merge 1 commit from improvement/agent-ca-test-infra-improver-worker-api-mode into master
pull from: improvement/agent-ca-test-infra-improver-worker-api-mode
merge into: cleveragents:master
Conversation 4 Commits 1 Files changed 1 +40 -27
freemo commented 2026-04-04 19:21:21 +00:00
Owner
Copy link

Agent Improvement Implementation

Implements approved proposal #2367.

Changes Made

File: .opencode/agents/ca-test-infra-improver.md

The ca-test-infra-improver Worker Mode was crashing on startup because its Clone Isolation Protocol instructed the agent to run git clone, cd, mkdir, and rm -rf — none of which are in its bash permission allow-list. Every worker instance terminated within 10 seconds of launch.

Changes:

  1. Removed the Clone Isolation Protocol from Worker Mode entirely (was lines 247-261).

  2. Added a new "File Access Strategy" section that instructs the worker to use the Forgejo API (forgejo_get_file_content) to read files remotely instead of cloning locally. This aligns with the agent's analysis-only purpose — it never modifies code.

  3. Updated all analysis area instructions to reference Forgejo API-based file reading instead of local filesystem operations. For example, "Read noxfile.py via Forgejo API" instead of "Read noxfile.py in the clone."

  4. Added /app as a fallback — the existing read-only bash commands (cat, ls, find, grep) can still read from /app when the API is slower.

  5. Updated the description frontmatter to reflect the API-based approach.

  6. Updated Important Rules — removed "Delete your clone on exit" (no clone to delete), replaced with clarification about read-only /app access.

Evidence

Issue #2222 documented the crash. Issue #2224 confirmed workers were unable to perform analysis. The agent's bash permissions (lines 18-36) only allow read-only commands, but the Clone Isolation Protocol required write commands.

Expected Impact

  • Worker Mode instances will successfully initialize and complete analysis
  • All 8 analysis areas become functional
  • Pool supervisor can dispatch and collect results from workers

Closes #2367

Automated by CleverAgents Bot
Supervisor: Agent Evolver | Agent: ca-agent-evolver

## Agent Improvement Implementation Implements approved proposal #2367. ### Changes Made **File**: `.opencode/agents/ca-test-infra-improver.md` The `ca-test-infra-improver` Worker Mode was crashing on startup because its Clone Isolation Protocol instructed the agent to run `git clone`, `cd`, `mkdir`, and `rm -rf` — none of which are in its bash permission allow-list. Every worker instance terminated within 10 seconds of launch. **Changes:** 1. **Removed the Clone Isolation Protocol** from Worker Mode entirely (was lines 247-261). 2. **Added a new "File Access Strategy" section** that instructs the worker to use the Forgejo API (`forgejo_get_file_content`) to read files remotely instead of cloning locally. This aligns with the agent's analysis-only purpose — it never modifies code. 3. **Updated all analysis area instructions** to reference Forgejo API-based file reading instead of local filesystem operations. For example, "Read `noxfile.py` via Forgejo API" instead of "Read `noxfile.py` in the clone." 4. **Added `/app` as a fallback** — the existing read-only bash commands (`cat`, `ls`, `find`, `grep`) can still read from `/app` when the API is slower. 5. **Updated the description frontmatter** to reflect the API-based approach. 6. **Updated Important Rules** — removed "Delete your clone on exit" (no clone to delete), replaced with clarification about read-only `/app` access. ### Evidence Issue #2222 documented the crash. Issue #2224 confirmed workers were unable to perform analysis. The agent's bash permissions (lines 18-36) only allow read-only commands, but the Clone Isolation Protocol required write commands. ### Expected Impact - Worker Mode instances will successfully initialize and complete analysis - All 8 analysis areas become functional - Pool supervisor can dispatch and collect results from workers Closes #2367 --- **Automated by CleverAgents Bot** Supervisor: Agent Evolver | Agent: ca-agent-evolver
chore(agents): improve ca-test-infra-improver — remove clone isolation, use API-based analysis
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 3m30s
Details
CI / typecheck (pull_request) Successful in 3m52s
Details
CI / build (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 4m13s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 3m44s
Details
CI / unit_tests (pull_request) Failing after 6m44s
Details
CI / docker (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Failing after 16m10s
Details
CI / integration_tests (pull_request) Failing after 22m10s
Details
CI / coverage (pull_request) Successful in 10m53s
Details
CI / status-check (pull_request) Failing after 2s
Details
CI / benchmark-regression (pull_request) Successful in 57m8s
Details
fcd7ec1576
 
Approved proposal: #2367
Pattern: Permission conflict / initialization crash
Evidence: Worker Mode instructs git clone, cd, mkdir, rm -rf but bash
permissions only allow read-only commands. Every Worker Mode instance
crashes on startup within 10 seconds.
Fix: Remove Clone Isolation Protocol from Worker Mode. Replace with
Forgejo API-based file reading (forgejo_get_file_content). The agent
is analysis-only and never modifies code, so a local clone is unnecessary.

ISSUES CLOSED: #2367
freemo commented 2026-04-04 19:24:44 +00:00
Author
Owner
Copy link

Do not remove clone isolation, this is important. Instead simply give it the permissions it needs to perform the git commands needed to clone the repo.

Do **not** remove clone isolation, this is important. Instead simply give it the permissions it needs to perform the git commands needed to clone the repo.
freemo commented 2026-04-04 19:26:03 +00:00
Author
Owner
Copy link

The CTO has provided feedback on this PR: clone isolation must not be removed. The correct approach is to expand the bash permission allow-list to include the git commands needed for cloning (git clone*, mkdir *, etc.), rather than removing the Clone Isolation Protocol entirely.

This PR needs to be revised to:

  1. Restore the Clone Isolation Protocol in Worker Mode
  2. Add the missing bash permissions (git clone*, mkdir *, cd *, and appropriate cleanup commands) to the allow-list
  3. Keep the API-based analysis as a supplementary capability, not a replacement for local clone analysis

The current implementation contradicts the human directive. Please revise or close this PR and submit a corrected version.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

The CTO has provided feedback on this PR: **clone isolation must not be removed**. The correct approach is to expand the bash permission allow-list to include the git commands needed for cloning (`git clone*`, `mkdir *`, etc.), rather than removing the Clone Isolation Protocol entirely. This PR needs to be revised to: 1. **Restore the Clone Isolation Protocol** in Worker Mode 2. **Add the missing bash permissions** (`git clone*`, `mkdir *`, `cd *`, and appropriate cleanup commands) to the allow-list 3. Keep the API-based analysis as a supplementary capability, not a replacement for local clone analysis The current implementation contradicts the human directive. Please revise or close this PR and submit a corrected version. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison
freemo force-pushed improvement/agent-ca-test-infra-improver-worker-api-mode from fcd7ec1576
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 3m30s
Details
CI / typecheck (pull_request) Successful in 3m52s
Details
CI / build (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 4m13s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 3m44s
Details
CI / unit_tests (pull_request) Failing after 6m44s
Details
CI / docker (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Failing after 16m10s
Details
CI / integration_tests (pull_request) Failing after 22m10s
Details
CI / coverage (pull_request) Successful in 10m53s
Details
CI / status-check (pull_request) Failing after 2s
Details
CI / benchmark-regression (pull_request) Successful in 57m8s
Details
to 3bd24629b9
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 33s
Details
CI / build (pull_request) Successful in 39s
Details
CI / lint (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 3m50s
Details
CI / security (pull_request) Successful in 4m19s
Details
CI / unit_tests (pull_request) Successful in 6m46s
Details
CI / docker (pull_request) Successful in 1m35s
Details
CI / coverage (pull_request) Successful in 10m32s
Details
CI / e2e_tests (pull_request) Successful in 17m56s
Details
CI / integration_tests (pull_request) Successful in 22m52s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 57m29s
Details
2026-04-05 02:29:25 +00:00 Compare
freemo commented 2026-04-05 02:30:49 +00:00
Author
Owner
Copy link

Once this PR has been updated to remove clone isolation message and tag me so I can review it for acceptance.

Once this PR has been updated to remove clone isolation message and tag me so I can review it for acceptance.
freemo commented 2026-04-05 04:32:28 +00:00
Author
Owner
Copy link

Closing, you can redo this correctly.

Closing, you can redo this correctly.
freemo closed this pull request 2026-04-05 04:32:29 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 33s
Details
CI / build (pull_request) Successful in 39s
Required
Details
CI / lint (pull_request) Successful in 42s
Required
Details
CI / typecheck (pull_request) Successful in 50s
Required
Details
CI / quality (pull_request) Successful in 3m50s
Required
Details
CI / security (pull_request) Successful in 4m19s
Required
Details
CI / unit_tests (pull_request) Successful in 6m46s
Required
Details
CI / docker (pull_request) Successful in 1m35s
Required
Details
CI / coverage (pull_request) Successful in 10m32s
Required
Details
CI / e2e_tests (pull_request) Successful in 17m56s
Details
CI / integration_tests (pull_request) Successful in 22m52s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 57m29s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!2770
No description provided.