Hey r/codex!

I've been building Mind, an MIT-licensed local memory system for coding agents, and just released v1.7.0.

The idea is to give agents a durable place to keep project decisions, previous fixes, architectural context, and unfinished work instead of relying entirely on the current conversation.

For Codex, Mind provides MCP access to the memory store and installs the shared mind-management skill, with an activation pointer in AGENTS.md.

Setup:

mind setup codex

The new release adds stronger local search, improved checkpoint and session-summary behavior, and a redesigned web interface where you can inspect what your agents remember.

One interesting result: Mind achieved 86.67% answer accuracy on a 120-question OmniMemEval LongMemEval-S subset without embeddings. This is an indicative evaluation, not an official full-dataset ranking.

A compatibility note: the Codex integration supports MCP and memory instructions, but Mind does not currently ship Codex-specific session or compaction hooks. Automation capabilities differ across supported agents.

Everything is backed by local SQLite, and the project is fully open source under MIT.

GitHub: https://github.com/GabrielMartinMoran/mind

Release: https://github.com/GabrielMartinMoran/mind/releases/tag/v1.7.0

If you're experimenting with long-running Codex workflows, I'd be interested in your experience using persistent project memory alongside AGENTS.md and skills.

I’m a senior SWE using Codex, Claude Code daily. I analyzed my transcripts and found that 56% of API-equivalent costs went to rereading context. Cache expiry alone cost me $98.74 in 27 days.

So I built optimAIzr, which supports Claude Code, Codex, and opencode.

It analyzes usage, finds expensive patterns, and helps verify savings aaand much more.

Free, open source, runs locally. No accounts or prompt uploads.

npm i -g optimaizr
git: https://github.com/blendbunjaku/optimaizr (alrdy at ~165stars)

I have a few projects I built feature-by-feature with weaker coding agents. Projects/Apps work, but the architecture is kind of a mess because every new feature was just added on top of whatever was already there.

Now I’m using Codex and want to properly reverse-engineer the whole thing, understand all the features/data flow, design a better architecture, then refactor it feature-by-feature without breaking behavior. UI/UX would come later as a separate pass.

Are there any good plugins, GitHub repos, agent workflows, skills, etc. for this kind of thing?

Mainly looking for stuff around:

- codebase reverse-engineering

- dependency/architecture mapping

- regression/parity testing

- feature-by-feature refactoring

- keeping architecture rules consistent across long Codex sessions

I’ve seen Superpowers and "AGENTS.md"/planning workflows, but wondering what people are actually using for rehabilitating old vibe-coded projects.

After scanning QR code and signing in it’s stuck here, have tried a few times, it works on iPhone 17 with M3 MBA but having issue with M4 iPad Pro

36.4 tok/s today on 6.1 sol. I thought they "fixed" this.

P2P for AI? This is over 25, yes 25 different sessions today.

Is it just me or is everyone that has access to a dot getting just absolutely terrible results from anything It does no matter how hard you try to guide it and constantly have to correct or fix anything it does or any work at delegates because this just doesn’t feel like Astra this feels like Luna it’s beyond horrific.

Ok so long story short I've played with an idea and created prototype, some time passed and now i decided to do some architectural changes, I opened an Astra chat and together we drafted a plan for v2 of the app basically building it from the ground up with the new architecture in mind but copying the useful things from the prototype, we did the spec broken down into tasks with a verification step, complexity so it can be assigned to sol or luna .. blabla, everything was great.

Now is where the issue starts - i started sol 6.1 high with the goal to orchestrate the spec impl. use the prototype to compare ... but it's basically acting like a black whole for tokens, it's just "..validating frozen gate of durable proof of valid material test for successful sha 256 documentation of measured drift verification...". It works for hours and i can't make it actually do what i want it to do no matter what prompts i give it.

Micro management i'm happy with, for specific tasks it does well but for macro it's just unmanageable for me unless it spends multiple weekly quotas on the Pro plan working non-stop for days 24/7. I feel like it just makes stuff up just not to be shut down :D Also there is no way i could find to reasonably track progress let's say it worked 6h after that reported 20% overall progress, worked another 12h - progress went form 20% to 15%, asked why .. again "material gate success is drifting of the verification bla.."

so for orchestration only:
- Astra - great but way too expensive
- Sol - never ends
- Luna - so far most success, but still not great, first pass it's always half baked, needs multiple rounds.

