Repository navigation
feat: allow session-only inherited MCP exclusions - #4761
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the
Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 Summary
Merge Risk:
|
|
Claude encountered an error after 0s —— View job I'll analyze this and get back to you. |
6faaa61 to
fe08307
Compare
69be161 to
9d5a525
Compare
fe08307 to
f3be6a5
Compare
9d5a525 to
77a3e83
Compare
f3be6a5 to
7604e81
Compare
77a3e83 to
fd8bb59
Compare
e14cef8 to
33d0c75
Compare
fd8bb59 to
359158d
Compare
[Medium impact] The PR changes MCP configuration for individual sessions and adds a bounded server-assignment path. The PR appears safe to merge, with a non-blocking recovery issue where application Retry clears rejected checkbox edits. Findings
|
8a71af4 to
c8ea290
Compare
ScreenshotsRecovery after a rejected save, captured from b1d7055 on isolated synthetic test data. Reload choices restores the accepted revision before application retry becomes available. |
|
@coderabbitai review |
fe1e2b0 to
d7b7dc4
Compare
|
Rebased onto current main Validation: 73 frontend cases, typecheck, translations, five affected backend race packages, two desktop and two phone MCP journeys, harness/spec checks and normal hooks pass. Seven focused smoke cases and translations pass again at the final commit. No feature or fixture logic changed in this rebase. The previous head's complete 118-report audit contains 4,444 passing attempts, 40 skips and zero retries/errors. Its final E2E aggregation job was still queued when this conflict-resolution push superseded it; those results are historical. Fresh CI is required for the new head. @coderabbitai review |
✅ Action performed
|
|
@coderabbitai review Please review 83c1ff0. It refreshes stale Settings workspace snapshots and corrects two browser fixtures. Focused tests and normal hooks passed; fresh CI is running. |
✅ Action performed
|
|
@coderabbitai review Please review 289c244. Two test-only corrections wait for the runtime update request after touch approval and target the declared Threads question scroll owner. Controlled reproductions failed before and passed after each fix; the probes were removed. Normal hooks and focused browser cases passed. |
✅ Action performed
|
There was a problem hiding this comment.
🔇 Additional comments: 1
docs/plans/session-mcp-exclusions/plan.md-1086-1086: 1
1086-1086:Minor · Maintainability & Code Quality · Quick win
⚠️ Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.Replace the unclear compound phrase.
request-admission delayis flagged as a spelling error and is unclear. Usedelay before request admissionor another established term.Source: Linters/SAST tools

Review info
-
Run configuration-
- Source mode: Auto
- Repository: Unavailable
- Branch: Unavailable
- File: No configuration file from this repository applied
- Commit: Unavailable
- Layers: Organization UI
- Review profile: QUIET
- Plan: Advanced
- Run ID:
836df24a-871d-437f-8e61-656e8aaeb1a2
Files selected for processing: 3-
apps/web/e2e/tests/settings/mobile-agent-runtime-update.spec.tsapps/web/e2e/tests/task/threads-clarification-helpers.tsdocs/plans/session-mcp-exclusions/plan.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.
-
|
Reviewed the grouped note in review 5691743635. The phrase “request-admission delay” means a temporary 250 ms delay before the mocked request reaches its handler. The surrounding verification record gives the delay, the exact expected-one/actual-zero failure, and both reproduction logs. This is an optional wording suggestion, not a verified defect; the historical test receipt remains unchanged. No production API or user-facing copy uses this phrase. The two test-reliability concerns retained in the summary are already addressed: distinct capture keys and verified manifests, and default recovery visibility timeout after causal state/error checks. The generic docstring-percentage advisory was also dispositioned in the first reply; no missing behavioral contract was identified. There are no unresolved inline threads at 289c244. Fresh CI remains in progress. |






Tip
PR walkthrough: Open the visual walkthrough
Inherited MCP servers can now be excluded from one existing agent session and restored without changing shared defaults or sibling sessions. Saved exclusions survive restarts and apply at idle or the next start, preserving the active turn's delivered tools.
Important Changes
Validation
Checklist
apps/web/), I have added or updated Playwright e2e tests inapps/web/e2e/and verified them withmake test-e2e.docs/public/**and updated them or noted why no docs change is needed.Screenshots