Skip to content

fix: mcp auth session UI improvements#3822

Merged
Pratham-Mishra04 merged 1 commit into
devfrom
05-27-fix_mcp_session_ui_fixes
May 28, 2026
Merged

fix: mcp auth session UI improvements#3822
Pratham-Mishra04 merged 1 commit into
devfrom
05-27-fix_mcp_session_ui_fixes

Conversation

@Pratham-Mishra04

Copy link
Copy Markdown
Collaborator

Summary

This PR bumps the bifrost/core and bifrost/plugins/mocker dependency versions in the semantic cache plugin and makes minor UI fixes to the MCP sessions table for label accuracy and badge styling consistency.

Changes

  • Updated bifrost/core from v1.5.12 to v1.5.13 and bifrost/plugins/mocker from v1.5.3 to v1.5.13 in plugins/semanticcache/go.sum
  • Renamed the "MCP Client" column header to "MCP server" to better reflect what is being displayed
  • Replaced the destructive Badge variant for the "Needs update" status with an outlined badge using red border/background styling, distinguishing it visually from hard errors while still signaling user action is required
  • Changed the em dash () used as a placeholder in the access expiry column for header rows to a regular hyphen (-) for consistency with other placeholder values in the table

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

Navigate to the MCP Sessions page and verify:

  • The first column header reads "MCP server"
  • Rows with a "Needs update" status display an outlined red badge rather than a solid destructive badge
  • Header rows in the access expiry column show a plain hyphen

Screenshots/Recordings

Before/after screenshots of the "Needs update" badge and column header rename recommended.

Breaking changes

  • Yes
  • No

Related issues

Security considerations

None.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai

coderabbitai Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@Pratham-Mishra04, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 32 minutes and 33 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6a2c31d3-6e23-49e8-9596-07db2f352655

📥 Commits

Reviewing files that changed from the base of the PR and between d774b61 and f597d4d.

⛔ Files ignored due to path filters (1)
  • plugins/semanticcache/go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • ui/app/workspace/mcp-sessions/views/sessionsTable.tsx
📝 Walkthrough

Walkthrough

SessionsTable receives three localized cosmetic updates: the first column header is relabeled from "MCP Client" to "MCP server", the "needs_update" status badge switches from destructive to outlined red styling, and the access expiry placeholder for header rows changes from em-dash to hyphen for visual consistency.

Changes

Sessions Table Styling Updates

Layer / File(s) Summary
Visual styling updates
ui/app/workspace/mcp-sessions/views/sessionsTable.tsx
Column header relabeled to "MCP server", status badge for needs_update changed to outlined red variant, and expiry placeholder character changed to hyphen for header row consistency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • akshaydeo
  • danpiths

Poem

🐰 A table dressed in finer threads,
Headers now say "server" instead,
Badges gleam with outlined red,
Dashes where em-dashes spread—
Small tweaks make the view less led! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change—UI improvements to MCP auth sessions—and is concise and clear.
Description check ✅ Passed The description includes all major template sections with relevant details about changes, testing steps, and affected areas. Testing instructions are provided and checklist is included.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 05-27-fix_mcp_session_ui_fixes

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

Safe to merge — all changes are cosmetic label and badge styling fixes with a consistent dependency version alignment.

The UI changes are purely visual (column rename, badge styling, placeholder character), following the existing pattern set by the orphaned badge. The go.sum hashes align with the go.mod that already targets v1.5.13 for both bumped dependencies. No logic, data flow, or API contracts are touched.

No files require special attention.

Important Files Changed

Filename Overview
plugins/semanticcache/go.sum Version bump for bifrost/core (v1.5.12→v1.5.13) and bifrost/plugins/mocker (v1.5.3→v1.5.13); go.mod already references v1.5.13 for both, so the hashes are consistent.
ui/app/workspace/mcp-sessions/views/sessionsTable.tsx Column header renamed to "MCP server", needs_update badge switched to outlined red (matching the orphaned badge pattern), and em dash placeholder replaced with a regular hyphen for consistency.

Reviews (4): Last reviewed commit: "fix: mcp session ui fixes" | Re-trigger Greptile

Comment thread ui/app/workspace/mcp-sessions/views/sessionsTable.tsx

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
ui/app/workspace/mcp-sessions/views/sessionsTable.tsx (1)

131-131: 💤 Low value

Terminology mismatch: UI label vs. data model.

The header now displays "MCP server" while the underlying data field is mcp_client (line 173), and code comments throughout refer to "MCP client". This creates a terminology inconsistency between the user-facing label and the implementation.

