Misc providers
The Misc tab tracks coding plans that do not yet have a full cost-and-status detail page. Every enabled provider is shown as a consistent quota card while retaining the provider's own reset-window and plan semantics.
Setup matrix
| Provider | Primary setup | Notes |
|---|---|---|
| Alibaba Bailian Coding Plan | Optional DashScope API key or Aliyun Web login/cookies | Choose a region. Web login can refresh the console session. |
| Alibaba Bailian Token Plan | Aliyun Web login/cookies | Choose Team or Personal. Personal currently uses China mainland; clone the row to track both editions. |
| GitHub Copilot | GitHub device-flow sign-in | Optional GitHub Enterprise host. The device token is saved in Keychain. |
| Zhipu GLM Coding Plan | Z.ai API key | Choose the appropriate region. |
| MiniMax Token Plan | MiniMax coding API key | Choose region. Environment fallbacks are also supported. |
| Kimi Coding Plan | Browser import or pasted Kimi cookie | Add another cookie slot for another account. |
| Cursor | Browser import or pasted Cursor cookie | Requires a signed-in Cursor web session. |
| Xiaomi MiMo Token Plan | In-app Web login or pasted cookie | The in-app login is preferred because newer Chrome cookie encryption can block direct import. |
| iFlytek Spark Coding Plan | Browser import or pasted console cookie | Re-import after the provider session expires. |
| Tencent Hunyuan Coding Plan | In-app Web login, browser import, or pasted cloud cookie | Short-lived sessions may show Needs re-login. |
| Tencent Hunyuan Token Plan | Same Tencent Cloud login | Pick the generic or HY3 variant; clone the row to track both. |
| Volcengine Coding Plan | In-app Web login, browser import, or pasted console cookie | Console sessions can expire after a few hours. |
| Volcengine Agent Plan | Access Key ID and Secret Access Key | Uses the provider's signed API; use a sub-user key with the minimum required read access. |
| Baidu Qianfan Coding Plan | In-app Baidu Cloud login or console cookies | Sign in with the account that owns the Coding Plan. |
| OpenCode Go | Browser import or pasted OpenCode cookie | Optional workspace ID or workspace URL when the account has several workspaces. |
| Kilo | kilo login or optional API key | Vibe Bar can read ~/.local/share/kilo/auth.json. |
| Kiro | Local Kiro CLI status | Sign in through Kiro, then refresh Vibe Bar. |
| Ollama Cloud | Browser import or pasted Ollama cookie | Requires an ollama.com session. |
| OpenRouter | OpenRouter API key | Optional API base URL override; the default is OpenRouter's public API. |
| Warp | Warp AI API key | Create it in Warp → Settings → AI → API Keys. |
Provider websites and private quota endpoints can change. If a previously working card asks for login again, refresh its credential before assuming the plan disappeared.
API keys and access keys
Paste credentials only into the matching secure field in Settings. Vibe Bar stores them in macOS Keychain, not settings.json.
Several adapters also recognize provider-specific environment variables or local CLI auth files. The Settings page tells you when such a route exists. Prefer a read-only or least-privilege credential when a provider offers one.
For a two-part AK/SK credential, both values must be present. Clearing stored credentials removes only the selected provider instance.
Browser cookies and Web login
Cookie-based rows offer one or more of these actions:
- Import from browser copies only the cookie fields required by the integration.
- Sign in via Web opens an isolated in-app login and captures the resulting provider session.
- Paste Cookie header accepts a manually copied header when import is not possible.
Imported cookies are snapshots; Vibe Bar does not control the original browser session. Providers may expire or rotate them at any time. When a card changes to Needs re-login, repeat the provider's sign-in/import action.
Never paste a cookie into an issue, chat, screenshot, or public log.
Multiple accounts and plan variants
Select the clone button on a provider row to create a separate instance. Clones are useful for:
- work and personal accounts;
- different regions;
- Team and Personal editions;
- generic and model-specific plan variants;
- separate workspaces.
Give each clone a visible name. Credentials, cookie slots, settings, cache, and visibility are isolated per clone. Deleting a clone deletes that clone's Vibe Bar-owned credentials and quota cache; it does not modify the remote account.
Cookie-based providers can also keep multiple cookie slots inside one instance. Vibe Bar averages the quota values across those slots. Use separate clones instead when you need to see each account independently.
Visibility and ordering
Drag rows in Settings to control the order on the Misc tab. Uncheck a row to hide it without losing setup. A hidden integration keeps its credentials and can be enabled later.
Misc cards are quota-only unless the adapter explicitly exposes local usage. They do not contribute to the core provider cost totals, service-status tiles, or mini window.