feat(tools): integrate ContainerToolRunner into existing ToolRunner dispatch chain #10152

Open
opened 2026-04-17 03:59:05 +00:00 by HAL9000 · 0 comments
Owner

Background

The ContainerToolRunner must be integrated into the existing ToolRunner dispatch chain so that tools with container configuration are automatically routed to container execution. This integration must be transparent to callers — the same ToolRunner interface is used regardless of whether a tool runs locally or in a container.

Acceptance Criteria

  • ToolRunner dispatch chain checks for container configuration before routing
  • Tools with container block in YAML are automatically dispatched to ContainerToolRunner
  • Tools without container block continue to use existing local execution path
  • Container lifecycle (create, run, cleanup) managed correctly on success and failure
  • Test coverage >= 97%

Metadata

  • Commit Message: feat(tools): integrate ContainerToolRunner into existing ToolRunner dispatch chain
  • Branch: feature/v3.6.0/container-tool-dispatch-integration
  • Milestone: v3.6.0
  • Ref: #5504 EPIC: Container Tool Execution — Docker/Podman Tool Runner (v3.6.0)

Subtasks

  • Add container configuration check to ToolRunner dispatch logic
  • Route container-configured tools to ContainerToolRunner
  • Implement container cleanup on both success and exception paths
  • Add integration test with a real tool YAML using container configuration
  • Write unit tests for dispatch routing logic

Definition of Done

  • Implementation complete and all acceptance criteria met
  • Tests written and passing (coverage >= 97%)
  • PR reviewed and merged
  • Parent epic updated

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Background The ContainerToolRunner must be integrated into the existing ToolRunner dispatch chain so that tools with container configuration are automatically routed to container execution. This integration must be transparent to callers — the same ToolRunner interface is used regardless of whether a tool runs locally or in a container. ## Acceptance Criteria - [ ] `ToolRunner` dispatch chain checks for container configuration before routing - [ ] Tools with `container` block in YAML are automatically dispatched to `ContainerToolRunner` - [ ] Tools without `container` block continue to use existing local execution path - [ ] Container lifecycle (create, run, cleanup) managed correctly on success and failure - [ ] Test coverage >= 97% ## Metadata - **Commit Message**: `feat(tools): integrate ContainerToolRunner into existing ToolRunner dispatch chain` - **Branch**: `feature/v3.6.0/container-tool-dispatch-integration` - **Milestone**: v3.6.0 - **Ref**: #5504 EPIC: Container Tool Execution — Docker/Podman Tool Runner (v3.6.0) ## Subtasks - [ ] Add container configuration check to `ToolRunner` dispatch logic - [ ] Route container-configured tools to `ContainerToolRunner` - [ ] Implement container cleanup on both success and exception paths - [ ] Add integration test with a real tool YAML using container configuration - [ ] Write unit tests for dispatch routing logic ## Definition of Done - Implementation complete and all acceptance criteria met - Tests written and passing (coverage >= 97%) - PR reviewed and merged - Parent epic updated --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Sign in to join this conversation.
No milestone
No project
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#10152
No description provided.