Cockpit Tools – one dashboard for all AI IDEs

XX If you’re actively vibcoding, you’re likely to have multiple AI IDE accounts at the same time – Cursor on the main task, Codex on the background, Copilot on VS Code. Each tool lives in its own bubble: a separate login, a separate dashboard of quotas, a separate process of switching accounts. It eats up time.

**Cockpit Tools solves exactly that problem. This is an open desktop application (Tauri + Rust + TypeScript), which combines the management of 12 AI IDEs in one window: look at quotas, switch accounts, run several instances in parallel - all without a manual logout and login. It has 6.2k stars and 137 releases on GitHub.

## What does Cockpit Tools do

Three basic scenarios under which the tool is sharpened:

*Quotas monitoring – you see residues and reset times across all platforms in one place. You don’t have to open each dashboard individually to find out where the credits are.

Switch accounts – one button changes an active account in the IDE without a manual logout. Convenient if you have multiple subscriptions on the same tool or work with team accounts.

**Multi-instance: Launching multiple independent instances of one IDE simultaneously, each with its own account and work folder. Two Codex windows with different accounts on different projects are real.

## Supported platforms (v0.24.9)

Gemini CLI and Zed don’t yet support multi-discovery — that’s a limitation of platforms, not Cockpit itself.

## Installation

macOS

Download .dmg from the release page - there are builds for both Apple Silicon (M1/M2/M3/M4) and Intel.

# Or through Homebrew.
brew tap jlcodes99/cockpit-tools https://github.com/jlcodes99/cockpit-tools
brew install --cask cockpit-tools

If macOS shows “app corrupted,” it’s standard Gatekeeper protection for non-App Store apps. Filmed by one team:

sudo xattr -rd com.apple.quarantine "/Applications/Cockpit Tools.app"

Windows

Download .msi (recommended) or .exe from the release page. The installer is standard, no additional steps are needed.

Linux

Starting with v0.22.21, official Linux packages returned to the release pipeline. .AppImage, .deb and .rpm formats are available for x86 64 and ARM64.

# Example: Ubuntu/Debian
sudo dpkg -i Cockpit.Tools 0.24.9 amd64.deb

All releases: github.com/jlcodes99/cockpit-tools/releases

## How it works from the inside out

The application assembled on Tauri is a framework that combines Rust-backend with a web interface (React + TypeScript). Rust is responsible for system operations: starting processes, reading / writing tokens, WebSocket server. The interface is normal React.

The data is stored locally:

• ~/.antigravity_cockpit – Antigravity accounts, configs, WebSocket state
• ~/.codex is the current Codex authorization file (auth.json)
• ~/.gemini – Gemini CLI local sessions
• Application system folder (com.antigravity.cockpit-tools) - account indexes of other platforms

Cockpit does not have a cloud server; everything stays on the machine. Network queries go only to the official API platforms (OAuth, token updates, quota request) and to check for updates to the application itself.

The WebSocket server (port 19528) listens only to 127.0.0.1 – it is necessary for communication with plugins. If the plugins are not used, it can be disabled in the settings.

## Key functions in more detail

Importing accounts

Most platforms support several ways to add an account:

• OAuth - standard browser input, the easiest way
• Token/JSON - insert the token directly, convenient for automation
• Local import – Cockpit reads tokens from an already authorized customer on a machine

Codex and Antigravity also have an import via Refresh Token – useful if you need to add an account without opening your browser.

Monitoring of quotas

On the dashboard for each account, you can see the progress bars of quotas and the time to reset. Automatic update is configured separately for each platform (by default every 5-10 minutes). If you need to follow one active account more precisely - there is a separate interval of the "current account" (you can set 1 minute).

Automatic awakening tasks (Wakeup Tasks)

Specific feature for Antigravity and Codex. Some AI models reset quotas on a timer that only starts when an active request is made. Cockpit can send light schedule requests to wake up the reset timer in advance. Tasks can be configured for a specific time or to start when the application starts with a delay.

Device fingerprints (Device Fingerprints)

