# fix\(server\): t3 pair refuses a server on another orchestration protocol · pingdotgg/t3code

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

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

Visibility: public

Requested revision: c502579298f719c4346f48ff75f3b7d896ba17c4

Requested commit: c502579298f719c4346f48ff75f3b7d896ba17c4

Commit: c502579298f719c4346f48ff75f3b7d896ba17c4

Tree: 64f17002a0f74dac110bd969d9cac951ac0815a4

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): t3 pair refuses a server on another orchestration protocol

An older CLI discovered a protocol 2 server, minted into a database that
server never reads, and printed a token it rejects. Pair now compares the
discovered descriptor's protocol before opening any local database and points
at the matching `npx t3@<serverVersion> pair`.

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

```

## Parents

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

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