All API Deck app icon All API Deck Docs and quick start
GitHub Download ZH

Documentation

Walk the new All API Deck workflow from key vault to proxy guard.

This guide follows daily use: install the desktop app, sync and test API keys, inspect sessions and toolchain state, configure the advanced proxy, then enable the prompt-injection guard and mini floating when needed.

Quick start

Download the right build from GitHub Releases. Windows has the most complete experience; sidebar, mini floating, floating windows, and some client takeover flows are verified there first.

Windows.exe / .msi
macOSuniversal .dmg
Linux.tar.gz / .deb / AppImage
Windows auto-update prefers the .msi installer, while .exe remains available as a compatibility fallback.
  1. Download and launch the desktop app.
  2. Open the key vault, then import or sync site records and API keys.
  3. Run quick checks by group, model, and status to confirm usable providers.
  4. Open Advanced Proxy and hand stable providers to Codex, Claude, OpenCode, or OpenClaw.
  5. Enable the guard and mini floating when you need request visibility.

Synced key vault

The key vault is the new main workspace. The header shows local record count, healthy count, last sync time, and the latest batch sync result. Records are organized by site, API key, status, and dedicated export actions.

Common actions

  • Filter records by all keys, project groups, or quick groups.
  • Filter quickly by relay site name.
  • Run quick live checks for one key, and copy the key or base URL.
  • Export usable records to target clients with dedicated buttons.
Key vault page preview

Sessions, MCP, and Skill

The new session view puts project sessions from different clients in one place. The left side lists sessions and entry icons, while the right side shows message history. The top tabs also switch to stats, MCP, and Skill.

  • Find historical sessions by project path and time.
  • Inspect user and assistant messages to recover task context.
  • Observe MCP and Skill state without switching across several tools.
Sessions and toolchain page preview

Advanced proxy takeover

Advanced Proxy brings provider queues, protocol fallback, request logs, and connection records together. Clients keep using the local entrypoint while All API Deck chooses the provider and records the real exit.

  1. Select usable providers in the key vault and confirm the model.
  2. Enable the local proxy entry for Codex, Claude, OpenCode, or OpenClaw.
  3. Watch provider, model, exit URL, route trace, and HTTP result.
  4. Tune the provider queue using elapsed time, latency, and failure summaries.

Proxy capabilities

  • Provider priority queues and automatic failover.
  • messages / responses / chat/completions 多协议 fallback。
  • Protocol preference memory by host / key / model.
  • Keep recent connections with status, session number, elapsed time, exit, provider, and entry.

Advanced proxy flow

All API Deck advanced proxy flow diagram
Advanced proxy interface preview

Prompt-injection guard

The guard configures dynamic toolchain watermarking, randomized algorithm prompts, and return-flow validation stats. Non-streaming proxy requests run gateway checks; streaming requests currently write bypass logs only.

  • When the guard is off, no red cross is shown and related strategies are disabled.
  • Strict mode rejects real toolcalls that lack legal guard JSON.
  • Useful for client takeover and dynamic toolchain calls where prompt-injection risk matters.
Prompt-injection guard page preview

Sidebar, miniBar, and floating windows

Sidebar / miniBar / floating windows let you keep observing scheduling state, organize call clusters, and run quick actions outside the main window. Mini floating is useful while coding or debugging clients.

  • Inspect record state from the sidebar, miniBar, or floating window.
  • Refresh one record, run quick checks, and switch models.
  • Watch provider queues and live scheduling hits, then use proxy logs to locate slow requests or bad routing.
All API Deck sidebar interface preview
Mini floating status window preview

Local development and build

The desktop project lives under desktop/. Recommended environment: Windows 10/11, Go 1.24+, Node.js 24+, npm 11+, and WebView2 Runtime.

Install dependencies 
cd desktop
npm install
Development mode 
npm run dev
npm run dev:web
Build 
npm run build:desktop
npm run build:desktop-debug
npm run build:web

Runtime log directories

  • Windows：%LOCALAPPDATA%\BatchApiCheck\runtime
  • macOS：~/Library/Application Support/BatchApiCheck/runtime
  • Linux：$XDG_STATE_HOME 或 $XDG_CACHE_HOME 下的 batch-api-check/runtime