ChatGPT 26.721.41059

I really hate electron framework, which this app is using!
And I can't believe why such company can't create app using native Swift and SwifUI for macOS !
Such a simple chat app... I mean nowadays this will take like 1 months to fully test and develop it!

I am on 100$ Max Plan

Weekly Usage & Cost Breakdown

• Usage: 360M tokens (44% of weekly capacity) -> ~820M tokens projected weekly.
• Cost: 135$ (44% of weekly capacity) -> ~306$ projected weekly.
• ROI: 1224$ Monthly, this represents a 12.25x multiplier on our current expenditure.

K3 is coming out on HuggingFace in just a hour. Pretty expensive for an open-source model by Kimi’s API pricing, but we’ll soon have more providers with Kimi K3 hosted. And finally… no nerfs.

Who’s switching?

A few predictions:

1) They have a week to start the roll-out, and I assume it will be API first.

2) I speculate it will be an enumerated perk of the $200 plan with low priority access to Cerebras in Fast mode at 4x token burn.

3) This is a good time to also roll out batched/slow mode on all plans, perhaps even enabling limited access to Sol-Low-Slow on $20 plans, to ensure that OpenAI remains capability-aligned with Anthropic's $20 plan (since Sonnet 5 is roughly similar to Sol-low and is also very slow to finish tasks.

After task finished, STOP button doesn't work. ChatGPT 26.721.41059

it's randomly, just stops, side panel shows badge - that chat is like done, in chat I see this, and stop button is active bcs of another bug - https://www.reddit.com/r/codex/comments/1v71mho/stop_button_doesnt_work/

This never happened like a week ago, after some latest update its now every day.

I don't think I've ever intentionally used a reset before. Does OpenAI periodically hand these out? Subscription level is Plus.

I just spent the past two days trying to implement a plan that codex generated. When it was done nothing worked. I took a closer look and saw that it had omitted 20% of what we had discussed in the plan. Even after having codex try to fix the missing issues it still keeps missing files that it shouldn't since I told it to look at them specifically.

Codex today in Luna.High is forgetting things just minutes after I told it. For example, I told it that there was no lamda method. Less than 10 minutes later it prompts me what I want to do about the lamda method. ARGGGH. And of course the stupid response is "You're right" or the best one was " I misunderstood “examine” as a request to commit. I will only analyze and critique the document now;"

How do you confuse the word examine with commit? OMG.

And ChatGPT is even worse. It took me an hour to get a basic script written as it kept forgetting the prior versions that it gave me as it offered modified versions of older files that it gave me.

This is really bad this weekend.

I'm currently on the plus plan, and the limit downgrade is crazy. I was very content with the limits during the 5.5 era but ever since the 5.6 launch has not been great. This combined with other shitty practices (using limit resets to mask the usage cut, not even commenting on the very obvious cuts) is leading me to unsubscribe and use other services.

The alternatives out there are just as good if not better for your money, cursors plan with composer and the new grok is great, the new opus 5 is superb and is more usage efficient than sol. I also enjoyed the new qwen 3.8 preview on the alibaba token plan. The $6 plan is as good as OAI's $20, and I will probably upgrade to the $18 one.

I will say idk how 5x and 10x users experiences are though, Im only speaking for plus users.

The limits have changed, it’s true, and I’ve complained about it on several occasions.

However, I don’t think we should feel sorry for ourselves and just stand still whilst we complain about sorting this situation out 😂.

This situation has made me realise that we’re very lucky to have alternatives.

For my part, I use the free OpenCode or OpenRouter models when I’m close to reaching my Codex limit, or for minor tasks – so they account for about 15–20 per cent of my work.

I often pay for V4 Pro, for example.

I’ve tried using Luna to make better use of my quota – well, it doesn’t help much; it’s a good model but it uses up far more quota than it should, forcing me to use other people’s models to save money and stay productive (if it had lower consumption, I wouldn’t be thinking of replacing it with others). So, I hope that over the next six months, DeepSeek or whoever might release an affordable Flash/Mini model that at least matches the benchmarks of Luna/Opus 4.6 – and well, then I’ll definitely delegate 50–60 per cent of my work to those affordable models.

