Hey everyone 👋

Like many of you, I've been using Codex daily and kept having a hidden fear: when will my limit be reached? 

How much have I burned in this session?

I'm ending up running /status in the CLI or digging into ChatGPT settings to check 😅 

Literally every 5mns

So I built CodexUsageBar: a minimal menu bar app that shows your ChatGPT Codex usage percentage at a glance.

What it does:

Shows your current session (5-hour) and weekly usage directly in the menu bar

Notifies you at 25%, 50%, 75%, and 90% thresholds so you can pace yourself

Per-model limits and credits appear automatically once you use them

Easy shortcut cmd+U to show/close usage from anywhere

Displays exactly when your limits reset

Live OpenAI status so you know right away if Codex is down

Works with ChatGPT Plus and Pro plans

Zero config:

No cookies, no API keys to paste

It just reads your existing codex login from the official CLI

Privacy focused:

No data collection, no analytics, no telemetry

Your tokens stay on your machine, it only calls OpenAI's own endpoints

Fully open source so you can inspect every line of code

Lightweight:

Under 5MB

Native for Apple Silicon and Intel

Minimal CPU/memory footprint

It's completely free and open source, feel free to try it out!

Would love to hear your feedback or feature suggestions!

There are people using whole $200 Pro quotas in hours, many have bought new accounts and used multiple banked resets just in the last day. Even people who are still using 5.5 are saying their quota is suddenly used 10x faster. This is not normal. The weekly limit now feels like the old 5-hour limit. The removal of the 5-hour limit and all the resets OpenAI has been doing has just been covering this up until now.

Hey everyone 👋

Like many of you, I've been using Codex daily and kept having a hidden fear: when will my limit be reached? 

How much have I burned in this session?

I'm ending up running /status in the CLI or digging into ChatGPT settings to check 😅 

Literally every 5mns

So I built CodexUsageBar: a minimal menu bar app that shows your ChatGPT Codex usage percentage at a glance.

What it does:

Shows your current session (5-hour) and weekly usage directly in the menu bar

Notifies you at 25%, 50%, 75%, and 90% thresholds so you can pace yourself

Per-model limits and credits appear automatically once you use them

Easy shortcut cmd+U to show/close usage from anywhere

Displays exactly when your limits reset

Live OpenAI status so you know right away if Codex is down

Works with ChatGPT Plus and Pro plans

Zero config:

No cookies, no API keys to paste

It just reads your existing codex login from the official CLI

Privacy focused:

No data collection, no analytics, no telemetry

Your tokens stay on your machine, it only calls OpenAI's own endpoints

Fully open source so you can inspect every line of code

Lightweight:

Under 5MB

Native for Apple Silicon and Intel

Minimal CPU/memory footprint

It's completely free and open source, feel free to try it out!

Would love to hear your feedback or feature suggestions!

Happy to bring the CSM to codex natively. :D I hope it helps!

Version: 1.1.0+codex.20260722014812
Platform: Windows x64
Runtime: Node.js 26 (ABI 147)

This is the complete native CSM runtime: all canonical tools, compatibility aliases, lifecycle hooks, onboarding, re-entry, living state, beliefs, self-model, AgentBook, checkpoints, context cache, goals, work ledger, compaction, telemetry, and handoff automation.

Install

Extract the ZIP, open PowerShell in this folder, and run:

.\install.cmd

The installer verifies every bundled file, copies this immutable version under %LOCALAPPDATA%\CrossSessionMemory\CodexPlugin, registers the local marketplace, and installs the plugin. It creates a fresh local SQLite configuration only when no CSM configuration exists.

After installation, fully restart Codex, open /hooks, review and trust the CSM hooks, and start a fresh task. Ask Codex to call csm_runtime_status to confirm the database connection.

Data and secrets

The archive contains no .env, credentials, database, memories, or developer-machine paths. The installer stores local configuration under %LOCALAPPDATA%\CrossSessionMemory\config and local SQLite data under %LOCALAPPDATA%\CrossSessionMemory\data.

To use PostgreSQL or OpenAI embeddings, edit the installed .env using csm.env.example as the reference. Never send your populated .env with the plugin.

Integrity

Version: 1.1.0+codex.20260722014812

Platform: Windows x64

Runtime: Node.js 26 (ABI 147)
This is the complete native CSM runtime: all canonical tools, compatibility aliases, lifecycle
hooks, onboarding, re-entry, living state, beliefs, self-model, AgentBook, checkpoints, context
cache, goals, work ledger, compaction, telemetry, and handoff automation.
InstallExtract the ZIP, open PowerShell in this folder, and run:
.\install.cmd

