What problem does this solve?

The Control UI renders a desktop top bar whose only content is the OpenClaw › agent › page breadcrumb. Every destination it offers is already covered by the sidebar (navigation, search/command palette, settings), and every page renders its own title header, so the bar spends 44px of vertical space duplicating chrome. On narrow viewports the same bar is real chrome (drawer toggle, brand, search), so only the desktop presentation is redundant.

Separately, the macOS app hosts the Control UI in a WKWebView with no browser chrome: no back/forward buttons, no swipe gestures. Since the UI routes via pushState, in-app history exists but is unreachable — after drilling into a page there is no way back other than re-navigating via the sidebar. The breadcrumb's single "OpenClaw" link also sits mostly under the native window-drag region in the Mac app, so it barely functions there.

Proposed change

• Remove the desktop top bar; the sidebar owns navigation. Keep the narrow-viewport header (drawer toggle, brand, command-palette search). Keep the top bar row only as the chat split-view toolbar's backdrop, which reuses that row on desktop.
• macOS app: add native back/forward buttons in the titlebar next to the traffic lights (enabled state tracking WKWebView history) and enable back/forward swipe gestures.

User impact

More vertical space for content on desktop, one navigation model instead of two, and working history navigation in the macOS app.