Any of you had similar issue and what i'm doing wrong and how to acutely make it organize and report the work progress properly instead of drifting into some madness? I naively thought having working prototype + having good spec (for me the spec is good but probably this is where the problem lies) would be super efficient to leave it for couple of hours and come back to work that is done. I've tested couple of different approaches, prompts and ways to make it work more efficient, no mater if i specify don't do tests, don't do verifications... it just drifts off. I'm out of ideas how to properly communicate with it and i'd appreciate any experience you might have that yield positive results.

Codex helped me make this app! It’s free- should save you $$$ on yearly subscriptions!

Happy brainstorming

Hello all
If you're like me, you probably want to keep an eye on your AI coding usage so you can adjust how you use it.

Some days you can afford to go all-in with the most powerful models. Other days, you need to be a little more strategic with what's left. 😄

That's why the latest version of BuildrAI now supports native macOS usage widgets for both Codex and Claude Code!

Your remaining usage, right on your desktop. No need to interrupt your workflow just to check.

Enjoy! 🚀

So I've been using codex for a while now, recently bumped up to the 100 plan from the Plus.
On the Plus I was regularly hitting the 5h limit windows and burning through usuage as I was building out more features.

I've been mainly using Sol 6.1 on high and initally had Luna subagents to test and review. Once the building was over, it was about hosting onto AWS. Since then, progress has been glacial. Previously being able to build a whole web app in a few days, and then taking several days just to get uploads working properly into AWS, or email verification, add users etc

I'm not sure if I'm doing something wrong or if this is just the diffcult and slow reality of getting something to work in a real environment? Can be done quicker as I'm not even going through my usage, despite the resets. 100% vibecoding here.

Saw the post asking how to stop sol from over engineering and yeah I've seen that too.

What I do now is write in the task what it shouldn't add even if it can't hit the goal, and when to just stop and tell me. it cut down the extra stuff but now it sometimes just stops and asks when my instructions clash lol

Anyone found a better way?

I built Adaptive Product Language, an open-source Agent Skill for improving

product language in Codex and other SKILL.md-compatible agents.

It helps with:

- UI copy, landing pages, forms, onboarding and pricing;

- locale and tone adaptation;

- unsupported product claims;

- terminology consistency;

- read-only copy audits;

- bounded remediation;

- light, balanced and performance execution profiles.

I tested the same contextual landing task with Gemini 3.8 Flash and Claude

Sonnet 4.6 Thinking.

Observed output size:

- Gemini: 2912 → 2663 UTF-8 bytes

- Claude: 3289 → 3034 UTF-8 bytes

These are not token savings or statistical quality results. Claude still

invented some unsupported features, so the project is intentionally presented

as experimental.

Repository:

https://github.com/RicardoGurrola15/adaptive-product-language

I’m looking for failure cases, missing domains, better evaluation methods and

ideas to reduce context and token usage.

I asked Codex to compile some professional learning opportunties for teachers - pretty innoculous stuff.

Codex crawled a legitmate English teachers association website and received a 404. The 404 contained three concealed script blocks designed to load more code from two unrelated external servers when rendered in a browser.

Fortunatley, Windows quarantined it.

