Codex review: needs real behavior proof before merge. Reviewed July 5, 2026, 8:04 AM ET / 12:04 UTC.

Summary
This branch rewrites the connected Control UI Overview into an operator dashboard, adds provider-native usage/quota rendering including OpenRouter credit/key usage hooks, and updates related tests, docs, styles, and i18n bundles.

PR surface: Source +3817, Tests +475, Docs +7, Other -17. Total +4282 across 75 files.

Reproducibility: yes. for the review blockers: source inspection shows the branch only loads usage for oauth/token profiles and copies cached quota windows on empty refresh, so the two provider-usage findings are reproducible from code.

Review metrics: 1 noteworthy metric.

• Provider Usage Contract Changes: 1 provider id added, 3 window label fields added. The diff changes shared gateway, CLI, and UI usage shapes plus auth-provider display behavior, so compatibility and upgrade behavior need focused review before merge.

Stored data model
Persistent data-model change detected: persistent cache schema: scripts/check-architecture-smells.mjs, persistent cache schema: scripts/lib/extension-import-boundary-checker.mjs, serialized state: extensions/openrouter/usage.test.ts, serialized state: scripts/check-architecture-smells.mjs, serialized state: scripts/lib/extension-import-boundary-checker.mjs, serialized state: scripts/lib/source-file-scan-cache.mjs, and 3 more. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🦪 silver shellfish
Proof: 🦪 silver shellfish
Patch quality: 🦐 gold shrimp
Result: blocked until stronger real behavior proof is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• [P1] Fix OpenRouter API-key usage enrollment and stale quota preservation.
• [P1] Add redacted live OpenRouter usage-path output, logs, diagnostics, or a recording that proves the real credential/network path.
• Rebase and resolve the relationship with the overlapping Overview dashboard PR.

Proof guidance:

• [P1] Needs stronger real behavior proof before merge: The supplied screenshots show synthetic fixture renders, but the PR adds a live OpenRouter credential/network usage path that still needs redacted terminal output, logs, live output, diagnostics, or a recording showing the real request path. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Mantis proof suggestion
A visible Control UI dashboard redesign would benefit from real connected and disconnected browser proof once the provider blockers are repaired. A maintainer can ask Mantis to capture proof by posting this exact PR comment:

@openclaw-mantis visual task: capture connected Control UI Overview showing provider quota data and disconnected Gateway Access/Snapshot behavior.

Risk before merge

• [P1] Normal OpenRouter API-key installs may not show the advertised credit display because the branch adds OpenRouter usage hooks but does not enroll API-key OpenRouter profiles in models.authStatus usage loading.
• [P1] A refreshed empty usage response can preserve and display a previous account or key's quota because cached windows are copied by provider id without identity continuity.
• [P1] The screenshots prove synthetic fixture rendering, not the live OpenRouter credential/network path added by the PR.
• [P1] The PR is draft and conflicting, and it overlaps feat: redesign control overview dashboard #77774, so maintainers still need to choose or consolidate the canonical Overview dashboard direction.

Maintainer options:

1. Fix Provider Usage Before Merge (recommended)
   Enroll OpenRouter API-key usage through the current auth-status contract and clear or identity-gate empty usage refreshes.
2. Accept Fixture Layout Proof Only
   Maintainers could accept the synthetic screenshots for layout review, but the live OpenRouter credential/network path would remain unproven.
3. Pause For Dashboard Consolidation
   Pause this PR until the overlapping Overview redesign is resolved and the branch is rebased out of conflict.

Next step before merge

• [P1] Human handling is needed because the PR is draft/conflicting, lacks live OpenRouter proof, and needs product-direction reconciliation with the overlapping Overview redesign.

Maintainer decision needed

• Question: Should this PR become the canonical operator-first Overview dashboard, should feat: redesign control overview dashboard #77774 own that redesign, or should both be narrowed before either lands?
• Rationale: Both open PRs redesign the same Control UI Overview surface, and automation cannot choose the product direction or reconcile the conflicting branches safely.
• Likely owner: steipete — This person authored the overlapping maintainer-labeled dashboard PR and has recent history on the Overview/provider quota surface.
• Options:
  • Repair And Decide Canonical (recommended): Keep this PR open while the contributor fixes provider/proof blockers, then have maintainers choose whether it or the overlapping dashboard PR should carry the final Overview redesign.
  • Move Direction To The Other PR: Use feat: redesign control overview dashboard #77774 as the canonical dashboard redesign and ask this PR to extract only non-overlapping provider-usage pieces.
  • Pause Both Redesigns: Hold both dashboard PRs until maintainers define the first-screen Overview information architecture and proof requirements.

