Restore session pace / deficit as a menu-bar layout token

[WilliamK6]

Summary

CodexBar 0.45.0 replaced the previous menu-bar display modes with the new drag-and-drop layout editor.

The old Both display mode could show the usage percentage together with the pace delta directly in the menu bar, for example:

40% · +11%

After upgrading to 0.45.x, this layout can no longer be recreated. The available tokens include:

• Session %
• Weekly %
• Auto %
• Usage bar
• Resets in
• Reset at
• Runs out

There is no token for the numeric pace, reserve, or deficit value.

Why Runs out is not equivalent

The Runs out token displays an estimated exhaustion time.

The former pace value answered a different and more immediate question:

How far ahead of or behind the sustainable usage rate am I?

For a five-hour Codex session, seeing 40% · +11% at a glance is more useful than seeing only 40% or an estimated run-out time.

Previous behavior

Before 0.45.0, selecting the Both display mode showed:

<usage percentage> · <pace delta>

The pace delta indicated whether usage was ahead of the expected rate and therefore in deficit, or below the expected rate and therefore in reserve.

Current behavior

1. Open Settings → Menu Bar → Layout.
2. Add Session % to the menu-bar strip.
3. Look for a pace, reserve, or deficit token.
4. No such token is available.

Consequently, the old Both configuration cannot be reproduced with the new layout system.

Requested behavior

Please add a token such as:

• Pace
• Pace delta
• Reserve / deficit

Ideally, it would support the same window selection as the percentage tokens:

• Session
• Weekly
• Auto

Example custom layout:

Icon + Session % + Separator + Session pace

Rendered result:

40% · +11%

A positive value could represent usage above the sustainable pace, while a negative value could represent usage below it. Alternatively, the token could render explicit text such as:

• 11% deficit
• 8% reserve

The calculation already appears to exist for the provider details and run-out estimates, so this request is primarily about exposing that value through the layout editor.

Related

• Add menu bar layout editor #2275 introduced the menu-bar layout editor.
• Show ahead/behind pace for all providers and in the menu bar #807 discusses displaying ahead/behind pace in the menu bar.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed August 2, 2026, 6:39 PM ET / 22:39 UTC.

Summary
Keep this issue open for a maintainer product decision. Current main and the shipped layout editor expose percentage and ETA-style tokens but no signed numeric pace token, while the linked open PR provides a viable, visually proven implementation candidate rather than a reason to dispatch competing work.

Reproducibility: yes. with high confidence from source and supplied UI evidence: current main's catalog and renderer have no pace token, and the prepared screenshot shows the released token palette without one. A live app run was not needed to establish the missing source surface.

Root-cause cluster
Relationship: canonical
Canonical: #2534
Summary: This issue is the canonical report of the missing layout-token capability; the open linked PR is a concrete candidate implementation, not a duplicate report.

Members:

• fixed_by_candidate: Add menu bar pace layout tokens #2540 - It directly adds the requested pace-token surface and references this issue, but remains open pending product-direction review.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Maintainer decision needed

Question	Recommendation
Should CodexBar add signed pace tokens for all existing layout windows now, and should legacy Pace/Both configurations remain mapped to Runs out or receive a separate migration plan?	Approve all matching pace tokens: Accept Session, Weekly, and Auto pace tokens to match the existing percentage palette, while leaving legacy-layout migration unchanged for this PR.

Why: This is a new persisted menu-bar capability and any migration changes the meaning of existing users' layouts; VISION.md requires sign-off for new features.

Next step
Do not dispatch a competing repair PR: #2540 already owns the implementation path, while a maintainer must choose its token scope and legacy-layout compatibility policy.

Review details

Best possible solution:

Approve a pace-token contract that mirrors the existing percentage-window vocabulary if desired, land the existing implementation candidate after scope review, and handle any legacy-layout migration as a separate, opt-in-safe compatibility decision.

Do we have a high-confidence way to reproduce the issue?

Yes, with high confidence from source and supplied UI evidence: current main's catalog and renderer have no pace token, and the prepared screenshot shows the released token palette without one. A live app run was not needed to establish the missing source surface.

Is this the best way to solve the issue?

Unclear until a maintainer selects the permanent token scope and migration policy. The linked implementation is a strong candidate, but its all-window scope and intentionally deferred legacy migration are product choices rather than mechanical bug fixes.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Adding pace tokens without an explicit migration decision leaves users who already upgraded from legacy Pace or Both layouts on the ETA-based Runs out mapping; changing saved layouts automatically could also overwrite an intentional post-upgrade customization.
• The linked PR expands the requested session-only restoration to Session, Weekly, and Auto tokens, so its final token scope needs owner approval before merge.

Codex review notes: model internal, reasoning high; reviewed against 5b0b9fa3e37c.

Label changes

Label justifications:

• P2: The missing token removes a useful at-a-glance menu-bar workflow but does not prevent usage tracking or app operation.
• impact:ux-friction: Users cannot recreate a previously available percentage-plus-pace layout through the new editor, despite other menu-bar tokens remaining usable.

Evidence reviewed

What I checked:

• Current token catalog: Current main defines layout tokens for percentage windows, usage bar, reset times, and runs-out, but no signed pace token. (Sources/CodexBar/MenuBarLayout.swift:10, 5b0b9fa3e37c)
• Renderer behavior: The renderer has a percentage-window branch and a separate runs-out branch; there is no branch that renders a numeric pace delta. (Sources/CodexBar/MenuBarLayoutRenderer.swift:230, 5b0b9fa3e37c)
• Legacy migration proves the semantic gap: The layout migration maps legacy Pace and Both display modes to the runs-out token, so the current layout path substitutes an ETA for the prior pace-oriented presentation. (Sources/CodexBar/MenuBarLayout.swift:222, 5b0b9fa3e37c)
• Released documentation: The shipped token reference lists Session %, Weekly %, Auto %, Usage bar, Resets in, Reset at, and Runs out; it describes Runs out as a pace estimate rather than a signed delta. (docs/ui.md:24, b1170d83963d)
• Feature provenance and likely owner: The menu-bar layout editor was merged through commit ecadcb1 by Peter Steinberger and is contained in release v0.45.0; the current token structure descends from that feature. (Sources/CodexBar/MenuBarLayout.swift:10, ecadcb1df43b)
• Existing implementation candidate: The linked open PR at Add menu bar pace layout tokens #2540 proposes Session, Weekly, and Auto pace tokens, includes regression coverage according to its discussion, and its prepared release-build screenshots visibly show signed deficit, reserve, and unavailable-placeholder states.

Likely related people:

• Peter Steinberger: Merged the menu-bar layout editor and is the sole visible author in the available local history for the current layout-token source boundary. (role: layout feature owner and merger; confidence: high; commits: ecadcb1df43b, b1170d83963d; files: Sources/CodexBar/MenuBarLayout.swift, Sources/CodexBar/MenuBarLayoutRenderer.swift, docs/ui.md)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[WilliamK6]

Thanks for the review. I have attached a screenshot of the current Menu Bar → Layout token catalog in v0.45.x.

The screenshot shows all currently available tokens:

• Session %
• Weekly %
• Auto %
• Usage bar
• Resets in
• Reset at
• Runs out

There is no token for the signed numeric session pace previously available through the old “Both” display mode.

Expected

A first-class Session pace token restoring the former display, for example:

40% · +11%

Actual

The closest available token is Runs out, but it displays an estimated exhaustion time rather than the numeric ahead/behind-pace delta.

To keep the scope narrow, this issue only requests restoration of the pace value for the Codex session window. Weekly and Auto support can be considered separately.