$ the-wire · showcase
OpenClaw unifies reply bypass logic, Crabbox adds delegated run output and Windows hydration
By RepoJournal · Filed · About OpenClaw
OpenClaw consolidates source-reply acknowledgement handling into one core change, Crabbox gains a delegated run session output flag, and Windows hydration support lands across the stack.
OpenClaw consolidated the `/new`, `/reset`, `/abort` (and friends) acknowledgement-visibility fix into a single core file change in `isExplicitSourceReplyCommand` [1]. This supersedes the per-channel sweep (PR #86863) and ensures every channel, current and future, gets the same behavior without repeating the authorized-control-command formula at each ingress. A packaged plugin runtime resolution failure now includes loader, package-root, candidate-path, plugin id, runtime property, and plugin source context, and was verified by installing published `openclaw@2026.5.20` into a fresh temp npm prefix and upgrading it [2]. Run-scoped `sessions_send` pingbacks now route directly into active targets when possible, falling back to the durable parent session key if transcript-commit steering is rejected, preventing stranded pingbacks on ended runs [3].
Crabbox added `crabbox run --lease-output <file>` as a generic delegated-run session output path, backed by a new core `RunSessionHandle`/`FeatureRunSession` contract and JSON writer, with Blacksmith Testbox as the first producer [4]. Opaque AWS EC2 Query HTTP 400 responses during provisioning are now treated as retryable capacity failures, while coded EC2 XML errors stay on their specific quota/policy/unsupported/fatal paths [5]. Native Windows Crabbox hydration is supported, including `--fresh-pr` checkout, local patch apply with PowerShell-safe git commands, and GitHub Actions runner hydration, cutting the native Windows hydrate job from 17m to 8m [6][7].
Run failure summaries in Crabbox no longer misclassify ordinary command/test output mentioning `provider_auth` as a provider/auth blocker, and now include failure digest context for shell `&&` chains, observed phases, structured JUnit failures, and capped results auto-discovery [8]. Hosted broker defaults were removed [9]. Docs work included preserving Mermaid chart line breaks in fenced code blocks so labels with `<br>` stay valid before client rendering [10] and adding a Cloudflare docs search API [11].
Action items
- → Review use of /new, /reset, /abort behavior across channels to confirm single-bypass logic is correct openclaw/openclaw [plan]
- → Test run-scoped pingback fallback path when upgrading to the fix for #86586 openclaw/openclaw [monitor]
- → Adopt crabbox run --lease-output for automation that needs structured output without parsing logs openclaw/crabbox [immediate]
- → Update AWS provisioning retry handling before next broker deployment to benefit from opaque 400 retries openclaw/crabbox [plan]
References
- [1] fix(reply): derive source-reply explicit-command bypass from authorized + control-command body ↗ openclaw/openclaw
- [2] Fix plugin runtime module resolution diagnostics ↗ openclaw/openclaw
- [3] Fix run-scoped sessions_send pingback fallback ↗ openclaw/openclaw
- [4] feat: add delegated run session output ↗ openclaw/crabbox
- [5] fix(worker): retry opaque AWS RunInstances failures ↗ openclaw/crabbox
- [6] ci: support native Windows Crabbox daemon hydration ↗ openclaw/openclaw
- [7] fix: support native Windows Crabbox hydration ↗ openclaw/crabbox
- [8] [codex] Improve run failure summaries ↗ openclaw/crabbox
- [9] fix: remove hosted broker defaults ↗ openclaw/crabbox
- [10] fix(docs): preserve Mermaid chart line breaks ↗ openclaw/docs
- [11] feat: add Cloudflare docs search API ↗ openclaw/docs
