# fix\(server\): a link card stays answerable after a steer, and Stop shows no new one · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 59b552379f8bdf91742c2740176dcbc8f339e102

Requested commit: 59b552379f8bdf91742c2740176dcbc8f339e102

Commit: 59b552379f8bdf91742c2740176dcbc8f339e102

Tree: 8bf3e5a99ce9b2e4f06874cbd9417c37ac41a1c3

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): a link card stays answerable after a steer, and Stop shows no new one

The link_request.record command required the run's current root node on
every update. A steer that restarts the turn moves the root, so an answer
recorded after it was refused once the link had already been made: the card
stayed pending, the agent never heard back, and each retry paired again.
The root and a live, unstopped run are now required only when a card is
created; an update keeps the card's own node and provider turn.

The same check closes a race with Stop: a request that read an active run
before thread.stop closed the thread's cards could still record a new
pending card, which would wake the agent when answered.

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

```

## Parents

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

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