Expose pinned state in orchestrator MCP thread tools (t3_thread_list / t3_thread_read)

[theo-stocchetti]

Summary

t3_thread_organize can pin / unpin a thread, but no MCP tool returns whether a thread is pinned.

Problem

An orchestrating agent doing bulk cleanup (for example settling or archiving threads that have been idle for more than 24h) cannot exclude pinned threads, because neither t3_thread_list nor t3_thread_read exposes pinned / pinnedAt. By contrast, settled, snoozed and archived are all readable. From MCP, the pin is write-only, so a bulk operation can silently settle a thread the user deliberately pinned.

Proposal

• Add pinned (and pinnedAt) to the thread summaries returned by t3_thread_list and t3_thread_read.
• Add an optional pinned filter to t3_thread_list, consistent with the existing settled and snoozed filters.

Related

• [Bug]: t3_thread_list reports linkedPullRequest: null for threads whose PRs are in another repo (or project has no git remote) #17103 (t3_thread_list reports linkedPullRequest: null for PRs in another repo)
• t3_thread_read: support reading the newest items of a thread (beforePosition or newest-first order) #17030 (t3_thread_read: read the newest items)
• Discussion Read-only thread metadata listing for local tools (thread IDs, titles and provider session IDs) #17593 (read-only thread metadata listing for local tools)

Observed on

Server 0.0.46-nightly.20261011.2980