From cad057fd64fbf44f953bc2784f70ce344f3389cf Mon Sep 17 00:00:00 2001 From: Peter Stone Date: Sat, 7 Mar 2026 08:30:13 +0000 Subject: agent: lower breakdown threshold to 3min; use claudomator create CLI for subtasks Replaces the API POST instructions with the claudomator create command, which is simpler and consistent with how operators queue tasks. --start is explicitly omitted so subtasks are queued but not auto-started. Co-Authored-By: Claude Sonnet 4.6 --- internal/executor/preamble.go | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'internal/executor') diff --git a/internal/executor/preamble.go b/internal/executor/preamble.go index 8a2cce3..71f8233 100644 --- a/internal/executor/preamble.go +++ b/internal/executor/preamble.go @@ -21,12 +21,12 @@ and noting it in your output. Before doing any implementation work: -1. Estimate: will this task take more than 5 minutes of implementation effort? +1. Estimate: will this task take more than 3 minutes of implementation effort? -2. If YES — break it down: - - Create 3–7 discrete subtasks by POSTing to $CLAUDOMATOR_API_URL/api/tasks - - Each subtask POST body should be JSON with: name, claude.instructions, claude.working_dir (copy from current task), claude.model, claude.allowed_tools, and claude.skip_planning set to true - - Set parent_task_id to $CLAUDOMATOR_TASK_ID in each POST body +2. If YES — break it down into subtasks: + - Create 3–7 discrete subtasks using the claudomator CLI, for example: + claudomator create "Subtask name" --instructions "..." --working-dir "/path" --parent-id "$CLAUDOMATOR_TASK_ID" --server "$CLAUDOMATOR_API_URL" + - Do NOT pass --start. Tasks will be queued and started in order by the operator. - After creating all subtasks, output a brief summary and STOP. Do not implement anything. 3. If NO — proceed with the task instructions below. -- cgit v1.2.3