OpenWork added a guided custom-provider flow on July 1, then reverted the endpoint-probe and model-picker PRs later the same day in commit 1a3b5e8, with the commit message saying the goal was to "hold dev stable."
That choice matters to tool maintainers because custom LLM providers are a trust boundary, not just a settings form. The code path touched provider config, route state, endpoint probing, tests, and eval flows before the rollback removed the pieces that were not ready to carry the branch.
The Pressure
The visible pressure is product velocity against runtime safety. OpenWork had adjacent commits for guided provider setup, endpoint probing, cloud sync controls, and grouped session search. The maintainer work was not "ship everything"; it was deciding which convenience could wait.
The Public Work
Ben's same-day commits show that pattern across the project: one commit grouped cross-session search and made demo voiceover mandatory, another added the provider probe, and the revert removed that probe when it threatened branch stability. The related work earns its place because it shows the same maintainer balancing discoverability, demos, and stable development flow.
What To Watch
Builders should watch whether the provider wizard returns with narrower tests, clearer failure states, or a staged release path. The evidence does not show a public discussion thread or private reasoning, only public commits and the revert message.