You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A minimal caller that only asks quota should-run and, when true, invokes turn run-once --host codex-cli cannot advance a subsequent hard-lease Todo
without an outside managed-claim step.
On a disposable canonical SQLite Goal, one prepared Todo completed through the
builtin host, independent validation, durable completion, refresh and one debit.
After the owner updated the specification/checks and reopened the next Todo,
the next decision returned should_run=true. Its complete work contract contains:
It supplies an ordinary todo claim and a postcondition to re-read the same
Goal/Agent/Todo until preparation is ready. The builtin Turn plan instead has route.kind=blocked, would_invoke_host=false. Executing the supported builtin
command returns ok=false, LoopX Turn route is not host executable before any
host invocation. A bounded caller reached its 14-call cap with 14 identical
pre-host rejections, zero additional host invocations, no additional debit and
the Goal still active. The caller performed no claim, repair or state edit.
Expected boundary
For this advertised host-executable preparation, either the builtin adapter
should execute the ordinary managed claim under its existing authority and
prove the same-Todo ready postcondition before inference, or the caller-facing
decision should provide a typed wait/action boundary that does not tell a
should-run/run-once caller to retry a non-executable route. Preserve the atomic
claim's ownership, workspace, scope and generation checks; do not auto-take over
another Agent's work or remove lease fencing.
Scope and qualification
Observed on Windows with Codex CLI 0.160.1, Python 3.12, canonical SQLite,
explicit isolated-headless execution and a clean disposable project.
The working first Todo was already prepared during onboarding; this is about
automatic preparation of subsequent Todos, not failure of the claim API.
No ACL, sandbox, journal, check, lease, accounting or installed runtime was
weakened or rewritten to make the loop continue.
Public-safe summary only. Private execution identities, local paths, prompts,
raw logs and credentials are not included.
Related owners: loopx/cli_commands/turn_run_once.py, loopx/control_plane/turn_driver/driver.py, and the existing work_items/execution_preparation.ts projection. The Codex lifecycle preparation
hook has an ordinary-claim bridge, but that does not establish that builtin
isolated-headless run-once consumes it.
Activity