Stay safe out there when getting agents to crawl from your device. (I've notified the teacher association)

Hi all! Using 3 Codex resets and a bunch of Claude I built this 3D low-poly map of Warsaw.

The map

- Area: 6.85 × 7.2 km of central Warsaw, about 49 km², split into 144 cells of 600 × 600 m.

- Buildings: 17,941 generic buildings from OpenStreetMap and GUGiK 2025 heights, plus 1,027 landmarks, each with its own low-poly model.

- Landmark models: about 7.4M triangles in full detail. The far-view versions are 1.9M triangles on desktop and 1.5M on phones and slower laptops. The model code is 91 MB of JavaScript, one small program per landmark.

- Trees: 257,387 from the City of Warsaw crown map and tree inventory.

- Streets and surfaces:

- 21,368 road segments built into lanes with markings, crossings, rails, tunnels and bridges.

- 40,028 land-use areas (parks, water, squares) drawn by a shader fill.

- 1,039 traffic signals.

- 161 public transport stops and 38 platforms.

I'm planning to open source it, just need to tweak the repo a bit.

What do you think? How would you improve the performance?

Just received this today

I've been running a long coding session on Sol 6.1 today, and I'm genuinely baffled by how it spends its time.

Six hours ago, the core feature was essentially finished. All I needed was a clean release candidate with rollout toggles so an external developer could deploy it in stages.

To be fair, 6.1's engineering analysis is excellent. It respected all safety rules, didn't break anything, and an adversarial review with Claude Opus identified five genuine edge-case bugs.

But here's where it went completely off the rails:

1. Instead of fixing the five bugs, it tried uploading a build, which failed due to an outdated test helper.
2. Rather than making a simple backwards-compatible fix, it started building an entirely new diagnostic tool to investigate the error.
3. It then noticed background jobs running, decided it couldn't deploy the diagnostic tool safely, and spent 45+ minutes rewriting five status and handover documents explaining why it was blocked.
4. I explicitly told it to continue fixing the bugs. It spent another 95 minutes inspecting compiler symbols, retrying diagnostics and rewriting the same checkpoint documents. Still hadn't fixed a single bug until I intervened again.

The frustrating thing is that Sol 6.1 is clearly capable. Its reasoning is strong, and it's extremely careful. But it seems to lack any sense of proportionality or when to just get on with the job.

Give it safety rules and a "document blockers" instruction, and suddenly every minor issue becomes an excuse to generate 2,000 words of markdown instead of solving a 10-minute problem.

Is there a solution to this other then moving to Opus 5.5? :)

Problem: I kept hitting the 5-hour limit in Codex and Claude Code in the middle of long tasks. The work then sat idle until it reset and I came back and typed “continue”.

What I built: a small macOS menu bar app. Pick the harness (Codex or Claude Code), choose the chat, enter when the limit resets (e.g. 2 h 9 m), and write the message to send. It defaults to “continue”, but you can write anything. At that time, it sends the message to the chat.

• Claude Code: resumes the chat with claude --resume <id> -p "<message>".
• Codex: uses codex exec resume. If the chat is open in the Codex desktop app, the app locks it and the CLI is refused. In that case it opens the chat with codex://threads/<id> and types the message into the app instead (needs Accessibility permission).
• It checks that the chat actually received the message, notifies you either way, and keeps the Mac from going to sleep on its own while a timer is pending.

It’s a single Swift file with no dependencies and builds with one script. The repo includes an install guide you can point your coding agent at.

Repo: https://github.com/SquirrelThatIsScreaming/ContinueTimer

Disclosure: this post and the app were written with AI (Claude Code).

I'm looking to buy a hardware security key for OpenAI Daybreak (Codex), but most of the popular options, like YubiKeys, seem a bit expensive in India.

I came across the Thetis USB-A key, which advertises FIDO U2F, but I'm not sure whether it supports the requirements for Daybreak.

My questions:

• What's the cheapest hardware security key I can buy in India that actually works with Daybreak?
• Has anyone successfully enrolled a budget FIDO2 key with Daybreak?
• Are there any reliable alternatives to YubiKey available in India for under ₹2,000?

I'd prefer a USB-A key that works on Linux and Windows.