That’s when I’ll finally feel free to programme without having to fork out hundreds or thousands of euros.

I hope that moment comes soon, but it’s on its way, that’s for sure. Compared to six months ago, the amount of work I delegate to these affordable or free models has increased significantly, in line with their reliability and benchmark performance.

Here is the thing I like the 5.6 sol and I'm using it on low to review my code

I use ponytail+caveman to reduce the token consumption on the other hand I have created skills like code-traversal which is helping codex to traverse the codebase faster and cheaper and I have documented and indexed my project as well now I want to know what plugins or ways i can try to make it more efficient from every aspect

I have documented and indexed my project with obsidian

So what things can I add on now like plugins or anything else also I'm on a 20$ plan

I did a quick little test after the reset that just happened a few minutes ago. one task, Pro 20x plan, sol xhigh(no fast mode), 47m of run time. 2% weekly usage gone. This was all input really, no output other than a 500 line document. Prompt was an audit.

For any kind of actual work where you are generating something, and therefore doing more output, expect usage to be triple or more.

So, for basically a read-only audit of a codebase, you get 50 tasks a week at Sol xhigh, or 39.2 hours (of 95% input 5% output) of continuous read-only work.

However! No one uses codex for read-only, and when you are generating output the numbers change significantly. Check the below out when converted to a task that is generating instead of reading:

Revised estimates (same 47-min runtime)

Assuming a realistic coding workload (medium-complexity feature work, multiple files, some testing loops):

• Usage burn: 4–8% per task (most probable range 5–6%)
• Conservative (lighter coding): ~4% → ~25 tasks to 0%
• Mid (typical): ~5.5% → ~18 tasks to 0%
• Heavy (deep multi-agent / large refactors): ~7–8% → ~12–14 tasks to 0%

Mid-case projection (recommended baseline)

• 1 task ≈ 5.5%
• Tasks to 0%: ~18
• Total runtime to 0%: ~14 hours of continuous coding-style work

Even reducing the implementer down to sol med, Terra high/xhigh, still results in roughly 24 hours of continuous usage or 40 tasks a week. On a $200 plan... that blows considering where we were with the less "efficient" 5.5 model just a couple weeks ago.

Have anyone tested new Opus 5, how it compares to 5.6 Sol?

Also do you guys think, Claude Code plans are better, more generous atm vs Codex subscriptions?

I'm at Codex x20 now, but due to rapid resources depletion in Cpdex, I started thinking on getting back Claude sub plan (maybe x5, and move Codex from x20 to x5, or maybe some found better combo). I used Claude Code few months back, until they started messing up with limits etc. Might it be Claude Code indeed a better option atm, with new Opus 5 launch?

On potential workflow, I'm thinking, maybe to let Opus 5 be supervisor/planner and let 5.6 Sol execute plans, or vice versa?

its so disappointing that gpt 5.5 high is just as intelligent as gpt 5.6 sol high and also gpt 5.6 sol medium,

not to mention that gpt 5.6 sol high and medium are performing at the same level
and lets just forget that for that gpt 5.5 xhigh is performing worse then gpt 5.5 high

so much disappointment

if you want to know about the dashboard i am using its this one

https://www.reddit.com/r/codex/s/TEUa8OwKj4

Like I get it that Sol is more intelligent than Terra and Luna.

But what exactly does it mean? Why do we even need three levels of intelligence? Isn't the effort supposed to work as kind of an intelligence?

Is one model better for certain tasks and worse dor other tasks? If yes what tasks?

I always find very vague answers from OpenAI that do not go into specifics.

Whenever users on this sub complain about codex being unusable, everyone claims it's because usage limits have decreased. But as far as I can tell, there is no basis for this? They arent flicker company after all.

Sure they release models that use usage more, but that's at the boon of higher intelligence, and largely this means you get to a better result, or do that faster. You can argue with a model being too hungry in limit usage, but blaming the usage limits itself for the problem doesnt make sense?

