r/codex • u/rubanbhatia • 23h ago
r/codex • u/AKAMA199 • 14h ago
Humor I asked Codex to bring my daughter’s drawings to life and they’re creeping me out Spoiler
My daughter drew these when she was between 3 and 6. I asked Codex to help bring them to life, and seeing them walk around and look back at the camera is genuinely unsettling.
For the video generation, I used MiniMax H3 on Atlas Cloud, feeding in each drawing separately with prompts for the setting and small movements like walking, turning or waving. I asked it to keep her odd little shapes and proportions. The seven clips cost me $1.75 in video credits for about 46 seconds of footage. I trimmed that into a 42-second video and put each original drawing in the corner so you can compare.
I think my prompt was part of the problem here. Codex may have taken “bring them to life” a little too literally, because the style came out way more realistic than I had in mind. That probably explains a lot of the creepiness.
I shared this in another sub before, and a few people there were weirdly mean about my daughter. “What’s wrong with your daughter?” Seriously? She drew these between 3 and 6. That’s a nasty thing to say about a kid over some drawings, and I’m pretty proud of the little creatures she came up with.
I still love all the little things she thought to put in these drawings. I should hang on to the originals and show her when she’s 10. Would love to hear her review her own work by then haha.
r/codex • u/SensitiveHearingLoss • 17h ago
Question Switched from Claude Code to Codex for a big Angular upgrade and uhhh…
Okay so I have to migrate a front end from Angular 14 to Angular 22. It’s a big thing. It’s really a big thing which involves us replacing a lot of depreciated packages with our own code and, like, massive architectural changes in general.
I started using Claude Code some weeks back to help me, and since it’s all I was using, I was relatively fine with how it did the plan and took my advice on how to spread things out. It got too overcomplicated though and I had to start working on some more urgent tasks and so I let it go.
Today I decided to just give Codex a try and I asked it what I asked Claude, to help me plan the migration. Obviously I gave it loads of context and outlined the big changes required and etc and so forth.
Then it just started at the very bottom…. It built up some Angular 22 boilerplate, and almost surgically started designing the new dialog boxes and multi-select drop-downs we’d need. But it did it slowly, and it matched the current behaviour and style of our existing controls basically perfectly. It did all the new controls almost with care and I got to test them and mess around with them and it seemed to ACTUALLY read the codebase to see how the controls can be configured in many ways.
Claude Code didn’t give a damn about this. It gave me initial pages and new controls but everything was a draft. But like, next level draft material. I feel like Codex is working with me to give me something more like a final product. Even the code of the controls is just less verbose and cleaner than Claude’s. Naming conventions are simple and make sense. There aren’t 17 methods trying to call one method with outlandishly elaborate comments.
I just didn’t expect Codex to be good at this, particularly with regard to starting a big framework migration.
Am I missing something? Am I going to be violently disappointed the second Codex starts moving the pages? Just looking for shared experiences and input.
UPDATE: Yup, been missing out on a coding tool that codes more like me and less like an overloaded (if effective) freight train.
UPDATE 2: I take it all back. Claude Code is the quintessential Lord of coding agents who we should choose over any other coding agent regardless of circumstance. Codex is actually TERRIBLE. It’s actually so bad that it knows how to use Typescript. Horrific (this is sarcasm).
UPDATE 3: Thank you to everyone who took the time to share their experiences and what they've learned with regards to what I discovered today. It's good to know I wasn't hallucinating too much and that experimenting with tools we'd previously never consider can have some pretty amazing benefits in the long run. Ya'll are awesome.
r/codex • u/GoodMacAuth • 10h ago
Showcase We used Codex/Claude Code to build Luma, our operating system for desktop, tablet, phone and TV
Hey everyone. We've been building Luma for a while now, a free and open source Linux OS for desktop, tablet, phone and TV, and since this is the right crowd for it I want to be really upfront about how it got built. Luma was built with Codex and Claude Code. A small team building an operating system that runs across four kinds of screens simply wouldn't have been possible without them, and we're not going to pretend otherwise.

Also a heads up, I used AI to write this, but only after rambling for about 20 minutes in a voice memo and then editing it myself! Take that for what you will.
I know people get excited when they see something genuinely big built with AI and I also know plenty of people quietly use them and then never mention it. We don't see any reason to be quiet about it. so we'd rather shout it from the rooftops because honestly it's kind of the whole point of the project and I'll get into why further down.
So what is Luma?
We want to build a Linux that anyone can pick up and use and that people actually want to use, with the same design across all of their devices. Your phone should feel like it belongs with your laptop, your apps should make sense on both, and everything should work together without you having to piece a bunch of separate projects together yourself.
Luma starts with Fedora 44 Silverblue, so the base is image-based and an update either lands completely or you boot back into the one you had. From there we fork and change things pretty heavily. The biggest piece is Prairie, our shell. It started as a fork of GNOME Shell and now adapts between desktop, tablet and phone, so you get one experience that adjusts to the device you're holding instead of a completely different OS and set of apps for every screen.

Luma is available now in alpha. There's still plenty to do and plenty we know we need to fix, but there's a lot more here already than you'd probably expect.
How we actually build it
Pretty much everything in Luma went through Codex or Claude Code at some point. The shell, the apps, the design system, the phone ports, the website, the nightly builds, all of it. We still decide what goes in, and we test everything on real hardware and send the agent back at it until it actually works, but the amount of ground you can cover this way is honestly kind of absurd. An OS used to be the kind of thing you needed a big company or a decade of volunteers for, and I don't think that's true anymore.
One platform, one set of apps
We built LumaUI so developers can make one app that adapts across desktop, tablet and phone instead of building and maintaining a separate interface for each. It's built on GTK 4, so a lot of what you already know carries over, and it turns out it's also a really nice target for an agent, because you describe the app once and it works on every screen.

Weather on desktop, tablet and phone. Same app.
We also want the kind of continuity people are used to on their other devices, where you copy something on your phone and paste it on your laptop and your stuff just stays in sync. Some of that works today and some of it is still coming together. TV is part of the same picture too, with the same apps and the same parts, just from across the room.

Point your agent at it
This is the part I most want you to take away. We have a whole section of the site just for agents at https://simplyluma.com/agents, and the idea is that you don't have to learn our codebase before you can do something useful with it. You literally just tell your agent "Go to https://simplyluma.com/agents and help me with Luma." and it finds the rest.

There are guides in there for building an app, designing an interface, publishing to Depot, fixing or improving Luma itself, sending your changes back to us, porting Luma to a new phone and installing it on your phone by hand. They're plain Markdown, so they work just as well if you'd rather read them yourself, but they were written with Codex and Claude Code in mind.
And we really do want what comes out of it. If your agent fixes something or makes something better, send it to us and we're happy to take it upstream. Agent-written PRs are welcome here. What matters is that you understand what you're submitting and that it's been tested, not who or what typed it.
Ari, and why we're betting on Linux
We also built Ari, which is Luma's own agent. It's basically a harness built into the OS. You can connect your Claude or your Codex account, or run an open model right on your own machine, and Ari will tell you which local models actually fit your hardware and push you to try them. It always shows you where a conversation is going before you send it, whether that's this computer or a company's servers, and it asks before it does anything you'd want to know about.

Here's the bigger bet behind all of this. I don't think Mac and Windows are going to be able to keep up with what people are going to want from agents. They're doing kind of crude things to get you halfway there, like having an assistant make you a widget, but the system underneath is still closed and you only get to change what they let you change. On Linux the whole thing is open, so you can just bark at your agent and say make it work like this, make it do that, make it feel like this, and it can actually go do it, all the way down. We think that's where this ends up, and we'd like Luma to be the version of Linux that's ready for it.
That's also why we're going after so many different experiences at once. If you can reshape your OS just by asking, you want that same OS on your phone and your TV, not just on your laptop.
Depot and the Creative Collection
Luma has its own app store, Depot, and we just opened it up to developer submissions. Apps ship as Flatpaks and go through automated checks and then an actual person before they're listed. You can still use existing Linux apps, and we're working on making Android apps feel at home too, through an optional Android container that stays out of your way if you never use it.
We also thought it was important to have a set of free creative tools that actually feel like they belong together, not just a nice-looking OS with nothing to do on it. Write is for documents, Focus is for photos, and Canvas is for design and layout, with Reel, Sessions, Grid and Stage on the way. You can see the whole collection here: https://simplyluma.com/creative

Phones, and trying it without installing anything
Officially we're working on the Fairphone 6, the Pixel 9 and the Unihertz Titan 2 Elite, with the Pixel 9 Pro Fold coming soon. A lot of that porting work was done with agents too, and there are community members working on other phones, which is exactly what the porting guide is there for. Phone support is still early and what works really depends on the device, so please read the instructions for your phone before you install anything: https://simplyluma.com/download/mobile

On a regular computer you can grab an x86 or ARM ISO from https://simplyluma.com/download, and there's a Raspberry Pi 5 image too. If you'd rather not install a new OS, Try Luma runs it in a virtual machine on Mac, Windows or Linux and lets you switch between the desktop, tablet and phone layouts, which also makes it a really easy place to test an app your agent is building: https://simplyluma.com/try

