Cockpit Tools is an account and quota manager for AI coding applications. Its scope is wider than Codex: the project currently lists Antigravity, GitHub Copilot, Windsurf, Kiro, Cursor, Grok CLI, CodeBuddy variants, Qoder, Trae variants, Zed, ZCode, and Codex itself.
The tool is most relevant to a developer or administrator who already has several legitimate accounts and wants one place to see which account is active, how much quota remains, and which application instance belongs to which profile.
What Cockpit Tools actually changes
Cockpit Tools is not a new language model. It works with account state, application paths, local services, and launch arguments. The exact integration differs by application.
Main functions
| Account switching | Imports supported credentials and activates the selected profile |
|---|---|
| Quota display | Shows available usage and reset information where the provider exposes it |
| Isolated instances | Launches supported apps with separate user-data directories and arguments |
| Wake-up tasks | Schedules supported account activity around quota cycles |
| Local API service | Uses an embedded CLIProxyAPI sidecar for Codex-compatible routing |
| Plugin link | Can synchronize state with supported companion integrations |
Account switching and isolated instances are not the same. Switching changes the active profile used by the normal application. An isolated instance launches another copy with a separate data directory, which reduces accidental profile crossover when two projects run in parallel.
Install it safely
Download the Windows .msi or .exe from the official releases page. The repository also publishes .dmg packages for macOS and .deb, .rpm, and .AppImage builds for Linux.
Before installation, verify that the download belongs to jlcodes99/cockpit-tools. Review the release notes and checksums when available. Account-management software reads authentication material by design, so a lookalike download is especially dangerous.
Add accounts without losing track
Start with one service and one secondary account. Confirm that switching works before importing everything.
- Open the relevant service page in Cockpit Tools.
- Use the supported OAuth, token, JSON, or plugin import flow shown for that service.
- Give the profile a name that identifies its owner and purpose.
- Refresh quota data and confirm it belongs to the expected account.
- Switch to the profile, reopen the application if required, and verify the account inside the application itself.
Do not name profiles only by plan type. Two entries called Plus become ambiguous quickly. A format such as work-codex-team or personal-copilot is easier to review.
Codex support and the local sidecar
Cockpit Tools gives Codex additional treatment. The repository says its local Codex API service is driven by an embedded CLIProxyAPI sidecar. Cockpit Tools handles account synchronization, projected configuration, status, and usage statistics while keeping a consistent local base URL and API key for clients.
This architecture is useful when a client needs a stable endpoint while the active upstream account changes. It also adds another process to troubleshoot. If Codex works directly but fails through Cockpit Tools, check the sidecar health and local proxy rules before reauthorizing the account.
The current documentation specifically warns about local proxy applications intercepting loopback traffic. Keep localhost and 127.0.0.1 in the bypass list for tools such as Clash when the local service cannot reach its own sidecar.
Quotas and automated wake-up tasks
Quota displays depend on provider data and can lag or change format. Use them as an operational view, not an accounting record. Confirm important limits in the provider’s own application.
Wake-up automation deserves more caution. The feature can schedule activity intended to trigger a quota or model cycle. That does not override a service’s terms. Leave the feature off unless you have checked the provider policy and understand what request the task sends.
Configure local services conservatively
The repository documents a local WebSocket service on 127.0.0.1, with port 19528 as the preferred default. Disable it when no plugin or client needs live communication. If the port is occupied, Cockpit Tools can fall back to another port, so check the displayed active port when a companion plugin cannot connect.
Long refresh intervals create less background traffic. Ten minutes is a reasonable starting point for status viewing. Short intervals make sense only when active switching depends on current quota information.
Keep automatic application detection enabled at first. Set a custom executable path only when the application lives outside its normal location. A bad path can look like an account problem because Cockpit Tools launches nothing after a successful switch.
Multi-instance use
An isolated instance needs a separate user-data directory, not just a different window title. Test with harmless projects before relying on it for work and personal separation.
Check three things after launch:
- The application shows the expected signed-in identity.
- The project path belongs to that instance.
- Closing one instance does not sign out or terminate the other.
Parallel agents can edit the same repository at the same time. Use separate worktrees or repositories when both instances can write files. Account isolation does not prevent source-control conflicts.
When not to use Cockpit Tools
One account in one editor does not need an account cockpit. The provider’s normal login is easier to understand and has fewer credential-handling components. A company that centrally provisions identities should also confirm that local token import and profile export fit its security policy before deploying Cockpit Tools.
The application is not a billing authority. Quota screens help with daily decisions, but provider invoices and administrative consoles remain the source for charges and entitlement. It is also not a repository isolation tool. Use worktrees, separate clones, or virtual machines when simultaneous agents must not touch the same files.
These limits do not make the tool less useful. They define the account-heavy workflow it was built to manage.
Troubleshooting
If switching appears to do nothing, close and reopen the target application. Some tools reload configuration immediately; others read it only at startup. If quota data is blank, revalidate the account and check whether the provider changed its usage endpoint.
For local API failures, confirm the sidecar is running, inspect its health diagnostics, and bypass loopback addresses in any system proxy. A WebSocket plugin failure may use a fallback port rather than 19528.
If an update fails, download the latest official installer instead of using an unverified mirror. Keep an encrypted export before a major upgrade, but do not leave credential exports in Downloads.
Cockpit Tools safety check
- Download only from jlcodes99/cockpit-tools releases
- Import one account first and verify its identity
- Use descriptive profile names
- Keep loopback traffic outside system proxies
- Disable WebSocket and wake-up features when unused
- Use separate worktrees for parallel writing agents
- Encrypt account exports and remove temporary copies
Cockpit Tools fits account-heavy IDE workflows. If the requirement is model and provider configuration across coding CLIs, CC Switch has a different focus. If you need protocol translation and fallback chains, read the 9Router setup guide.
