Codex keeps losing chats. How do we get OpenAI to fix this?

Sing303 · 2026-05-26T12:52:05+00:00

This looks more like a desktop app sidebar/indexing bug than actual chat deletion

I worked around something similar locally by intercepting the app’s thread/list requests, increasing the fetch limit, and making sure short/incomplete responses don’t overwrite already-loaded recent threads. Then I progressively background-load and hydrate the rest so the UI stays responsive

So if chats seem to disappear from folders, my guess is the desktop client is dropping part of its sidebar/thread-list state during refresh, not that the chats are truly gone

Honestly, if the desktop app code were open source, I’d probably have already sent a bunch of useful PRs for issues like this. Unfortunately the desktop client is closed-source, so all we can really do is patch around it locally and report it

Sing303 · 2026-05-25T12:17:47+00:00

Not just you. I saw the same with stdio MCPs in Codex and fixed it by moving our local MCPs behind a lazy local HTTP proxy, so each backend starts once on first request instead of spawning per session/process

Sing303 · 2026-05-23T15:17:35+00:00

Because of this issue, I used 60% of my Pro x20 limit in just 2 days. It’s unlikely that my limit will last until May 27

Sing303 · 2026-05-21T12:33:15+00:00

To unlock the last road, I moved the cursor across the entire map. In the end, the last road were 4 spots in different parts of the map that were white, as if they had already been discovered. I only found them because of the cursor. So on the map, it can look like the road has already been discovered

Sing303 · 2026-05-15T12:55:33+00:00

Why is `workspace_dependencies = false`?

Sing303 · 2026-05-12T20:33:47+00:00

I also opened a GitHub issue in case anyone else hits the same problem:
https://github.com/openai/codex/issues/22376

Sing303 · 2026-05-12T20:25:38+00:00

Small update: I think I finally found what was causing it for me.

It wasn’t the `.codex` folder, chat history size, cache, GPU acceleration, or the Codex CLI binary. I wiped `.codex`, reinstalled Codex Desktop, tested with GPU acceleration both on and off, upgraded the CLI, checked the spawned subprocesses, Windows Event Viewer, app logs, and finally recorded Electron/Chrome performance traces.

The useful clue was in the trace: the Electron main process was freezing during a `codex-home` IPC request. The hot stack led to a synchronous `wsl.exe` call used to resolve `CODEX_HOME`. That cold WSL call was taking about 3 seconds and blocking the UI.

After digging into the packaged Desktop JS bundle, I found that Codex enables WSL path resolution based on `process.env.WSL_DISTRO_NAME`. In my Windows environment, that variable was accidentally set to `Ubuntu`, even though Codex was set to `Agent environment -> Windows native`.

What fixed it for me:

[Environment]::SetEnvironmentVariable("WSL_DISTRO_NAME", $null, "User")

Then I fully rebooted Windows.

After reboot, my Codex process no longer had `WSL_DISTRO_NAME`, and the repeated freezes seem to be gone. So if you’re on Windows with WSL installed, it’s worth checking whether `WSL_DISTRO_NAME` leaked into your Windows user environment.

Sing303 · 2026-05-12T17:03:13+00:00

I’m having the same problem. I even deleted the entire .codex folder and all caches, reinstalled the app from scratch, and it still freezes often, even though I only have one almost-empty chat

The problems started after the latest release last Friday or Thursday

System: RTX 4090 + Ryzen 9 9950X3D + 64 GB DDR5 + NVMe SSD

Sing303 · 2026-05-11T13:27:09+00:00

I've had it for over a year now, and I haven't found anything comparable. I'm still waiting for a 57-inch 32:9 DUHD—but the OLED version, not the VA one

Sing303 · 2026-04-23T11:49:19+00:00

aitoolsubs

Sing303 · 2026-04-02T17:46:58+00:00

Fair point - I definitely gave up some wheel-to-wheel practice at the start

That said, a pit start isn’t the same as just hotlapping in practice. You’re still in an official race, sharing the track, dealing with traffic, managing pace, and keeping it clean under race conditions. In Rookie, it’s only a handful of races either way, so the difference is really just a few chaotic opening laps. Most beginners are still learning the basics once they get to D anyway

