Portability + coordination layer for multiple AI CLIs: write a skill once and run it in Claude, Gemini, Qwen, iFlow, Qoder, CodeBuddy, Codex, KiloCode, and opencode — and share session context across CLIs.
Stigmergy CLI
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
> **Write a skill once. Run it in every AI CLI.**
> Stigmergy is a portability + coordination layer across the AI CLIs you already use. Install an agent skill in one place, and Claude, Gemini, Qwen, iFlow, Qoder, CodeBuddy, Codex, KiloCode, and opencode can all use it — and share session context instead of making you re-explain everything.
**English** · A portability + coordination layer for multiple AI CLIs: install skills once and use them anywhere, recover session context across CLIs, and (optionally) route or fan out one task to several agents.
**中文** · 多 AI CLI 的可移植与协作层:技能装一次、处处可用;会话上下文跨 CLI 恢复;可选地把一个任务路由或并发派发给多个 agent。
The problem
You already run several AI CLIs (Claude, Gemini, Qwen, iFlow, Qoder, CodeBuddy, Codex, KiloCode, opencode…). Each keeps its **own** skills directory (~/.claude/skills, ~/.qwen/skills, …), its **own** session history, and its **own** conventions. So you reinstall the same skill everywhere, re-explain the same context every time you switch tools, and cannot hand a task from one CLI to another.
Stigmergy centralizes that: **one skill store, one session bridge, one optional router.**
60-second demo (real output, trimmed)
The scan/status lists are produced by probing your PATH; skill list
counts only skills actually installed. **Letter-for-letter transcript:**
examples/quickstart.md.
The one thing to try
Cross-CLI skill and session portability is the core, demand-backed use case (see the comparison below): sibling projects prove the niche is real, yet multi-CLI skill sharing remained largely un-served.
How it works
Skills land in one **shared store** that every CLI reads through its deployed hooks; the **session bus** lets one CLI pick up where another left off; the optional **router** fans a single task out to several agents. No CLI is replaced — they are coordinated.
Install
Requires Node.js >= 16.
> **Status — read before production use.** Stigmergy is effectively **pre-1.0**: the npm latest tag currently points at a 1.10.10-beta.5 build, while this repository is at 1.11.0. A true stable release (cutting 1.11.0 and moving betas to the @beta tag) is on the roadmap. Recent work hardened cross-CLI skill sync so it writes only the memory filenames each CLI actually reads — see CHANGELOG.md. Pin @beta and check the changelog before relying on it.
How it compares
| Project | Focus | Cross-CLI skill portability | Cross-CLI session recovery |
|---|---|---|---|
| **Stigmergy** | Portable skills + session bridge across many AI CLIs | ✅ install once, run anywhere | ✅ shared session bus |
| rtk-ai/icm (543★) | Cross-agent memory | partial (memory, not skills) | partial |
| Kaseban/baton (26★) | Session conversion | no | yes (converts one session) |
| opencode | One AI coding agent for the terminal | no (single tool) | no |
| Cline (69,556★) | Autonomous coding agent in the IDE | no (single tool) | no |
Star counts measured 2026-10-10. Single-tool projects are excellent — they just do not span multiple CLIs by design. Stigmergy **coordinates** the tools you already use rather than replacing them.