Codex desktop application integrates with a third-party token plan
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.818.61809
What subscription do you have?
none
What platform is your computer?
Darwin 23.6.0 arm64 arm
What issue are you seeing?
After connecting to the third-party token plan, I did not configure 5.6luna. However, during actual use, 5.6luna consumption would occur in the background, approximately costing around $1 per day, which seriously consumed the token usage.
What steps can reproduce the bug?
Feedback ID: 01a03707-4fbd-7000-ba61-414e10dd54df
What is the expected behavior?
Do not secretly invoke 5.6 Luna in the background.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating the desktop app's third-party token-plan integration using feedback ID 01a03707-4fbd-7000-ba61-414e10dd54df. Reproduce on the reported Darwin arm64 platform with no subscription and check whether 5.6luna is consumed without configuration. Done means unconfigured 5.6luna is no longer invoked in the background.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100