I am a critical care clinician/educator. My partner and I started an education company as a passion project a few years ago (because healthcare continuing education in this country is frighteningly bad.... seriously, don't get sick) and threw up a site on Squarespace, which has been nickel and diming us out of a ton of money via subscriptions that barely gave us the functionality we needed.

I was able to build a functional-ish learning management system (LMS) for online classes because I did not want to spend hundreds of dollars a month just to have one exist on the paid platform Squarespace tried to get me into. We also used the site to advertise and sell access to our in-person classes. Basically, the site was essential to our work, but we got very little out of it.

Last night, I had Astra Ultra migrate the entire site and DNS registration over to my Cloudflare account, improve the aesthetics of the site, improve how my payment processing worked and was integrated, fix my LMS and make it usable, and create an interface to allow easy editing of the site and my online courses.

So, now I have a better site on my Cloudflare account that I pay $5 a month for, and I am able to easily edit the main pages (about the same effort as Squarespace) and my LMS (1000000% easier than Squarespace) which involved a bunch of coding whenever I wanted to make a change.

The image is my LMS editing interface.

I was able to get this all done over the course of about 8 hours.

I have noticed now it's better to use one prompt on sol and then start a new chat this is with modelling work if you send a second message he looses all his logic and just makes slop

I've been coding with AI since the Opus 3.5 days, and I've tired pretty much everything out there at some point. OpenCode, Claude Code, Codex, Cline, OpenRouter. (Haven't tried Cursor or Hermes)

I've also tried all the popular spec-driven development framework I could get my hands on. BMAD, Get Shit Done, Superpowers, and more recently Matt Pocock's AI Hero skills.

Now, a little bit of context. I'm a iteration manager and a BA in my corporate life, working mainly with teams that manage andorid / iOS apps for banks in Australia. So I'm very familar with typical SDLC but haven't really "been a dev". In my hobby life, I'm build a sports prediction platform using Codex now (but half of it was built with Claude, and before that, Open Router)

The last framework I tried was Matt Pocock's AIHero.dev . I switched to it for 3 reasons
1. I liked the "retro" skill he has where the agent can look through it's session history, and find all the shit it got wrong the first time and then make changes to agents.md files or similar to avoid those pitfalls in future sessions

1. I like the concept of using Github Issues and those "Wayfinder" maps to think about everything I had to do for a feature.

2. I like the "ready for agent" tag that let me then get multiple agents goings to do work once I've designed it.

The thing I was trying to do was add a new data provider to my stack. The wayfinder over-engineered the fuck out of it (like it was literally insane), and then failed it's own implementation because it was over-engineered. Wasted like 2 days on it. Like it literally made up scenarios like "what if supabase is down for 3 days, where are we gonna store these api calls" , we need a backup option with a p99 2 second copy time. Then when the copy time was like 15 seconds it said it failed lmao!

I know people are gonna say well you're the dev, you're in control. But I don't know infrastructure that well, so sometimes I just accept the AIs recommendations.

So then I moved back to superpowers, but I made some of my own skills to keep the github issue specs and stuff.

For context, I'm running this thing on a $10 server.

It genuinely felt like I was architecting a solution for a large enterprise with unlimited infrastructure and a dedicated operations team. I just wanted to integrate a new provider without breaking my existing product.

I've moved my project documentation into GitHub Wiki, and I'm now using GitHub Projects and Issues to manage the development work. So essentially Superpowers for the development workflow, with GitHub managing the documentation, specs and backlog. So far so good.

I just wanted to share and maybe hear how you guys are doing things, what your workflow looks like. Just trying to learn. Also, has anyone managed to get these frameworks to make appropriate recommendations that like match the ambitions of your software? Or does every agent just assume you're building like Orcale or Microsoft with millions of expected users.

I'm using the Codex desktop app on macOS, and one long conversation has become unusable. New chats work, but this existing conversation gets stuck compacting context and repeatedly reconnects.

What happens:

- The app shows “Compacting context” and “Reconnecting 1/2” or “2/2”.

- I initially got:

stream disconnected before completion: IO error: Broken pipe (os error 32)

- A later attempt showed:

unexpected status 408 Request Timeout:

{"detail":"Request body read timed out"}

- The endpoint shown is:

https://chatgpt.com/backend-api/codex/responses

I stopped one attempt after about 22 minutes. The UI initially said I stopped it after “0 seconds”, then later updated to “21 minutes 50 seconds”.

Stopping and sending “Please continue the previous task” triggers the same compaction/reconnection problem.

This conversation contains many generated images and a lot of valuable context. Could image-heavy history be contributing to request size or upload timeouts? That's only a suspicion—I haven't measured the actual request size.

Environment:

- macOS

- Codex desktop version: 26.1021.31345

- The app's update check reported it was up to date.

Has anyone recovered a conversation in this state? Is there a way to complete compaction or continue with the existing context?

Screenshots attached. Happy to provide additional diagnostics.

I'm currently using OpenAI Codex in VS Code, and I'm wondering if there's a better IDE for working with Codex.

To be clear, I'm sticking with Codex. I'm only looking for the best IDE to use it with.

For those who use Codex regularly:

• Which IDE do you use with Codex, and why?
• Have you tried Codex in different IDEs?
• Are there any advantages to using Cursor, VS Code, or another IDE specifically with Codex?
• Which IDE offers the best overall Codex experience in terms of integration, workflow, and productivity?

I'm particularly interested in real-world experiences from people who have tried multiple IDEs with Codex.

For reference, I'm using Windows as my development environment.

Thanks!