# feat\(web,mobile\): Continue on… a linked environment · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/5c04c88b64820bb1c6b5db6407cd29220749abcb)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 5c04c88b64820bb1c6b5db6407cd29220749abcb

Requested commit: 5c04c88b64820bb1c6b5db6407cd29220749abcb

Commit: 5c04c88b64820bb1c6b5db6407cd29220749abcb

Tree: 6fa3f79ee4a9151e27099d2ead141b3a73b52a0c

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(web,mobile): Continue on… a linked environment

Moving a thread to a linked environment was reachable only through the
t3_thread_handoff MCP tool. Users now pick "Continue on…" from the web
sidebar and chat-header thread menus, the command palette, and mobile's
long-press and thread header menus. Targets are read from
threadHandoff.options when the menu opens.

The thread shows the move's state above the composer: waiting for the
turn to end (with Keep it here), under way, moved (with Open on <machine>),
or failed. While the thread is departing or departed, the composer is
closed on both clients.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

```

## Parents

- [be89710151b212a24dc62721e0b3c46e67441475](https://git.cafe/pingdotgg/t3code/commit/be89710151b212a24dc62721e0b3c46e67441475?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/5c04c88b64820bb1c6b5db6407cd29220749abcb?format=markdown)
