Skip to content

feat(FIX-2142): show Claude Code usage left, from its runs - #3795

Merged
jhoffner merged 9 commits into
claude/project-thread-8qgqolfrom
claude/project-thread-3x3z3h
Oct 25, 2026
Merged

jhoffner merged 9 commits into
claude/project-thread-8qgqolfrom
claude/project-thread-3x3z3h

Conversation

@jhoffner

Copy link
Copy Markdown
Collaborator

Requested by Jake · project thread

The problem

A person running Shift Manager on a Claude subscription can't see how close Claude Code is to its 5-hour or weekly limit. They find out when a run stops. The Usage view from FIX-2141 shows Codex only.

What this does

Usage gets a Claude Code card. Each window a run reported shows its limit, its reset time, and how close it is. That is a percent when Claude Code sent one (it sends one only near a limit) and otherwise words: "under Claude Code's warning line", "near its limit", "limit reached". The card says the window came "from a run, X ago". An API-key or signed-out Claude Code says so, with no window.

The windows come from the rate_limit_events Claude Code sends during a run. claudeCodeAgent takes a new onUsage hook, and the harness manager and the session door both pass one that writes into the same per-user usage record as Codex. Looking at Usage asks who is signed in (readClaudeUsage) and adds the plan, but no windows, because no allowed source gives a percent without a run. Nothing reads a credentials file, calls a usage endpoint, or uses the SDK's experimental usage call.

What's asked of you

Nothing new: this implements the approved spec (specs/issues/FIX-2142/). Three Codex findings on the spec were still open when it merged. All three are fixed in the writer (see Engineering calls), and one of them changes a rule the spec stated. It makes the writer more conservative, so there's nothing to approve beyond reading it.

Leg g is owed by a person. No CI has a Claude sign-in. Until you run a real coding task on your own Claude subscription and compare Usage with Claude Code's /status, the verdict is goal met except leg g.

Parts worth reviewing closely

  1. packages/harness-manager/src/harness-usage.ts: applyReading and applyRunWindow (pure), which share accountStep. These cover account rebinds, accountAt ordering, and when a run may lift a no-number status.
  2. packages/claude-code/src/sdk/agent.ts: the rate_limit_event branch. The account is asked once per run (accountInfo(), 5 s cap). The hook is awaited and tracked, a throw is logged and the run carries on, and it is not fenced by inSessionOnly.
  3. goals/shift-manager/it-shows-claude-usage-left/: the scripted SDK seam, and leg d's talk through the session door.

FIX-2142 · epic FIX-2139 · spec #3771 (merged) · stacked on #3768 (FIX-2141) · merges when approved

How to review this

How to review this. This implements an approved spec: a human has already signed off on the approach and the numbered decisions in its DECISIONS.md. Please review the code against that direction, not the direction itself. The canonical set is retained at specs/issues/<ISSUE-ID>/ on main. Linear links to it and to the original merged spec PR, which keeps the review history. Follow-up amendment PRs explain later changes of direction. Current architecture docs remain the authority for shipped behavior (BP-037).

Most valuable here:

  • correctness on the second path: the legacy shape, the null boundary, the concurrent case, the cancel path;
  • anything deriving an auth or routing decision from caller-controllable input;
  • a behaviour the tests assert around rather than on.

Already settled upstream: the approach and every decision in the spec's DECISIONS.md, and the conventions in docs/contributing/best-practices.md. If a decision is wrong, say so as a spec finding and it gets folded back. Don't re-argue it inline.

Engineering calls

The three Codex findings open at the spec's merge (#3771, commit e465664) are fixed here, with unit tests in harness-usage.spec.ts:

  • Named to token-only is a rebind. A null account counts as an identity of its own, so any change of account, in either direction, clears the windows and the plan. This replaces the spec's "a reading with no account keeps the stored one". It is the conservative side of the same rule the spec applied to null-to-named.
  • accountAt advances on every accepted write, not only on a rebind, so the A→B(stalled)→A ordering can't let the late B win.
  • A no-number reading older than accountAt is refused, so a delayed api-key or signed-out look can't clear a newer run's window. A run write advances accountAt to its observed time.

