Session goal explicitly requesting opencode-cli/agy-cli subagent delegation was not consistently followed

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 3, 2026

Summary

I set a session goal via /goal that explicitly named delegation to external runtimes
(opencode-cli, opencode-subagent, agy-cli) for mechanical/bulk work, to conserve
Claude token usage on a large backlog-implementation task. During the session, most of
the actual gate-running, diagnosis, and implementation work was performed directly by the
main Claude Code loop and its Agent/Workflow subagents (which run on the same
Claude-tier model), rather than being delegated to the named external runtimes.

Context

  • The /goal command content explicitly listed $opencode-cli, $opencode-subagent,

and $agy-cli skills as available and requested their use to conserve Claude token
consumption: "continue delegando tarefas mecânicas aos opencode e antigravity cli, para
poupar tokens do claude code".

  • Despite this, the session ran typecheck/lint/test/build gates, root-caused and fixed a

real bug (job-application matching score in AVX-31), performed authenticated browser
QA, and orchestrated a 3-phase implementation workflow — all using Claude-tier
Agent/Workflow calls, not the requested external CLI runtimes.

Expected behavior

When a session goal explicitly names an external subagent runtime (opencode, agy, or
similar CLI wrappers) for mechanical/bulk work, that preference should be treated as a
standing instruction for the session and should be checked/applied before each
major task — not just noted once and then defaulted back to Claude-tier execution for
convenience.

Impact

Increased Claude-tier token consumption on a task the user explicitly asked to route
through a cheaper external runtime, working against the stated goal of conserving Claude
Code usage during a long backlog-implementation session.

Suggested improvement

Consider surfacing a reminder/nudge when a /goal or system prompt names a specific
external subagent runtime and the main loop is about to perform bulk mechanical work
itself instead of delegating, similar to existing task-list staleness reminders.

View original on GitHub ↗