# fix\(web\): handoff menus, sends and banners respect the move's state · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 3673a045599a564dc19ea5a3435b5c4216032e25

Requested commit: 3673a045599a564dc19ea5a3435b5c4216032e25

Commit: 3673a045599a564dc19ea5a3435b5c4216032e25

Tree: 0306439c1608a53ae2b2b90d86f0ce9ab99b88ca

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(web): handoff menus, sends and banners respect the move's state

"Open on <machine>" showed for a destination this client knew about but
was not connected to; it now needs a connected environment.

The thread menus waited for move targets and then showed the menu even
if the user had since closed it, opened another, or switched threads.
Each open now takes a token, and a stale one is dropped before showing.

Preview annotations and app messages reached onSend and sendAppMessage
directly, past the closed send button, so they could clear the composer
for a thread that is moving away. Both now check the handoff first.

The handoff notice sat ahead of the system notices, so on a priority tie
it hid an update or reconnect notice in the collapsed stack.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

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

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