claude-code - 💡(How to fix) Fix Inbox notification count (● Nmsg) should be per-project, not global [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56412Fetched 2026-05-06 06:28:45
View on GitHub
Comments
2
Participants
1
Timeline
6
Reactions
0
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Problem

The status bar shows ● 4msg (inbox notification count) globally across all projects. When switching between different project directories, the same notification count persists — messages from unrelated projects clutter the current workspace.

Expected behavior

The inbox notification count should be scoped to the current project directory, similar to how .claude/settings.json and other project-level config are already per-directory.

Why it matters

When working on multiple projects, global notifications are noise. Users can't tell which messages are relevant to their current context. This defeats the purpose of having per-project workspaces.

Suggested fix

Scope inbox messages by project root (the directory containing .claude/), and only show the count for the active project in the status bar.

extent analysis

TL;DR

Scope inbox messages by project root to display only relevant notification counts in the status bar.

Guidance

  • Identify the project root directory containing .claude/ for each project to determine the scope of inbox messages.
  • Modify the notification system to filter messages based on the active project directory.
  • Update the status bar to display only the notification count for the active project.
  • Consider storing project-specific notification settings in a file like .claude/settings.json to maintain per-project configuration.

Example

No code snippet is provided as the issue does not contain specific implementation details.

Notes

The suggested fix assumes that the project root directory can be reliably determined and that the notification system can be modified to filter messages based on the project scope.

Recommendation

Apply workaround: Modify the notification system to scope inbox messages by project root, as this directly addresses the issue of global notifications cluttering the workspace.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The inbox notification count should be scoped to the current project directory, similar to how .claude/settings.json and other project-level config are already per-directory.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING