codex - 💡(How to fix) Fix Codex is now searching the web way more frequently and at unnecessary times [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20988Fetched 2026-05-05 05:54:52
View on GitHub
Comments
3
Participants
3
Timeline
10
Reactions
0
Timeline (top)
labeled ×4commented ×3closed ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.128

What subscription do you have?

Plus

Which model were you using?

gpt-5.3-codex high

What platform is your computer?

linux

What terminal emulator and version are you using (if applicable)?

xfce4-terminal

What issue are you seeing?

A few days ago codex started searching the web way more frequently and at unnecessary and bizarre times where it obviously wouldn't find the answer. It now searches the web 2-10 times frequently for even basic tasks when before it would search 0 times and it would only use the web when logical. It's searching the web for proprietary details and things clearly only invented by me.

What steps can reproduce the bug?

• Explored └ Read LocalBoardApi.kt Search robust_loc_scale|sigmoid|solve_shift_for_target_sum|xorshift128plus|generate_flat(| kMaxWords|g_dictionary_words|thread_word_indices|list_words in main.cpp Search dictionary|word_to_id|g_dictionary|vector<string>|all_words|list_words in main.cpp

• Searching the web

• Searched

• Searching the web

• Searched

• Explored └ Read main.cpp, boardgen_jni.cpp

• Searching the web

• Searched

• I’ve confirmed the sampled EWMA is failing for a concrete reason in your device log. I’m now checking the native generator code for an existing on-device EWMA routine we can call directly (instead of desktop path execution).

• Explored └ Search ewma|total_rating|board-analysis|bot-speed|benchmark_summary|rating in main.cpp

• Searching the web

• Searched

• Searching the web

• Searched

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be related to an incorrect or failing Exponential Weighted Moving Average (EWMA) calculation, leading to excessive web searches.

Guidance

  • Review the native generator code for an existing on-device EWMA routine that can be called directly, as mentioned in the steps to reproduce the bug.
  • Investigate the sampled EWMA failure in the device log to understand the root cause of the issue.
  • Check the main.cpp and boardgen_jni.cpp files for any recent changes or updates that may be contributing to the problem.
  • Verify that the gpt-5.3-codex model is correctly configured and functioning as expected.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue may be specific to the gpt-5.3-codex model or the Codex CLI version 0.128, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and fix the EWMA calculation issue, as it is likely the primary cause of the excessive web searches.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex is now searching the web way more frequently and at unnecessary times [3 comments, 3 participants]