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

Price deduplicated Codex request subtotals across SSH hosts

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the existing Codex-only JSON CLI export from #4447 and the pricing behavior referenced by #3036; the payload does not name source files or tests. Trace how request identities and token categories are exported, then identify where model evidence and a single pricing snapshot can be applied. Done means deduplicated requests are priced only when model evidence is consistent and every accepted request has a price, with missing prices reported as null and partial or conflicting records preserved.

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster P3

The situation

I use Codex on a Mac and over SSH. #4447 now gives me an identified-request subtotal across both machines, with copied requests counted once. costUSD is still null.

What works today, and why it is not enough

Separate host reports estimate dollars, but adding them would double-count copied history, as discussed in #3036. The identified export already carries a length-framed SHA-256 identity from provider, session/thread ID and response ID, restricted to native requests owned by that session.

Ask

Extend that contract to price the identified subtotal:

  • Keep the existing identity and UTC window. Copies count once; token or timestamp conflicts stay excluded even after another clean copy appears.
  • Carry the request's model identifier alongside its token categories. Price the deduplicated records with one pricing snapshot on the collecting machine. Pricing conflicts retain tokens with an unknown price.
  • Return numeric costUSD only when every accepted request can be priced. Missing model or price means null, never zero. Preserve explicit partial-source and excluded/conflicting-request reporting.
  • Keep the export limited to accounting fields and hashed identity: no prompts, paths or raw session/response IDs. Make the snapshot version boundary explicit.

First slice: pricing for the existing Codex-only JSON CLI path. App presentation and per-machine grouping come afterward; Claude Code and Pi need their own identity contracts.

Refs #3036
Refs #4447

Dominant language
Swift
Stars
22.8k
Forks
2.2k
Avg merge
23h 46m
Merged PRs (30d)
372

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.