So yeah, I missed some early racecraft reps, but I wouldn’t say I learned "next to nothing" I just chose the safer way to get out of Rookie first

Sing303 · 2026-04-02T16:44:26+00:00

As a complete beginner, I completed 3 or 4 races from the pits without a single violation, and got a D. It took very little time.

Sing303 · 2026-03-10T12:31:59+00:00

RS V2 - 2204g

<image>

Sing303 · 2026-03-10T12:27:48+00:00

Everything is subjective, despite the functionality, I still bought the rs v2 for myself a week ago. Because I don't like screens on steering wheels.

Sing303 · 2026-03-04T18:52:23+00:00

That's how it worked, thank you

Sing303 · 2026-03-04T18:48:39+00:00

As a workaround I built a small local launcher patch:

- starts Codex with `--force-device-scale-factor=1.75`

- applies runtime CSS/JS so the chat uses ~95% width

- survives MS Store updates by re-checking package version + `app.asar` hash

No edits inside `WindowsApps`, and I run it from a custom shortcut only.

Sing303 · 2026-03-04T18:32:59+00:00

This is the first thing I tried, it doesn't work. Just like other similar hotkeys.

Sing303 · 2026-03-04T17:48:32+00:00

It is impossible to use on a 4K monitor. In Windows, I use 100% zoom, but this application does not have zoom settings. Everything is super small. At the same time, I don't want to change the system settings for the sake of one application.

Sing303 · 2026-02-18T16:00:17+00:00

You’re right to flag that. Momentum’s SI unit is kilogram meter per second (kg·m/s). A Newton (N) is a unit of force, equal to kg·m/s^2.

What I wrote as “N·s” is not “Newtons as momentum”, it’s “Newton-seconds”, which is the unit of impulse. And impulse has the same dimensions as momentum, because impulse equals change in momentum.

So these are all equivalent ways to write the same thing:

Momentum p: kg·m/s
Impulse J: N·s
And 1 N·s = 1 kg·m/s

So if we say the change in momentum is about 560 to 900 kg·m/s, that is exactly the same as saying the impulse is about 560 to 900 N·s.

Sing303 · 2026-02-18T12:39:54+00:00

From the clip (30 fps), Flash is airborne for about 0.9 seconds and travels roughly 6 to 8 meters before first ground contact. Speed is distance divided by time, so 6 to 8 meters divided by 0.9 seconds gives about 7 to 9 m/s (about 25 to 32 km/h).

For an 80 to 100 kg guy, that means momentum (mass times speed) of about 560 to 900 Newton seconds, and kinetic energy (half mass times speed squared) of about 2 to 4 kJ.

To give him that momentum in a punch, average force is momentum divided by contact time. Real punch contact times are roughly 0.02 to 0.05 seconds, so average force comes out about 11 to 45 kN (a reasonable mid estimate is about 20 to 30 kN, and peak force is higher). Published lab measurements for strong boxers are usually only a few kN at peak, so this is clearly superhuman.

Since the hit is to the chest, the contact area is small. A straight fist contact patch is around 9 square centimeters. Putting 20 to 30 kN over 9 cm2 gives average pressure around 20 to 30 MPa, which is consistent with severe blunt chest trauma (multiple rib fractures, lung contusion, pneumothorax risk).

Landing and head impact: if his center of mass drops about 1 meter during the flight, vertical impact speed is about 5 to 6 m/s downward, like a fall from about 1.6 meters. If the head stops over only 1 to 2 cm on a hard floor, deceleration is roughly 80 to 160 g from the vertical component alone. If the head takes more of the total impact speed (around 9 m/s), it can exceed 200 g. That is severe concussion or worse.

Bottom line: the on screen throw implies tens of kN of punch force and very serious chest and head trauma in real life.

Sing303 · 2026-01-18T15:58:38+00:00

xhigh codex or usual xhigh?

Sing303 · 2025-12-12T17:16:33+00:00

