@thsottiaux Think it’s related to memory processes, combined with some random windows or chrome overlapping bugs. The dependencies are causing background services to spin up, fill SQLite stores, confuse agents & create bad code. Users then try to fix bad code… rinse, repeat.
@PhiUnit chrome extension has runaway calls combined with codex inability to manage memories causes background processes to spiral, sqlite store to explode and your chat fails/confused/makes mistake/writes old memories into new work. I would be very cautious.
Codex now works directly in Chrome on macOS and Windows.
It’s even better at working with apps and sites in Chrome, and now works in parallel across tabs in the background without taking over your browser.
To get started, install the Chrome plugin in the Codex app.
@RealEverNever@nickgaiski@thsottiaux Its still not really fixed. they patched 1 issue. it's widespread. codex & codex memories cannot handle real coding. it's just a wrapper for vibe coding
think i solved my codex 5.5 issues!
it's bad memory compaction & concurrent handling of runtime processes. especially if you're building an app with various surfaces (cli, mcp, api, etc.), codex memory gets confused and throws instructions everywhere.
fun!
@DevAdventur3s@thsottiaux its not even just speed, its that codex is choosing to elevate old threads (even archived) if it thinks its relevant. even if thread counteracts what you're currently working on. codex memory is broken.
@thsottiaux background hidden logic on cache/threads/memory. spent 2 weeks debugging all runtime surfaces with custom monitors. found that the active Codex Desktop/app-server has a stale prompt state in memory & continues to write it back to .codex even when i try to clean it up.
I analyzed over 10 million lines of public data to build a (free) tool for NYC renters.
You can check any building across all five boroughs.
It consolidates rent stabilization records, bedbug, pest, and mold reports, and management company patterns.
In the last 5 years across NYC apartment buildings:
- 43% had immediately hazardous violations
- 39% had confirmed bedbugs
- 34% had mold complaints
Some features:
- rent stabilization status
- bedbug, pest, and mold reports
- a 0-100 health score for every building
- data aggregated by management company
- search by any address or click into a neighborhood
check your building before you sign.
https://t.co/Mb4SBmLfJH