iiRecord
Agentic AI Atlas · GAP-TOOLS-036: Bash Background Execution
page:docs-harness-features-backlog-gaps-tools-capabilities-gap-tools-036a5c.ai
II.
Page reference

page:docs-harness-features-backlog-gaps-tools-capabilities-gap-tools-036

Reading · 2 min

GAP-TOOLS-036: Bash Background Execution reference

Add background execution support and description param to babysitter's bash

Pagewiki/docs/harness-features-backlog/gaps/tools-capabilities/GAP-TOOLS-036.mdOutgoing · 0Incoming · 1

GAP-TOOLS-036: Bash Background Execution

FieldValue
Categorytools-capabilities
PriorityMedium
EffortS
StatusMissing

Description

Add background execution support and description param to babysitter's bash agentic tool to match CC's BashTool feature set.

Current State

Babysitter's bash tool spawns a child process synchronously (waits for completion). Has env and cwd params that CC lacks. Missing run_in_background and description.

CC's BashTool params: command, description (required human-readable task summary), timeout, run_in_background (boolean -- runs command in background, returns task ID, notifies on completion).

Target State

Add to the bash agentic tool:

with a task/effect ID. Completion notification via journal event or callback. The Pi session continues executing while the command runs.

for logging, embedded SDK dashboard display, and permission prompts.

  • **run_in_background**: Boolean. When true, spawn the process and return immediately
  • **description**: String. Human-readable description of what the command does. Used

Background execution requires:

  • Tracking background processes by ID
  • Collecting stdout/stderr asynchronously
  • Delivering completion notification back to the session
  • Cleanup on session termination

Dependencies

  • GAP-TOOLS-030 -- effect cancellation (to cancel background commands)

Key Files

ComponentPath
Agentic toolspackages/sdk/src/harness/agenticTools.ts
CC BashToolsrc/tools/BashTool/BashTool.tsx

Recommendation

Phase 2. Medium priority. Background execution is valuable for long-running builds, tests, and deployments during orchestration. The description param is low-effort and should be added regardless.