OpenClaw’s Plugins workspace received a small but visible navigation fix just hours after the 2026.9.4 release.
PR #144661, titled fix(ui): preserve plugin category navigation while searching, merged on September 11th at 07:59 UTC. The change prevents plugin category chips and saved home shelves from disappearing when a category response lands while the user is starting a search.
This is the kind of bug that feels minor in a diff and annoying in a real interface. Search results still appeared before the fix, but the surrounding navigation could empty out until the overview loaded again. For a plugin catalog, that means users lose the context that helps them browse, narrow, and recover from a query.
What Changed
The issue came from request timing. Typing in the Plugins search box clears the selected category immediately, but the actual query is committed after a 250 ms debounce. The older completion path looked at mutable UI state to decide whether a response represented the overview.
That meant a pending category response could arrive during the debounce window and be treated like something it was not. Because the category response did not contain the full overview data, it could overwrite the saved category and shelf state with empty values.
The fix carries the overview classification with the task result from the captured request arguments. Completion then uses that recorded fact instead of trying to infer it from UI state that may already have moved on.
The PR says the repair adds seven production lines, keeps the request protocol unchanged, and preserves debounce behavior.
User Impact
For users, the result is straightforward: the Plugins page keeps its navigation while search is in motion.
The expected behavior now holds across these cases:
- Previously loaded category chips remain visible while a search starts.
- Saved home shelves stay available instead of being cleared by a stale category response.
- Search results continue to render normally.
- Home loading, filtered reconnects, and pagination keep their existing behavior.
This matters more after OpenClaw 2026.9.4 because plugins are now a larger part of the product surface. The release puts bundled plugins, ClawHub plugins, setup, settings, and access management in one Plugins workspace. A unified catalog is useful only if its navigation remains steady while users browse it.
Validation
The PR includes both controller-level and browser-level proof. The reported test set includes 24 controller and catalog-renderer cases plus 18 Plugins browser cases. The browser reproduction used the mock Gateway to select a category, type a search, resolve the older category request before debounce completion, and then resolve a distinct search result.
Before the fix, the PR reports that all 12 category chips disappeared in that sequence. After the fix, all 15 original navigation labels remained.
The validation also notes screenshot evidence, changed-file checks, and independent review through P2.
Why It Matters
Plugin catalogs are navigation-heavy by nature. Users often begin with categories, switch into search, then go back to browsing when the query is too broad or too narrow. Losing category state during that handoff makes the UI feel unreliable even when the underlying data is fine.
OpenClaw’s fix keeps the catalog predictable without adding a new state machine or changing protocol shape. It captures what the request meant when it was sent, then uses that meaning when the response returns. For a fast-moving Control UI, that is the right kind of repair.