docs(codex): document mobile remote thread visibility limitation for provider-table form - #6029
codingbooo wants to merge 1 commit into
Conversation
…provider-table form Closes lidge-jun#5848
|
✅ Deterministic PR hygiene checks passed. |
✅ READY
Review readiness checklist
✅ 4/4 boxes ticked. This pull request has been marked Ready for Review. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: lidge-jun/opencodex/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe Codex integration guide now explains how ChangesRemote thread visibility
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to This documentation-only change has no established merge-blocking issue; the translated-page request is not required by the supplied guidance. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Closing as overlapping work with the earlier #6007 for #5848. #6007 already contains the runtime/CLI and dashboard warnings plus the guide explanation, has resolved review threads, and exact-head Cross-platform CI is green. The version-specific reproduction and note that new client-created threads can also retain |
Closes #5848
What
With provider-table routing, both
openaiandopencodexthread identities can exist in the sameCodex home. A user reported that the ChatGPT Android remote client listed only
opencodexthreads,so conversations they could still see on Codex Desktop looked deleted on mobile.
Finding
These are Codex app-server
thread/listsemantics, not a proxy routing bug. The reporter confirmedagainst app-server 0.157.0:
modelProvidersomitted → only the root provider's threads (opencodex)modelProviders: []→ threads from bothopenaiandopencodexClients can explicitly create
openaithreads even when the root default isopencodex, so thisaffects new conversations as well as old history. The retained
openai_base_urlkeeps those threadsrouted; it does not change the remote list's provider filter.
Change
Documentation only — this repo does not own the RPC.
docs-site/src/content/docs/guides/codex-integration.mddocuments the filter behaviour, themodelProviders: []workaround for remote-client maintainers, and the fact that OpenCodeX does notperiodically rewrite thread providers to work around it.
in-memory provider back, and changing only the row can disagree with its rollout metadata.
syncResumeHistory: falseremains the opt-out from history remapping, and client-compaction-onlyrouting preserves existing thread identities.
An earlier revision of this branch also carried a doc-side rewrite of thread providers. That
approach was dropped: it cannot be made durable, and the remaining change is the documentation the
issue actually calls for.
Verification
bun run structure:check,bun run privacy:scan— cleanReview readiness checklist
This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:
Required local validation passed; commands, results, and any full-suite exception are documented.
I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
I resolved all correct Codex and CodeRabbit findings.
My PR is ready for review.
Summary by CodeRabbit