Pinning a conversation with a non-OpenAI provider leaks all pinned OpenAI conversations into the list

Open
#34,574 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Start by reproducing the issue with a custom provider using a custom base_url and wire_api = "responses". Trace the pin action and the full reload of the pinned list, then verify that the list remains scoped to the active provider and that continuing a conversation does not bypass its provider.

Written by the indexing model from the issue text.

Description

app bug custom-model session

Describe the bug

When Codex is configured with a custom provider (e.g. wire_api = "responses" with a custom base_url), the conversation list is correctly scoped to that provider — OpenAI conversations are not visible.

However, as soon as you pin any conversation while on the custom provider, all conversations that were previously pinned on the OpenAI provider suddenly appear in the pinned list.

Steps to reproduce

  1. Configure Codex with a non-OpenAI provider (custom base_url, wire_api = "responses")
  2. Start a new conversation — confirm you only see conversations for that provider
  3. Pin that conversation using the pin action
  4. Observe: the pinned list now shows the just-pinned conversation plus all conversations previously pinned on the OpenAI account

Expected behavior

Pinning a conversation should not affect visibility of conversations from other providers. The pinned list should remain scoped to the active provider.

Actual behavior

Pinning triggers a full reload of the pinned list that ignores the active provider filter, causing all OpenAI-provider pinned conversations to bleed into the view.

Additional context

If the user then continues one of the leaked OpenAI conversations, requests are sent to the OpenAI API directly (bypassing the custom base_url), silently charging the personal OpenAI account.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.