codexmate vs herdr
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 — Agent multiplexer for your terminal: every Claude Code/Codex session in real panes — blocked/working/done at a glance, detach and reattach over SSH, plus a socket API agents drive themselves.
Same many-sessions-one-surface job: Codex Mate is a local web dashboard with provider switching and session search; herdr keeps you in the terminal with live panes and a socket API agents can drive.
| codexmate | herdr | |
|---|---|---|
| Stars | 327 | 21k |
| Forks | 33 | 1.4k |
| Language | JavaScript | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | 7 days ago | yesterday |
| Topics | coding | coding, orchestration |
| Curated connections | 4 | 3 |
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.
herdr — the curator's take
tmux, rebuilt for the agent era: real terminal views (not wrapped reinterpretations), sessions that survive restarts and reattach over SSH, prefix keys AND mouse both first-class. The differentiator is the socket API — agents can spawn panes, read each other's output and wait on each other, which turns the multiplexer itself into coordination infrastructure, and the plugin marketplace suggests real ecosystem ambition. NOT an orchestrator: no task queues, no verification gates, no workflow graphs — it multiplexes and observes, you still decide. If you've already shaped your life around tmux, the marginal win is the agent-state awareness; weigh the switching cost honestly.