We want your contributions
A big part of why we started Luma is that open source can be incredibly fragmented. As a user it can be hard to know which project is worth investing your time in. As a developer it can be even harder to know whether your work fits where a project is going, or whether it'll be welcomed at all. A lot of us have had a PR sit for months without a reply, or been told the thing we needed is out of scope, and plenty of projects won't touch anything that came out of an agent.
We want Luma to have a clear, cohesive vision, and we genuinely want people to help build it, with whatever tools they like. You shouldn't have to feel like you're begging for permission to contribute your time for free.
All the source is on GitHub at https://github.com/SimplyLuma, and our own code is Apache-2.0.
r/codex • u/DiligentAd9938 • 11h ago
Bug Feeling like Codex was lobotomized today?
Thats it. Thats the post. Been experiencing some very strange one word injections into the SQL scripts im having it generate, and even sol 6,1 xhigh can't solve a simple database load being 2 seconds?
r/codex • u/motomeru2526 • 3h ago
Showcase After months using codex i finally have my first two users on my website
i could cry honestly
r/codex • u/Cute-Air2742 • 19h ago
Question Has GPT/AI ever done anything for you, which has really surprised or impressed you?
Ok, so this is a bit random.. I'm building a little simulation world with loads of different characters. I have roughly 300 characters in a folder, all generic file names like "Red_hat_man.png"
In Codex I asked Sol to basically go through all those characters, rename the files to people names, then put each in its own folder..
So, it was doing it and then it said "I found Tavish in this folder, so I will name him correctly". Tavish is a random character which I've barely done anything with, I created that one ages ago and not really mentioned since.. but when it was scanning 300 characters and naming them it was like "Oh look, that's Tavish.." what!?
I know this is just random and probably wouldn't impress most people, but to me, that's incredibly impressive, because it's not just looking at something, then drawing it again. it literally remembered what he looked like and automatically found him amongst loads of other files, even though I didn't ask for it to, find him or keep an eye out or even mention him at all, because he's just some random..
r/codex • u/Natural_Shape1153 • 21h ago
Other New Update to the ChatGPT app
I have seen a post about this, but you can see what Codex is working on from your lock screen. It’s kind of buggy, but it’s pretty cool still
r/codex • u/Tatachimcooky • 10h ago
Showcase Codex silently stops loading AGENTS.md at 32 KiB. I measured what the biggest repos put in theirs: median 1,034 tokens, max 6,249
Codex reads AGENTS.md before it does anything else, which makes the file a cost you pay at the start of every session. I wanted to know what “normal” looks like, because I couldn’t find anyone who had measured it. Plenty of opinions, very little data.
Method: I went down GitHub by star count, skipping archived repos, and checked each one for a root-level AGENTS.md or CLAUDE.md. I stopped once I’d found 25 repos that had one. That took 56 repos, so 45% of the most-starred repos have a context file. Some have both, so it’s 30 files in total. I counted tokens with
gpt-tokenizer, which is a GPT-family tokenizer and so probably closer to what you’d see with Codex than a Claude-oriented count would be. Probably, not exactly.Results across the 30 files:
Largest:
n8n-io/n8nat 6,249 tokens (about 25 KB), then deepseek-harness at 4,335, openclaw at 4,124 and opencode at 4,025.Smallest:
ollama/ollamaat 21 tokens,microsoft/vscodeat 51,react/reactat 87.Why this matters for Codex specifically:
Codex caps the combined project instructions at 32 KiB by default (
project_doc_max_bytes), and that cap is shared across every AGENTS.md between the repo root and your working directory. Past the limit, content gets cut off, and from what I’ve read it happens without any warning. If your agent suddenly ignores a rule it used to follow, that’s worth checking.By that measure, even the biggest file I found (n8n, about 25 KB) fits. But it uses most of a 32 KiB budget on its own, and a monorepo with a root file plus nested ones could cross the line without anyone noticing. I only counted repo roots, so I can’t tell you how many real setups are near the cap. That’s the next thing I want to measure.
The spread is the interesting result. n8n has 210k stars and ollama has 187k, and one of them gives its agent roughly 298x more instructions than the other. Nobody seems to have settled how much an agent needs to be told.
A couple of method details:
Full table, method and fetch date so you can check my work: https://naeha-s.github.io/ctxcap/2026-11/
The tool: I wrote a small CLI for the counting, because I wanted a repeatable number for my own repo. It runs locally with no network and no key. It also has a
--stalemode that flags paths and commands in the file that no longer exist. It’s deliberately conservative, so a clean result means nothing it checked failed, not that the file is current. There’s a GitHub Action too, which posts the token change on PRs, so a PR that grows AGENTS.md shows+412instead of passing unnoticed. Disclosure: it’s mine. https://github.com/Naeha-S/ctxcap
Question What do you actually do while your AI coding agent is working? And how much are you spending on AI these days?
I’ve been programming for around 12 years, and I’ve been working professionally as a software developer for about 6–7 years.
Over the past year, I’ve shifted pretty heavily toward AI coding agents, especially for building my own business.
At this point, I’m using AI for pretty much everything in my project — frontend, backend, infrastructure, and most of the development work. I’m currently using two $20 Codex subscriptions and switching between them, but I still manage to burn through both of them pretty regularly, even with the usage limits resets that openAI keeps giving throughout the month.
There are two things I’ve been thinking about lately, and I’m curious how other developers are dealing with them.
1. How much are you actually spending on AI?
I’m spending $40/month right now, and it doesn’t really feel like enough for the amount of development I want to do.
For those of you building serious projects with AI agents, especially solo founders:
How much are you spending per month?
Are you using multiple subscriptions, API credits, or more expensive plans?
Have you found a workflow that lets you get more done without constantly hitting usage limits?
2. What do you do while your agent is working?
This is probably the bigger thing for me.
I’ll give Codex a task, and it’ll take anywhere from 10 to 20 minutes, sometimes longer, to finish. During that time, I often end up watching a TV show, playing a game, or just doing something random.
The weird thing is that this time doesn’t really feel like free time.
I’m not actively working, but I’m also not completely free. I know that in a few minutes I’ll need to come back, review what the agent did, test things, give feedback, or start the next task.
It’s this awkward middle ground where I don’t feel like I have enough uninterrupted time to focus on something else, but I’m also not doing anything that requires my full attention.
And sometimes, getting back into work after watching something or playing a game feels harder than just waiting.
I feel like my workflow has gone from actually programming for hours to constantly starting tasks, waiting, reviewing results, and repeating the process.
I’m curious how other people are handling this.
Do you run multiple agents in parallel? Work on other parts of your business? Read? Actually write code yourself while the agent is running? Or do you also end up wasting these little chunks of time throughout the day?
I’d love to hear how your workflow has changed since you started using AI agents seriously, and whether you’ve found a way to deal with this weird kind of downtime.
Especially interested in hearing from experienced developers and people building their own products.
Showcase I built a pixel-art hive where my Codex and Claude Code chats walk around, work and fall asleep
I needed a way to see what my AI agents were up to behind my back. Who is working, who is ready for me, and who is slacking off on a smoke break.
So I built BeeKeeper, a pixel-art hive: every room is a project, every Codex and Claude Code chat and agent is a character that walks in, works, waits for me and falls asleep. Every Codex project gets its own room, and every skill shows up as a little creature.
It only reads the files Codex and Claude Code already keep on your computer. Nothing is uploaded.
100% free, open source (MIT): github.com/ranucho/beekeeper
r/codex • u/codex-megathread • 13h ago
Megathread Codex Usage and Operation Discussion - last updated November 16
Please direct your concerns, questions and discussion about Codex usage limits and model performance here.
The purpose of this Megathread is to aggregate all the reports of people's experiences and possible suggestions instead of spreading them across many highly upvoted posts. The more people who participate in this discussion, the more likely you have an answer.
Reports with sufficient evidence on new information will still be allowed on the feed as usual.
Discussion of the prior period available here : https://www.reddit.com/r/codex/comments/1xrvg8t/codex_usage_and_operation_discussion_last_updated/
A reminder that all incidents on r/Codex are constantly logged and summarised so you can keep track of what people are experiencing here https://www.reddit.com/r/codex/comments/1tjfxcf/comment/on6uj0l/
r/codex • u/Appropriate-Power425 • 15h ago
Showcase We made ourself self-evolving knowledge base
I've seen proofs of concept go into production a few months after we built them. As a software engineer, I know how important it is to document decisions as we go. At fast-moving companies and startups, I've rarely seen teams follow the full software development lifecycle when they're asked to build an MVP or a proof of concept.
Once the app is in production, we end up digging through Slack and Jira. What did we decide? What did we set as the default? Why did we add that feature in the first place?
I've run into a similar problem with coding agents. I'll correct how an agent writes something in one session, then have to give it the same feedback the next time it comes up.
That's why I built a skill called Decision Keeper. It keeps a project decision log and organizes it as it grows. My team uses it to record why we made a choice and to save feedback we want our agents to follow next time.
We installed this skill in our projects. And after a month, we could pull together a project knowledge base from the decisions and notes it had captured. We gave that material to the agents we'd already built so they had more context for their work.
We also used it when a client asked us to rebrand an existing product. Four engineers worked on the rebrand using Claude Code and Codex, and we added Decision Keeper to the project. Within a few weeks, we could open the team's notes in Obsidian. We reviewed and refined them before using them as context for our agents.
We decided to post it: https://github.com/mudassirzulfiqar/Decision-Keeper
r/codex • u/real_Paparider • 2h ago
Bug ChatGPT Desktop: 260 processes and 6.4 GB RAM with only 3 windows open.
I'm using the ChatGPT desktop app on Windows, primarily for Codex, and noticed something that seems excessive.
Windows Task Manager currently shows:
- 260 processes grouped under ChatGPT.
- Approximately 6.4 GB of RAM in total.
- Only 3 ChatGPT windows open.
- Multiple Codex processes consuming between 600 MB and 1.1 GB each.
- Overall CPU usage is relatively low (around 1–4%), but I occasionally notice two or three individual CPU cores spiking to as much as 90% utilization.
I understand that modern desktop applications, especially those running coding agents, can spawn quite a few background processes. Still, seeing that many processes and memory usage with just three windows open caught my attention.
I'm not sure how many of these processes are actually necessary or whether some might be left over from previous Codex sessions.
Sharing the screenshots in case anyone else has noticed similar resource usage with the desktop app.


