OpenClaw wizard lands: 106 commits, 12,437 lines added
New Year’s Day, and I was deep in openclaw. This is the public fork of the clawd messaging-agent daemon, the project that would carry my January cadence more than any other. The goal for the morning: get an onboarding wizard in front of a cold-start user so the repo could stop being a power-user-only artifact. Everything that landed today was about lowering the activation threshold for a first-time install.
Signal
106 commits to openclaw in 8 minutes of session time on January 1. The onboarding wizard, Signal provider support, remote CDP browser config, and session switchers all landed in one burst.
Evidence
106 commits, 12,437 additions, 2,420 deletions in openclaw. Wizard coverage: feat: add onboarding wizard, feat: expand onboarding wizard, feat: expand wizard setup flow, test: harden wizard e2e flow, all in sequence. Remote infra extended: add remote gateway client config, add remote CDP browser support. Skills config unified alongside Telegram token resolution fix. 1 session, 8 minutes total, $0.53 cost.
The wizard landed as four discrete commits rather than one large one, which is the shape I prefer. Each feat commit corresponds to a user-facing step that can be stubbed, tested, and rolled back in isolation. The e2e harness commit that closes the sequence is the one that actually earned the release: without it the wizard is just happy-path UI, and the entire point of a first-install flow is that it has to survive edge cases users hit but developers never do.
Remote CDP browser support is the quieter but more important structural move. It means openclaw can drive a Chrome instance that lives off-box, which matters for any deployment where the daemon runs headless but needs a real browser surface. Pairing it with the remote gateway client config in the same session gives the repo a clean split between “daemon here, browser there” and the local all-in-one default.
So What
A single 8-minute session on a holiday produced more structural surface area than most full workdays. The wizard plus remote CDP support means openclaw can now onboard a user and connect to a remote browser in one flow. This is the foundation, not a feature.
Starting the year this way set the tone for the rest of January. The cadence goal was never “ship a feature a day”; it was “leave the repo more installable than I found it.” Day one hit that squarely. The wizard is what you see. The remote CDP path is what holds up when the wizard succeeds and the user tries to do something real. Both shipped together. That matters because otherwise one or the other becomes a nine-month backlog item, and by the time you get back to it the abstraction has rotted.
The $0.53 cost is almost a footnote, but worth naming: an 8-minute session that adds 12K lines of real product for pocket change is the shape of high-leverage work. Most of what matters on day one is knowing what to type, not typing it.
What’s Next
The e2e wizard harness is hardened: does it cover the remote gateway path, or only the local flow? If only local, the next milestone is a matrix test that exercises both paths against a synthetic gateway. Otherwise the first user who hits the remote path from the wizard will be the person who finds out.
Log
- Sessions: 1 across 1 projects, 8m total
- Top projects: openclaw (8m)
- Commits: 106 across 1 repos (12437 +, 2420 -)
- Top repo: openclaw (106 commits)
- Cost: $0.53