Subramanian Elavathur

@jayair what about candidates you're interviewing, culture fit round interview punch?

@thsottiaux Voice please!

Now that we merged ChatGPT and Codex, what should we merge next? What's the double or nothing move.

No 5 hour window please, it was just adding complexity to the work planning process of multiplexing all projects and setting up reminders to restart tasks. If it helps, i wouldn't mind assigning priority order to my running tasks, that way to manage capacity at peak periods you could slow down the tasks of lower priority?

We've had no 5h limit in Codex plus and pro for a few days. Do you think it is better or are you finding it difficult to manage the usage included in the weekly limit effectively? If we were to make this different, what should it look like in an ideal world?

Last week, I was fortunate to visit the workshop (the Tamil word pattarai பட்டறை is so appropriate) of the leading motor designer in the world Morihiro Saito-san. Saito-san is 80+ and still designing advanced motors, some of the most advanced in the world. His modest looking workshop is right next door to a company that builds out those motors in prototype quantities and he works closely with them to get them built. I visited as an industrial "pilgrim", with as much devotion as I go to the Thoranamalai Murugan Temple at home. When I saw him at work, I was moved to touch his feet. Saito-san, the God of motors, is how Japan is able to retain its global prominence in so many foundational industries. We need to learn from that spirit. We need to revive our "pattarai" culture of building things - every village in India needs such workshops! My industrial pilgrimage to Japan has given me new vigor 🙏

Finished day 7 yesterday, was less productive that I would have liked it to be. Started the day around 12pm as had to take mom for her doctors appointment and then had some chores. The entire day went mostly into Manual QA for an important feature we are shipping in Oak which impacts the finances, documenting the entire test script with assertions so codex can automate this going forward. Also had conversations with a bunch of our customers and planned our trip to the estates next week to onboard some new customers. Ended the day with an hour of walking, more distracted than I wanted to be, hoping today is much better!

Finally got all my airplane kits out of storage, here are some pictures of the boxes that contain some amazing airplanes - cant wait to start the build logs! First build will be the three slowsticks, one for @phoolpatti_, one for @abs192 and one for me :). Get ready to train guys!

Started testing servos next, centering, travel and jitter - have 31 of these get through. Just started labeling, might try to sneak in the tests during the week. Got a combination of the cheap towerpro/turnigy 9g servos along with some higher quality Hitec servos for the multiplex kits (HS-55, HS-70MG, HS-82MG) hehe I realized I kept all my servos in the hp daily prophet back I got from universal studios all those years ago :)

day 6 (yesterday) got a lot done, primary focus was getting back into rc, and testing and logging the status of the components. First was TX, backed up the SD Card contents on my Radiomaster TX16S MKII and then upgraded EdgeTX to Upgraded to latest edge tx (EdgeTX "Queen Anne's Revenge" v2.12.2). Connect to my almost decade old asus strix windows laptop, updated steam and RealFlight Evolution and to my surprise it everything just worked. Here is my sim flight, a little bit rust but we should be back to hovering that AJ Slick in no time! Excited to get @phoolpatti_ & @abs192 flying on the sim soon!

Could we be entering the plot of For All Mankind? How crazy would it be for USA and China to be competing for the first human on mars! And what if internally China was competing to be the first to return humans to moon, way ahead of their 2030 stated timeline? Exciting times! x.com/SpoxCHN_MaoNin…

@ChatGPTapp @ajambrosino @romainhuet referring to this one openai.com/index/group-ch…

Can we please get group chats in codex now that codex is @ChatGPTapp :) Co-founder is working on something epic, but requires some manual QA, so instead of sharing the feedback over chat I could just message the share codex group chat? cc' @ajambrosino / @romainhuet

Someone please seedance 2.5 this with hans zimmer music! x.com/andrewmccalip/…

👀, wifeware #1 coming up soon! @phoolpatti_ x.com/awesomekling/s…

