Repository navigation
Revert "feat(server): thread tools return a ready t3-thread link" - #24791
juliusmarminge wants to merge 1 commit into
Conversation
)" This reverts commit 003b64d.
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a small, explicit revert of the ready-made thread-link feature, removing stale title-based link fields while preserving thread IDs and core MCP behavior. The contract and documentation updates are consistent with the revert and introduce no broader product or infrastructure change. You can add or adjust custom eligibility rules. Learn more. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Remove generated links from MCP results packages/contracts/src/orchestratorMcp.ts, apps/server/src/mcp/OrchestratorMcpService.ts, apps/server/src/mcp/toolkits/project/*, apps/server/src/mcp/toolkits/thread/*, apps/server/src/mcp/OrchestratorMcpService.test.ts, packages/shared/src/threadLinks.test.ts |
The thread response contracts and handlers no longer include generated link fields. Thread search returns its result directly. Related tests no longer expect the removed fields. |
Update thread link guidance apps/server/src/mcp/toolkits/orchestrator/tools.ts, apps/server/src/mcp/toolkits/project/tools.ts, docs/orchestration-v2/orchestrator-mcp-server.md |
Tool descriptions and documentation tell callers to construct thread links from the returned thread ID. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Bug fix
Possibly related PRs
- pingdotgg/t3code#24784: Adds the link fields and guidance that this PR removes.
Suggested labels: bugfix
Suggested reviewers: t3dotgg
Merge Risk: 
Minimal · up to 43b5c
-
The PR consistently replaces generated thread links with caller-constructed links without an established repository-side regression.
Pre-merge checks: 
3 · 
1
-
Failed checks: 1 warning Passed checks: 3 passedFull details: Description check
-
Resolution
Add the required section headings. Describe the expected behavior and reproduction context under Problem, explain the affected components under Change, provide the linked issue or maintainer approval and scope rationale under Scope and approval, and list focused tests or manual checks with observed results under Verification.
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
|
you are goated for reading the code and finding this. i really hope that this gets merged soon or my threads will start breaking cause i have a habit of renaming em lol. i havent installed the latest version |
Reverts #24784
thread titles are not constant and should not be treated as such 😭 😭 😭 titles change and then the links will show stale data