Cursor Codebase / Origin web UI (cursor.com/codebase)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

On the Code tab, viewing a feature branch still shows a banner that the associated pull request is open, even after that PR has been merged and closed.

In repo jeremy-4/Test, branch cursor/create-main-branch-a65d shows:

PR #2 is open for this branch.

with a Go to Pull Request button.

The same repo’s Pull Requests tab shows Open 0 / Closed 2 and No open pull requests.

The Origin CLI also reports PR #2 as merged (cursor/create-main-branch-a65d → main. The branch page is stale: it treats a merged PR as still open.

Both merged PRs in this repo (#1 and #2) used the same head branch. Related, but not the same UI:

Steps to Reproduce

In Cursor Codebase, create a pull request from a feature branch (here: PR #2 from cursor/create-main-branch-a65d in jeremy-4/Test).
Merge the PR.
Open the repo Code tab and select that still-existing feature branch.
Observe the banner: PR #2 is open for this branch.
Open the Pull Requests tab (is:open author:@me). It correctly shows Open 0, Closed 2, and No open pull requests.

Expected Behavior

The Code tab banner should not say a PR is open after merge/close. It should show merged/closed, or hide the open-PR banner. Branch view, PR list, and PR detail should agree.

Operating System
Web

Version Information
Cursor Codebase / Origin web UI, reproduced 2026-09-12. Repo:

For AI issues: which model did you use?
N/A — Codebase UI status bug.

Does this stop you from using Cursor
No - Cursor works, but with this issue

Operating System

MacOS

Version Information

Web (cursor.com Codebase)

Version Information
Cursor Codebase / Origin web UI, reproduced 2026-09-12. Repo: https://cursor.com/codebase/jeremy-4/Test/tree/main

For AI issues: which model did you use?
N/A — Codebase UI status bug.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

8

Hey @Jeremy_James, thanks for the report, and for the clear steps.

I was able to confirm what you’re seeing. The pull request itself is recorded as merged (which is why the Pull Requests tab and the CLI agree), but the Code tab’s branch banner is showing a cached answer from just before the merge instead of asking again. I’ve flagged this to the team so the banner refreshes properly after a merge or close.

In the meantime, a full page reload on the branch view (Cmd+Shift+R on Mac) will clear it, and it also corrects itself on its own after about five minutes.