$ the-wire · showcase
Clawrouter withdraws OpenAI subscription onboarding, Fusion fixes leaked adviser accounting
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
The day's most consequential work is corrective: ClawRouter pulled an advertised OAuth path that never had a registered client, Fusion stopped leaking charged reservations on abandoned adviser responses, and OpenClaw's doctor no longer blocks updates over plugins that haven't converged yet.
fix(openai): withdraw unsupported subscription onboarding openclaw/clawrouter
The bundled OpenAI provider advertised "Connect with provider" using a fixed Codex OAuth client and the deployment's own callback URI, sending custom-domain operators into `invalid_authorize_request`. That declaration is gone from both the console and the authorize endpoint; Platform API-key setup and direct Codex subscription login are the supported paths, and the released stored-grant transpo...
fix(fusion): finalize discarded adviser responses openclaw/clawrouter
Fusion skipped HTTP-error adviser bodies and abandoned responses past the adviser deadline, and because proxy accounting settles only when a body is consumed or canceled, those paths left audit events pending and failed-adviser reservations charged until lease expiry; a local workerd reproduction hung and never delivered the usage event. Fusion now cancels every response it won't consume, inclu...
fix(doctor): defer missing-plugin migrations with a warning instead of blocking openclaw/openclaw
Doctor could hit a configured plugin's migrations before its package was available or converged, blocking updates and Gateway startup. It now defers those migrations with an actionable warning, which also keeps legacy inputs available for retry while preventing them from overwriting canonical configuration, session edits, deletions, or ACP closures made during recovery.
fix(acp): stop cancelled turns before provider start openclaw/openclaw
Cancelling an ACP turn now stops already-accepted work before it reaches the provider, including while queued or waiting on runtime setup. The manager owns each accepted turn from admission through settlement, cancels the exact requested turn or accepted snapshot, and joins a runtime handle that appears after cancellation.
fix: release dashboard rejects matching packaged gateway openclaw/openclaw-windows-packaging
Release builds could reject a packaged Control UI with `control ui build rejected` even when the dashboard and Gateway came from the same OpenClaw commit, because the packaging workflow ran `pnpm ui:build` after `pnpm build` despite the pinned build already producing the Control UI, generating a different release identity under `OPENCLAW_CONTROL_UI_RELEASE_BUILD=1`. Shorter work: subagent maint...
Action items
