StackFerry

StackFerry

  English · 简体中文

Desktop control plane for coding CLIs. It keeps providers, local failover, Skills, and MCP in one place, then writes them into the CLI you enable. Codex, Claude Code, Grok, and Pi work today. More CLIs will be added the same way.

Demo

https://github.com/user-attachments/assets/d73a89a6-6dde-4cb2-8d1f-55257e16d8b3

StackFerry does not replace those CLIs. It sits beside them: official login or a custom gateway, a backup before each write, and an optional failover queue on 127.0.0.1.

Contents

- CLIs
- Integrations / Supported Providers
- What it does
- Install
- Usage
- macOS
- Configuration
- Development
- Contributing
- License

CLIs

Integrations / Supported Providers

- A2Agent — an API gateway with tested model discovery and basic Messages, Responses, and Chat Completions requests; see configuration and verification scope.

What it does

- Providers. Official login or a custom gateway, per CLI. Enable one and StackFerry backs up, then writes that CLI's live config. A gateway can hand the user a stackferry:// import link; fields are in docs/provider-import.md.
- Local routing. One failover queue per CLI. A non-empty queue sends that CLI through a loopback proxy with a circuit breaker. Official login stays out of the queue.
- Skills. Import SKILL.md from a GitHub repo or a local folder, keep StackFerry's copy, then project it onto Claude, Codex, Grok, DeepSeek Harness, and Pi.
- MCP. Add stdio or HTTP servers, or import definitions already in a CLI, and apply them to Claude, Codex, Grok, and/or Pi.
- CLI binaries. Detect, install, update, or uninstall the local Codex, Claude Code, Grok Build, and Pi binaries. Uninstalling a CLI does not delete StackFerry's provider data.
- Desktop. English and 简体中文, theme, Windows 11 Mica, a…