0 Releases 91 Tags

RSS Feed

• v2.0.3 47abbb6e3c

  Compare

  v2.0.3: CLI client + human inbox + cost tracking + Boomerang new_task

  indifferentketchup released this 2026-05-25 04:25:18 +00:00 | 60 commits to main since this release

  Phase 7 of v2.0. BooCoder gains a terminal-driven UX and subagent
  isolation primitive.

  CLI (src/cli.ts): standalone entry point for terminal use.

  • boocode run "task" [--agent x] [--model y] — create + stream output
  • boocode ls [--state x] — formatted task table
  • boocode attach — WS stream of running task
  • boocode send "msg" — follow-up message to task session
    Connects to BOOCODER_URL (default http://100.114.205.53:9502).

  Human inbox (routes/inbox.ts): GET /api/inbox (failed/blocked tasks),
  POST /api/inbox/:id/retry (reset to pending for re-dispatch).

  Cost tracking: dispatcher aggregates tokens_used from all messages in
  the task's session after completion, stores in tasks.cost_tokens.
  GET /api/stats/costs?group_by=project|agent|day for aggregation.

  Boomerang subagent isolation (3 new tools):

  • new_task: creates child task with parent_task_id linkage, runs in
    fresh isolated session. Orchestrator sees only output_summary.
  • list_tasks: query child tasks of current parent
  • check_task_status: read task state + output_summary

  The orchestrator pattern: an agent with tools: [new_task, list_tasks,
  check_task_status] can ONLY dispatch — can't read files or MCP. This
  is the Roo Code Boomerang Tasks capability-restriction principle.

  Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)