Other calls:

  • usedPercent is rounded to one decimal place (0.29 → 29, not 28.999…). A utilization above 1 is not a fraction and is dropped. An event with no rateLimitType (an API-key run) writes nothing.
  • Window lengths: five_hour is 300 minutes, and every seven_day* is 10 080. Any other id has no length and is labelled by its id.
  • The fsd profile gets the claude-code reader too (teams/devteam/fsd.fsdev.config.mts). The spec named only the devteam config, but the profile already serves Usage, so leaving it out would show Claude Code as "not checked yet" there forever.
  • The goal's SDK seam: lab/scripted-sdk.mjs replaces @anthropic-ai/claude-agent-sdk through the goals' module patch. It answers runs with per-status event fixtures, in the shape the pinned CLI (0.3.234) builds, and passes the account probe through to the real SDK for the empty-home and API-key looks.
  • HarnessFeeds.onUsage is required, like the other feeds. DevTeam's harness stub, and the two goals that wrap claudeCodeHarness, now pass the feeds through whole.
Everything else

Verification (local, on this head's content):

  • Goal check goals/shift-manager/it-shows-claude-usage-left/run.mts: PASS on legs a–f in 97 s, with g owed. Each control FAILs where it must:

    • no-scale → b:91 (0.91%)
    • absent-as-zero → a:no-number (0%)
    • fan-out → d:no-claude-window
    • read-replaces-run → e:keeps-the-runs-window

    The verdict table is in goal.md.

  • The Codex goal (it-shows-codex-usage-left) still PASSes over the reworked writer. Its five controls were re-pointed at the writer's new lines, and each still fails on its own assertion.

  • Tests:

    • @flow-state-dev/core 2519
    • @flow-state-dev/claude-code 348, including the new test/sdk/usage.spec.ts
    • @flow-state-dev/harness-manager 287 (harness-usage.spec.ts now 22)
    • @flow-state-dev/codex 109
    • @flow-state-dev/shift-manager 566 (usage.test.ts gains levelLabel). command.test.ts fails locally on the base branch too, because the pages are not built here.
  • pnpm typecheck, check-retired-terms and check-new-dead-code PASS.

  • Docs were written by the docs-writer pass, and a separate docs-editor pass checked them against the source. The docs site builds.

Files

  • packages/core/src/types/harness.ts:
    • usedPercent is nullable.
    • level is new; the schema defaults it to null, so stored Codex rows still parse.
    • New HarnessUsageReport and HarnessUsageHook.
  • packages/claude-code/src/sdk/usage.ts (new): usageWindowOf, readClaudeUsage, CLAUDE_CODE_HARNESS. Also agent.ts (onUsage) and types.ts.
  • packages/harness-manager:
    • harness-usage.ts: accountAt, the run-window writer, and the recordHarnessUsage(ctx, report) overload.
    • manager.ts: HarnessFeeds.onUsage, the collection installed, and a reserved accessor.
    • session-door.ts: the same feed and collection.
  • packages/codex/src/usage.ts: windows get level: null.
  • packages/shift-manager:
    • Usage card: level wording and run age.
    • DevTeam harness feeds, plus the claude-code reader in both configs.
  • Docs:
    • Tools → Claude Code SDK ("Reading usage left")
    • Tools → Coding agents
    • Orchestration → Harness manager
    • READMEs of core, claude-code, harness-manager and shift-manager
  • Changeset: patch bumps for the five published packages.

Generated by Claude Code

Claude Code's rate_limit_event windows reach the per-user usage record through
a new onUsage hook on claudeCodeAgent, fed by the harness manager and the
session door. readClaudeUsage adds the account and plan. Windows gain a
nullable usedPercent and a level; the record gains accountAt. The writer also
folds in the three Codex findings open on the spec at merge.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG
@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 23, 2026 11:59pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 23, 2026 11:59pm UTC
flow-state-dev-ui Ignored Ignored Preview Oct 23, 2026 11:59pm UTC

Request Review

@linear-code

linear-code Bot commented Oct 23, 2026

Copy link
Copy Markdown

FIX-2142

@jhoffner jhoffner self-assigned this Oct 23, 2026

Copy link
Copy Markdown
Collaborator Author

@codex review

Please look hardest at:

  • packages/harness-manager/src/harness-usage.ts, specifically accountStep, applyReading and applyRunWindow. Check the ordering under concurrent writes and late retries: account rebinds (including named↔null), accountAt advancing on every accepted write, a no-number reading older than accountAt being refused, and a run lifting a no-number status only if it started after checkedAt.
  • packages/claude-code/src/sdk/agent.ts, the rate_limit_event branch. Check the abort path, the one-time accountInfo() with its 5 s cap, a hook throw that must not fail the run, and in-flight tracking.
  • The session door (session-door.ts): its writes must land only in the talking user's row.
  • BP-030: whether the legacy row (no level, no accountAt) still parses.

Generated by Claude Code

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-24T00:01:40.536389Z 9722357 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Copy link
Copy Markdown
Collaborator Author

Second look + architecture pass (FIX-2142)

Reviewed the code against the approved spec, not the direction. Two findings are worth acting on and the rest are notes. Nothing here re-opens a spec decision.

1. Real bug: a slow or failed accountInfo() wipes the stored windows and plan

packages/claude-code/src/sdk/agent.ts (accountOf) returns null on timeout (5 s), on a throw, and when accountInfo isn't a function. It returns null for a genuine token-only sign-in too. applyRunWindow (harness-usage.ts) now treats null as an identity of its own, which is the rule this PR adds. So a signed-in named account whose probe is merely slow produces null, which is a rebind. That clears the plan and every other window, and the stored account becomes null. The next run whose probe answers (named account) rebinds again and clears them again.

So a transient probe failure is indistinguishable from "this is a token-only account" and costs the person their readings. The "null is its own account" rule is only safe if null means known to name no account, not couldn't find out.

Suggested fix: let accountOf return undefined (or a tagged "unknown") for timeout, throw and missing method. When the account is unknown, skip the report. It's the safe side, since the event only refreshes one window. Only a probe that answered with no email should report accountId: null. Add a unit test: named stored account + unknown-account run event leaves the windows and plan intact.

2. Orphaned doc comment (BP-034)

agent.ts around the new ACCOUNT_TIMEOUT_MS / accountOf: the JSDoc for resolveMcpTools ("Call a mcpTools resolver, racing it against the run's signal…") now sits above ACCOUNT_TIMEOUT_MS, and resolveMcpTools has lost its doc. Move the new constant and accountOf above that comment, or into usage.ts (see 4).

3. The first usage event blocks the vendor stream for up to 5 s

The hook is awaited inside the message loop, and the first event also awaits accountOf (5 s cap). The awaiting is deliberate (nothing lands after the run ends) and matches onSession. But the cost is paid in the middle of the stream, on the first event of every subscription run. Cheaper shape: start accountOf when the query starts, or at init, and let it resolve in the background. By the first rate_limit_event it has usually settled, and the per-event await then costs nothing. Optional, but if you take fix 1 this is a small extra change in the same lines.

4. Architecture notes (only because this PR is already in these files)

  • accountOf belongs in sdk/usage.ts with usageWindowOf and readClaudeUsage. It is Claude-account logic, not run-loop logic, and agent.ts is already very large. It also makes fix 1 unit-testable without driving a fake query. This is the one refactor worth doing here, because the PR touches the code anyway.
  • recordHarnessUsage overloads (string+reading vs report) force typeof harnessOrReport === "string" plus non-null assertions (reading!, checkedAt!). Two named exports (recordHarnessReading / recordHarnessRunWindow) sharing the CAS body would drop the assertions. Low priority; the existing Codex callers are the only reason to keep the overload.
  • applyReading and applyRunWindow both compute accountAt the same way (rebind ? t : max(stored, t)). A one-line helper beside accountStep removes the drift risk. Don't generalize beyond that. The two functions otherwise differ enough on purpose.
  • Not worth changing: the HarnessFeeds.onUsage required-field ripple, the per-process inFlight map (already documented), and the scripted SDK seam in the goal.

5. Test gaps on the second path

  • No test where the stored row is a legacy Codex row (level and accountAt absent) and a Claude run window arrives. The schema defaults handle it, but the PR claims BP-030 tolerance, so pin it.
  • utilization exactly 0 and exactly 1 (boundaries of >= 0 && <= 1) are untested in usage.spec.ts. 0 shows "0%" and not "under the warning line", which is the absent-as-zero control's whole point.

Net: fix 1 before merge; 2 is a trivial fix; 3 and 4 are optional but cheap while in these lines; 5 is test-only.


Generated by Claude Code

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplify pass (FIX-2142)

Verdict: The dual path (on-demand readClaudeUsage for account/plan + run-time onUsage for rate_limit_event windows) is the right shape for this vendor surface, not an over-built fork of Codex. Codex can fill HarnessUsageReading.windows from account/rateLimits/read; Claude has no sanctioned off-run percent API in this stack, so pushing merge semantics into harness-usage and a fourth HarnessFeeds hook is load-bearing. The goal controls (read-replaces-run, absent-as-zero, fan-out) make that case: simpler policies fail the product bar.

Where the weight is: Most new complexity sits in applyReading / applyRunWindow (account rebind, runStartedAt vs checkedAt, keeping run windows across refresh). That is hard to read, but it is tested and documented; I would not collapse it without dropping requirements.

Simpler approaches that do not fit (unless product changes):

  • Polling-only / reader-only for Claude → Usage stays empty until someone runs work and hits limits.
  • Claude-only sidecar storage → duplicates the shared harnessUsage query or leaves Claude off the same screen as Codex.
  • A third-party rate-limit library → does not replace the store-backed refresh claim without losing cross-host throttle semantics.

Low-cost simplifications worth considering (none blocking): optional onUsage on HarnessFeeds (docs already say harnesses that report nothing ignore it), tighten origin to an enum, align Claude reader registration with Codex by threading signal, and reduce shift-manager DTO drift (see inline).

No performance concerns at expected rate_limit_event frequency; awaiting onUsage on the SDK loop is intentional so writes cannot land after the run ends.

Approving directionally — merge logic is the main long-term maintenance cost, and the tests/docs are the right mitigation.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread packages/harness-manager/src/manager.ts Resolved
Comment thread packages/shift-manager/src/lib/usage.ts Resolved
Comment thread packages/claude-code/src/sdk/agent.ts Resolved

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Snob — already tight on 6351a16. No POC.

I read packages/harness-manager/src/harness-usage.ts (accountStep, applyReading, applyRunWindow, recordHarnessUsage), packages/claude-code/src/sdk/usage.ts, the rate_limit_event branch and accountOf in packages/claude-code/src/sdk/agent.ts, HarnessUsageWindow / HarnessUsageReport in packages/core/src/types/harness.ts, windowsOf in packages/codex/src/usage.ts, levelLabel and Usage.tsx, the manager and session-door onUsage feeds, claudeCodeHarness (it already spreads feeds), the goal (run.mts, controls.mts, lab/scripted-sdk.mjs, lab/fsdev.config.mts), and the writer tests.

A rewrite does not shrink the contract:

  • accountStep is the one comparison both writers share. Inlining repeats the null-account rule. A helper that also hashes is the same length.
  • The run-window keep is one line (read-replaces-run patches it). A Map changes window order. Folding applyRunWindow's two scans saves about a line.
  • The recordHarnessUsage overload is shorter than a second writer plus a shared compare-and-swap. The four-argument form is the existing call.
  • The two onUsage feeds are the same call with different reasons (a replaced attempt is still a true reading; a talk writes the person talking). One shared feed drops the second.
  • accountOf is the 5s cap on the query this run already holds. Inlining it into the message loop is longer.
  • WINDOW_MINUTES names the ids that have a length. A seven_day prefix would lengthen an id the table leaves unlabeled.
  • levelLabel is the three words. The card shows words when the level is reached or there is no percent, and the percent otherwise.
  • claudeCodeHarness already spreads the feeds, and the two goals pass them through whole. HarnessFeeds extends the manager's.
  • The unit test's resolveClaudeAgent and the goal's SDK module seam are two fakes. Folding them hides the load path the goal grades.
  • applyReading and applyRunWindow stay off the package index. The ordering cases call them so each one does not boot a flow.

The long notes are the rules the names do not carry: a null account rebinds either way, accountAt moves on every taken write, a no-number look older than accountAt is refused, and a run lifts api-key only when it started after that look. I left the recorded calls (one-decimal percent, utilization above 1 dropped, the fsd reader, required onUsage, the scripted seam).

Open in Web View Automation 

Sent by Cursor Automation: Code Snob

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6351a16aa9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .changeset/claude-code-usage-left.md Resolved
Comment thread packages/claude-code/src/sdk/usage.ts Resolved
The usage reader now threads its abort signal through probeClaudeAccount
and the idle query, so a refresh that gives up closes Claude Code instead of
leaving it waiting out the probe's timeout. HarnessFeeds.onUsage is a new
required field, so harness-manager's bump is minor. Stored window origin is
an enum, and Shift Manager's usage level reuses core's type.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG

Copy link
Copy Markdown
Collaborator Author

@codex review

This is on 3d82a64. Please check the new abort path in packages/claude-code/src/sdk/idle-query.ts: a signal that is already aborted, removing the listener, and the handle being closed on abort. Also check that the origin enum still parses every stored row.


Generated by Claude Code

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3d82a64dc4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/claude-code/src/sdk/usage.ts Resolved
… read

A probe that times out, is aborted or throws now marks its none as
unanswered, and readClaudeUsage reads that as unavailable, so a failed
refresh keeps the last good reading instead of clearing it as signed-out.
A run whose account lookup fails drops that window rather than record it
under a null account, which would rebind the row.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG

Copy link
Copy Markdown
Collaborator Author

@codex review

This is on 6db241a. Please check the new "unknown account" path:

  • accountOf returning undefined, and the run dropping that window and retrying on the next event (agent.ts).
  • probeClaudeAccount's unanswered flag mapping to unavailable in readClaudeUsage, which must keep the stored reading.

Generated by Claude Code

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Copy link
Copy Markdown
Collaborator Author

@codex review

The last run on 6db241a failed on Codex's side. Same focus as before: the unknown-account path in agent.ts (accountOf → undefined, window dropped, retried next event), and unanswered → unavailable in readClaudeUsage.


Generated by Claude Code

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…to claude/project-thread-3x3z3h

# Conflicts:
#	packages/codex/src/usage.ts
#	packages/core/src/types/harness.ts
#	packages/shift-manager/src/lib/usage.ts
#	packages/shift-manager/test/usage.test.ts

Copy link
Copy Markdown
Collaborator Author

Test (2/3) failed on 6db241a in @flow-state-dev/store-postgres, at delta-verbs.test.ts:312. That test is a timing benchmark (patchField must take less than 3× the time of set on PGlite), and the run measured 286 ms against a 240 ms limit. This PR doesn't touch store-postgres or anything it depends on, so this isn't this PR's failure, and no fix for it exists yet. My next push merges #3768's new head and re-runs the whole suite on a new commit.


Generated by Claude Code

@jhoffner

Copy link
Copy Markdown
Collaborator Author

Architect: not approving yet. The diff is fine, but this PR is stacked on #3768 (base claude/project-thread-8qgqol), which is still held on an open P2. Retargeting to main once #3768 merges would unblock the label.

— FSD Architect

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7728056c83

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

An unavailable reading kept the stored record only once a look had set
checkedAt, so a run's windows written before any look were cleared by a
failed first refresh. It now keeps any record that holds something.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG

Copy link
Copy Markdown
Collaborator Author

@codex review

Both round-3 P2s are fixed (0eeb790, cb079fc), and base 394d8ae is merged in. Please look closely at the ordering rules in applyReading / applyRunWindow in packages/harness-manager/src/harness-usage.ts: when a failed look keeps what is stored, and when a run that started before a look may still write.


Generated by Claude Code

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cb079fcaaa

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…on an unanswered look

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAhoCzQzu8TK82zvC4anTG
@jhoffner
jhoffner added this pull request to stack #3880 October 25, 2026 16:21
@jhoffner
jhoffner merged commit 16a8dab into main Oct 25, 2026
18 checks passed
@jhoffner
jhoffner deleted the claude/project-thread-3x3z3h branch October 25, 2026 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants