Repository navigation
Let a thread hand work out to an outside assistant ("cite to assistant") #39203
fabiocolor
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everybody,
I use T3 Code every day across a lot of machines for my film restoration research. Through the MCP server, an outside assistant can already read threads, send messages and launch new ones. That part works really well.
But it only goes one way. From inside a thread there is no way to hand something back. When an agent finds a problem that belongs somewhere else, for example a timeout on another workstation, I end up copying text between windows and starting the new thread myself.
So I built a small workaround for myself: grokbot-at-bot (v0.2.0 release). I select a line in an assistant reply, click Cite, type
@botand what I want, and send. My assistant gets the quote, the source thread's IDs and my instruction. Then it can answer in its own chat, check back in that thread later, or open a new thread on the machine and project I name. The first thread keeps working the whole time.36 s video, one real run with the waits sped up: at-bot-demo-36s.mp4. I also posted it on X.
To be honest about the limits: the citation part is a local patch to the T3 Code (Beta) 0.1.10 desktop app, plus a small local relay that holds the webhook credentials. I have to rebuild the patch after every T3 update, and it only works on that build. That's the main reason I'm writing this.
None of it is really specific to Grok Bot. The patch just sends a passage, its source IDs and an instruction to a URL. The same hook could point at other assistants, like dots/Muse or Duet, or at someone's own script.
So the idea, without asking for any particular architecture: a provider-neutral "send to assistant" action next to Cite/Comment. Something like:
The assistant can then use the existing MCP tools to come back to the thread or open a new one, so the loop closes with what T3 already has.
Happy to share more about how I use it day to day, or test anything if it helps. And if this doesn't fit where T3 is going, no problem, the workaround is there for anyone who wants it.
Thanks for T3 Code, it has changed how I work across my machines.
All reactions