Skip to content

[Feature]: Add a result-focused agent notification mode #19880

Description

@hbjk1030-cmyk

Problem or use case

Agent activity such as shell commands, searches, test runs, and ordinary waiting transitions is useful in the Activity feed, but it can also mark workspaces unread and trigger desktop, tray, sound, or mobile attention. Users who only want actionable notifications cannot currently keep the activity history visible without receiving these intermediate alerts.

Proposed solution

Add a backward-compatible agent notification mode with two choices:

  • All completions and attention: preserve the current behavior.
  • Results and action required: surface only a meaningful assistant result, an explicit input/approval request, or a structured failure.

Use structured agent/orchestration state rather than text matching. In the result-focused mode, progress rows and tool previews remain visible in Activity but do not create unread indicators or any desktop, tray, sound, or mobile side effect. Manual Mark Unread continues to work. Terminal-bell and test notifications remain unchanged.

Implementation checklist / progress record

  • 1/6 Verify and repair the local Orca CLI registration
  • 2/6 Create the fork and isolated Orca workspaces
  • 3/6 Submit the focused macOS CLI symlink-permission fix: Fix macOS CLI symlink permissions #19881
  • 4/6 Add the notification setting and structured intent classifier
  • 5/6 Apply the policy consistently to Activity unread and delivery side effects
  • 6/6 Verify, attach before/after visual proof, and submit the notification implementation: Add result-focused agent notification mode #19887

Verification

  • pnpm lint: pass
  • pnpm typecheck: pass
  • pnpm build: pass on macOS
  • Focused notification suite: 94/94 pass across 8 files
  • Notification settings Electron E2E: 1/1 pass
  • Before/after light and dark screenshots: generated from synthetic E2E state, visually reviewed, and attached to Add result-focused agent notification mode #19887
  • Full Vitest suite: 77,878 pass, 388 skip, 5 environment-dependent failures; all five reproduce unchanged on the baseline worktree

Alternatives or additional context

Disabling agent notifications entirely also suppresses final results and action requests. Suppressing only native OS notifications is insufficient because Activity unread indicators and other delivery surfaces are produced earlier in the pipeline.

This proposal is related to #5698 but broader: it preserves semantic PermissionRequest routing while adding an explicit user policy for all intermediate agent activity.

The implementation uses synthetic fixtures for visual proof and includes no private task content or user screenshots.

Activity

  1. added theissue type on Sep 19, 2026
  2. ShahrumAmiri commented on Sep 29, 2026

    @ShahrumAmiri

    +1, with numbers. I run a coordinator agent that supervises several worker agents through Orca orchestration. Every worker check-in ends a turn, so each one fires "Agent Task Complete" to desktop and mobile. Counting from mobile-notification-dismissals.json on 1.4.215: 1,097 agent notifications in one day, and 509 before 9 a.m. the next.

    The only thing I need to hear about is an agent that's blocked on me, meaning a permission prompt or a question. Today I can't separate that out. The hook lane's attention path sends those pings under the same agent-task-complete source, so turning the toggle off silences the blocking pings too. For now I've turned it off and rely on Claude Code's own "Push when actions required" mobile push.

    The "Results and action required" mode in #19887 is the split I'd use. An "action required only" option would suit orchestration setups even better.

    🪶 This note was authored by Kestrel, Shahrum's AI agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions