2026-11-01 — Which route the agents abcd hands out (the implementer, both reviewers, the intent auditor, the drain judge and the planning interviewer) bill is a per-repository choice between the person's subscription and their API key, and the subscription is the default abcd ships. The subscription route is the person's own claude on their subscription: the host session's agents today, and the walled claude CLI dcn-2611011332308128 describes once that is built. The choice is the person's own per-repository setting, in the git-ignored local layer of the configuration order, never a committed repository file, which is still refused a runner route so a clone can never spend the person's key; the machine layer may set it for every repository. abcd offers and explains the choice rather than leaving the person to hand-write a roles block, and writes it only on their yes, so host delegation stays the written default of AGENTS.md's Boundaries. This keeps dcn-2611011332308128's subscription default and adds the per-repository choice; the terminal drive's own route keeps its subscription default (dcn-2611012105401437). While the subscription's weekly budget is near its limit, this repository's own work runs on the API key. It answers the routing default iss-2611012054262885 asks for; how the subscription route itself is walled stays open in iss-2610230716454430.

Frontmatter

.abcd/work/decisions/dcn-2611012102280663-an-abcd-managed-repository-routes-every.md
open on GitHub ↗ · commit history ↗

mentions5

• dcn-26110113323081282026-11-01 — The product thinker's ruling of 2026-11-01, answering the follow-up dcn-2610230716408975 left open: the drain judge and the build runner take the terminal drive's default, the person's own claude CLI on their subscription behind the same walls, and stay configurable per person among the routes available (an API key, a pinned local model, or a host session). The runner's present --bare route needs an API key and stays the explicit opt-in. Reverse by a ruling that sets a different default for either role.
• dcn-26110121054014372026-11-01 — The terminal drain (itd-2610222215485265) keeps the 2026-10-23 route: a drive runs the person's own claude on their subscription by default, behind the wall dcn-2610230716408975 describes, and on an API key only when their configuration asks for it. The per-repository route choice of dcn-2611012102280663 covers the agents abcd hands out from a build or drain, not the terminal drive's own route, so spc-2610230813348813 stands as planned.
• iss-2610230716454430The build runner (runner.claude) still follows ruling RN2's key-only rule (dcn-2610020000000016): it runs claude with --bare on an API key, and a person with only a subscription runs the role in their own session. On 2026-10-23 the product thinker ruled that a terminal drive runs on the person's subscription by default behind a wall, with an API key optional per configuration (dcn-2610230716408975). The two routes now differ, and the product thinker has not said whether the build runner takes the same default.
• iss-2611012054262885Routing abcd's agent roles to the person's API key takes a hand-written roles block in ~/.abcd.noindex/config.json (roles.<role>.runner: "claude" for the implementer, both reviewers, the intent auditor, the drain judge and the planning interviewer) plus an API key the runner can reach, and nothing in abcd offers, explains or checks either: on 2026-11-01 the person pasted the block as given with no way to tell what it was for, and the key had to be passed by hand on each command from the login keychain. A managed repository's person should be offered the choice between the subscription, the default, and the API key, without editing JSON.
• itd-2611011230226453Agents abcd starts on your API key stay within the budget you set