Security
Cleared: No concrete supply-chain, permission, or secret-handling regression was found; the credential-backed concerns are functional auth-provider blockers covered by review findings.

Review findings

• [P2] Enroll OpenRouter usage before advertising credits — extensions/openrouter/index.ts:173-181
• [P2] Gate cached quota preservation on account continuity — src/gateway/server-methods/models-auth-status.ts:107-113

ClawSweeper PR egg

🔥 Warming up: real-behavior proof passed; findings, security review, or rank-up moves are still in progress.

Hatch command

Comment @clawsweeper hatch when this PR is hatchable.

Hatchability rules:

• Merged PRs are hatchable.
• Open PRs are hatchable when they are status: 👀 ready for maintainer look, status: 🚀 automerge armed, or labeled clawsweeper:automerge.
• Closed unmerged PRs are hatchable only when one of those hatchable labels is still present in the durable record.

@clawsweeper re-review

Updated in abc70d034f8948bcf2f2ca39b26536847dd8bc45:

• Restored digit-run blurring for connected Overview recent-session names.
• Added a regression test covering a numeric iMessage-style direct session identifier.
• Moved new operator Overview copy into Control UI i18n keys and ran locale sync/check.
• Rebuilt and installed the Control UI bundle locally, then exercised the connected Overview with Playwright.

Validation:

npm test -- src/ui/views/overview.render.test.ts
npm test -- src/ui/app-render.helpers.node.test.ts
pnpm ui:i18n:sync
pnpm ui:i18n:check
npm run build
git diff --check

Real behavior proof from the connected local Gateway Overview after installing the built bundle:

{
  "hasOverview": true,
  "recentRows": 3,
  "moreButtons": [
    "6 more sessions"
  ],
  "usageNote": "Codex 5h window resets 2m."
}

The redacted screenshot was captured locally during that same proof run after replacing private identifiers before capture.

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

@clawsweeper re-review

The PR body now uses the required Real behavior proof fields, and the latest Real behavior proof check passes on abc70d034f8948bcf2f2ca39b26536847dd8bc45.

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

Re-review progress:

• State: Complete
• Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/26401907574
• Updated: 2026-05-25T13:14:35.417Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

• State: Complete
• Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/26404072286
• Updated: 2026-05-25T14:04:25.893Z

@clawsweeper re-review

Current head: 0f16555433e6ac5ea4023c60b5e6b86e93c48744.

Please re-review the current head after the latest main sync, conflict resolution, provider-title change, and PR body/proof refresh.

Since the earlier needs-changes review, this branch now:

• Uses quota data from any provider that reports it, including API-key providers, while keeping OAuth/token auth-health rollup separate.
• Preserves OpenRouter provider-native credit labels and avoids forcing labels like Credits quota.
• Updates the Overview usage card title to the rendered primary quota provider when quota data is present, for example Codex Usage or OpenRouter Usage.
• Keeps fallback wording generic while loading or when no provider quota data exists.
• Refreshes sanitized Codex/OpenRouter screenshots and PR proof text.

Latest local validation completed before this re-review request:

pnpm ui:i18n:check
pnpm --dir ui exec vitest run --config vitest.config.ts src/ui/views/overview.render.test.ts src/ui/views/chat.test.ts
pnpm --dir ui exec vitest run --config vitest.config.ts src/ui/views/overview.render.test.ts src/ui/views/chat.test.ts src/ui/views/provider-auth.test.ts
pnpm ui:build
git diff --check
PNG dimension/string checks for sanitized screenshots
raw screenshot URL 200 checks

Current GitHub state observed before this comment: PR is still draft, mergeable, and current visible checks are pass/skip except Socket Project Report still pending.

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

• State: Complete
• Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/26510857681
• Updated: 2026-05-27T12:36:20.456Z

@homer-byte thanks for the PR. ClawSweeper is still waiting on real behavior proof before this can move forward.

Useful proof can be a screenshot, short video, terminal output, copied live output, linked artifact, or redacted logs that show the changed behavior after the fix. Please redact private tokens, phone numbers, private endpoints, customer data, and anything else sensitive.

Once proof is added to the PR body or a comment, ClawSweeper or a maintainer can re-check it.

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

ClawSweeper status: review started.

I am starting a fresh review of this pull request: Redesign Overview as an operator-first OpenClaw dashboard This is item 1/1 in the current shard. Shard 12/22.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.