Codexometer: track your quota, usage, orchestrate sessions & benchmark models!

Bug fix: API EQ calculation was way out for Fast mode … here we try to do a little better.

thanks @aprendendo.next

Diggin the design, we need more retro

Trying to improve Quality of Life here on the Monitors page once again.

  • You were always able to move up and down sessions with the cursor keys or mouse, now i’ve changed the detail level navigation by using the right and left cursor keys to change the level of detail.
  • I’ve added mouse control to level of detail - click the left half of the detail area to move to less detail, clicking on the right moves you to more detail.
  • The next command composer has been added to the mid detail view and is shown if there’s enough room - so you now can drive an individual session from the session list without diving completely into the detail screen (although that still has a better information layout upon which to make decisions as it leverages the extra space)
  • You can confirm a one-off decision by re-pressing 1 now instead having to reach for c. A permanent change to permissions still requires you to hit c to make it harder for more impactful decisions. NB this only works on terminals supporting key-release events (for example, through the Kitty keyboard protocol) - that means e.g. Windows Terminal App 1.25 supports it, but 124.x does not. At the time of writing 1.25 is still in Preview. macOS native terminal.app does not support this unfortunately - use the Kitty terminal instead.
  • Finally, “Monitor” has been renamed “Sessions”

Very happy to consider feedback on this experience.

New “Resets” view and new warning on Quota tab if one of them will expire within 72 hours.

(but you can change that default window with the new switch when launching codex, e.g.: --reset-warning-hours 2000)

Codexometer Sessions interface has been refined yet further in 0.17.0!:

with a much more useful summary bar and mouse clickable stacked approval links that each take you straight to the detailed approval request.

feedback on efficiency of use and intuitiveness is very welcome!

there’s also a bit of a easter egg :egg: … quite a big one in fact … (although if you check the release highlights it’s pretty obvious :sweat_smile: )

A little more experimentation with the attention pills row on Sessions:

Whenever your interaction is needed, or potentially needed, codexometer renders a call to action pill on a line at the top, with “highest priority” items on the left. Clicking these takes you to the place to unstick that session.

More Quality of Life improvements on Sessions tab!

A minor QofL tweak:

From v0.17.4 through v0.18.3, the biggest improvements are:

  • Copy useful output anywhere: copy replies or activity text—even while Codex works—from terminal and browser detail views, including read-only web mode. Offscreen text within the captured preview is included. (0.17.4, 0.17.5)

  • Quota-aware model switching: configure consumption thresholds to change model, reasoning level and speed for subsequent turns—with per-session approval or opt-in automation. Requires shared app-server sessions. (0.18.0, 0.18.1)

  • Sessions are easier to recognise and navigate: session names appear alongside short IDs, attention pills use matching identities, and clickable status badges jump directly to the corresponding detail. (0.18.3)

and finally, a small release with the new GPT 6 models and their prices:

If you use the web mode, please update, this release contains a security patch to resolve a vulnerability.

As ever, simple upgrade instructions in the release highlights linked above.

FYI for Windows Terminal app users (I :heart: the Windows Terminal app!!)

Approvals Interface

Better keyboard shortcuts for confirmations were released way back in Release v0.14.5 — Your Monitor, with fewer detours · merefield/codexometer · GitHub

Pressing 1, then C is a bit of a pain, but it prevents issues with holding the key continuously and misinterpreting a confirmation because of a held key.

Kitty support allows us to guard against this, in which case we can safely support 1, 1 key presses.

Stable Windows Terminal 1.25.2733.0, published 2 October, supports the Kitty keyboard protocol and includes a fix for auto-repeat events. Its rollout is staged, so your Microsoft Store installation may not have updated yet. Microsoft’s release notes

That’s what Codexometer needs for safe 1 → release → 1 confirmation: it distinguishes a deliberate second press from holding the key down.

After updating, restart Terminal and Codexometer. Codexometer enables repeated-number confirmation only when it detects the necessary support; otherwise 1 then C remains available.

In Windows Terminal, open the ▼ menu beside the tabs → Settings → About.

Look for 1.25.2733.0 or later for the stable Kitty keyboard support discussed above.

Alternatively, run this in PowerShell:

(Get-AppxPackage Microsoft.WindowsTerminal).Version

I believe the native macOS terminal does NOT have Kitty support yet … sorry.

Looking at the performance improvements for 6-Astra and 6.1-Sol:

Can you create a benchmark with Codexometer?
Just in case it’s only 49% and we get a Reset on top.

Unfortunately it can’t yet automatically compare with past benchmarks - but you could do this manually if you have a recording of an old one … and I do have published benchies for 6 and 6.1 Sol, so I’ll run it again tomorrow and see if there’s a time reduction?

I can’t. My only available device is running Windows and it’s blocking the unknown app…

Let’s move this conversation to the project topic.

If you run WSL with Ubuntu it will happily run there.

So in Powershell it won’t install?

I have a .exe flying around. This didn’t execute because Smart Guard blocked it.
Cannot recall how I originally got the app to run.

There’s an issue for the bundled 5.1 version of Powershell, working on an update.

Sorry, but this won’t magically fix windows blocking unsigned code.

Can you make it self-healing? It takes in bug reports, fixes, then pushes code?

I heard of someone doing that with a game or something … then thought it could easily be messed with if you sent bogus bug reports…

Sorry for thread drift!