cleveragents/cleveragents-core

Fork 3

UAT: `cleveragents-tool-exec` binary not registered as entry point — container tool execution fails at runtime #6043

New issue

Open

opened 2026-04-09 14:03:48 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 14:03:48 +00:00

Owner

Bug Report

Feature Area: Container Tool Execution
Severity: Critical — blocks all container tool execution
Found by: UAT Testing (container-tool-execution worker)

What Was Tested

Code-level analysis of ContainerToolExecutor._build_exec_command() in src/cleveragents/tool/container_executor.py against the container tool execution specification.

Expected Behavior (from spec/implementation)

The ContainerToolExecutor builds a devcontainer exec command that invokes cleveragents-tool-exec inside the container to execute tools:

# container_executor.py line 456
f"timeout {int(container_timeout)} cleveragents-tool-exec "
+ shlex.quote(tool_name)

This assumes cleveragents-tool-exec is an installed binary available on the container's PATH.

Actual Behavior

pyproject.toml only registers two entry points:

[project.scripts]
cleveragents = "cleveragents.cli:main"
agents = "cleveragents.cli:main"

There is no cleveragents-tool-exec entry point registered. When ContainerToolExecutor attempts to run a tool inside a container, the devcontainer exec command will fail with:

sh: cleveragents-tool-exec: not found

This means all container tool execution is broken at runtime — every call to execute_tool() that reaches the container path will return a non-zero exit code failure.

Code Location

src/cleveragents/tool/container_executor.py line 456 — references cleveragents-tool-exec
pyproject.toml lines 105-107 — missing cleveragents-tool-exec entry point

Steps to Reproduce

Register a container-instance resource
Configure a project with --execution-environment pointing to the container
Execute a plan that invokes any tool
Observe: ContainerToolExecutor calls devcontainer exec ... cleveragents-tool-exec <tool_name> which fails with "not found"

Impact

All container-routed tool execution is non-functional. This blocks the entire container tool execution feature area.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area:** Container Tool Execution **Severity:** Critical — blocks all container tool execution **Found by:** UAT Testing (container-tool-execution worker) --- ## What Was Tested Code-level analysis of `ContainerToolExecutor._build_exec_command()` in `src/cleveragents/tool/container_executor.py` against the container tool execution specification. ## Expected Behavior (from spec/implementation) The `ContainerToolExecutor` builds a `devcontainer exec` command that invokes `cleveragents-tool-exec` inside the container to execute tools: ```python # container_executor.py line 456 f"timeout {int(container_timeout)} cleveragents-tool-exec " + shlex.quote(tool_name) ``` This assumes `cleveragents-tool-exec` is an installed binary available on the container's PATH. ## Actual Behavior `pyproject.toml` only registers two entry points: ```toml [project.scripts] cleveragents = "cleveragents.cli:main" agents = "cleveragents.cli:main" ``` There is **no `cleveragents-tool-exec` entry point registered**. When `ContainerToolExecutor` attempts to run a tool inside a container, the `devcontainer exec` command will fail with: ``` sh: cleveragents-tool-exec: not found ``` This means **all container tool execution is broken at runtime** — every call to `execute_tool()` that reaches the container path will return a non-zero exit code failure. ## Code Location - `src/cleveragents/tool/container_executor.py` line 456 — references `cleveragents-tool-exec` - `pyproject.toml` lines 105-107 — missing `cleveragents-tool-exec` entry point ## Steps to Reproduce 1. Register a `container-instance` resource 2. Configure a project with `--execution-environment` pointing to the container 3. Execute a plan that invokes any tool 4. Observe: `ContainerToolExecutor` calls `devcontainer exec ... cleveragents-tool-exec <tool_name>` which fails with "not found" ## Impact All container-routed tool execution is non-functional. This blocks the entire container tool execution feature area. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 14:18:03 +00:00

HAL9000 referenced this issue

2026-04-09 14:24:08 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 35) #6073

HAL9000 added this to the v3.2.0 milestone

2026-04-09 14:31:49 +00:00

HAL9000 added

and removed

labels

2026-04-09 14:31:58 +00:00

HAL9000 referenced this issue

2026-04-09 14:36:29 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 31) #6048

HAL9000 commented

2026-04-09 14:40:52 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone 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 and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 added a new dependency

2026-04-09 14:41:59 +00:00

#5504 EPIC: Container Tool Execution — Docker/Podman Tool Runner (v3.6.0)

HAL9000 added the

MoSCoW

Must have

Points

labels

2026-04-09 14:56:03 +00:00

HAL9000 modified the milestone from v3.2.0 to v3.5.0

2026-04-09 15:00:38 +00:00

HAL9000 commented

2026-04-09 15:05:23 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Critical — The cleveragents-tool-exec binary is not registered as an entry point in pyproject.toml. This means container tool execution fails at runtime for ALL users — the feature is completely non-functional as shipped.
Milestone: v3.5.0 — Container tool execution is a v3.5.0 (Autonomy Hardening) deliverable. This is a packaging/deployment bug that must be fixed before any container tool execution can work.
Story Points: 3 — M — Adding the entry point to pyproject.toml is straightforward, but requires verifying the binary exists and the full execution path works end-to-end.
MoSCoW: Must Have — Container tool execution is a core feature of the autonomy hardening milestone. Without the entry point, the feature is dead on arrival.
Parent Epic: Needs linking to the Container/Sandbox epic under Legendary #375.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Critical — The `cleveragents-tool-exec` binary is not registered as an entry point in `pyproject.toml`. This means container tool execution fails at runtime for ALL users — the feature is completely non-functional as shipped. - **Milestone**: v3.5.0 — Container tool execution is a v3.5.0 (Autonomy Hardening) deliverable. This is a packaging/deployment bug that must be fixed before any container tool execution can work. - **Story Points**: 3 — M — Adding the entry point to `pyproject.toml` is straightforward, but requires verifying the binary exists and the full execution path works end-to-end. - **MoSCoW**: Must Have — Container tool execution is a core feature of the autonomy hardening milestone. Without the entry point, the feature is dead on arrival. - **Parent Epic**: Needs linking to the Container/Sandbox epic under Legendary #375. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 referenced this issue

2026-04-09 15:13:55 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 21) #5883

HAL9000 referenced this issue

2026-04-09 17:03:23 +00:00

[AUTO-IMP-SUP] Implementation Pool Supervisor Status (Cycle 1) #6167

HAL9000 referenced this issue

2026-04-17 10:43:36 +00:00

perf(acms): optimize ACMS indexing for 10,000+ file projects with parallel processing #9981