Noted on #1860 during the stack:1635 review, non-blocking, and not fixed there.
What is missing
#1635 lets a permission request outlive its turn. Answering one, or letting it expire, resolves the request and opens a new turn carrying the outcome — that is how the answer reaches an agent whose peer is gone and whose sandbox may be suspended.
That resume turn is a turn like any other. It opens a connection, pays a handshake, runs the agent, and burns credit against SandboxUsage's turn_seconds at CREDIT_TURN_HOUR_CENTS on a platform-paid provider. The expiry sweep opens the same turn, so a request nobody answers also costs one.
Nothing written for a reader says so:
docs/concepts/permissions.md explains the resume turn and that opening it wakes the sandbox, but not that it is billed.- The CHANGELOG entry describes the mechanism without the cost.
docs/concepts/credits.md (and whatever else describes what a turn costs) does not mention this as a way a turn gets opened.
Why it matters
The shape this feature invites is a deterministic operation whose approvals arrive as separate turns — approve the apply, confirm the delegation, sign off the deletes. A run like that opens one resume turn per approval, and the person budgeting it will want that stated rather than inferred. It is also the one cost question the feature raises that the ADR 0014 amendment does not answer: the amendment is careful to say no sandbox is held open, which is true and is about a different cost.
Suggested
A sentence in docs/concepts/permissions.md under "Answering one" and a line wherever the manual lists what opens a billable turn. No behaviour change — the billing is correct, it is only undocumented.
Noted on #1860 during the
stack:1635review, non-blocking, and not fixed there.What is missing
#1635 lets a permission request outlive its turn. Answering one, or letting it expire, resolves the request and opens a new turn carrying the outcome — that is how the answer reaches an agent whose peer is gone and whose sandbox may be suspended.
That resume turn is a turn like any other. It opens a connection, pays a handshake, runs the agent, and burns credit against
SandboxUsage'sturn_secondsatCREDIT_TURN_HOUR_CENTSon a platform-paid provider. The expiry sweep opens the same turn, so a request nobody answers also costs one.Nothing written for a reader says so:
docs/concepts/permissions.mdexplains the resume turn and that opening it wakes the sandbox, but not that it is billed.docs/concepts/credits.md(and whatever else describes what a turn costs) does not mention this as a way a turn gets opened.Why it matters
The shape this feature invites is a deterministic operation whose approvals arrive as separate turns — approve the apply, confirm the delegation, sign off the deletes. A run like that opens one resume turn per approval, and the person budgeting it will want that stated rather than inferred. It is also the one cost question the feature raises that the ADR 0014 amendment does not answer: the amendment is careful to say no sandbox is held open, which is true and is about a different cost.
Suggested
A sentence in
docs/concepts/permissions.mdunder "Answering one" and a line wherever the manual lists what opens a billable turn. No behaviour change — the billing is correct, it is only undocumented.