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

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

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

Visibility: public

Requested revision: fc8a3e32d2c8b4add80c947182411a3a6dc83b37

Requested commit: fc8a3e32d2c8b4add80c947182411a3a6dc83b37

Commit: fc8a3e32d2c8b4add80c947182411a3a6dc83b37

Tree: 3d0f1a18d230f9945fd273e1de8b6969960de437

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

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

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