Repository navigation
fix(server): agents read a Linear issue once when given its link - #38425
juliusmarminge merged 3 commits into
Conversation
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Resolving a standalone tracker's URL already reads the issue to check its workspace; resolveUrl now returns that read, and read_issue and link_issue use it instead of reading the issue again. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Grok 4.7 <noreply@x.ai> Co-authored-by: GPT 6.2 Sol <codex@openai.com>
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — The change reuses an issue fetched during URL validation instead of reading it again when an agent reads or links it. Workspace validation and existing access safeguards remain unchanged. You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
EvidenceSend a full Linear issue URL in a connected, team-bound project. Invoke
Scenario · Replay forwarding driver · Controlled Linear proxy and issue seed
Not shown:
|
**v0.1.11-nightly.20261118.4877** · 24 changes from 13 contributors - **Paused tasks.** Running a paused one-time task manually no longer deletes it. - **Claude subagent results.** Resumed Claude subagents retain their earlier results instead of replacing them. ### Plus 20 more bug fixes. <details> <summary>Full changelog</summary> ## What's Changed * fix(server): agents read a Linear issue once when given its link by @StiensWout in pingdotgg/t3code#38425 * fix(server): All issues pages skip the signed-in account read by @StiensWout in pingdotgg/t3code#38431 * fix(server): recover JSON-stringified delegate targets by @MINIlaolao in pingdotgg/t3code#38436 * fix(mobile): retrying an issue filter only reloads repositories that failed by @StiensWout in pingdotgg/t3code#38423 * fix(web): pairing links never use the desktop app's t3code:// address by @juliusmarminge in pingdotgg/t3code#38442 * chore: vouch mvanhorn by @t3dotgg in pingdotgg/t3code#38455 * docs: vouched contributors can open small feature PRs by @t3dotgg in pingdotgg/t3code#38456 * fix(server): preview pages loaded through a service worker identify as Chrome, not HeadlessChrome by @Sean-R-Wilson in pingdotgg/t3code#38445 * fix(web): switching back to a thread no longer jumps through its HTML renders by @pouyarezvani in pingdotgg/t3code#38458 * fix(mobile): A document whose upload failed can be retried in the composer by @mwolson in pingdotgg/t3code#38443 * fix(server): running a paused one-time task by hand no longer deletes it by @juliusmarminge in pingdotgg/t3code#38463 * fix(server): codex text generation identifies as T3 Code by @juliusmarminge in pingdotgg/t3code#38464 * fix(server): review diff previews reuse the cached repository layout by @amv146 in pingdotgg/t3code#38451 * fix(web): Paste as Text pastes text when the clipboard also holds an image by @juliusmarminge in pingdotgg/t3code#38475 * fix(web): opening a file in the preview browser shows its current contents by @juliusmarminge in pingdotgg/t3code#38470 * fix(github): page closing pull requests past the first twenty on issues by @StiensWout in pingdotgg/t3code#38487 * fix(web): older comments no longer reappear after refreshing an issue by @StiensWout in pingdotgg/t3code#38489 * fix(web): typing into a simulator no longer answers a waiting question by @ipanasenko in pingdotgg/t3code#38476 * fix(server): keep-awake logs a hold only once acquired and reports why the inhibitor failed by @juliusmarminge in pingdotgg/t3code#38505 * fix(server): write the Windows service task as UTF-16LE so non-ASCII paths survive by @juliusmarminge in pingdotgg/t3code#38494 * fix(muse): failed Muse text generation explains Muse's error category by @saphid in pingdotgg/t3code#29861 * fix(server): imported Claude threads show prompts, not Claude Code markup by @dominikzabcik in pingdotgg/t3code#33403 * fix(server): a resumed Claude subagent keeps its earlier result by @ahalekelly in pingdotgg/t3code#34663 * fix(server): a preview navigation request issued before its frame exists no longer crashes the server by @Isaac-b-ux in pingdotgg/t3code#30946 ## New Contributors * @Sean-R-Wilson made their first contribution in pingdotgg/t3code#38445 **Full Changelog**: pingdotgg/t3code@v0.1.11-nightly.20261118.4864...v0.1.11-nightly.20261118.4877 </details> Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.1.11-nightly.20261118.4877


Given a Linear issue link, read_issue and link_issue fetched the issue twice: resolving the URL reads it to confirm the link belongs to the connected workspace, then the tool read it again, spending a second request against Linear's rate limit. resolveUrl now returns the issue it read for a standalone tracker, and both tools use it and read the issue only when resolution did not.
Fixes #38424
Related: #38001, #38078
Reproduction on main
Commit f92c5e8f98 (main). T3 Code fetches the full issue to check the workspace, then fetches it again before replying. If Linear rate-limits that second fetch, the agent gets an error instead of the issue. The cause is at
apps/server/src/issue/IssueService.ts:676. Rancd apps/server && pnpm exec vp test run src/mcp/toolkits/issues/handlers.test.tswith the repro test added: it failed in 2 of 2 runs on a clean checkout, withLinear's rate limit was reached.in the output.Evidence
Environment: Linux x64, the repository's own tests
Proven: the test fails on base 3e1b7c4e93 and passes on head c446e238d6.
Linear's rate limit was reached.in the outputTests
pnpm exec vp run check:changedpassed on head.Not in this change
Who did the work
Made in T3 Code by Grok 4.7, Claude Opus 5.5 and GPT 6.2 Sol