You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 63b1258
Browse filesBrowse the repository at this point in the historyBrowse files
feat(web,mobile): the @ picker lists threads on linked machines
Attaching a thread from another environment needed a pointer drag, and a
pasted or dropped thread chip from another machine was dropped or turned
into a transcript. Where the composer's environment offers linked
environments, its linked machines' threads now stay live chips:
- The @ picker on web and mobile also lists threads from the machines the
composer's environment links to, read from the existing thread shells and
named "Thread on <machine>".
- Paste on web and mobile, sidebar drop on web, the composer chip's
unreadable state, and the web and mobile send guards accept a thread chip
from a linked machine. With the beta off or no link, nothing changes.
- The chip already names its environmentId, and agents pass it to
t3_thread_read without an extra instruction, so the agent's text is
unchanged.
- evals/mcp-tool-use can turn the beta on per case and project a case's
context chips through the real projection; a new guard case checks that
the agent reads a linked machine's thread chip there.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments