Context gauge for Codex team members (TODOS.md)

Closed
#414 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@Yash-Nimkar0 is already working on this.

Since Oct 14, 2026.

  • #415 by @Yash-Nimkar0 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
devtools

Research direction

Start with readContextTokens, which only parses Claude Code transcripts, and with findRollout in codexUsage.ts, which already locates the Codex rollout file. Read the last token_count event and its last_token_usage field to see the context size. Done means a Codex agent's context gauge shows a value, covered by tests using sample rollout files. Pull request #415 is already open against this issue, so check it before starting.

Written by the indexing model from the issue text.

Description

enhancement
Problem / motivation

The context gauge stays empty for a Codex team member. hive:agentContext reads the agent's transcript with readContextTokens, which only understands Claude Code's transcript format. TODOS.md lists this under "Make a second engine (Codex first) ready for an office", gap 2: "the context gauge for Codex (readContextTokens reads only the default engine's transcripts)".

Proposed solution

For a Codex agent, read the context size from its rollout file, which the app already finds for usage (findRollout in codexUsage.ts): the last token_count event's last_token_usage. Tests with sample rollout files.

I'd like to take this one and will open a PR.

Screenshot, mockup or recording

No response

Alternatives considered

No response

Area

Other

Pre-flight
  • I attached a screenshot, mockup or recording above.
  • I searched existing issues and discussions, and this isn't a duplicate.
Dominant language
TypeScript
Stars
273
Forks
211
Avg merge
2d 18h
Merged PRs (30d)
385

Getting set up

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 agentvivekkumar/dontbemichael

All issues in agentvivekkumar/dontbemichael

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.