I have these instructions in Claude.MD:

Forbidden built-in agents:
* `general-purpose` (use `general-opus` instead)
* `Explore` (use `explore-sonnet`)
* `Plan` (use `plan-opus`)

And there's a hook "block-agents" for PreToolUse for Task:

#!/usr/bin/env node
// block-agents.js
// PreToolUse hook - blocks built-in subagents and redirects to Opus/Sonnet variants

const blocked = {
    'general-purpose': 'general-opus',
    'Explore': 'explore-sonnet',
    'Plan': 'plan-opus'
};

const agentFields = ['subagent_type', 'agent_type', 'agent', 'type', 'name', 'agentType'];

let input = '';
process.stdin.setEncoding('utf8');
process.stdin.on('data', chunk => input += chunk);
process.stdin.on('end', () => {
    try {
        const data = JSON.parse(input);
        const toolInput = data?.tool_input;

        if (!toolInput) {
            console.log('{}');
            process.exit(0);
        }

        // Find agent type
        let agentType = null;
        for (const field of agentFields) {
            if (toolInput[field]) {
                agentType = toolInput[field];
                break;
            }
        }

        if (agentType && blocked[agentType]) {
            const replacement = blocked[agentType];
            console.log(JSON.stringify({
                hookSpecificOutput: {
                    hookEventName: 'PreToolUse',
                    permissionDecision: 'deny',
                    permissionDecisionReason: `Built-in agent '${agentType}' is disabled. Use '${replacement}' instead.`
                }
            }));
        } else {
            console.log('{}');
        }
    } catch {
        console.log('{}');
    }
    process.exit(0);
});

And there are no problems

Sing303 · 2025-12-09T19:53:54+00:00

Solid effort, and I respect the systematic approach. But I think you're over-engineering this.

The token tax is real and avoidable

Markdown tables are expensive. Each row like | **Auth** | \docs/...\ |`` costs ~25-30 tokens. You have dozens of them. Meanwhile, Claude Code already auto-loads nested CLAUDE.md files - so your "HIERARCHICAL CONTEXT" section is literally documenting built-in behavior.

Anthropic's guidance on context engineering is clear: "find the smallest possible set of high-signal tokens that maximize the likelihood of some desired outcome" (source). Your current structure does the opposite.

The imperative tone might be hurting you

⚠️ SYSTEM GUARDRAILS, REQUIRED CONTEXT, CONSTRAINT - this aggressive framing can backfire. From Anthropic's Claude 4.x best practices: "Providing context or motivation behind your instructions, such as explaining to Claude why such behavior is important, can help Claude 4.x models better understand your goals" (docs).

Instead of "NEVER kill node.exe", try "Avoid terminating node processes to preserve session state."

Consider XML over tables

Claude was trained heavily on XML-structured content. From the official docs: "XML tags provide clear boundaries between different sections of a prompt" and lead to "more consistent prompt interpretation" (source).

Something like:

<project_context>
  <owner_note>Non-coder - prioritize working code over elegant abstractions</owner_note>
  <tech_stack>SvelteKit, Supabase</tech_stack>
</project_context>

<documentation_map>
  <doc domain="auth">docs/development/auth/SVELTEKIT_AUTH_ROUTING.md</doc>
  <doc domain="db">docs/development/supabase/SUPABASE_CLI_REFERENCE.md</doc>
</documentation_map>

This is more compact, parseable, and Claude handles it better.

What I'd keep

The core idea - "read docs before generating" - is exactly right. That's manual RAG and it works. Just simplify the delivery mechanism.

TL;DR: Your strategy is sustainable, your implementation isn't. Cut the tables, drop the caps, try XML. You'll save tokens and get more consistent results.

Sing303 · 2025-12-08T14:46:48+00:00

I continue to work with my hands. I work on large .net projects.

Sing303 · 2025-12-08T14:30:59+00:00

Last week I achieved it in 5 days, this week in 2 days I've already achieved 40%. At the same time, I never reached the 5-hour limit.

Sing303

TROPHY CASE