Files

T

Peter Steinberger 8fc67d7f04 feat: cut over Synthetic, Poe, xAI, and z.ai to JavaScript on all platforms (#2758 )

* feat(synthetic): cut over provider to JavaScript

* feat(poe): cut over provider to JavaScript

* feat(xai): cut over provider to JavaScript

* feat(zai): cut over provider to JavaScript

* style(zai): use predicate count

* test: give the hung-script watchdog assertion CI headroom

The 0.15s interrupt must fire promptly, not wait out the hang; the 1s
elapsed bound flaked at 1.66s on a loaded ARM64 runner. 5s still proves
prompt termination against an unbounded loop.

* test: give hooks-watch interrupt assertion CI headroom

The 0.3s stop signal must beat the 10s interval; the 2s elapsed bound
flaked at 2.02s on a loaded x64 runner. 5s still proves prompt
interruption.

2026-08-07 22:35:39 -07:00

2.5 KiB

Raw Permalink Blame History

summary, read_when

summary

read_when

Synthetic provider data sources: API key quota endpoint and usage lanes.

Debugging Synthetic API key usage

Updating Synthetic quota parsing

Explaining Synthetic setup and environment variables

Synthetic provider

Synthetic is API-key only. CodexBar reads the quota endpoint and maps the known Synthetic quota lanes into the shared provider card.

Authentication

Create an API key using Synthetic's API guide, then add it in Settings -> Providers -> Synthetic, or set:

export SYNTHETIC_API_KEY="..."

You can also store the key through the CLI:

printf '%s' "$SYNTHETIC_API_KEY" | codexbar config set-api-key --provider synthetic --stdin

Data source

CodexBar sends a read-only request to Synthetic's quota API:

GET https://api.synthetic.new/v2/quotas
Authorization: Bearer <api key>
Accept: application/json

The parser first looks for Synthetic's known quota slots, either at the root of the response or under data:

rollingFiveHourLimit -> Five-hour quota
weeklyTokenLimit -> Weekly tokens
search.hourly -> Search hourly

If those keys are absent, CodexBar falls back to generic quota payloads such as quotas, quota, limits, usage, entries, or subscription.

Display

The menu card shows the five-hour, weekly token, and search-hourly lanes when present. The compact menu bar metric uses the five-hour or weekly lane.
Usage is normalized from percent fields when present, or computed from used/remaining/limit values.
Reset timestamps are shown when Synthetic returns one. When no timestamp is available, CodexBar uses the returned or inferred window duration when present.
Plan name, when returned, is displayed as provider identity context.
Synthetic does not currently provide CodexBar cost history.
External status page: status.synthetic.new (not linked or auto-polled by CodexBar).

CLI usage

codexbar usage --provider synthetic
codexbar usage --provider synthetic.new

Key files

Sources/CodexBarCore/Providers/Synthetic/SyntheticProviderDescriptor.swift (descriptor and script fetch strategy)
Sources/CodexBarCore/Resources/Plugins/synthetic.js (HTTP client and parser)
Sources/CodexBarCore/Providers/Synthetic/SyntheticSettingsReader.swift (environment variable parsing)
Sources/CodexBar/Providers/Synthetic/SyntheticProviderImplementation.swift (settings field and availability)

2.5 KiB Raw Permalink Blame History