From b8e4785f28b4c4d05f1531e103ed45b905efb6d8 Mon Sep 17 00:00:00 2001 From: garrytan Date: Sat, 31 Oct 2026 14:17:59 +0000 Subject: [PATCH] docs/ship-budget.md: GSTACK_SHIP_SUBAGENT=1 stands in for --subagent only Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/ship-budget.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ship-budget.md b/docs/ship-budget.md index 0554a89ee..4ad11533a 100644 --- a/docs/ship-budget.md +++ b/docs/ship-budget.md @@ -77,8 +77,8 @@ one program measure nothing: Capy books a call after its program ends. A jam's own counter includes its own subagents, outside voices too (measured 2026-10-30: +10.92M across a six-reader dispatch with two ~0.35M parent calls between). `"this"` is the root thread, whose counter also holds every sibling tree. A subagent running /ship cannot read its own jam id, so it -reads `"this"` and starts with `--subagent --reading-from this --meter-scope tree` (or -`GSTACK_SHIP_SUBAGENT=1` in its brief): the run is tree-scoped, and every BUDGET, NOTE, BUDGET_FINAL +reads `"this"` and starts with `--subagent --reading-from this --meter-scope tree` (`GSTACK_SHIP_SUBAGENT=1` in its +brief stands in for `--subagent` only; `--reading-from this` is still required): the run is tree-scoped, and every BUDGET, NOTE, BUDGET_FINAL and BUDGET_TIMELINE line it prints is followed by `METER: tree (root counter, upper bound)`. A subagent that asks for `--meter-scope self` while reading `"this"` is refused (`METER_SCOPE_PARENT`). A `--token-cap` on a tree-scoped run stops on that upper bound, so sibling