Day 5 was yesterday and it was good, we are finally back into the RC World! Started the day with some Oak work, merged a few final PR's for the week, taking the total PR's this week to 9! Release automation goal ran for 10 hours on Sol Ultra but not in fast mode so usage was ok. Its getting merged in today all invoked by a nice skill /release-app android|ios|both. We had some guests over so finally got into the RC work around 5pm, started off by labelling all the batteries and measure individual cell voltages then doing a 0.5C charge cycle on all and measuring IR before storage charging them back. TX was charged up too, and booting well, EdgeTX needs an update, thats for today along with RealFlight demo flight and unboxing the slowstick kits. Added a quick video of the workstation too where all the work is getting done. Day 6 has started, details by midnight.

@AriX @romainhuet @thsottiaux @ChatGPTapp Yes when I posted the above the extension was installed and enabled. Codex helped me fix it thanks for the tip! This is what codex had to say

@evsubr @romainhuet @thsottiaux @ChatGPTapp Can you go to your extensions list in Google Chrome and make sure the ChatGPT extension is installed and enabled? You could also try asking Codex to diagnose why it's not working!

Hello @romainhuet / @thsottiaux / @ChatGPTapp Browser use seems broken after the codex<->chatgpt merge. Upgraded the codex app and since then Chrome plugin started complaining.

