# feat\(orchestration-v2\): route Codex thread feedback uploads through v2 \(\#7949\) · pingdotgg/t3code

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

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

Visibility: public

Requested revision: ea87825eea9948a55dccaadea619f7ef002aadcf

Requested commit: ea87825eea9948a55dccaadea619f7ef002aadcf

Commit: ea87825eea9948a55dccaadea619f7ef002aadcf

Tree: 41b94191e53b9b750552878be4a330638d7045b5

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(orchestration-v2): route Codex thread feedback uploads through v2 (#7949)

The round-10 rebase stubbed providerUploadFeedback to an explicit error
because its v1 ProviderService route died with the v2 rewrite. The route
now goes through the v2 runtime: session runtimes may expose an optional
uploadFeedback capability, the Codex adapter implements it against the
app-server's feedback/upload request, and the WS handler resolves the
thread's live provider session through ProviderSessionManagerV2 —
failing with a plain-language reason when no session has run, the session
is gone, or the driver has no feedback channel. This also un-blocks the
dormant mobile feedback UI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

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

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