Skip to content

audit(quota-plane): name the two token-exception providers definitively #1155

New issue
New issue
Open
Open
audit(quota-plane): name the two token-exception providers definitively#1155
Assignees
dezren39
Labels
effort/sSmall: expected under 2 hours of workkind/docsDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudpriority/criticalDrop everything: main broken, security exposure, repo-wide outagequeue/queuedHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanstatus/needs-triageNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this item

Description

@dezren39
dezren39
opened on Oct 27, 2026

Priority P0 — order 3 (quick; gates the exception issues' scope). Horizon: Week. Design: quota-plane-design-2026-10-26.md (usage-billing-hub goal files), Stage 2. Parent context: epic #1047. (§5)

Name the two exception providers definitively. Drew's belief (2026-10-26): all but two providers' quota/plan data is reachable by the gatherer using the browser token against the dashboard's own API. Current evidence points at Meta High Usage (console behind auth.meta.ai, blocked from the Muse browser; API key carries no quota state) and Google/Antigravity (OAuth blocked on the sandbox host; quota plan-tied to the app sign-in, not the API key) — verify or correct that identification provider by provider, with the tested route (or the exact wall) recorded for every console-only pool: Claude, ClinePass, OpenCode Go, Command Code, Open Design, Meta, Antigravity.
Acceptance: a coverage table in the design doc's terms — per provider: route class (official API / dashboard-API-via-token / file-export / exception) — and the two exception issues re-scoped to the confirmed pair.

Acceptance criteria

  • A coverage table exists in the design doc's terms — per provider (Claude, ClinePass, OpenCode Go, Command Code, Open Design, Meta, Antigravity): route class (official API / dashboard-API-via-token / file-export / exception), with the tested route or the exact wall recorded — restating the body's Acceptance section as the criteria section.
  • The two exception providers are named definitively (the body's current evidence points at Meta High Usage and Google/Antigravity — verify or correct it, provider by provider).
  • The two exception issues are re-scoped to the confirmed pair.

Activity

  1. dezren39
    added
    meta/follow-upFollow-up spun out of earlier work
    on Oct 27, 2026

  2. developing-today commented on Oct 27, 2026

    @developing-today
    developing-todayBot
    on Oct 27, 2026 – with developing.today
    Contributor

    CODE-291

  3. github-actions
    assigned
    dezren39
    on Oct 27, 2026

  4. dezren39 commented on Oct 27, 2026

    @dezren39
    dezren39
    on Oct 27, 2026
    MemberAuthor

    REVIEW STARTING TABLE (2026-10-26, from the OpenChamber quota catalogue — verify each against live accounts; this replaces guesswork with an inventory):
    Providers WITH adapters already: claude (OAuth usage API), cline-pass, codex (wham/usage), opencode-go (console API + zen usage API), opendesign (AMR API, cookie credential), antigravity (cloudcode-pa quota summary), google, deepseek, openai, cursor, copilot, openrouter, + ~18 more.
    Providers with NO adapter in the catalogue: meta, command-code.
    Open questions the audit must still answer per provider: does the adapter's credential source exist for OUR accounts on the gatherer host (e.g. claude needs a Claude Code OAuth credential in the store; antigravity needs a Google access token whose provenance on this host is unsettled — OAuth was blocked here 2026-10-24)? Reachability exceptions and coverage exceptions are different lists; name both.

  5. dezren39 commented on Oct 27, 2026

    @dezren39
    dezren39
    on Oct 27, 2026
    MemberAuthor

    CORRECTION (2026-10-26 23:2x CDT, per Drew — my earlier wording was wrong): "no meta provider / no command-code provider" was imprecise. Precise state:

    • The META inference provider exists and is in daily use (sessions ran on it today; the funded team key was proven live 2026-10-25). What does not exist is a meta QUOTA FETCHER in the OpenChamber quota catalogue. Meta quota DATA exists — it was read from the dev.meta.ai console on 2026-10-25 (weekly window 46% used at first read) — it is simply not automated. That automation is plan(quota-plane): exception integration — Meta (login, token capture, console API) #1167, now with Drew's explicit route: log in via the laptop (RustDesk), view usage at dev.meta.ai with the credentials there, capture how the console reads it.
    • COMMAND CODE: a quota provider DID exist — built upstream (279f248a0) and DROPPED in an upstream sync (1b1a95ff6) because "the official API has no usage endpoints; the old source was the unofficial studio API." The module DOCUMENTATION.md still documents that route: GET /alpha/whoami then GET /alpha/billing/credits(?orgId=). Drew used Command Code quota reads this week (fleet CLI/console reads). Restoration is re-scoped in feat(quota-plane): adapter — Command Code via CLI/app credential #1165: recover the dropped provider from git history, re-point/verify against the /alpha studio API with our credential.
    • CODEX: provider exists and WORKS (verified live 2026-10-26 23:2x after the server restore below: codex ok on the legacy-login row; the token-sharing row errors by design).
      Also live-verified in the same pass: with opencode-serve restored, openchamber quota --json returns per-provider results — cline-pass ok, deepseek ok, opencode-go ok, openai.alternate ok; claude ERRORS "session expired" (credential present, needs re-login — a fixable state, tracked in the resilience issue filed alongside this comment).
  6. dezren39
    added
    kind/docsDocumentation improvement or addition
    priority/criticalDrop everything: main broken, security exposure, repo-wide outage
    effort/sSmall: expected under 2 hours of work
    source/humanFiled directly by a human
    status/needs-triageNot yet triaged; needs a first look
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 28, 2026

  7. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    MemberAuthor

    Intake review

  8. dezren39
    added
    mode/onlineFully doable remotely: design, config, code, cloud
    on Nov 1, 2026

  9. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    Agent note — triage verdict: no architectural exceptions on the laptop (queue task 2435, 2026-11-03)

    Bottom line: the Meta + Antigravity exception hypothesis is refuted by live reads. All seven console-only pools return data on this laptop right now; the single failure (Claude) is credential hygiene (expired session, re-login fix), not architecture. Recommend closing this audit once Drew confirms the #1169 re-scope below.

    Coverage table (route classes, live-tested 2026-11-03 ~04:08 CST via running OpenCode on the laptop)

    Provider Route class Live result
    Claude dashboard-API-via-token (OAuth usage API; Keychain/credentials-file/OpenCode auth) CONFIGURED but ERROR: session expired, re-login required. Fixable, not architectural.
    ClinePass official API (api.cline.bot plan usage-limits) OK — 5h/weekly/monthly
    OpenCode Go console API (Console Go status) + legacy zen usage API, per-workspace OK on workspaces with subscription; one workspace correctly reports no-subscription (host state, not a wall)
    Command Code official API (api.commandcode.ai, restored provider ca9b4e0f6/a23d5e732/c472a9c33) OK — monthly plan window + 5h/weekly + balances
    Open Design dashboard-API-via-token (AMR API session cookie) OK — 5h/7d
    Meta official-API-via-token (POST api.meta.ai/muse-code/key with the account OAuth token from muse auth store, NOT the minted inference key) OK — plan Muse Code High Usage, 5h 8%, weekly 86%
    Antigravity panel-API-via-captured-token (cloudcode-pa quota summary, per-model windows) OK — per-model 5h/weekly live

    The pair, definitively

    Evidence pointers

    Origin: openchamber-scheduled-lane, task 2435. Verdict from fresh gh + code + live openchamber quota --json reads; no files changed.

  10. dezren39
    added
    work/assignedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    queue/queuedHas a queued task in the Supabase agent queue
    status/needs-triageNot yet triaged; needs a first look
    task/triageQueue packet kind: verify, reproduce, and route this item
    and removed
    status/needs-triageNot yet triaged; needs a first look
    status/in-progressQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 3, 2026

  11. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 70 (priority/critical). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

  12. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · handed off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort/sSmall: expected under 2 hours of workkind/docsDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudpriority/criticalDrop everything: main broken, security exposure, repo-wide outagequeue/queuedHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanstatus/needs-triageNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions