codexmate vs magpie
Local-first CLI + web dashboard for your coding agents — switch providers, browse sessions across Codex/Claude Code/Gemini CLI, share skills, queue tasks, and bridge Codex/Claude to any API. — versus — Pick any model for any coding agent from one menu-bar app: a local gateway translating OpenAI, Anthropic and Gemini APIs, with subscription sign-ins and quota failover across accounts.
Both switch providers per coding agent and bridge Codex/Claude to other APIs; codexmate adds session browsing and task queues, magpie a gateway with routing groups.
| codexmate | magpie | |
|---|---|---|
| Stars | 354 | 8.6k |
| Forks | 35 | 565 |
| Language | JavaScript | Go |
| License | Apache-2.0 | MIT |
| Last activity | 3 days ago | yesterday |
| Topics | coding | gateway, coding |
| Curated connections | 6 | 4 |
codexmate — the curator's take
Use it when you juggle several local agent CLIs and are tired of each one's config/session/skills silo: one web UI to switch providers (with health probes and bulk cleanup of dead configs), search and export sessions across four agents, and edit global/project CLAUDE.md and AGENTS.md with shared presets. The bridges are the sleeper feature — Codex's Responses API normalized to OpenAI-compatible (with official-looking fingerprint headers), and Claude Code pointed at any Chat Completions provider or Ollama. NOT an autonomous orchestrator despite the DAG task queue — for issue-driven unattended runs use contrabass. Early-stage, and it mutates ~/.codex and ~/.claude configs, so keep backups.
magpie — the curator's take
Worth it the moment you run more than one agent, provider or account — Claude Code on Kimi, Codex on DeepSeek, failover when a plan runs dry, 50+ agents configured in place. Not needed for one agent on its vendor's own plan (the README says so itself). It reads your agents' stored sign-ins by default; turn account discovery off if that's a policy problem.