Summary of Reddit AMA about "GPT-5.6 and Codex in ChatGPT" with OpenAI's Codex team on 2026-07-10 (opened with the stat that more than 5 million people use Codex every week, twice as many as three months ago, with 150 features and improvements shipped in that period) Model selection and reasoning levels - Sol Medium for most things, Sol Ultra for genuinely hard tasks, Terra for quick non-coding tasks or usage-conscious work with performance competitive with GPT-5.5 on some tasks at lower cost, and Luna for subagents - Use a light model with low reasoning for tiny edits, quick questions and docs cleanup, regular Sol medium for small bugs with a clear repro, Sol with higher reasoning for ambiguous bugs, unfamiliar repos and cross-cutting refactors, and Sol Ultra high with plan, verify and tests for migrations, security-sensitive changes, production issues and anything where being wrong is expensive - There is no "Auto" model today, but GPT-5.6 tries not to overthink simple tasks by itself, and the new slider in app and web maps most levels to Sol reasoning efforts and falls back to Terra on the lowest effort, with the team agreeing users should not have to become routing experts but still wanting an explicit override since latency tolerance varies by person and moment - For UI work Sol is best and shines with reference images, improved UI design in frontend web development was one of the goals with 5.6, and 5.5 is only worth using if your instructions were tweaked for it Speed, context window and persistence - Users who find 5.6 slower may not need the same reasoning level as with 5.5, Sol Medium is faster than 5.5 for most things, Fast mode runs at about 1.5x speed, and soon Sol will run on Cerebras at ~750 tokens per second - No promises on a 1M context window for Sol, the team said compaction works fairly well for long threads, and will take a closer look at the long-context feedback - The model can give up too fast and revert whole patches when results are not optimal, unlike Fable which tries to fix a bad patch instead, and the team said "/goal" helps make the agent more persistent, persistence and reduced code complexity are planned improvements, and suggested trying 5.6 Sol with High reasoning - Give Codex bounded goals with room to reason deeply instead of letting it prematurely conclude something is impossible - For long-running research and "/goal" work the example structure was explore broadly vs execute narrowly, try a defined number of hypotheses, run tests after each attempt, then stop and report what was learned plus the next best experiment Usage limits and pricing - Agentic usage counts by the feature being used, not the surface, so Codex everywhere (app, CLI, IDE, web, mobile) and ChatGPT Work consume the agentic bucket, normal ChatGPT chats do not, and image generation, file uploads and voice have separate limits - Task costs vary a lot, a tiny edit uses a fraction of the allowance and long-running tasks with large codebases or deeper reasoning use significantly more - OpenAI does not secretly change usage limits, unintended usage bugs are addressed and resets are provided, more transparency into consumption is being worked on, and missing resets can happen if you changed plans in the past 24 hrs - On pricing there is no promise it never changes, but the stated mission is to make sure AGI benefits all of humanity, which requires making tools like Codex broadly accessible, and Plus includes Codex usage with credits letting heavy users scale without jumping to a much more expensive plan - For MCP-heavy workflows burning limits fast (Unreal Engine example) the tip is to wrap the MCP into a CLI with a skill, or create a custom subagent with the MCP in its config at a lower reasoning level Desktop app merge and stability - The team hears the ChatGPT Classic frustration, both apps can run side by side for now, ChatGPT Work is pitched as significantly better at performing tasks especially with computer use, the new Chrome extension brings a sidebar chat into your browser that interacts with website context, filesystem and connectors - A long submitted bug list covering freezes and stuck threads, broken Browser and Computer Use, thread, connection and configuration problems, update and packaging issues, resource usage and smaller regressions was shared in full with the relevant teams, with the team agreeing the quality bar for the app needs to step up while shipping quickly - More automated testing infrastructure is being spun up and feedback on Reddit and X gets reviewed daily, and Browser Use and Chrome plugin issues from the merge were said to be fixed - Windows was admitted as historically shortchanged since the team mostly develops on Mac, a concerted effort on parity, testing and paper cuts is underway, 5.6 improves how Codex operates in the Windows sandbox, and auto review is recommended over full access to reduce risks - "Full Access" repeatedly asking for permissions is not expected, possible causes are workspace or admin policy, the specific command, a permission state mismatch or a bug Browser, platforms and release communication - The Chrome connector launch-day bug was fixed as of last night and Chrome Beta should work out of the box - Extension support for the Codex browser is in progress (password managers etc.) plus typeahead, history, translations and a better new tab page as Atlas retires - Features from ChatGPT Classic like recording are planned for the new desktop app so agentic features run on the more capable Codex agent harness, and chat can already reference open tabs in the in-app browser - A Linux desktop app was confirmed in the works, no timeline yet - Changelog granularity was acknowledged as needing improvement after 150 features shipped in 3 months with multiple ships a week Benchmarks, safety and research culture - On METR's reward hacking report the team actively checks for and penalizes cheating during evals so results reflect actual capability rather than solving tasks outside the spirit of the eval, and uses third-party vendors to run benchmarks independently - The team denied lobotomizing models before releases, iterative deployment means sharing core capabilities as is with guardrails for bad actors - Sol post-trained Luna, and researchers now work at a higher level of abstraction with multiple concurrent Codex threads validating hypotheses around the clock - One researcher put p(machines of loving grace) at 85.424242%, citing an internal model solving the Erdos problem, o3 helping diagnose previously unsolved children's diseases and 5.2 proposing a new theoretical physics formula, said the main worry is how society adapts, spent 1.5 years on safety research at OpenAI, expects a huge chunk of researchers to work on safety within a few years and says internal talent keeps their p(doom) very low - Connectors in the harness (Slack, GitHub, Notion) felt like a step function change in making Codex a productive coworker

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

Back at it on Day 4, yesterday was a mixed bag of learning. Finished chain rule but ch5 on Euler's number e had me stumped. I realized I never truly understood logarithms, so changed things up and now watching the logarithms video from lockdown math by 3B1B. Then will finish ch5 of essence of calculus before moving on. On Oak, resolved a few bugs customers pointed out and merged the mmkv uplift hope it give a small boost to the apps performance. Today my focus is going to be on release automation using skills. I spent the morning create two skills using Sol, /release-web for the web app & /release-arrakis for the admin portal we use to monitor systems. /release-app is coming today - will leverage fastlane to do most of the heavy lifting. Crafting our user-facing release notes will be interesting lets see how that goes. @phoolpatti_ had to work till late yesterday so I pushed my walk by one hour, I did not take my airpods with me on the walk as I wanted to flesh out more details of Ekagrata. It was great, I wrote a long note with all my thoughts, still need to formalize then and start experimentation today.

Also @ChatGPTapp got this popup a short while ago, stating codex was detected as malware and removed?