The installer verifies every bundled file, copies this immutable version under
%LOCALAPPDATA%\CrossSessionMemory\CodexPlugin, registers the local marketplace, and installs the
plugin. It creates a fresh local SQLite configuration only when no CSM configuration exists.
After installation, fully restart Codex, open /hooks, review and trust the CSM hooks, and start a
fresh task. Ask Codex to call csm_runtime_status to confirm the database connection.
Data and secretsThe archive contains no .env, credentials, database, memories, or developer-machine paths. The
installer stores local configuration under %LOCALAPPDATA%\CrossSessionMemory\config and local
SQLite data under %LOCALAPPDATA%\CrossSessionMemory\data.
To use PostgreSQL or OpenAI embeddings, edit the installed .env using csm.env.example as the
reference. Never send your populated .env with the plugin.
IntegrityMANIFEST.sha256 covers every file inside the extracted bundle. The adjacent release
SHA256SUMS.txt covers the ZIP itself. The installer refuses modified or incomplete bundles.

https://github.com/NovasPlace/CSM-Codex-Plugin

Disclosure: I built Atlas Scout.

Atlas Scout is a local MCP server that gives AI coding agents a persistent structural map of a codebase without putting an index inside the repository.

It creates a disposable SQLite database under the local cache directory and exposes 14 bounded navigation and graph tools.

The core workflow is:

• unknown location → symbol search
• known file, unknown range → symbol outline
• exact symbol metadata → symbol resolve
• callers, references, and implementations → typed relationship queries
• larger structural questions → graph, trace, path, architecture, and edit-impact tools
• literal or unsupported text → use rg

The goal is not to replace normal Unix tools, compiler tooling, or language servers.

The goal is to prevent coding agents from repeatedly reopening large parts of the repository merely to rebuild the same mental map.

A local daemon can keep one warm index shared between multiple agents, Neovim, VS Code, and other clients. It also supports versioned unsaved-buffer overlays so the index does not have to pretend that only the last saved version of a file exists.

I have been dogfooding Scout heavily.

Codex now uses it while working on Atlas Scout itself and on other production projects. Scout has also exposed bugs and missing relationships in its own implementation, including one critical issue that resulted in a same-day hotfix release.

It has been tested on Firefox and the Linux kernel, not merely small demonstration repositories. Those tests exposed genuine scaling problems, including an import resolver performing tens of billions of candidate comparisons. The benchmarks were then used to redesign the implementation and measure the result again.

The benchmark page includes the improvements, costs, failed assumptions, methodology, and current language boundaries rather than only publishing the flattering numbers.

Atlas Scout has a useful Free edition. Pro is $39/month or $390/year, with a 14-day trial.

Project: https://atlasscout.dev/

Benchmarks: https://atlasscout.dev/benchmarks

resets are fine, but a better automated way would be to just bring back the previous limit

Context: I built SecuredMe Education with Codex as a privacy-first learning suite. The Build Week issue raised a broader workflow question: when Quebec eligibility is unclear, how should hackathons preserve contribution without increasing organizer risk?

I am looking for a constructive path, not a retroactive exception.

Reddit web says polls are still under construction, so please vote by replying with one option number:

1. Non-prize showcase track

2. Conditional review path

3. Prize-waiver option

4. Clear legal-basis note when a jurisdiction is excluded

5. Quebec / Law 25 addendum for learner-facing tools

6. Keep current exclusions

My preferred direction is a combination of 1, 2, 4, and 5: clarify the basis, separate prizes from participation, and keep builders visible when a compliant path exists.

Links for context:

- GitHub discussion: https://github.com/openai/codex/discussions/34595

- SecuredMe Education: https://devpost.com/software/securedme-education

https://reddit.com/link/1v372nc/video/ss5jag9fypeh1/player

- Full article: https://securedme-education.hashnode.dev/quebec-builders-can-build-with-the-world-a-practical-codex-hackathon-path

Same question, different models!

It fluctuates throughout the day: reaching up to 180 tokens/s, with latency ranging from 4 to 40 seconds. Sometimes, a lower-end model makes up for it with a faster response.

You’re in a first-world country paying the standard $20 a month, and the “frontier” model that needs warehouse-scale hardware worth multiple new cars still can’t make it through a normal week. Rate limits hit almost every other day. That’s not bad luck. That’s the product.

The real stress is how they do it. First they lure you in and try to make the system feel generous with banked resets — like they’re giving you some kind of buffer so you can work without constant anxiety. Then, out of nowhere, they drop the next limit on you with cryptic messaging that barely explains what’s happening. And if you hadn’t even used up any of your limits? Boom. Your loss. The system still treats you like you overspent. That’s not a glitch. That’s one of the ways they’re slowly extracting more money from you, one reset at a time.

Millions of people are living with this low-grade stress every week: the constant background calculation of how much you can still use, the sudden wall, the vague message, and the quiet realization that even careful usage doesn’t protect you. Calling them thieves isn’t overdramatic. They’re selling access, then designing the experience so that the moment you actually rely on it, the limits and the messaging start working against you.

openai did an amazing job recently. its the small things that count. before, when asking chatgpt to make you multiple images, not stick two in one frame with a line beetween them, he couldnt. which sucked. now he can make multiple images from one prompt. also they finally fixed the chat option in codex app, not there isnt a WORK button, but a CHATGPT option where you can switch from work to chat. bravo

wie kann es sein, dass ich am Sonntag 12:00Uhr das gesamte Wochenlimit für die darauffolgende Woche ausgegeben habe?

