# fix\(server\): Codex keeps your permissions profile when T3 resumes the thread between turns \(\#20266\) · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 41f688b86bb4cecb7ac7e7f1ab5f2eacf48bc1fa

Requested commit: 41f688b86bb4cecb7ac7e7f1ab5f2eacf48bc1fa

Commit: 41f688b86bb4cecb7ac7e7f1ab5f2eacf48bc1fa

Tree: 267f7891aab772e13f9bf133b6f423a5ac0ab527

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): Codex keeps your permissions profile when T3 resumes the thread between turns (#20266)

T3 resumes a loaded Codex thread before every turn whose runtime settings
changed. That thread/resume response reports the thread's current state,
which has no active permission profile after a Full access (or any legacy
sandboxPolicy) turn, so the adapter forgot the user's profile and the next
Auto turn fell back to sandboxPolicy, dropping the profile's .env denies.

A response without a user-defined profile now leaves the remembered one in
place. The round-trip test now issues the thread/resume calls T3 really
makes between turns.

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

```

## Parents

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

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