storeValue cannot name a derived capability, so deploy run handles are unnameable #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The machine-admin system prompt documents this as the way to keep a handle on a deploy run:
That call throws:
storeValueonly accepts references the daemon can name by formula. A runobserver returned from
start()is a derived object, so the documentedpattern cannot work, and the agent loses its handle at the end of the turn.
The recovery the agent found on its own is not documented anywhere:
A later
lookup('endo-run-r-d2dfab0419e7')on a half-written name failed withNo formula exists for number "c3542a21...", which leaves a name in theinventory that cannot be resolved or obviously cleaned up.
Wanted: either a
provideHandle-style way to give a derived cap a durablename, or a prompt/doc fix that points at the workflow-service path and stops
telling agents to call
storeValueon a run.Seen throughout session
mt82q1ns-l8nrge("self-hosted goo").Closing on the second option in Wanted - the prompt fix - delivered in
046bfeb. The machine-admin preset no longer tells agents to callstoreValueon a run; it states that a run observer is derived and has no formula, and points at the workflow service:The underlying gap is unchanged: there is still no
provideHandle-style way to give a derived capability a durable name. Worth a separate issue if that is wanted on its own merits.