If "MCP server" is the correct user-facing term (which it appears to be, since the MCP is the server that this system connects to), consider updating code comments and potentially the data model field name in a follow-up to maintain consistency, or document why the data model uses different terminology.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/app/workspace/mcp-sessions/views/sessionsTable.tsx` at line 131, The
TableHead text "MCP server" conflicts with the data field/identifier named
mcp_client and comments referring to "MCP client"; update the code so UI label
and implementation terminology match: either change the header text to "MCP
client" to match the mcp_client field (TableHead) or rename the data field and
related comments from mcp_client to mcp_server across the component
(sessionsTable.tsx) and any column/renderer that uses mcp_client to preserve
consistency; ensure you update any tooltip/comment near TableHead and the data
mapping that reads mcp_client to use the chosen term.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/app/workspace/mcp-sessions/views/sessionsTable.tsx`:
- Around line 285-291: Update the stale comment above the JSX return that
renders the Badge for the "needs_update" state to reflect that it uses an
outlined red variant (className "border-red-500 bg-red-100 ...") rather than the
destructive variant; mention the distinction between needs_update (outlined red,
user action required) and needs_reauth (uses variant="destructive", represents a
hard error) and remove the reference that they have the "same destructive
treatment." Reference the Badge rendering for the "needs_update" case so it's
clear which comment to change.

---

Nitpick comments:
In `@ui/app/workspace/mcp-sessions/views/sessionsTable.tsx`:
- Line 131: The TableHead text "MCP server" conflicts with the data
field/identifier named mcp_client and comments referring to "MCP client"; update
the code so UI label and implementation terminology match: either change the
header text to "MCP client" to match the mcp_client field (TableHead) or rename
the data field and related comments from mcp_client to mcp_server across the
component (sessionsTable.tsx) and any column/renderer that uses mcp_client to
preserve consistency; ensure you update any tooltip/comment near TableHead and
the data mapping that reads mcp_client to use the chosen term.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2ad328df-883f-44ff-bd31-91e5f0c4e530

📥 Commits

Reviewing files that changed from the base of the PR and between 437294d and d774b61.

⛔ Files ignored due to path filters (1)
  • plugins/semanticcache/go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • ui/app/workspace/mcp-sessions/views/sessionsTable.tsx

Comment thread ui/app/workspace/mcp-sessions/views/sessionsTable.tsx Outdated
@Pratham-Mishra04 Pratham-Mishra04 force-pushed the 05-27-fix_mcp_session_ui_fixes branch from d774b61 to b87f181 Compare May 27, 2026 19:36
@Pratham-Mishra04 Pratham-Mishra04 force-pushed the 05-27-fix_mcp_session_ui_fixes branch from b87f181 to 16ac7ee Compare May 27, 2026 19:54
@Pratham-Mishra04 Pratham-Mishra04 force-pushed the 05-27-fix_mcp_session_ui_fixes branch from 16ac7ee to f597d4d Compare May 28, 2026 07:26

Pratham-Mishra04 commented May 28, 2026

Copy link
Copy Markdown
Collaborator Author

Merge activity

  • May 28, 7:29 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • May 28, 7:29 AM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

@Pratham-Mishra04 Pratham-Mishra04 merged commit d154891 into dev May 28, 2026
12 of 14 checks passed
@Pratham-Mishra04 Pratham-Mishra04 deleted the 05-27-fix_mcp_session_ui_fixes branch May 28, 2026 07:29
akshaydeo pushed a commit that referenced this pull request May 29, 2026
This PR bumps the `bifrost/core` and `bifrost/plugins/mocker` dependency versions in the semantic cache plugin and makes minor UI fixes to the MCP sessions table for label accuracy and badge styling consistency.

- Updated `bifrost/core` from `v1.5.12` to `v1.5.13` and `bifrost/plugins/mocker` from `v1.5.3` to `v1.5.13` in `plugins/semanticcache/go.sum`
- Renamed the "MCP Client" column header to "MCP server" to better reflect what is being displayed
- Replaced the destructive `Badge` variant for the "Needs update" status with an outlined badge using red border/background styling, distinguishing it visually from hard errors while still signaling user action is required
- Changed the em dash (`—`) used as a placeholder in the access expiry column for header rows to a regular hyphen (`-`) for consistency with other placeholder values in the table

- [x] Bug fix
- [ ] Feature
- [ ] Refactor
- [ ] Documentation
- [ ] Chore/CI

- [ ] Core (Go)
- [ ] Transports (HTTP)
- [ ] Providers/Integrations
- [x] Plugins
- [x] UI (React)
- [ ] Docs

```sh
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build
```

Navigate to the MCP Sessions page and verify:
- The first column header reads "MCP server"
- Rows with a "Needs update" status display an outlined red badge rather than a solid destructive badge
- Header rows in the access expiry column show a plain hyphen

Before/after screenshots of the "Needs update" badge and column header rename recommended.

- [ ] Yes
- [x] No

None.

- [ ] I read `docs/contributing/README.md` and followed the guidelines
- [ ] I added/updated tests where appropriate
- [ ] I updated documentation where needed
- [ ] I verified builds succeed (Go and UI)
- [ ] I verified the CI pipeline passes locally if applicable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants