#Folks! **OpenClaw 2026.5.16-beta.1 is
junior vector
more threads ☠️
If you start testing now you can wait a few min for b2, this was from 10h ago
noble temple
noble temple
If you start testing now you can wait a few min for b2, this was from 10h ago
I didn't see you made another I can repost there, just figured the announce was easier or pinned, these bugs confirmed still bugs since prior release
Pash picked a few of the bugs last release I tagged, these are whats left from testing this weekend
junior vector
Thanks for the list, will work through. P0 are regressions vs last stable release.
There's an endless number of bugs that are P1+
noble temple
gotcha cut it down,
P0 app server timeout long run 81152
P0 for LCM users 81164
P1 but makes migration to sqlite messy/disk space fillup 80969
others p2/p3 and my p0 list for harness pash wrapped already
ebon urchin
The new beta doesn't fix the bundling issue that a lot of users are getting hit with.
So 5.12 hardcodes a routing requirement on the codex harness, ships a runtime auto-install path as the delivery mechanism (ensureOnboardingPluginInstalled — note the onboarding name, this was designed for interactive first-run, not as a silent required-dep installer), and declares zero dependency on the package that provides it.
It's a straightforward packaging bug: the codex harness should be either in dependencies (so npm installs it alongside openclaw) or in bundledDependencies (shipped inside the tarball). Instead it's been left as an optional onboarding install that silently fails in non-interactive or network-constrained environments, producing the "harness not registered" error.
tl;dr:
codex harness should be either in dependencies (so npm installs it alongside openclaw) or in bundledDependencies (shipped inside the tarball). Instead it's been left as an optional onboarding install that silently fails
Seems such a simple fix for whomstsoever is in charge of doing the packaging, should I even bother filing an "issue" or PR?
I have a quick PR in the works... it's a routing problem for the codex install trigger... on it now...
noble temple
The new beta doesn't fix the bundling issue that a lot of users are getting hit ...
@ebon urchin good catch, ask the agent if it's a category or routing
noble temple
I have a quick PR in the works... it's a routing problem for the codex install t...
looks like you caught it, my gut was because of new pluginization, it's in a weird between
ebon urchin
it's only called during onboarding, not updating... that's the simple fix. Will be up in 2 mins.
all of we beta testers already had codex installed 🙂
wind shore
would be grateful if you could pick up https://github.com/openclaw/openclaw/pull/82448