Repository navigation
feat(server): agents can read Linear issues through T3's connection - #419
Merged
Merged
Conversation
The thread MCP could link a Linear issue but only ever returned its identity, so an agent without its own Linear MCP server could not read the issue a thread was linked to. Add read_linear_issue (the linked issue by default), search_linear_issues and list_linear_filter_options, backed by the environment's existing Linear connection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An agent in a thread linked to a Linear issue still couldn't read that issue. The thread MCP's
link_linear_issueandlist_thread_issuesreturn only the issue's identifier, title and URL. Agents without their own authorised Linear MCP server had no way to see the description, comments or status.Three read-only tools are added to the thread MCP's issue-links toolkit. They all use the environment's existing Linear connection (
LinearApi):read_linear_issue: reads the whole issue as markdown, the same text a composer#ENG-123chip sends. That covers state, priority, assignee, team, project, labels, parent, sub-issues, attached links, description and comments. It reads the thread's linked issue by default, or takes an identifier, UUID or URL. It fails withNoLinkedLinearIssueErrorwhen nothing is linked.search_linear_issues: looks up an identifier, runs a text search, or applies filters, wrappingLinearApi.listIssues. Filter fields are optional and missing ones default to empty.list_linear_filter_options: lists teams, statuses, projects and milestones, users, and labels, which supplies the ids the filters need.The tool descriptions now say they use T3 Code's own Linear connection.
link_linear_issueandlist_thread_issuespoint toread_linear_issue. The new tools need the samepull-requestscapability as the other issue-link tools, and they work for read-only clients. They have work-log labels and summaries.docs/fork-differences.mdis updated.Tests:
vp test runonissueLinks/handlers.test.ts,toolkits/core.test.tsandworktree/registration.test.ts, plus typecheck of server, shared, client-runtime and web.Write tools (commenting, changing status) are not included.
Done by Claude Opus 5.5 in Claude Code via T3 Code.
🤖 Generated with Claude Code