# fix\(server\): refresh repository identity where remotes change · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 6ef9464ea4b2ca587265405d9f6099059ca83128

Requested commit: 6ef9464ea4b2ca587265405d9f6099059ca83128

Commit: 6ef9464ea4b2ca587265405d9f6099059ca83128

Tree: 2123735f9931255d315fca76b6909dd97b883c07

Author: Claude

Committer: Claude

## Message

```
fix(server): refresh repository identity where remotes change

With longer identity TTLs, paths that add a remote must refresh it
themselves:

- PR discovery after a finished turn refreshes the project identity, so a
  remote the agent just added gets its PR link right away.
- Publish and Initialize refresh the identity for their directory.
- A failed `git remote -v` is no longer cached as "no repository".

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WvDgDwRRG8xvtoABQ8KwtC

```

## Parents

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

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