@vtxmacro/cli 2026.8.48 → 2026.8.50

package/README.md

@@ -64,6 +64,13 @@ and VTX grant. VTX resolves the package-owned pinned Copilot platform runtime
 explicitly and rejects an `auto`-only catalog because it cannot prove the
 effective model.
 
+An explicitly capable Codex model can also control Main in **Agent** mode using
+the same VTX OAuth grant and private Codex login. VTX assigns the running bot but
+does not send a VTX-authored prompt or set the analysis cadence. Codex keeps a
+durable Agent thread, chooses when to wake, requests only the assignment-scoped
+VTX data it needs (or none), and submits the normal structured decision for VTX
+to validate and execute. Review and Screener remain Provider-only.
+
 Before the first Codex login, enable **Device code authorization for Codex** in
 ChatGPT Security settings. Only enter a device code from a login you initiated,
 and never share it. The automated host reads the authenticated Codex model
@@ -124,10 +131,12 @@ The command never kills an arbitrary process, logs either account out, changes
 VTX profile settings, or controls a Trader. If any package-owned VTX automation
 is still live, recovery fails closed and preserves its evidence.
 
-For each VTX profile and lane, **Subscription #1** is tried first and later
-compatible subscriptions follow in the saved Account cascade order.
-Quota/credits exhaustion, unusable authentication, and exhausted recoverable
-provider failures can advance the same logical call. VTX never changes
+For each VTX profile and lane, **Host #1** is tried first and later compatible
+hosts follow in the saved Host cascade order. Distinct computers may use the
+same authenticated subscription; provider quota remains account-level.
+Quota/credits exhaustion can advance only to a later host reporting a different
+account identity. Unusable authentication and exhausted recoverable host failures
+can advance the same logical call. VTX never changes
 provider, model, effort, or response mode, and never cascades a bad request,
 policy rejection, or uncertain dispatch outcome.
 
@@ -212,7 +221,7 @@ specific limitation instead of treating headless support alone as durability.
 Keep `agent-run` open in a separate terminal and keep calling `agent-next`
 while the host should remain available. The independent keeper preserves
 truthful liveness while the harness reasons. This same loop
-supports Main, Review, and Screener; Provider and Decision;
+supports Main, Review, and Screener in Provider mode;
 and normally running VTX Client Mode or Server Mode bots. Server Mode keeps the
 normal VTX call fee. Client Mode has no VTX platform fee. Neither mode falls back
 to another model when the agent host is unavailable.