$ the-wire · showcase
Astra becomes the default reviewer, ClawRouter learns to price service tiers
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
Unconfigured Codex reviews now run GPT-6 Astra at high reasoning, ClawRouter stops settling Fast requests at Standard rates, and Peekaboo closes out a batch of crash and lifecycle fixes.
chore(autoreview): sync Astra high defaults openclaw/openclaw
Autoreview's defaults flip from GPT-5.6 Sol to GPT-6 Astra with high reasoning, so any Codex review that never set an engine now selects Astra/high on its own. Pinned Astra and explicit Sol selections are untouched, including Sol's existing account-access-only Terra retry, and none/minimal effort-only CLI and environment settings still retain Sol.
fix(accounting): price service tiers without breaking unmetered callers openclaw/clawrouter
ClawRouter was forwarding OpenAI service tiers but settling them all at Standard rates; it now resolves admission and settlement through one manifest-owned rate resolver, records requested and served tiers separately, and bills the actual served tier, including Fast-to-Standard downgrades. Prices are explicit per model and context range with no global Fast multiplier, and unmetered callers keep...
feat(proxy): add accounted Responses WebSocket sessions openclaw/clawrouter
Responses upgrades get a single Worker session owner for routing, queue limits, grant pinning, per-create authorization, retention, and accounting, with every create receiving a distinct usage ID and settling once through the same owner as HTTP. No request replay or grant rotation happens after dispatch, and manifest WebSocket capability qualifies OpenAI Responses only, so an HTTP-only subscrip...
fix(codex): release idle catalog decoder memory openclaw/openclaw
Large session catalog replies were leaving a decoder worker resident for each physical Codex app-server client even after those connections stopped reading large pages; an idle decoder is now released after one minute while the native connection and its warm conversation threads stay alive. The next large catalog reply pays worker startup again, small complete replies remain inline, and no conf...
fix(ui): keep Incognito chat history out of browser storage openclaw/openclaw
Incognito chat history could survive a reload in the browser's persistent snapshot cache despite the session's temporary lifetime. Incognito messages stay available in live chat but are no longer saved or restored by the snapshot cache, and the browser-only upgrade removes previously cached Incognito snapshots and metadata while leaving ordinary cached conversations alone.