feat(codex): submit thread feedback to OpenAI

[t3dotgg]

Codex users could not submit a T3 Code thread to OpenAI or get the thread ID needed to share it with OpenAI employees.

Type /feedback in an existing Codex thread to upload the conversation and Codex logs. Add an optional reason, then copy the returned thread ID on web, desktop, or mobile.

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
New operate-scoped RPC uploads conversation data and Codex logs to OpenAI, and can recover stopped Codex sessions before upload. Errors are sanitized so provider details are not returned to clients.

Overview
Lets Codex users send /feedback (optional reason) in an existing thread so T3 Code uploads the conversation and logs to OpenAI and returns a shareable thread ID.

Adds provider.uploadFeedback RPC, contracts, and ProviderService.uploadFeedback. Codex-only adapters implement it via feedback/upload (classification: bug, includeLogs: true). Stopped Codex sessions are recovered before upload; other providers fail without restart. RPC requires orchestration operate scope; failures map to ProviderUploadFeedbackError without leaking provider internals.

Web and mobile intercept the command (no attachments), show local user/assistant pseudo-messages, and surface success with copy-ID or an error. Codex provider status now advertises the feedback slash command.

^{Reviewed by Cursor Bugbot for commit 07f159b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add /feedback command to submit Codex thread feedback to OpenAI

• Adds an end-to-end feedback flow: users type /feedback [reason] in a Codex-backed thread, and the client uploads the thread and logs to OpenAI via the new provider.uploadFeedback RPC, returning a shareable feedback thread ID.
• Server side: ProviderService.uploadFeedback resolves a session (optionally recovering a stopped one), validates adapter support, and calls CodexAdapter.uploadFeedback → CodexSessionRuntime.uploadFeedback, which issues a feedback/upload request to the Codex app-server with classification: 'bug' and includeLogs: true.
• Client side: parseCodexFeedbackCommand detects the command, submitCodexFeedback manages upload state (uploading → sent/failed/interrupted), and codexFeedbackMessage renders synthetic user/assistant messages in the timeline on both web and mobile.
• Adds contracts types (ProviderUploadFeedbackInput, ProviderUploadFeedbackResult, ProviderUploadFeedbackError) and registers WsProviderUploadFeedbackRpc in the RPC group, requiring AuthOrchestrationOperateScope.
• Risk: ProviderAdapterShape.uploadFeedback is optional on the base interface but required on CodexAdapterShape; any out-of-tree adapter implementations must add the method. ProviderUploadFeedbackError.message redacts the upstream cause to avoid leaking error text.

^{Macroscope summarized 07f159b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e656af30-743f-401b-8317-d58f4ab74d2c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

One finding on the new Codex feedback toast in apps/web/src/components/ChatView.tsx: the "Copy ID" action bypasses the shared clipboard helper and loses its unavailable-API handling. Everything else in the web diff reuses the existing toast helper and provider slash-command plumbing, so no other consistency issues were found.

^{Posted via Macroscope — UI Consistency}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.4 KiB	13.4 KiB	−18 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−8 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.5 KiB	−10 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.0 KiB	55.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	13.4 KiB	13.4 KiB	−11 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−6 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	55.8 KiB	55.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 30be311 · PR result: 07f159b · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Reviewed the new provider feedback path against the Effect service conventions. The adapter/service layers (CodexAdapter.uploadFeedback, ProviderService.uploadFeedback, CodexSessionRuntime.uploadFeedback) follow the existing routing, span-annotation, and domain-error pass-through patterns. One issue: the new RPC-boundary error is unstructured and drops the underlying failure.

^{Posted via Macroscope — Effect Service Conventions}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a4d66cd. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a new /feedback workflow across web and mobile, backed by a websocket/provider integration that uploads the Codex thread and logs to OpenAI. The cross-layer behavior and sensitive external-data transfer warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding on the new Codex /feedback composer path in apps/web/src/components/ChatView.tsx: the in-flight upload blocks sending but is not surfaced in the composer's send affordance. The previously flagged clipboard issue is resolved now that the action routes through writeTextToClipboard.

^{Posted via Macroscope — UI Consistency}