Skip to content

abacus.md

Latest commit

 

History

History
92 lines (64 loc) · 4.67 KB

abacus.md

File metadata and controls

92 lines (64 loc) · 4.67 KB
Raw
summary Abacus AI provider: browser cookie auth for ChatLLM/RouteLLM compute credit tracking.
read_when
Adding or modifying the Abacus AI provider
Debugging Abacus cookie imports or API responses
Adjusting Abacus usage display or credit formatting

Abacus AI Provider

The Abacus AI provider tracks ChatLLM/RouteLLM compute credit usage via browser cookie authentication.

Features

  • Monthly credit gauge: Shows credits used vs. plan total with pace tick indicator.
  • Reserve/deficit estimate: Projected credit usage through the billing cycle.
  • Reset timing: Displays the next billing date from the Abacus billing API.
  • Subscription tiers: Detects Basic and Pro plans.
  • Cookie auth: Automatic browser cookie import (Safari, Chrome, Firefox) or manual cookie header.

Setup

  1. Open Settings → Providers
  2. Enable Abacus AI
  3. Log in to apps.abacus.ai in your browser
  4. Cookie import happens automatically on the next refresh

Manual cookie mode

  1. In Settings → Providers → Abacus AI, set Cookie source to Manual
  2. Open your browser DevTools on apps.abacus.ai, copy the Cookie: header from any API request
  3. Paste the header into the cookie field in CodexBar

How it works

The bundled abacus.ts plugin owns requests, parsing, and snapshot projection on QuickJS and JavaScriptCore. Two API endpoints are fetched concurrently using browser session cookies:

  • GET https://apps.abacus.ai/api/_getOrganizationComputePoints — returns totalComputePoints and computePointsLeft (values are in credit units, no conversion needed).
  • POST https://apps.abacus.ai/api/_getBillingInfo — returns nextBillingDate (ISO 8601) and currentTier (plan name).

The credits GET is required and uses the configured web timeout (normally 60 seconds), bounded to the host's 1–90-second request range. At most five cookie candidates (including the cache) are tried per refresh. The total plugin deadline is min(90 seconds, credits timeout × 5 + min(credits timeout, 5 seconds)); it bounds both engines without changing other providers' runtime deadlines. Each candidate gets its own credits deadline within that total: the hard 90-second cap can end a refresh before all candidates run when earlier requests are slow. The billing POST is optional; its request timeout and collection budget are the smaller of the credits timeout and five seconds. The collection budget starts with the credits request. Billing errors or timeouts retain credits with the 30-day fallback window and no guessed plan/reset. Unfinished billing work is cancelled when collection ends.

The existing native cookie importer retains abacus.ai and apps.abacus.ai cookie discovery and session validation (anonymous/marketing-only cookie sets are skipped). The shared broker first tries the cached session, then Chrome; other browsers are imported only after Chrome candidates are exhausted. Requests send the session only to the declared https://apps.abacus.ai origin. Manual mode is exclusive. Auth/parse failures reject stale imported sessions and continue to later candidates; network failures continue without evicting the cached session.

When a billing reset is available, the window spans the preceding Gregorian calendar month in the host time zone, using Foundation month-end clamping and DST arithmetic through ctx.date.addMonths. Without a reset date, the window retains its 30-day fallback; pace estimates require a real reset date.

Menu-bar percentage

Explicit Credits selection uses the monthly allowance and announces Credits, rather than leaving a blank session lane or describing the billing month as hundreds of hours. Billing/reset timing and pacing retain the full month; Automatic selection is unchanged. Editor tokens, conditional metrics and pace accessibility use the same Credits label.

CLI

CLI text and cards retain used/total compute credits beside the real billing reset. When a reset date is unavailable, credit amounts remain details without a reset label; native quota details and pacing are unchanged.

codexbar usage --provider abacusai --verbose

Troubleshooting

"No Abacus AI session found"

Log in to apps.abacus.ai in a supported browser (Safari, Chrome, Firefox), then refresh CodexBar.

"Abacus AI session expired"

Re-login to Abacus AI. The cached cookie will be cleared automatically and a fresh one imported on the next refresh.

"Unauthorized"

Your session cookies may be invalid. Log out and back in to Abacus AI, or paste a fresh Cookie: header in manual mode.

Credits show 0

Verify that your Abacus AI account has an active subscription with compute credits allocated.