$ the-wire · showcase
OpenClaw hands compaction back to Codex, crabs get experimental Wayland
By RepoJournal · Filed · About OpenClaw
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
OpenClaw stops preempting Codex-owned compaction, Crabbox adds an experimental Wayland desktop, and Codex usage-limit messaging grows actionable recovery paths.
Codex compaction now fails at the Codex boundary instead of being treated as an OpenClaw-owned safeguard [1]. OpenClaw previously could preflight-compact Codex reply turns, post-turn compact Codex CLI transcripts, replace Codex app-server compaction via a context-engine plugin, and force plugin compaction around Codex turn/start overflow handling. That is the wrong boundary; Codex owns automatic compaction inside the runtime, and OpenClaw should not predict when a Codex thread needs it. Expect OpenClaw-driven compaction calls against Codex to stop working, with errors surfacing at the boundary.
Codex users running into usage limits get better recovery copy [2]. The no-reset fallback no longer depends on the /codex account; it now shows actionable guidance, while structured reset and retry-time messages appear when Codex provides that data. Blocked-window summaries stay useful even when Codex omits a reset timestamp. Separately, the new ephemeral Control UI Activity tab at /activity derives browser-local entries from the existing session.tool tool-event path, with no new Gateway event family, SSE endpoint, or protocol version [3]. Only sanitized summaries, hidden-argument counts, and redacted or truncated previews enter Activity state; "raw tool arguments and raw results stay out of the Activity model."
Crabbox adds an experimental Wayland desktop environment behind desktop_env=wayland or --desktop-env wayland [4]. Sway plus WayVNC bootstrap for brokered Linux and local-container leases, with desktop.env discovery for screenshots, browser launch, WebVNC reset, terminal, and keyboard helpers. XFCE stays the default, and unsupported Wayland video or proof capture paths now reject with explicit errors.
Test infrastructure gets a routing fix: explicit unit UI Vitest targets now go to the lightweight unit UI config instead of the heavier Control UI startup path, with path classification shared between the runner and Vitest configs [5]. Meanwhile, openclaw/docs received five automated sync commits mirroring upstream doc changes, with no manually authored content [6][7][8][9][10].
Action items
- → Review Codex integration code that relies on OpenClaw preflight or post-turn compaction; it will fail at the boundary now openclaw/openclaw [immediate]
- → Test Codex usage-limit messaging for actionable recovery copy after the fallback change openclaw/openclaw [plan]
- → Try crabbox with --desktop-env wayland if you need upstream Wayland coverage, but expect unsupported video/proof capture paths to error openclaw/crabbox [plan]
- → Monitor the merge of PR 81153 now that commitment serialization added a queue plus file lock openclaw/openclaw [monitor]
References
- [1] Fail Codex compaction at the Codex boundary ↗ openclaw/openclaw
- [2] Fix Codex usage-limit recovery copy ↗ openclaw/openclaw
- [3] Add ephemeral Control UI Activity tab ↗ openclaw/openclaw
- [4] feat: add experimental Wayland desktop env ↗ openclaw/crabbox
- [5] fix: narrow UI vitest target routing ↗ openclaw/openclaw
- [6] chore(sync): mirror docs from openclaw/openclaw@3dd0e8ed6a7cafdd2b4bf46114b417d758409f1b ↗ openclaw/docs
- [7] chore(sync): mirror docs from openclaw/openclaw@dd47e479aedbd3cec2621f44c3750545a1981d79 ↗ openclaw/docs
- [8] chore(sync): mirror docs from openclaw/openclaw@9db04a27eb20609e6b2e2f06a564db8992b0ff9b ↗ openclaw/docs
- [9] chore(sync): mirror docs from openclaw/openclaw@3a72a300745b5d99a0fd840c423813834a2078b4 ↗ openclaw/docs
- [10] chore(sync): mirror docs from openclaw/openclaw@f68ed721b16ce37a18452339c0a34b6b285eb647 ↗ openclaw/docs
