No actionable comments were generated in the recent review.
Walkthrough
-
Valid token resolution no longer refreshes the credential’s liveness timestamp. The expiration test checks that the token still resolves after 99 ms and expires after 101 ms.
Changes: MCP credential liveness
Layer / File(s) Summary Credential resolution and expiration test
apps/server/src/mcp/McpSessionRegistry.ts,apps/server/src/mcp/McpSessionRegistry.test.tsValid token resolution returns the recorded scope without updating lastAliveAt. The test checks resolution before the liveness window expires and expiration after it.Estimated code review effort: 2 (Simple) | ~8 minutes
Change: Bug fix
Possibly related issues
- pingdotgg/t3code#16184: This change affects when requests can extend the liveness window, but it does not make retry IDs stable across credentials.
Possibly related PRs
- pingdotgg/t3code#26352: Both changes stop
McpSessionRegistry.resolvefrom refreshinglastAliveAtand test expiration after token resolution.
Suggested labels:
bugfixSuggested reviewers:
juliusmarminge
Merge Risk: External image Minimal · up to bade7
-
Credential reads no longer extend validity, while active provider sessions retain trusted refreshes. No merge-blocking risk was identified.
Pre-merge checks: Passed 4
-
Check name Status Explanation Title check Passed The title clearly describes the change to MCP credential liveness. Description check Passed The description covers the problem, change, scope, verification results, and agent details. 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.
Finishing Touches
-
Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
-
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
-
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
External image Recent review info
-
External image Run configuration
-
- Source mode: Auto
- Repository: pingdotgg/t3code
- Branch: main
- File: .coderabbit.config.ts
- Commit: 25b5329
- Layers: Repository TS config
- Review profile: CHILL
- Plan: Advanced
- Run ID:
3e08e4a6-ef42-4249-896a-7f5d6dc7c1b7
External image Commits
-
Reviewing files that changed from the base of the PR and between 25b53299b75d4d8d1d0667ad47e9cfed3749776e and bade789580b108fa9f3a7f680fd4d64a4fc589a4.
External image Files selected for processing: 2
-
apps/server/src/mcp/McpSessionRegistry.test.tsapps/server/src/mcp/McpSessionRegistry.ts
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.
External image Recent review info
-
External image Run configuration
-
- Source mode: Auto
- Repository: pingdotgg/t3code
- Branch: main
- File: .coderabbit.config.ts
- Commit: 25b5329
- Layers: Repository TS config
- Review profile: CHILL
- Plan: Advanced
- Run ID:
3e08e4a6-ef42-4249-896a-7f5d6dc7c1b7
External image Commits
-
Reviewing files that changed from the base of the PR and between 25b53299b75d4d8d1d0667ad47e9cfed3749776e and bade789580b108fa9f3a7f680fd4d64a4fc589a4.
External image Files selected for processing: 2
-
apps/server/src/mcp/McpSessionRegistry.test.tsapps/server/src/mcp/McpSessionRegistry.ts
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.
-