# fix\(cli\): auth session list reports sessions connected to the running server · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 528b93de82a04b4c626edf54ae71d49067e7c96a

Requested commit: 528b93de82a04b4c626edf54ae71d49067e7c96a

Commit: 528b93de82a04b4c626edf54ae71d49067e7c96a

Tree: d0368de4b6a17788edb054c7d94f7edbf7d412ca

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(cli): auth session list reports sessions connected to the running server

Which sessions hold an open WebSocket lives only in the running server's
memory, so `t3 auth session list` read from the database alone always
printed connected:false. When a server runtime state is recorded, the CLI now
asks that server through GET /api/auth/clients with a short-lived access:read
session, revoked before the list is read, and fails loudly if the server does
not answer instead of reporting every session as disconnected.

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

```

## Parents

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

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