Skip to content

docs(codex): document mobile remote thread visibility limitation for provider-table form #6029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
codingbooo wants to merge 1 commit into from
Closed

docs(codex): document mobile remote thread visibility limitation for provider-table form #6029

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions docs-site/src/content/docs/guides/codex-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -513,6 +513,36 @@ There is no automatic local truncation mode. A response being accepted is not pr
long conversation retained its goals; verify the next turn on the original model before
treating an emergency summary as a recovered task.

### ChatGPT mobile remote thread visibility

Provider-table routing can leave both `openai` and `opencodex` thread identities in the same
Codex home. Reaching the same proxy does not make those identities equivalent for thread lists.
In [issue #5848](https://github.com/lidge-jun/opencodex/issues/5848), the reporter observed
this behavior with Codex app-server 0.157.0 and the ChatGPT Android remote client:

| `thread/list` parameters | Result with root `model_provider = "opencodex"` |
| --- | --- |
| `modelProviders` omitted | Only `opencodex` threads |
| `modelProviders: []` | Both `openai` and `opencodex` threads |

This can affect newly created Desktop and mobile conversations as well as older history:
clients can explicitly create `openai` threads even when the root default is `opencodex`.
The retained `openai_base_url` preserves routing for those threads; it does not change the
remote list's provider filter. A missing mobile entry does not mean the conversation was deleted.

If you maintain a remote client, send `modelProviders: []` in `thread/list` to list all providers,
keeping the existing pagination and other filters. The ChatGPT mobile client must make that
change upstream, or Codex app-server must change its omitted-filter behavior. These RPCs are
handled by Codex app-server, not OpenCodeX's Responses proxy. Until the remote client supports
that behavior, use Codex Desktop to access the affected conversations.

OpenCodeX does not periodically rewrite thread providers to work around this filter.
`syncResumeHistory: false` remains an opt-out from history remapping, and client-compaction-only
routing preserves existing thread identities. Paginated history belongs to Codex's native
writer. Direct SQLite retagging is not a durable fix: a loaded thread can write its in-memory
provider back, and changing only the row can disagree with its rollout metadata. Changing the
root provider merely changes which group an omitted filter selects; it does not combine them.

### Authless Codex Desktop (opt-in)

In **Dashboard → Overview**, **Open Codex without signing in** controls this existing
Expand Down
Loading