Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Title: Workspace header counter labelled "repository" should say "merges" or "branches" [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#56057•Fetched 2026-05-05 05:59:19
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
lucafornarolucafornaro
Participants
lucafornarolucafornaro
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

Root Cause

In our case the workspace is scoped to 3 actual GitHub repositories (configured via MCP), but the counter shows 30 because we've done 30 PR merges across those 3 repos. The list below the chat input ("Unito" entries like polaris-licensing: develop ← claude/<branch>) confirms the counter is tracking merges, not repos.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

In the Claude Code web app, the workspace pinned at the top shows an activity counter labelled N repository / <workspace name> (e.g. "30 repository / XXX YYYY"). The number actually counts merged PRs / branch operations performed in the workspace over time, not distinct repositories.

In our case the workspace is scoped to 3 actual GitHub repositories (configured via MCP), but the counter shows 30 because we've done 30 PR merges across those 3 repos. The list below the chat input ("Unito" entries like polaris-licensing: develop ← claude/<branch>) confirms the counter is tracking merges, not repos.

What Should Happen?

rename the label to N merges, N changesets, or N branch ops. "Repository" is misleading because users assume it counts distinct repos and worry that something is misconfigured.

Error Messages/Logs

Steps to Reproduce

Open Claude Code web app (claude.ai/code) Create / pin a workspace connected to one or more GitHub repositories via MCP (in my case: bitsensech/polaris-licensing, bitsensech/polaris-pwa, bitsensech/field-operations-backend — 3 distinct repos) In one or more Claude sessions, have the agent run mcp__github__create_pull_request + mcp__github__merge_pull_request for N PRs (even all targeting the same repo) Go back to the workspace and look at the header Expected: the "repository" counter reflects the number of distinct repositories linked to the workspace (3 in my case).

Actual: the counter shows the cumulative number of merged PRs (30 in my case, because we've done 30 merges over time). The list under the chat input ("Show N more", with entries like polaris-licensing: develop ← claude/<branch> Unito) confirms the number tracks merges, not repos.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The activity counter label in the Claude Code web app should be renamed to accurately reflect the count of merged PRs or branch operations, rather than implying a count of distinct repositories.

Guidance

  • Verify the current behavior by reproducing the steps provided and observing the counter value.
  • Consider renaming the label to "N merges" or "N changesets" to better reflect the actual count.
  • Review the code responsible for updating the counter to ensure it accurately tracks the desired metric (merged PRs vs. distinct repositories).
  • If the issue is due to a misunderstanding of the counter's purpose, update the documentation or tooltips to clarify its meaning.

Example

No code snippet is provided as the issue does not specify the exact code responsible for the counter update.

Notes

The issue may not be a bug, but rather a misunderstanding of the counter's purpose. Clarifying the label or documentation may be sufficient to resolve the issue.

Recommendation

Apply workaround: Rename the label to "N merges" or "N changesets" to accurately reflect the count, as this is a more straightforward solution than modifying the underlying code or waiting for a potential fix in a future version.

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…
#api#model save/load#optimization#mixed precision#training loop

Still need to ship something?

×6

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

Back to top recommendations

TRENDING