Make thread IDs in chat messages clickable

[jal-co]

When I run orchestration in T3, agents constantly mention other threads by ID, things like mcp:c0ec54b0-e649-4e44-a833-ca11682282e8. Right now that's dead text. To open the thread I have to scroll the sidebar or search for it, and I do this dozens of times a day.

I'd like known thread IDs in chat messages to render as a small chip with the thread's title, and clicking it opens the thread. It should also work inside inline code, since agents almost always wrap IDs in backticks.

What I have in mind:

• Only IDs that resolve to a thread in the same environment become chips. Unknown IDs stay plain text.
• Real links and fenced code blocks don't change.
• Web and desktop message rendering only. I'd leave mobile for later.

I built this on my fork to try it out. It reuses the existing thread title chip and the current thread lookup, so the change is small. Before and after:

Before	After

If this direction works for you, I'm happy to open a PR scoped to exactly this. Branch for reference: jal-co/t3code-pi@main...feat/thread-id-links

[SunkenInTime]

Thanks for this, and for building it out to try. Theo landed #16782 today, which takes this from the other side: thread tools now return a ready [title](t3-thread://…) link, agents are told to paste it, and web and mobile render it as a clickable thread link.

#16948 adds the same link to delegate_task, task_status, create_threads and t3_thread_fork, which is where IDs like your mcp:… example come from. With both in, I'd rather not also detect raw IDs in message text. If you still see agents printing raw IDs after these land, post an example here and we'll look at where it came from.