[teamleaderleo]

Summary

When an agent needs you while you're in another app, cmux only posts a banner, which is easy to miss. Settings > Notifications now has Bounce Dock Icon (notifications.dockBounce), with three choices: Off, Once (default) and Until You Switch to cmux.

The bounce follows the same rule as the banner and the phone push: a notification that would alert on this Mac, arriving while cmux isn't the active app, bounces the Dock icon. Muted workspaces, quiet hours and banners set to Never don't bounce, and showcase captures post nothing.

• NotificationPolicy.decide sets Decision.bounce alongside the rest of the arrival decision, so it's covered by a table test. NotificationCenterService only calls requestUserAttention: .informationalRequest for Once, .criticalRequest for Until You Switch to cmux.
• To keep CmuxNextApp from growing, the pure NotificationPolicy (and NotificationTrigger) move beside the preferences they read, in CmuxNextSettings, as a struct over the preferences (decide, clears). No behavior change; CmuxNextApp source is 62 lines under the base.
• macOS Focus: the bounce does not read Focus or Do Not Disturb state. A Focus that hides cmux banners still lets the Dock icon bounce; quiet hours and muted workspaces do stop it.
• Agents can't set the key (userOnly).
• The strings are translated into all 21 locales in the settings catalog.

This is the second of the session-settings PRs, after #21730. The two are independent.

Testing

• After review: merged feat-cmux-next, moved NotificationPolicy out of the App, added a quiet-hours case (fd6bfda, exports at c99d0c8). At c99d0c8 these passed on the fleet: DockBouncePolicyTests (8), SettingsSchemaExportTests, ManagedPreferencesManifestTests, FinishedBannerBurstTests, ApprovalBannerTests, ProgramAlertTitleTests, NotificationPreviewTests.

• The fleet export step at fede4fa built the package and its tests and regenerated the settings schema, MDM docs and stamp; the regenerated files are committed here.

• package-test-lane.sh suite at 8ff936b passed: DockBouncePolicyTests (7), SettingsSchemaExportTests, ManagedPreferencesManifestTests, FinishedBannerBurstTests and ApprovalBannerTests.

• Local checks: check-no-godfiles.sh --base, localization_catalog.py check (no findings in this catalog), and defaults_guard.py snapshot/check-fresh. check-concurrency.sh and the namespace lint report only base files (TextWeightProbe, existing singletons).

• Not run: the webviews bun test, and no tagged build, so I haven't watched the bounce itself live.

• Default: notifications.dockBounce = once, approved by the coordinator under Leo's rule for settings defaults ("you pick, we toggle"); it stays a user toggle.

Changelog

Added: The Dock icon bounces when an alert arrives while cmux is in the background (once by default, or until you switch back, or off).

Proof

Settings row and a Dock bounce. No recording yet: there's no tagged build from this Linux box.

🤖 Generated with Claude Code

[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: a064baaf-1877-4898-ab4c-3f6484f6f38c

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

• Autofix · 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]

Receipt for 3508036 (this PR's head; a new push replaces it)

• Visual review: HQ feed card · gallery before/after runs
• Checks: this head
• App of this head (app.zip, kept 1 day): gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr21735 -f ref=feat/next-dock-bounce -f platform=macos -f backend_mode=local

[github-actions]

red: web / Web status; do not merge until green; see lane-rules
red: web / react-apps-check; do not merge until green; see lane-rules
red: web / react-apps-check (1); do not merge until green; see lane-rules

[github-actions]

Unclear: web / react-apps-check (1) failed: no known signature; failed step: Test webviews.

CI failed on 3508036636 (run 39171863558 attempt 1): 2 unknown.
macOS jobs did not run: compile and app tests were skipped: Fast static checks skipped.

Job	Verdict	Why
web / react-apps-check (1)	unknown	no known signature; failed step: Test webviews
web / react-apps-check	unknown	no known signature; failed step: Check webview test shards

Not re-run automatically: web / react-apps-check (1), web / react-apps-check are not machine failures.

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.

[github-actions]

CI fast guards failed on 3508036636 (https://github.com/manaflow-ai/cmux/actions/runs/39171863558). It does not block the merge; a red guard merged into main breaks it for every open PR.
The log named no failed step; see the run.

Agents: python3 scripts/ci/guard_attribution.py fix applies the mechanical fixes locally. This comment is updated in place on each push.

[teamleaderleo]

Bead cx-rylw8 created for this PR by the cmux coordinator.

[blacksmith-sh]

Found 4 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmpd0p2xw0e/summary-missing.json (live):/summary-missing.json (live):	View Logs
/tmp/tmpzv3bfg50/summary-fail.json (live):/summary-fail.json (live):	View Logs
test/narrow-layouts.test.ts/narrow-layouts.test	View Logs
test/narrow-layouts.test.ts/narrow-layouts.test	View Logs

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

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.

[github-actions]

cmux-next tour of 3508036636aa17615dd1ecd1de5cfe3f561f1a5c (run)

The tour job failed before the tour ran (build or setup); the run log has the output.

The tour produced no media.

_{Tours are data in scripts/cmux-next/media/tours: add a step or a tour file to show your feature.}

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3929331184001 (83d36a611f)
• cmux NEXT nightly 1.0.0-nightly.3930148023001 (9d185ebb26)