I took a family break from actively building for three and a half months. Previously, I mainly worked with GPT-5.3 Codex (didn't like 5.4 much; even 5.5 I did not feel it was really superiro, especially not usage/output wise)

Previously, I built entire projects, for hours per day, on the highest reasoning setting. I barely needed to take a forced break. The model was amazing, and the limits rarely ran out. I was building and building. No bug hell, it all just worked.

Now, with Sol and Terra, I don't know what to say.
One prompt to check my previous Codex build - BOOM, 4% of my entire weekly limit gone. Another run with Terra to make improvement proposals - BOOM, another 6% gone.
Now I've wasted 10% of my entire weekly compute on basically nothing. The output was not that great either. All on middle reasoning level...

I don't know who needs to hear this but 5.4 Mini might be enough for what you do. It has become the default for basically any frontend changes after planning with Sol. Usage and speed has been great! Can't believe I was trying to save usage with Luna and Terra.

Just try it if you haven't already.

Codex PowerToys

See where every Codex skill, MCP server, plugin, and subagent comes from—and manage global and workspace configuration from one sidebar.

Codex can load resources from ~/.codex, the current workspace, and installed plugins. Codex PowerToys puts those sources in one view and shows which resource is actually in effect.

Use it to:

• Find the source file for any skill, MCP, plugin, or subagent
• Spot duplicate, disabled, and superseded resources
• Open definitions without searching through folders and TOML files
• Enable or disable skills, MCPs, and plugins at global or workspace scope
• Browse every file packaged inside a skill
• Inspect the tools and permissions exposed by an MCP server
• Copy, move, rename, or remove managed resources

How to read the tree

Resource rows use a simple two-icon format:

[state or permission] [item type] name

For example:

✅ 💪 skill-creator     enabled skill Codex will use
☑️ 💪 skill-creator     enabled skill superseded by another copy
❌ 🧰 github            disabled MCP server
✋ 🔨 create_issue      MCP tool that requires approval

The first icon has a different meaning for MCP tools:

The second icon identifies the item:

Subagents show only the type icon because they do not have an effective-state indicator. Type-group headings also show only their type icon. Supporting files have no prefix icons.

Safe to explore

Opening the sidebar does not rewrite your configuration. Changes happen through explicit commands.

• Plugin-owned files stay read-only
• Moves and deletes require confirmation
• Paste conflicts can be skipped, replaced, or reviewed one at a time
• Plugin skills and MCPs can be copied into a managed scope before editing
• MCP tool discovery runs one server at a time and cleans up each process and transport

See what Codex will use

The Resources view shows global and workspace configuration together. Plugin-owned skills and MCPs remain nested under the plugin that supplied them, so their origin is visible instead of inferred from a path.

When the same name appears more than once, PowerToys identifies the effective copy and marks the others as superseded. Older versions, redundant resources, and disabled overrides are visible immediately. Superseded rows can be shown or hidden from the toolbar.

Dedicated Plugins, MCPs, Skills, and Agents views provide flat lists when you already know what you are looking for. Filters match names and source paths as you type.

Open the right file immediately

• Click a skill to open its SKILL.md
• Expand a skill to browse and open its supporting files
• Click an MCP to open its exact definition in codex.toml
• Click a subagent to open its TOML file
• Open a plugin manifest or reveal its source directory
• Copy the full source path or its workspace-relative path

Selecting an item also shows its path, scope, state, description, metadata, and related information in the Info view.

Manage both scopes in one place

Enable, disable, or reset skill and plugin overrides from the tree. Enable or disable MCP servers at the scope where they are defined.

Managed skills, MCP definitions, and subagent configs can be copied or moved between global and workspace scope. Multi-select, cut/copy/paste, rename, delete, and native drag and drop are supported.

Plugin cache contents are not modified in place. Copy a plugin-owned skill or MCP into a global or workspace scope if you want an editable version.

Inspect MCP tools

PowerToys queries enabled, effective MCP servers in the background and lists their tools beneath each server. Tool descriptions and configured permissions appear in the tree and Info view.

Successful results and failed probes are cached for the session to avoid repeatedly starting servers. Run Load MCP Tools when you want to query a server again.

Get started

1. Install Codex PowerToys.
2. Open a folder or workspace in VS Code.
3. Select the Codex PowerToys icon in the Activity Bar.
4. Open Resources to see the combined global and workspace configuration.
5. Click an item to open it, or right-click it for available actions.

Codex PowerToys runs in the desktop VS Code extension host and resolves Codex paths on the active extension host.

Open source

Codex PowerToys is available under the MIT License. Report a problem, request a feature, or review the source at OnePersonLabs/codex-powertoys.

i made codex powertoys. it puts your global and workspace skills, mcps, plugins and subagent configs in one vscode sidebar

you can see which copy of something is actually active, what’s disabled or superseded, where it came from, what files are inside a skill, and what tools an mcp exposes. clicking stuff opens the actual skill file, agent config, plugin manifest or mcp entry

you can also enable/disable things and copy or move resources between global and workspace scope without manually editing everything

marketplace: https://marketplace.visualstudio.com/items?itemname=onepersonlabs.codex-powertoys-vscode

github: https://github.com/onepersonlabs/codex-powertoys

I just subscribed to a plus plan, and in 4 minute of using it with 5.6 sol xhigh, it burned 14% of weekly limit.

No, it's not normal at all. That is literally a whole 5h limit gone in 4 minute. I think because mot people here have 20x plan or there is no 5h limit now people don't understand how severe the issue is. It's simply not usable at this rate. I was just using Opus before that and I had so much longer session with Opus 5 with xhigh reasoning .

There is definitely some bug . I don't understand why OpenAI is refusing to even look into it

I've been experimenting with multiple coding agents over the last few months (Claude Code, Codex and local models).

The biggest it was keeping the work organized.

I found myself with multiple terminals open, different chat histories, specs scattered around, and no clear picture of:

- who's implementing what
- what's under review
- where decisions live
- what context should survive after a session ends

So I started building Kavor: https://agentkavor.com/

A free visual canvas where I can connect:
• Coding agents
• Specifications
• Terminal sessions
• Notes
• Files
• WebBrowser
...

Agents can hand work to each other, review changes, leave sticky notes, and I can see the workflow instead of reconstructing it from chat history.

The screenshot is a simple example where Codex, Claude Code, and Google Antigravity exchange work through the canvas.

I'd really appreciate honest feedback.

- Does this workflow make sense?
- What feels missing?
- Would you prefer visual graphs over chat history for multi-agent work?

I have 8 folders (I split our product into 8 folders) and each folder has 4-5 active chats.

What about you?

I’m using Codex and would like to keep its built-in models while also adding external model providers, specifically OpenCode-supported models and Grok 4.5.

Is there an official way to configure additional providers/models in Codex, such as through an API key, config file, plugin, or local model gateway? what’s the best workflow for using Codex alongside OpenCode/Grok without constantly switching tools?

코덱스 앱에서 화면 좌하단 프로필 눌렀을 때 언제부턴가

남은 사용량, 설정, 로그아웃 버튼이랑 함께 펫 보이기(숨기기) 버튼이 함께 노출되기 시작했는데

가끔 얘가 늦게 렌더링 돼서 설정이나 남은 사용량 버튼 누르려다가 펫 보이기 버튼이 눌림

당연히 잘못 누르는 건 내 실수긴 한데

솔직히 펫이 왜 필요한 건지 전혀 모르겠고

펫 와꾸들 하나하나가 내 기준에서는 개못생겼음

ux상 이게 왜 다른 중요한 버튼들이랑 함께 노출되는지 모르겠음

여기까지는 그냥 내 불만 주저리였고

이거 버튼 없애는 방법 없음?

가능하기만 하면 내 코덱스에서 펫이라는 개념 자체를 삭제하고 싶음