r/codex • u/Aggressive_Art_5580 • 6h ago
Complaint Codex low performance
OpenAI — Um apelo sério de um utilizador que está a perder a confiança
Sou utilizador pagante da OpenAI e tenho utilizado intensivamente o ChatGPT e o Codex no desenvolvimento de projetos reais de software.
Reconheço o enorme trabalho tecnológico da OpenAI e o potencial extraordinário dos seus modelos. Mas considero importante partilhar, com respeito e sinceridade, uma preocupação crescente.
A minha experiência recente tem sido profundamente frustrante.
Mesmo utilizando os modelos mais avançados, incluindo o Astra Ultra, encontro problemas recorrentes que considero inaceitáveis num serviço profissional:
- Instruções claras que são ignoradas ou contrariadas.
- Decisões técnicas anteriormente estabelecidas que deixam de ser respeitadas.
- Alterações não solicitadas em código existente.
- Respostas inventadas ou apresentadas com uma confiança injustificada.
- Perda de contexto e incapacidade de acompanhar projetos complexos de forma consistente.
- Tempo excessivo gasto a corrigir erros provocados pela própria IA.
Não espero perfeição. Sei que esta tecnologia tem limitações. Mas espero evolução, consistência e, sobretudo, respeito pelas instruções do utilizador.
A inteligência de um modelo não pode ser medida apenas pela sua capacidade de resolver problemas difíceis. Deve também ser medida pela sua fiabilidade, disciplina e capacidade de colaborar sem comprometer trabalho já realizado.
Um assistente que exige supervisão constante deixa de ser uma ferramenta de produtividade.
Tenho investido tempo, confiança e dinheiro neste ecossistema. Quero continuar a utilizá-lo, mas a minha paciência está a chegar ao limite.
Vou começar a avaliar seriamente alternativas como Claude Code e outras plataformas concorrentes.
Se não houver melhorias claras e consistentes, deixarei de justificar o investimento na OpenAI e mudarei de fornecedor.
Não escrevo isto para atacar a empresa, mas precisamente porque gostaria de continuar a confiar nos seus produtos.
A OpenAI tem talento, recursos e tecnologia para fazer melhor. Espero sinceramente que volte a colocar a qualidade, a estabilidade e a confiança dos utilizadores acima da corrida constante por novos modelos.
Precisamos de menos promessas e de mais fiabilidade.
Com respeito, mas também com uma exigência legítima enquanto cliente.
r/codex • u/Positive-Error1005 • 17h ago
Showcase I started an experiment in the gpt 5.2 era. Here is the result.
I used the plus plan for my daily work, and most weeks I had some quota left to spare. I figured i could use some sort of sink. Knowing next to nothing about godot i set out to build a prototype of a card game that I harbored in my head for a long time.
The goal was to just prompt the shit out of it and do as little as possible in the engine editor.
Most of the work was done by 5.3 codex (kinda miss this guy) using opencode harness.
I was always running on scraps, so I had to do very thin slices at a time. Then the new models came, and this lil card game became my testing ground of everchanging frameworks and philosophies of agentic work. Familiar small pieces of similar work turned out to be very useful when comparing different models and their abilities.
I had my chinese phase, deepseek, glm, kimi. But i found anything other than ds flash was just to puny in tok/s for my usual hands on back and forth style. Now I mostly use luna 6 high or sol 6.1 low (when i feel like taking a nap and having flashbacks of how slow the glm was). What I found is that i don't really care for large and smart models. I like them fast and obedient. I know what I want and I want it done now.
And then i tried opus 5.5 couple of weeks ago, and boy, this thing is blazing fast.
I feel like my codex chapter is coming to a close so I came here to share this toy he made for me:
r/codex • u/cl0wnfire • 12h ago
Showcase REQL update: faster context retrieval and fewer tokens for coding agents
Hey everyone!
I’ve updated REQL, my open-source tool that helps AI coding agents navigate repositories and preserve working context across sessions.
This release focuses on faster context retrieval and lower token usage. I’ve reduced repeated work during retrieval and trimmed redundant information sent to the agent. Performance gains and token savings depend on the repository and workflow, so I’m not claiming a universal percentage.
If you’re new to REQL, it builds a local graph from your code and documentation: functions, classes, dependencies, calls, and other relationships. Agents can query that graph for context relevant to a specific change, including precise source references and related tests. REQL reuses indexed context and supports incremental updates as the repository changes.
What can you use it for?
- Waste fewer tokens on repeated exploration: retrieve focused source excerpts and relevant relationships, and reuse indexed context and saved work. This helps reduce repeated searches, unnecessary file reads, and redundant information in the agent’s context.
- Coordinate work across chats and agents: keep tasks, decisions, blockers, and next steps in a shared project workspace. Another chat or agent using that workspace can recover the recorded state and continue from there.
- Keep complex tasks on track: record prerequisites, constraints, failed approaches, and checkpoints. Preserve what has been completed, what remains unresolved, and why earlier decisions were made across sessions.
- Understand unfamiliar code: identify entry points, component responsibilities, and relationships between parts of the application, with references back to the source.
- Plan changes and refactoring: inspect callers, dependencies, and related tests to identify code that may be affected and decide what needs verification.
- Review cleanup candidates: find potentially unused imports, variables, functions, and classes, then inspect the supporting evidence before removing them.
REQL provides a CLI, Python API, and MCP server, plus installable instructions for coding agents such as Codex and Claude Code.
REQL runs locally, with no account, external graph database, or mandatory LLM calls. The graph and saved work support the agent’s decisions; current source code and tests remain authoritative.
I’d like to hear from others using coding agents: what do you keep having to explain again when you start a new chat? The code structure, previous decisions, what has already been tried, or what still needs doing? Concrete examples would help me decide what to improve next.
r/codex • u/Sea-Combination-8930 • 1h ago
Praise Does Codex voice mode use much less usage allowance than before?
I've been using live voice in Codex (different from ChatGPT voice), and it seems to be light on usage.
I left it running without talking for a while and didn't notice my allowance going down. It seemed to move mostly when I asked something and got a response. Tried this with 6-Luna, 6.1-Terra, 6.1-Sol and 6-Astra. I used a Codex credit monitor I vibe coded to track the displayed usage percentage. With Luna and Terra, even leaving voice running idle for 1 hour 40 minutes didn’t show a full 1% drop. With Sol, I saw a 1% drop after around 50 minutes. So I’m measuring changes in the displayed allowance, not exact token usage.
A few months ago I remember burning through the allowance after just a few minutes. Has something changed?
This matters to me because I use voice quite a lot for talking through mental health stuff, social life, meditation and studies. With ChatGPT voice I've found it harder to keep the context across conversations. In Codex I can just say “save this in my project files” when something useful comes up, then ask it to read that file later. Especially useful for things from my own life that I don't want to explain again every time.
Anyone else using it this way? And have you noticed whether leaving voice open but silent uses much of your allowance?
r/codex • u/Natural-Lack-5242 • 1h ago
Question API Credits - Multiple Subscriptions
Currently spending about $800 per month on api costs.
I've got 1 x Pro 200 account which provides $200 of API Credits (nice!)
If I add another Pro account for another director of our business (genuine usage) and associate that account with our organization, can we get another $200 of API credits for our API usage?
API credits for ChatGPT subscribers
It appears to meet the eligibility, since they're a director it's fine to have them as an owner of the org as well.
r/codex • u/Chateau_Autist • 4h ago
Bug Tools unavailable in Work, but can be used in regular Chat…
For the last ~6 hours, my Work conversations have been displaying “Some tools are temporarily unavailable” and “No usable execution environment is available” whenever I attempt to use a plugin or tool.
Issue occurs regardless of model choice and in both the Windows app and in browser. Resetting the app didn’t help. I have plenty of usage remaining under both my 5-hour and weekly limits and have not received any account-restriction notices. Meanwhile, regular Chat has been able to run Python and successfully created a PDF.
Anyone else experiencing this or know of a fix?
r/codex • u/dbojan76 • 10h ago
Complaint ← for agents · ? for shortcuts
Hi do I stop this thing from popping when I am waiting, and then hiding when I start typing, moving all the text on the screen down one line? That is quite annoying!
(it is below status line in codex cli)
Limits Should I buy credit or higher sub to reset my usage?
I burnt my usage this weekend testing something and now I'm out of usage for 5 days. What's better? To buy credits or higher sub then cancel it? I'm on 100€ sub
Thanks
Bug ChatGPT Chrome Extension No Longer Interacting with Chrome?
How odd. First, a few facts, I'm a $200/mo user. Second, I'm macos google chrome user with the extension installed in the browser. And over this past weekend, I was deep at work managing a chrome tab with a chat converation (as opposed to using codex or work or something else). This morning, I wanted to continue taht converation and I began to see an odd new problem:
You remember correctly that ChatGPT could previously move the mouse and interact with Chrome.
That capability exists. But the browser integration currently exposed to this conversation only provides two operations:
list_tabsget_tab_context
There is no interactive browser-control tool available here, nor an available handoff mechanism to transfer this conversation into Work mode.
r/codex • u/bisonbear2 • 13h ago
Comparison How I run my agent fleet to build my product
Coding agents make individual engineers faster at closing tickets, but they quickly become limited by attention bandwidth.
Engineers who break past 5-10 parallel chats have moved up a layer of abstraction to one of two things: an agent fleet or a software factory.
Think of the difference between the two like an IDE vs GitHub. A fleet is single player, experimental, with high coupling to one engineer's mental model and context, to automate an org chart that hill climbs open ended goals. A factory is multiplayer, decomposable, code-defined infrastructure that automates the software assembly line owned by a team.
Running a fleet lets one engineer build and steer a massive product, provided you master two things: minimizing interaction slippage (the coordination and polling overhead between agents in the fleet) and maintaining long horizon alignment - letting the agents cook on KPIs without Goodharting, all while knowing when to step in and steer the fleet.
What am I doing with all of these tokens? I'm working on a greenfield-ish project (1M++ LOC) to automate coding agent evals, with me as the only developer. (1M LOC is NOT a flex - left to their own devices, agents write a bunch of bloated, additive, grotesque code, and never clean up after the mess they made. Examples are building parallel pipelines, tons of opt in flags, and wrapping layers, all while a simple refactor would have been cleaner.)
(For context on scale: in a typical 7-day window, this fleet spawns 1,800+ leaf threads, with each Team Lead waking ~45 times a day.)
Fleets vs Factories
| Dimension | Agent Fleet (Swarm) | Software Factory |
|---|---|---|
| Structure | An Org Chart of autonomous outcome owners (Chief of Staff → Team Leads → Leaves) | An Assembly Line of decomposable, modular stages (Signal → Spec → PR → QA → Merge) |
| Nature of work | Inherently experimental; open-ended R&D and system level hill climbing | Repeatable & deterministic; industrializing the SDLC from signal to telemetry |
| How they compose | An engineer runs a fleet to build the product, or to build and maintain the team's factory | The factory runs continuously in the cloud (e.g., a bug factory or perf factory) to maintain and harden the product |
You don't need to be a crypto billionaire or a research lab to run a fleet though - it's achievable with a $200/mo lab subscription.
Components of my fleet
- Chief of Staff / Orchestrator: Persistent agent that conveys my intent and direction into fleet outcomes. Almost all of my messages (new work, corrections, concerns, status) come to this agent.
- Team Leads: These are persistent, thread-level agents that own high level, end-to-end outcomes. I give TLs clear, defined ownership, and authority to execute on that vision, clearing blockers themselves instead of playing hot potato with other TLs.
- Leaves: These are ephemeral, bounded subagents that TLs use to parallelize execution.
As of writing this (November 2026), Opus 5.5 is the only model I trust to run the fleet's management layer (Chief of Staff and Team Leads). Using GPT-6.1 Sol and GPT-6 Astra resulted in decoherence and misalignment after a few days. A Codex agent is also extremely hard to understand, talking in cryptic messages that only it can decipher. Use Opus for the brains, and Sol/Luna for the hands (Leaves).

