Personal Copilot quota works automatically when OpenCode is already signed in. When no copilot-quota-token.json exists, the plugin reads the OpenCode Copilot OAuth token from ~/.local/share/opencode/auth.json and queries GET https://api.github.com/copilot_internal/user with Authorization: Bearer <access token>.

For managed billing, create copilot-quota-token.json under the OpenCode runtime config directory. You can find the directory with opencode debug paths.

Organization example:

{
  "token": "github_pat_...",
  "tier": "business",
  "organization": "your-org-slug"
}

Enterprise example:

{
  "token": "ghp_...",
  "tier": "enterprise",
  "enterprise": "your-enterprise-slug",
  "organization": "optional-org-filter",
  "username": "optional-user-filter"
}

Behavior notes:

• Personal output is labeled [Copilot] (personal).
• Managed organization and enterprise output is labeled [Copilot] (business).
• Managed output includes the org or enterprise slug in the value line so the billing scope is still visible.
• If both OpenCode OAuth and copilot-quota-token.json exist, the PAT config wins.
• If no PAT config exists, OpenCode Copilot OAuth is treated as personal quota auth via /copilot_internal/user.
• If the PAT config is invalid, the plugin reports that error and does not silently fall back to OAuth.
• business requires organization.
• Enterprise premium usage does not support fine-grained PATs or GitHub App tokens. Use a supported enterprise token such as a classic PAT.

Useful checks:

• Run /quota_status and inspect copilot_quota_auth.
• Look for billing_mode, billing_scope, quota_api, effective_source, and billing_api_access_likely.

No extra setup is required if OpenCode already has OpenAI or ChatGPT auth configured.

Qwen support is local-only estimation for the free plan. The plugin does not call an Alibaba quota API.

Current behavior:

• Free tier only: 1000 requests per UTC day
• Free tier only: 60 requests per rolling minute
• Counters increment on successful question-tool completions while the current model is qwen-code/*

State file path:

• .../opencode/opencode-quota/qwen-local-quota.json

Run /quota_status to verify auth detection, qwen_local_plan, and local counter status.

Alibaba Coding Plan uses native OpenCode auth from either alibaba or alibaba-coding-plan in auth.json, instead of the Qwen companion plugin. Quota estimation is request-count based with rolling windows.

Supported tiers:

• lite: 1200 requests / 5 hours, 9000 / week, 18000 / month
• pro: 6000 requests / 5 hours, 45000 / week, 90000 / month
• If tier is missing from auth, the plugin uses experimental.quotaToast.alibabaCodingPlanTier and defaults that setting to lite
• Counters increment on successful question-tool completions while the current model is alibaba/* or alibaba-cn/*

State file path:

• .../opencode/opencode-quota/alibaba-coding-plan-local-quota.json

/quota_status shows whether Alibaba auth is configured, the resolved Alibaba coding-plan tier, the Alibaba state-file path, and the current 5h/weekly/monthly usage when this plan is active.

If OpenCode already has Firmware configured, it usually works automatically. You can also provide an API key:

{
  "provider": {
    "firmware": {
      "options": {
        "apiKey": "{env:FIRMWARE_API_KEY}"
      }
    }
  },
  "experimental": {
    "quotaToast": {
      "enabledProviders": ["firmware"]
    }
  }
}

{env:VAR_NAME} and direct keys are both supported.

If OpenCode already has Chutes configured, it usually works automatically. You can also provide an API key:

{
  "provider": {
    "chutes": {
      "options": {
        "apiKey": "{env:CHUTES_API_KEY}"
      }
    }
  },
  "experimental": {
    "quotaToast": {
      "enabledProviders": ["chutes"]
    }
  }
}

This provider requires the opencode-antigravity-auth plugin. Account credentials are stored under the OpenCode runtime config directory.

If you are debugging detection, /quota_status prints the candidate paths checked for antigravity-accounts.json.

No extra setup is required if OpenCode already has Z.ai configured.