Show HN: Myco – coordinate Claude and DeepSeek and other LLMs in one agent swarm
Myco is a coordination protocol designed to manage multiple AI agent sessions simultaneously without conflicts. It allows agents like Claude and DeepSeek to share relevant information while maintaining their individual contexts. This tool aims to enhance productivity by reducing chaos in collaborative coding environments.
- ▪Myco enables parallel sessions of AI agents to communicate through a shared, filtered view of their actions.
- ▪The protocol is vendor-agnostic and works with any Anthropic-compatible model.
- ▪Myco addresses the challenges of running multiple agent sessions by preventing conflicts and stale assumptions.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/primoia/myco |
| Publication time | Fri, 22 May 2026 11:51:34 +0000 |
| Retrieval time | 2026-05-22T12:02:01.659Z |
| Last seen | 2026-05-22T12:02:01.659Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | LxoMG1rP7nqD |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
myco 🇧🇷 Leia em português Problem: running multiple Claude Code sessions in parallel produces conflicts, repeated work, and stale assumptions — the agents have no shared awareness. myco is a text-only coordination protocol + tiny Python daemon that gives N parallel agent sessions a shared, filtered view of each other's actions. No central orchestrator. No tool calls. Vendor-agnostic (Claude, DeepSeek, anything Anthropic-compatible). The name comes from the mycelium: an underground fungal network that connects independent trees, silently transporting signals between them. Why If you use Claude Code (or any agent CLI) intensively, you've probably hit the wall: Long sessions degrade attention. Even with a 1M context window, late-conversation precision drops.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.