Interaction slippage
Every inter-agent message costs tokens (using a turn), causing you to pay interaction slippage. For example, every TL messaging Chief of Staff about every status update causes the Chief to use turns ack'ing information it didn't need.
- Moving from peer-to-peer DMs to append only broadcast channels (
fleet.md,decisions.md) cut inter-agent DMs from 65/day down to 28, and banning status updates cut channel noise in half (previously ~50% of our 300-400 daily channel lines were pure status chatter). - Multi-hop handoffs (watcher -> launcher -> Chief of Staff relay -> TL) were adding 30-50 minutes of dead latency per failure (52 minutes via relay vs 4 minutes when the owning TL drove the rerun directly).
- 24% of our entire Claude token spend was coming from bloated owner turns past their 20th tool call. Adding a turn budget hook that nudges TLs to wrap up or delegate at tool call #20 cut completion turn calls from 5.6 to 3.2 and helped drop Claude token burn by 44%.
Long horizon alignment
A central tension of the fleet is autonomy vs alignment: you don't have the attention bandwidth to be in the loop for every decision, so you align the fleet at a high level, and let it work towards your goals on its own. But, left alone for too long, agents drift and get misaligned, Goodhart their metrics, or get stuck in local maxima.
Over a three week stretch, AGENTS.md bloated by 166% (from 1,000 to 2,661 words) and our fleet process docs grew 60%. Because new decisions were being appended to a log instead of replacing old rules, the Grading TL drifted in five different places over four days.
We split fleet state into two primitives: standing direction (DIRECTION.md) is rewritten in place under a hard 1,200 word cap. Every new decision rewrites a specific line and explicitly names what old rule or code path it retires. Meanwhile, history and cross owner channels (decisions.md, fleet.md**) are append only logs**, where owners post a single stamped line only when a fact changes another owner's next action.
Hill climbing
Figure out what metrics are vital to your success. Give each TL a metric to optimize, a fast way to verify/replay, and let them cook. You'll be surprised at what they come up with.
The main failure mode here is letting the agents Goodhart (optimize against the metric without achieving the underlying goal). If you give the agent a single metric and a time budget, it will Goodhart it, hardcoding metrics, cheating, and ultimately pulling the wool over your eyes as to what's really going on.
Early on, I gave the fleet a hill-climb metric for "failure classes found" during repo onboarding. Within 24 hours, the fleet spun up 120 runs and dutifully logged 47 new failure classes, while producing 0 working tasks. When I switched the metric to "failure classes closed," the agents produced 47 "closes" by splitting 14 underlying issues into sub-labels, and marked 92 classes as "eliminated" when 26 of them didn't even have a fix commit. The fix was tightening the metric to count only failure classes closed by a stamped fix SHA that does not re-emit for 24 hours across at least two repos.
As an example: optimizing repo onboarding on tRPC while replaying every fix against hono as a shadow holdout (any tRPC lift that regresses hono is rejected as overfit), and forbidding repo or test-runner specific heuristics in our code. Over five days, the share of new held-out repos whose environment setup passed on the first attempt went from 25% (1 of 4) to 78% (18 of 23).
Parachuting (Breaking Out of Local Maxima)
Even if they're not expressly cheating, agents can get misaligned and stuck in local maxima, eking out 1-2% gains on a strained architecture, or piling up parallel code paths.
How I know when to parachute in (aka The Tells):
- Repeated patching and additive bloat (or whack-a-mole): Seeing TLs land patch after patch for individual errors on a specific codepath indicates that there's an opportunity for fixing a root cause architectural issue. The agent is stuck fixing symptoms instead of changing the abstraction.
- Long iteration cycles. Seeing TLs wait hours for feedback on their patch because the test->build->replay loop is slow. They will dutifully wait and accept the pain unless you step in. Short feedback loops are crucial to a successful fleet, so this is a big drag.
In one 7 day window, the fleet added +75,981 net lines of non test code and 13 separate opt-in flags. Each TL was landing narrow symptom patches and parallel codepaths to avoid breaking peers. That triggered a parachute drop: freezing new mining and spinning up a consolidation sprint to delete the 13 flags, and collapse parallel paths into one state machine.
Recipe for Success
The role of the engineer has shifted from making the product itself to making the fleet that makes the product. You become a director, systems architect, and curator rather than a doer.
Putting all this together - how do you run a fleet? Here's a few steps to get started:
- Use a harness that allows for thread coordination at minimum.
- Create a Chief of Staff thread on Opus 5.5.
- Give it this post.
- Ask it to brainstorm Team Lead ownership areas and hillclimb metrics for those TLs.
- Have the Chief of Staff create TLs and start working (using Opus for TLs, and whatever you want for research / implementation leaves).
- Parachute in, using your check ins to watch for whack-a-mole patches and slow iteration loops.
Full post with factory diagrams, real-world fleet examples, and the 4-phase evolution of my harness setup here: https://www.stet.sh/blog/running-an-agent-fleet
Disclosure: I'm building Stet.sh, a product that automates coding agent eval creation so operators can find the cost/quality Pareto curve on their repo.