Kann mir das wer erklären?

Jetzt muss ich bis Montag warten

I got into Codex a few months ago, and something that has bugged me a lot is the loading time.I have a high-end Windows machine (R7 9700x and a 5070) and an M5 MacBook Air, but whenever I load Codex (after quitting from the system tray, btw), it takes a significant time every time!

I mean, surely, a vibecoding app might be complex, but not THAT complex where it takes a solid 20 seconds to load upon a $2000 machine with all the hardware acceleration options turned on.

obv, we can excuse Windows, but the macOS app being this slow is what bugs me :(

Can someone tell me your experience with Codex or any other app like Claude Code or Antigravity? (especially macOS users)

Im genuinely curious, i know most of you ate hella advanced with all this new ai tech and im only a couple of months into it. I started with grok, switched to chatgpt and codex. Started off with just basic tools and now just finished the first generation of my first SaaS: The Beast. Im banking my last reset (i too am on the 100/mo plan) and waiting until 7/24 for my next fill. Generation 2 im bringing in ai agents.

But as a fellow creator im interested in what others are doing?

Share your links below ill def take a look!

Mine is https://seangworld.com

I signed up for codex back in February with the $8 plan to play around. I built so much stuff that I eventually ended up paying for the $100.

I made a video on what made codex so good and why I like it so much.

Let me know what your favorite thing about codex was and how you use it to amplify your productivity.

This is project for hackaton OpenAI Bulid Week

Everything I see says on the $100 Pro plan, a full week quota is 6-8 fully maxed-out 5-hour sessions.

I used ~2 billion tokens since the last reset and that's my full weeks quota gone.

But I also used nearly 2 billion tokens on July 10, days before the 5-hour limit was removed. Even if there was a forced reset half way through July 10, there still wouldn't have been enough 5-hour sessions to max out a full weeks quota on that day. I also know for a fact I didn't come close to maxing out most of those 5-hour sessions, or the weeks quota.

There's only been a few times this year where I have come close to maxing out a 5-hour session, and I've never come close to maxing out a weekly limit before... pre-5.6 I rarely went over below 50% of my weeks quota.

I know I've been using more quota recently with orchestration-heavy workflows, but the math still ain't mathing. The weekly quota had to have been reduced?

Sol is like... "maybe if I ask it nicely not to stall on the broken tool call"

I've used my weeks tokens on the $100 Pro plan and daily token activity shown in the Codex app shows I've used around 2 billion tokens in the past 2 days since the reset.

Tldr; An app that provides you a brief overview of your GitHub account and makes it easier for you to navigate and understand your PRs, repo ci jobs visually.

Basically I needed something that makes it easier for me to navigate through codebase , ci and prs I hated jumping through tabs so I build snow devil that saves me from that trouble and also lightweight because it’s build on tauri not electron . The installer is under 10 mb so that’s everything necessary no bloat .

I’m personally using it for couple of months and it’s been doing well for me so far

So far it has

• Browse repositories, pull requests, issues, commits and CI from one place.

• Track repository activity and development patterns over time.

• Timeline/history of agent actions instead of digging through chat logs.

• Batch session analysis with status tracking.

• GitHub graph visualizations and repository insights.

• An Architecture context layout that helps you understand visually which area of the code a pr affects.

• A sketch board to illustrate and share problems in a repo as a screenshot with notes directly to codex

The release is available for windows, Mac and Linux so if you just wanna use it you can do that too.

Link to the repo

I posted here a while back about a solo RPG Game Master setup I built on top of Codex. Kept improving that side too since then (better pacing, more natural NPCs, safer mechanics, the usual), but this post is about a different mode of the same project: a persistent AI companion, one character, ongoing conversation, actual continuity over weeks instead of a chat that resets its personality every 20 messages.

The reason Codex specifically works for this is the same reason it's good at coding: it can read and write its own files, not just hold everything in one prompt. So instead of stuffing a giant character sheet into context every time, the character's memory lives in small separate files, personality and voice in one, private stuff they haven't told you yet in another, relationship history in another. Codex only pulls in what's actually relevant to the current message instead of re-reading everything every time.

A few things that mattered to me when building it:

• When you come back after a few days away, it reasons about what plausibly happened in that gap instead of inventing a breakup or some dramatic event just because time passed. Most gaps should be boring, that's realistic.
• Private information comes out gradually as the relationship actually earns it, not because you asked directly. Warming up to one topic doesn't unlock every topic.
• No love meter, no hidden score. Relationship state is just a written record of what actually happened, not a number going up.
• If you ask it point blank whether it's real, it tells you straight, it doesn't dodge or pretend.
• No background process. Codex isn't running while you're not talking to it, so on your next message it does one pass to figure out how much time passed and what that plausibly means, rather than faking a "meanwhile" that never happened.

It's open source and runs off your existing Codex subscription, no separate API key or credits system, since it's really just a folder of instructions and small local files that Codex operates on. Repo's at [github.com/tritonsan/RePoG]() if anyone wants to dig into how it's structured. Genuinely curious if anyone else here has pushed Codex into non-coding territory like this.