Add TypeSafe AI Jev usage tracking

[mohitsbsftester]

TypeSafe AI exposes Jev account usage in its signed-in console at https://console.typesafe.ai/usage via GET /api/usage?granularity=day.

Please add Jev as a browser-cookie usage provider in CodexBar, showing request and token usage from the dashboard response while keeping credentials in the existing cookie cache/import flow.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 20, 2026, 5:08 AM ET / 09:08 UTC.

Summary
Keep open: request/token tracking remains distinct from the billing integration proposed in #3756. Neither current main nor the latest release includes Jev, and repository policy disables automatic closure.

Reproducibility: not applicable. this requests new provider coverage rather than reports broken behavior; the proposed daily usage endpoint has not been independently validated.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
Coordinate with #3756 and obtain a redacted daily-usage response with reporting-period semantics before commissioning overlapping implementation work.

Review details

Best possible solution:

Extend the TypeSafe integration with verified request/token detail rows while preserving its isolated session handling and shared provider UI.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this requests new provider coverage rather than reports broken behavior; the proposed daily usage endpoint has not been independently validated.

Is this the best way to solve the issue?

Yes, reusing the provider architecture is appropriate; coordinate with the existing TypeSafe PR and verify the daily response before adding parsing rather than creating competing integrations.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The daily endpoint’s response shape, reporting period, and session requirements remain unverified.

Codex review notes: model internal, reasoning medium; reviewed against c1e063d1e06b.

Label changes

Label changes:

• add P2: This is a concrete optional provider enhancement with limited scope and no demonstrated existing-user outage.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.

Label justifications:

• P2: This is a concrete optional provider enhancement with limited scope and no demonstrated existing-user outage.

Evidence reviewed

What I checked:

• Repository policy applied: Read the complete root AGENTS.md and applied provider isolation, existing-helper reuse, Chrome-first imports, and restrictions on live credential probes. The supplied repository profile prohibits automatic closure. (AGENTS.md:1, c1e063d1e06b)
• Current implementation and release: The complete current-tree search found no Jev or TypeSafe implementation. The provider registry on current main and at v0.62.0 has no corresponding provider. The release registry was inspected with git show v0.62.0:Sources/CodexBarCore/Providers/Providers.swift. (Sources/CodexBarCore/Providers/Providers.swift:22, c1e063d1e06b)
• Provider additions fit repository direction: VISION.md welcomes provider support following existing descriptor, strategy, settings, and test patterns; new host APIs or unclear authentication/privacy behavior require sign-off. (VISION.md:9, c1e063d1e06b)
• Existing credential and presentation boundaries: The cookie broker resolves provider-owned settings, manual cookies, cached sessions, and browser imports. docs/plugins.md documents browser-cookie capabilities and generic request-count detail rows; a separate UI or credential store is not established as necessary. (Sources/CodexBarCore/Plugins/ProviderPluginCookieBroker.swift:26, c1e063d1e06b)
• Related open implementation only partially overlaps: GitHub search found feat(typesafe): add plugin-backed billing provider #3756, confirmed open and unmerged at bb140e6. Its full TypeScript patch reads the billing server action and returns spend, balance, plan, and credit expirations; it does not fetch the requested daily usage endpoint or return request/token totals. Its body supplies real-account billing output and cookie-isolation evidence, useful groundwork for this request. (Sources/CodexBarCore/Resources/Plugins/typesafe.ts:166, bb140e668e91)
• Requested endpoint contract remains unverified: The captured issue body names GET /api/usage?granularity=day but supplies no response example, aggregation semantics, or authenticated runtime output. The supplied discussion contains no additional human evidence. Billing proof from the related PR does not establish this different endpoint’s contract.

Likely related people:

• Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[mohitsbsftester]

Based on comparison with PR #3756, I agree this should be consolidated into the existing TypeSafe provider rather than implemented as a separate Jev provider. PR #3756 already provides the correct provider identity and hardened cookie/session handling.

The remaining feature is the daily usage detail endpoint: GET https://console.typesafe.ai/api/usage?granularity=day, exposing request, input-token, and output-token buckets. The response shape and reporting-period semantics should be added as redacted fixture/runtime evidence to PR #3756.

PR #3777 is being closed as superseded; this issue remains open to track the consolidated request/token capability.