Function for Antigravity. Allows you to generate and link to the account a unique device identifier - reduces the likelihood of triggering antifraud when switching accounts.

Multi-opening instances

Each instance gets its own independent user folder, which is key. Two Cursor windows don’t see each other: different settings, different sessions, different accounts. Start/stop/forced shutdown is controlled from Cockpit. This is especially useful when you need to run two independent projects with different AI keys.

## New in the latest versions

v0.24.9 (may 2026)

• Support for xAI accounts in Codex API Sidecar – xAI can enter the pool of accounts and participate in routing requests
• Codex API Sidecar opens OpenAI-compatible endpoints for images and video
• Setting up streaming timeouts is now read from saved config, not from code

v0.24.8 (may 2026)

• Codex API Service: Switching between Sidecar and Legacy Gateway from your account card
• Request logs are filtered by gateway mode

v0.24.0 (may 2026)

• Antigravity integration is fully translated into the official Antigravity IDE**: paths, directories, process recognition, metadata – all synchronized with the official client

v0.22.21 (may 2026)

• Linux is back in official releases: AppImage, deb, rpm for x86 64 and ARM64
• Codex accounts support notes – you can sign each account manually
• *Windsurf: Support for Devin Auth’s new authorization system (for accounts created after April 2026)

v0.20.19 (april 2026)

• Independent update interval for the current account on each platform (default 1 minute)
• Awakening Tasks for Antigravity and Codex can now be started immediately when the application starts

## Settings that should be changed immediately

Once installed, go to Settings and check out a few things.

Quotas update intervals. By default, 5-10 minutes for each platform is a reasonable balance. If there are many accounts and you need an actual picture - you can put 2-3 minutes. Too short an interval increases the number of API requests.

WebSocket service. You only need to use a plugin for IDE. If not, turn off fewer processes in the background.

Paths to applications. By default, Cockpit defines paths automatically. If the IDE is installed in a non-standard location (for example, you use multiple versions of Cursor), manually specify the path.

Window closing behavior. Select "Ask every time" or "Turn to tray" - the second option is convenient if you want auto-update quotas to continue in the background.

## Security and privacy

A few important points to understand before using:

Cockpit stores authorization tokens locally in the file system – in the same directories where they are stored by the IDE itself. This means that if someone gains access to your file system, the tokens will be compromised. On shared or corporate machines, delete accounts before leaving your computer.

The default WebSocket server is only available with localhost (127.0.0.1) - it is not visible from the outside. This is done deliberately for safety.

Cockpit does not collect analytics or send account data to its servers, only directly to official API platforms. You can check this out yourself, as the project is completely open.

License: CC BY-NC-SA 4.0 - free for personal use, commercial use requires separate permission from the author.

## Source assembly

If you want to collect or participate in the development:

# Requirements: Node.js 18+, npm 9+, Rust (stable)
git clone https://github.com/jlcodes99/cockpit-toolsX
cd cockpit-tools

npm install

# Development regime
npm run tauri dev

# Final assembly
npm run tauri build

Stack: Rust (58% code) + TypeScript/React (35%) + CSS (6%). Backend on Tauri handles everything system – processes, files, WebSocket. Frontend - interface and display logic.

## Conclusion

Cockpit Tools is one of the rare tools in the vibcoding ecosystem that solves a real problem rather than creating a new one. If you work with multiple AI IDEs at the same time, managing accounts and quotas through one dashboard saves time every day.

The main thing to remember is that this is a local tool with no cloud component, the data remains with you, the code is open. For most Vibcoders, this is exactly what you need.

** Quick start:**

1. Download from github.com/jlcodes99/cockpit-tools/releases
2. Install and launch
3. In the section of the desired platform add an account via OAuth or token
4. Set up intervals for updating quotas for yourself
5. If you need multi-discovery – create instances in the tab of each platform

The project is actively developing: since the beginning of 2026, more than 100 releases have been released. It is convenient to follow updates through the Releases tab on GitHub or directly in the application – it can check for updates automatically.