fix(usage): hide the Cursor keychain prompt when Cursor isn't set up

[Gigioxx]

The Usage page asks for macOS Keychain access to Cursor on every Mac environment, even when Cursor isn't installed, is disabled, or its CLI isn't working. For most people that card is just noise.

Fix

The Enable prompt now shows only when that environment's Cursor provider is ready. The check lives in needsCursorKeychainAccess in client-runtime, and web and mobile share it. The Cost/Tokens rows and the Limits card both read it. You can still turn it on from Cursor's provider settings.

No server or contract change.

Before	After

Proof: With a real data copy and no Cursor CLI installed, the Limits card and the Cost row are gone after this change. src/state/usage.test.ts in client-runtime (9 tests, including the new readiness cases) and src/state/usage.test.tsx in web both pass. tsc --noEmit passes for client-runtime, web, and mobile.

Made by Claude Opus 5.5 (1M context) in Claude Code, running in T3 Code.

Summary by CodeRabbit

• Bug Fixes
  • Cursor keychain-access prompts are now shown only when the usage summary calls for them and a Cursor provider is ready. Prompts are no longer shown when provider information is missing, disabled, or in an error state. This behavior is consistent across mobile and web.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 5ccd200c-15d1-49be-820a-2bd4c399b705

📥 Commits

Reviewing files that changed from the base of the PR and between ed809f7 and c8e1185.

📒 Files selected for processing (7)

• apps/mobile/src/features/usage/UsageRouteScreen.tsx
• apps/mobile/src/state/usage.ts
• apps/web/src/components/usage/UsagePage.tsx
• apps/web/src/state/usage.test.tsx
• apps/web/src/state/usage.ts
• packages/client-runtime/src/state/usage.test.ts
• packages/client-runtime/src/state/usage.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

A shared predicate identifies environments with a ready Cursor provider and a usage summary that includes the Cursor keychain action. Mobile and web usage state expose the result, and their screens use it to select environments for existing Cursor enable prompts.

Changes

Cursor keychain access

Layer / File(s)	Summary
Define and test the access predicate packages/client-runtime/src/state/usage.ts, packages/client-runtime/src/state/usage.test.ts	Adds and tests needsCursorKeychainAccess. It returns true only when the summary includes the Cursor keychain action and a Cursor provider is ready.
Expose and consume access status apps/mobile/src/state/usage.ts, apps/mobile/src/features/usage/UsageRouteScreen.tsx, apps/web/src/state/usage.ts, apps/web/src/components/usage/UsagePage.tsx, apps/web/src/state/usage.test.tsx	Mobile and web usage state compute and expose the predicate result. Their screens select environments using the status flag. The web test fixture initializes the new field.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: stienswout, juliusmarminge

Merge Risk: ⚪ Minimal · up to c8e11

The Cursor Keychain prompt is limited to environments with a ready Cursor provider. No merge-blocking issue is identified.

Security Architecture Review

Security architecture risk: 🔵 Low · up to c8e11

The change narrows when an existing Cursor access prompt appears. The reviewed client flows still use the existing, environment-specific settings action; no new credential-access path was identified. Server-side authorization was not independently assessed.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The changed prompt visibility can affect selected environments in both clients, but the inspected enable actions retain an explicit environmentId rather than broadening the settings update to other environments.

Trust Boundaries and Controls

• inferred — The inspected client path changes display eligibility, not the existing settings-command destination. It does not establish whether server-side authorization or Keychain controls are sufficient.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 7 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: hiding the Cursor keychain prompt when Cursor is not configured.
Description check	✅ Passed	The description explains what changed and why, identifies the implementation, documents the UI change with before-and-after screenshots, and reports validation results. The checklist is omitted, but t…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved at c8e1185

Macroscope's review found this PR approvable — This is a narrowly scoped usage UI bug fix with a shared readiness predicate, web/mobile wiring, and targeted tests. It changes no server contract, product default, deployment behavior, or static-analysis configuration.

^{You can add or adjust custom eligibility rules. Learn more.}