# fix\(server\): a client relink keeps the CLI-desired link mode in step · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 398793caf8d8b414e35621626b172225e4fa3e65

Requested commit: 398793caf8d8b414e35621626b172225e4fa3e65

Commit: 398793caf8d8b414e35621626b172225e4fa3e65

Tree: 8a8ccded7c3542a86d3173dd55313e5f00fb4d39

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): a client relink keeps the CLI-desired link mode in step

A CLI-desired link relinks at startup in its stored mode, so turning
exposure off from Settings came back as a managed tunnel after restart.
Relay config applied by a client now rewrites that mode (publish_only
without a runtime, managed with one) under the link-state lock, and
only when the CLI asked for the link.

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

```

## Parents

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

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