Development record
2026-11-03 — The run builds on the person's subscriptions: the build loop's roles are routed to the host, so each stage runs as a sub-agent of the coordinating session on its subscription, since the claude runner's --bare launch always bills a key; the keys stay a fallback at 95% of a subscription window, per dcn-2611031615094092. The main work moves to the account that always runs the latest build, and a second account keeps the latest release.
decisiondcn-2611031720012399
2026-11-03 — The run builds on the person's subscriptions: the build loop's roles are routed to the host, so each stage runs as a sub-agent of the coordinating session on its subscription, since the claude runner's --bare launch always bills a key; the keys stay a fallback at 95% of a subscription window, per dcn-2611031615094092. The main work moves to the account that always runs the latest build, and a second account keeps the latest release.
Frontmatter
| id | dcn-2611031720012399 |
|---|---|
| type | decision |
| date | 2026-11-03 |
.abcd/work/decisions/dcn-2611031720012399-the-run-builds-on-subscriptions.md
open on GitHub ↗ · commit history ↗
mentions3
- dcn-26110316150940922026-11-03 — The product thinker's rulings for an experiment testing a long autonomous run (given 2026-11-03): during the experiment a release is cut whenever every gate passes, and any refusal waits for the product thinker; each API key has a hard monthly cap and no separate daily limit; sessions use the person's subscriptions first and move to a key when a subscription window reaches 95%, returning once it resets; the run may use the API keys the person has named to it; agents may plan a draft whose open questions each have one defensible answer on the record, and hold every other draft for the person; and the run keeps the person informed through one private daily digest page (what merged, what stalled, spend per key, what waits for them).
- dcn-26110317225120372026-11-03 — The product thinker ruled on 2026-11-03 that drain --drive keeps its walled subscription route, and that watching is no control: a person cannot interrupt a tool call as it runs, so a person's presence never makes an unwalled agent acceptable. So every session that coordinates unattended work starts walled itself (no connectors or MCP servers, no personal memory, abcd's own guard hook kept), and a stage run as a host sub-agent gets only file and shell tools, never the person's connectors, browser or documents; a stage that cannot run within that limit does not run. This refines dcn-2611031720012399's host routing.
- itd-2611040344170206Unattended work runs on a named profile, one per way of paying