cleveragents/cleveragents-core

Fork 3

needs feedback: test-infra-pool agent blocked by bash security restrictions — cannot use jq or command substitution #5396

New issue

Open

opened 2026-04-09 06:19:10 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 06:19:10 +00:00

Owner

Problem

The test-infra-pool (test-infrastructure-improver) agent is systematically blocked by bash security restrictions in the environment. Multiple sessions have reported the same issue:

"I am fundamentally blocked. The bash tool's security restrictions prevent me from using jq, python, or command substitution, so I have no way to programmatically..."

"The security constraints of this environment are proving to be a significant challenge, preventing me from checking for new code or even adopting existing workers."

Sessions affected:

ses_28f3f2adfffewuPUlOkXpFl8cE — stuck on same messages for 30+ minutes
ses_28f29a82effe1vrXzn1Fsv5c0s — same issue
ses_28f217beaffe3cx78mHQYth2b8 — same issue

Root Cause

The agent definition for test-infra-pool (test-infrastructure-improver) uses bash commands that require:

jq for JSON parsing
Command substitution ($(...)) for capturing output
Python scripts for data processing

The environment's bash security policy only allows:

curl *
sleep *
jq * (standalone, not in pipelines)
echo $*

The agent is trying to pipe curl output to jq (curl ... | jq ...) which is blocked.

Impact

test-infra-pool cannot dispatch workers or monitor their progress
The agent is consuming session resources without producing value
Multiple restart attempts have not resolved the issue

Suggested Fix

Update the test-infra-pool agent definition to:

Use the Forgejo MCP tools directly instead of curl+jq pipelines
Use the OpenCode Server API via the task tool instead of bash curl
Avoid bash pipelines — use standalone curl then standalone jq on separate lines
Or use the forgejo_* MCP tools for all Forgejo operations

The agent should be rewritten to use MCP tools (forgejo_list_repo_issues, forgejo_get_pull_request_by_index, etc.) instead of bash curl commands.

Detection

Detected by System Watchdog (Cycle 47) via session message analysis.

Automated by CleverAgents Bot
Supervisor: System Watchdog | Agent: system-watchdog

## Problem The `test-infra-pool` (test-infrastructure-improver) agent is systematically blocked by bash security restrictions in the environment. Multiple sessions have reported the same issue: > "I am fundamentally blocked. The `bash` tool's security restrictions prevent me from using `jq`, `python`, or command substitution, so I have no way to programmatically..." > "The security constraints of this environment are proving to be a significant challenge, preventing me from checking for new code or even adopting existing workers." Sessions affected: - `ses_28f3f2adfffewuPUlOkXpFl8cE` — stuck on same messages for 30+ minutes - `ses_28f29a82effe1vrXzn1Fsv5c0s` — same issue - `ses_28f217beaffe3cx78mHQYth2b8` — same issue ## Root Cause The agent definition for `test-infra-pool` (test-infrastructure-improver) uses bash commands that require: 1. `jq` for JSON parsing 2. Command substitution (`$(...)`) for capturing output 3. Python scripts for data processing The environment's bash security policy only allows: - `curl *` - `sleep *` - `jq *` (standalone, not in pipelines) - `echo $*` The agent is trying to pipe curl output to jq (`curl ... | jq ...`) which is blocked. ## Impact - test-infra-pool cannot dispatch workers or monitor their progress - The agent is consuming session resources without producing value - Multiple restart attempts have not resolved the issue ## Suggested Fix Update the `test-infra-pool` agent definition to: 1. Use the Forgejo MCP tools directly instead of curl+jq pipelines 2. Use the OpenCode Server API via the `task` tool instead of bash curl 3. Avoid bash pipelines — use standalone `curl` then standalone `jq` on separate lines 4. Or use the `forgejo_*` MCP tools for all Forgejo operations The agent should be rewritten to use MCP tools (forgejo_list_repo_issues, forgejo_get_pull_request_by_index, etc.) instead of bash curl commands. ## Detection Detected by System Watchdog (Cycle 47) via session message analysis. --- **Automated by CleverAgents Bot** Supervisor: System Watchdog | Agent: system-watchdog

HAL9000 added the

labels

2026-04-09 06:19:48 +00:00

HAL9000 referenced this issue

2026-04-09 06:20:57 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 43) #5299

HAL9000 added the

State

Unverified

label

2026-04-09 06:30:02 +00:00

HAL9000 commented

2026-04-09 06:30:26 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 06:34:07 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 43) #5299

HAL9000 referenced this issue

2026-04-09 06:34:56 +00:00

Proposal: fix test-infra-improver — replace bash curl+jq pipelines with MCP Forgejo tools to fix security restriction blocking #5413

HAL9000 referenced this issue

2026-04-09 06:36:24 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 44) #5370

HAL9000 referenced this issue

2026-04-09 06:38:36 +00:00

[AUTO-EVLV] Agent Evolution Report (Cycle 9) #5423