@vtxmacro/cli 2026.8.11 → 2026.8.13

package/README.md

@@ -47,6 +47,15 @@ credential.
 
 ### Automated Codex host
 
+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 advertises `gpt-5.6-sol` with
+`medium`, `high`, and `xhigh` reasoning effort. Before starting a Trader,
+confirm that the VTX AI page shows the intended authenticated ChatGPT email and
+plan. The host reads the live Codex account window: a reached limit pauses new
+dispatch until its reported reset, while a transient throttle uses a short
+bounded cooldown.
+
 ```bash
 vtx inference-host login
 vtx inference-host codex-login
@@ -63,6 +72,21 @@ OAuth grant. It also keeps its ChatGPT subscription login in a dedicated private
 Codex home. Neither credential is copied from or widens the ordinary CLI or Codex
 session. VTX logout/revoke and Codex logout are intentionally separate operations.
 
+Use `vtx inference-host --help` for command discovery. The VTX login verifies
+that the selected credential store can read back the exact saved grant. If an
+OS credential store such as Windows Credential Manager cannot retain it, VTX
+revokes the new remote grant and fails with an actionable error. Retry with the
+supported private-file store by setting
+`VTX_INFERENCE_HOST_CREDENTIAL_STORE=file` before running
+`vtx inference-host login` again. In PowerShell use
+`$env:VTX_INFERENCE_HOST_CREDENTIAL_STORE="file"`; in bash use
+`export VTX_INFERENCE_HOST_CREDENTIAL_STORE=file`.
+
+The browser callback shows a VTX authorization-complete page. If a browser
+extension instead shows `ERR_BLOCKED_BY_CLIENT` but the CLI reports
+`logged_in` and `doctor` reports `credential-present`, only the local
+confirmation page was blocked; the grant succeeded.
+
 ### Any compatible agent harness
 
 Codex, Claude Code, Cursor, GitHub Copilot, Antigravity, and other agents that can
@@ -77,6 +101,7 @@ vtx inference-host agent-connect \
   --model-label "<display label>" \
   --effort <reasoning-effort> \
   --json
+vtx inference-host agent-run
 vtx inference-host agent-next --wait-seconds 50 --json
 ```
 
@@ -99,16 +124,26 @@ Use `not_dispatched` only when no harness inference began,
 `outcome_unknown` when dispatch itself cannot be confirmed. Pipe exactly one
 object to `vtx inference-host agent-fail --json`.
 
-Keep calling `agent-next` while the host should remain available. This same loop
+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 response and Decision candidate;
 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.
 
+After any approved Trader start, use `vtx --profile <profile-id> bots status`
+to confirm the normal Trader remains running. If it returns to Stopped, use
+`vtx --profile <profile-id> runtime events` to read the latest error before one
+controlled retry. A start receipt or a brief Live label is not proof of a
+running bot.
+
 ## Remove
 
-First revoke the VTX inference grant, then uninstall the package. Automated
-Codex users should also remove the dedicated Codex login:
+First stop the foreground run or agent-run process, revoke the VTX inference
+grant, then uninstall the package. Cleanup refuses while a foreground host
+process still owns the host. Automated Codex users should also remove the
+dedicated Codex login:
 
 ```bash
 vtx inference-host revoke
@@ -116,3 +151,7 @@ vtx inference-host revoke
 vtx inference-host codex-logout
 npm uninstall -g @vtxmacro/cli
 ```
+
+If an older failed login left no local credential to revoke, disconnect that
+inactive inference grant from Connected Agent Apps on the VTX Insights page
+before logging in again.