Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Codex: expose provenance-aware plan and allowance metadata in Hooks

Open
  • Is something wrong?
#4,775 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@LeoLin990405 is already working on this.

Since Oct 27, 2026.

  • #4800 by @LeoLin990405 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
api

Research direction

Read Sources/CodexBarCore/Hooks/HookEvent.swift and Sources/CodexBarCore/Providers/Codex/CodexPlanFormatting.swift to understand current Hook fields and how display labels are mapped. Check existing usage metadata and tests before proposing a structured representation for provider-reported values, estimates, and unknowns. Done means Hooks can expose provenance-aware plan and allowance changes without treating display labels or observation time as verified facts.

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:queueable-fix issue-rating: 🌊 off-meta tidepool no-stale P3

I use CodexBar’s Hooks to keep a private history of my remaining Codex allowance. When a subscription tier or temporary allowance boost changes, the same percentage can represent a different amount of available usage. I would like to compare those periods without manually maintaining plan changes.

In v0.81.0, CodexPlanFormatting maps pro to Pro 20x and prolite variants to Pro 5x. A formatted label alone therefore cannot establish the currently effective multiplier. HookEvent does not include plan or allowance metadata, although other outputs already expose a plan display label.

Would you consider adding optional structured metadata to usage Hooks?

  • The observed plan/tier and its source.
  • A verified allowance multiplier, reference baseline and applicable quota window, only when the available source supports it. Otherwise leave it unavailable, rather than infer it from price or a display label.
  • Observed plan/allowance changes through a dedicated event or timestamped usage metadata. Observation time should not imply exact effective time unless supplied upstream.

This would let external charts show percentage remaining or baseline-normalized allowance, with estimates and unknown values explicit. Display mappings should remain distinguishable from provider-reported values. No credentials or account-identifying information are needed.

If an existing field or issue covers this, please point me to it; I would prefer to reuse it.

Source: https://github.com/steipete/CodexBar/blob/v0.81.0/Sources/CodexBarCore/Providers/Codex/CodexPlanFormatting.swift
Hook fields: https://github.com/steipete/CodexBar/blob/v0.81.0/Sources/CodexBarCore/Hooks/HookEvent.swift

Dominant language
Swift
Stars
22.8k
Forks
2.2k
Avg merge
21h 55m
Merged PRs (30d)
403

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from steipete/CodexBar

All issues in steipete/CodexBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.