GPT Astra Ultra loosing connection... not working at all.. since realese...
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.901.41600
What subscription do you have?
PRO 20x
What platform is your computer?
Windows
What issue are you seeing?
I'm trying to run a PCB task on this new model... I already ran one on the "old" version and it went well... However, with this one... for the past day, it feels like it's not actually doing any work... The only thing it's done well so far is burn through tokens... I'm not seeing results like I do with the 5.6 SOL... And just a few minutes ago... it kept losing the connection... It usually works so well... but when it has issues... it's a real headache... I don't want to complain too much, since they sometimes offer replacements, but it gets a bit annoying when I need it to work and it doesn't, lol. Yesterday I had 100% usage... currently it's at 45% with zero results... With the 5.6 SOL, I ran a PCB task that took over 48 hours non-stop; it provided details and reported everything correctly... But today, Codex is acting weird... especially when using this new model...
What steps can reproduce the bug?
Feedback ID: 01a06e70-d9c3-75a1-9ace-866842d8da09
What is the expected behavior?
No response
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 reviewing Feedback ID 01a06e70-d9c3-75a1-9ace-866842d8da09 alongside the reported Codex App version 26.901.41600, Windows platform, and GPT Astra Ultra model. The issue names no repository file, test, or expected behavior; progress would require a reproducible connection failure and a defined result for the PCB task.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100