cmux-next sidebar: the footer becomes Back on a destination page

[teamleaderleo]

Summary

While a window shows a full-page destination, the sidebar's footer becomes one wide Back button in the same spot, a universal way back to where you were (Leo's T3 Code reference).

• Before: the footer (account avatar and Settings gear) stayed the same on a destination page. The way back was the title bar's Back, the trail, or picking a workspace again.
• Now: opening a destination (a top page other than Home, such as the App Store) swaps the footer band for a full-width "← Back" button. Clicking it leaves the page for the workspace the window showed. On the workspace the footer's items come back.
• Home keeps the footer: it is where you land, not a destination.
• The destination tiles at the top of the sidebar stay as they are. This only adds the Back affordance.

How it works:

• SidebarModel.showsBack and onBack. The sidebar view lays Back over the footer band's spot (SidebarView+Back).
• The window root reports each content swap (onContentChange). WindowController sets showsBack from the shown top page, so Back follows pages, workspace switches and a restored page alike. Back runs leaveTopPage().

Testing

• SidebarFooterBackTests:
  • the footer shows its items until a destination opens;
  • a destination turns the footer into one wide Back button in the footer's spot, and leaving restores the items;
  • a click runs onBack.
• SidebarFooterBackWiringTests:
  • a destination page shows Back, and Back returns to the workspace the window showed;
  • Home keeps the footer.
• Red at test commit 3320d1a (fleet suite result in a comment). Green comes from this PR's CI swift test.
• check-no-godfiles, check-concurrency, check-crash-safety and check-l10n pass locally.
• Localization: one new string, sidebar.footer.back ("Back"), in all 21 locales, copied from the existing "Back" translations.
• Captures come later: the reserved recording mini isn't named yet.

Changelog

• Added: On a full-page destination, the sidebar footer becomes a Back button that returns to your workspace.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

---

Summary by cubic

Turns the sidebar footer into a wide "← Back" button while a window shows a full-page destination, giving a universal way back to where you were.

• Before, the footer (account avatar and Settings gear) stayed the same on a destination page; now the footer band gives way to a Back button in the same spot.
• Back leaves the page for the workspace the window showed; Home keeps the footer since it's where you land, not a destination.
• The window root reports each content swap, so Back follows pages, workspace switches, and restored pages alike.
• Adds one new localizable string (sidebar.footer.back, "Back") in all 21 locales, and tests cover layout, wiring, Home keeping the footer, and the button staying clean after drawing.

Bug Fixes

• Fixed the Back button redrawing every frame, which hung the test run; styling now happens on init, window moves, and appearance changes instead of in updateLayer.

^{Written for commit 1a93db0. Summary will update on new commits.}

---

Note

Medium Risk
Proxy policy changes affect how remote browser profiles route traffic (including loopback); behavior is tested but still network-isolation sensitive. Removing Cmd-K search chats is a user-visible regression unless another entry point replaces it.

Overview
This PR bundles three unrelated areas: CEF remote-store proxy policy, recent-chat project scoping, and removal of the agent pane’s Cmd-K “Search chats” sheet.

CEF shim: Per-profile Chromium proxy settings (fixed_servers to http://127.0.0.1:<port> with bypass_list <-loopback>) move into a CEF-free context_proxy_policy.h. shim_proxy.mm applies that helper and uses ContextProxyPortValid for port checks. A standalone context_proxy_test.cpp locks the behavior in.

Agent recents: AcpmuxRecentChats.newest gains an optional in project: filter (applied before the limit), plus a projects list derived from chat folders ordered by recent activity—supporting project-scoped recents in the app feed.

Agent pane search: The dedicated search-chats overlay is dropped: showSearchChats() / searchChats bridge command, ~160 lines of .acpmux-search* CSS in index.html, and search.* strings from locale bundles. Native action catalog entries for search chats may still exist elsewhere in the repo.

^{Reviewed by Cursor Bugbot for commit 1a93db0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: manaflow-ai/cmux/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 30695b7e-6cdf-4c8a-92e6-e379193189d9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Not verified: macOS jobs did not run: compile and app tests were skipped on 1a93db017f; ci-status is green without them.

CI passes on 1a93db017f (run 37616023633 attempt 1).
macOS jobs did not run: compile and app tests were skipped: Fast static checks skipped (the macos job needs both to succeed). Re-run CI once they pass, before merging.

Written by scripts/ci/classify_failures.py (ci-failure-attribution.yml); signatures are its SIGNATURES table. A machine verdict is the runner's fault, not this PR's; yours means the failing file is one this PR changes, also red on main that main's latest full suite fails the same way, seen on other PRs that it failed on another pull request's run lately.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3d63ba6. Configure here.}

[cursor]

Back button hover never appears

Low Severity

SidebarBackButton creates a ChromeHover for the chrome hover look, but it never installs tracking areas or forwards mouse entered, exited, or pressed into that hover. The fill stays idle, so the wide Back control has no hover or pressed feedback.

 

^{Reviewed by Cursor Bugbot for commit 3d63ba6. Configure here.}

[teamleaderleo]

Red/green for the swift test hang on dacfb46:

• Red: hosted cmux-next swift test (run 37605227811) never finished: 2110 tests started, exit 143, test helper at 52.3 GB. The hang sample shows the main thread looping in SidebarBackButton.updateLayer() (SidebarView+Back.swift:67). It set the image and title there, which marks the button for display again, so every Core Animation commit drew it again.
• Regression test: 3e8b415 drawingTheBackButtonLeavesItClean (needsDisplay stays false after updateLayer).
• Fix: b952964 styles the button on init, window moves and appearance changes. updateLayer only sets the corner radius.
• Green: hosted PR CI on b952964.

The earlier fleet red step for this PR failed on the since-fixed base compile break in PageWebView+Lifecycle.swift, so it doesn't count as evidence.