From the source
When maintaining a project as large as OpenClaw, there are hundreds of possibilities for what our maintainers can choose to work on.
As we’ve shipped update after update, we’ve realized these changes were causing difficulties for users, a hard problem made harder by the impossibly large permutations of user configs.
But when we released 2.0 in early September, the issue of breaking updates became too large to ignore.
Today, Jason Sy, Member of Technical Staff at OpenClaw and a contributor from its earliest days, shares more about the update problem we’ve been grappling with, why it was so hard to fix, his recent work to tackle this challenge, and what the end game is for making updates fully seamless.
The scale of configurations A lot of the feedback was the usual, ‘I updated, it didn’t work,’ and it became a talking point for us during our stand-ups.
Before Jason’s recent fix, there were two possible outcomes when updating your OpenClaw: incremental improvement or catastrophic failure, with no in-between.
In the latter case, not only would your update not work, but the old version of your Claw would be down, so there was no agent around to help out with the fix.
…
