claudeers.
// Integrations & Connectors

myco

Connect Claude Code, Codex and any agent CLI across machines. Agents find each other, delegate tasks and reply through one hub. Single Go binary, one-line se…

// Integrations & Connectors[ cli ][ api ][ web ][ claude ]#claude#integrations$open-sourceupdated 13 days ago

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up myco (release-binary project) into my current project.
Found on https://claudeers.com/myco
Repo: https://github.com/chenhg5/myco
Homepage/docs: —
Detected install method: release-binary → inspect the README
Category: integrations. Platforms: cli, api, web.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or install directly (release-binary)

Grab the latest release asset from GitHub.

# download a build from https://github.com/chenhg5/myco/releases
// or clone
git clone https://github.com/chenhg5/myco

// compatibility

Platformscli, api, web
Operating systems—
AI compatibilityclaude
License—
Pricingopen-source
LanguageGo

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

myco

The mycelium for your AI agents.

Connect Claude Code, Codex and any agent CLI across laptops, VPSes and the cloud —
so they can find each other, hand off tasks, and reply, while you're away.

English · 中文 · Install Guide · Architecture · HTTP API

https://github.com/user-attachments/assets/31de0488-f6c0-4acf-9e66-96d903718e48

Quick Start

The lazy way: let your agent do it

Paste this into Claude Code or Codex:

Read https://github.com/chenhg5/myco/blob/main/INSTALL.md
Set up a myco hub for me and connect this session to it.

The 3-step way

1. Start a hub (once). Pick whichever fits; each one prints a join link at the end. No VPS is needed: the hub can run on a computer you already own, reachable through Cloudflare Tunnel or Tailscale Funnel.

WhereCommandYou need
Your own VPScurl -fsSLO https://raw.githubusercontent.com/chenhg5/myco/main/deploy/install-hub.sh && sudo bash install-hub.sh --domain autoLinux with a public IP and port 443 open. --domain auto gets a real HTTPS cert via sslip.io, so no domain is required
No VPS: Cloudflare Tunnelmyco hub up --tunnel cloudflare --hostname hub.example.comA free Cloudflare account, a domain on Cloudflare, and cloudflared
No VPS: Tailscale Funnelmyco hub up --tunnel tailscaleA free Tailscale account with Funnel enabled. You get a fixed https://<machine>.<tailnet>.ts.net URL
Just trying it outmyco hub up --tunnel cloudflareOnly cloudflared. The trycloudflare.com URL changes on every restart

For the hub up options, install the CLI first (curl -fsSL https://raw.githubusercontent.com/chenhg5/myco/main/deploy/install-client.sh | bash). They run the hub on a computer you already have (Mac, Linux, a home server) as a background service. That computer has to stay on and must not sleep. Details: INSTALL.md 1.1.

2. Add each machine (macOS / Linux / WSL). Paste one line:

curl -fsSL https://<your-hub>/j/<link> | bash

3. Add each agent session. Say this to Claude Code, Codex or claude.ai:

join myco: https://<your-hub>/j/<link>

That's it. Now delegate from anywhere:

myco agent list --online
myco message send --to vps-codex-a91e --body "Fix the failing tests in ./pkg/api" --wait 15m
myco broadcast send --selector "group=review" --body "Review PR #42" --wait 30m
myco ui --open

Staying up to date: myco version shows this machine's, the hub's and the latest version; myco upgrade upgrades and restarts the local services (sudo myco upgrade on a server installed with install-hub.sh).

More setups (claude.ai cloud sessions, exec nodes, aliases, webhooks, GitHub wake-ups) are in INSTALL.md (Chinese; your agent reads it fine).

Why myco

You already run several agents: Claude Code on your Mac, Codex on a VPS, a claude.ai cloud session doing research. Today they're islands, and you are the message bus: copying prompts between them, waiting, pasting results back.

myco gives them a shared network. Each agent gets a name and an inbox. Any agent can find the others, send them work, and get the answer back. Idle agents are woken up when a message arrives, and each one resumes its own session, so it keeps all of its context.

Highlights

  • One line per machine. curl … | bash installs myco, enrolls the machine and starts a background runner. No tokens to copy.
  • No VPS required. Run the hub on a VPS, or on a computer you already have behind Cloudflare Tunnel or Tailscale Funnel.
  • Spawn agents remotely. myco agent spawn --on wsl --dir ~/code/app starts a new Claude Code or Codex session in a folder on another machine and joins it. That machine's own rules decide who may, where, and with what permissions.
  • One sentence per agent. Tell any Claude Code or Codex session "join myco: <link>" and it registers itself.
  • Agents keep their memory. Every message resumes the same Claude Code or Codex session, so context accumulates instead of resetting.
  • Bring any CLI. Built-in support for Claude Code, Codex, Pi, Kiro, Cursor, Gemini CLI and OpenCode, plus a template for anything else (full list).
  • Delegation that scales. Use 1:1 tasks with --wait, or broadcast by label (group=review,machine=vps) and track every reply.
  • Exec nodes. myco exec --to vps-shell --cmd "df -h" runs a command on a remote machine and returns its output, like ssh. Senders are allow-listed and every command is audited.
  • Attachments. Send files with --attach. Only the recipient can download them, and each one is checked with SHA-256.
  • Safe by default. Every agent has an allow-list of who may send it work, and messages are leased, redelivered and idempotent. myco won't interrupt a session you are typing in.
  • Live dashboard. myco ui --open shows who's working, who has work queued, who's idle and every conversation. It's embedded in the binary.
  • A CLI agents can drive. JSON output, structured errors with a suggestion field, distinct exit codes, --dry-run, and myco schema for introspection.
  • One static Go binary. The hub, CLI and runner are the same myco program. SQLite storage, no cgo.
myco dashboard: every agent in the network with its live status

`myco ui --open`: every agent and every conversation, live.

How it works

flowchart TB
  subgraph HUB["myco hub"]
    direction LR
    REG["Registry<br/>names, labels, aliases, allow-lists"]
    BOX["Inboxes and threads<br/>leases, retries, attachments"]
    WAKE["Wakers<br/>webhook, Claude routine, GitHub"]
  end

  subgraph MAC["Your Mac"]
    direction TB
    R1["myco runner"] -.-> S1["Claude Code session"]
    R1 -.-> S2["Codex session"]
  end

  CLOUD["claude.ai cloud session<br/>myco inbox wait"]

  subgraph VPS["A VPS or WSL box"]
    direction TB
    R2["myco runner"] -.-> S3["Codex session"]
    R2 -.-> S4["exec node: shell"]
  end

  UI["myco ui<br/>local dashboard"]
  EXT["Agents woken by push<br/>webhook, routine, GitHub Actions"]

  BOX <-->|"long-poll / reply"| R1
  BOX <-->|"long-poll / reply"| CLOUD
  BOX <-->|"long-poll / reply"| R2
  UI -->|"read-only"| REG
  WAKE -->|"push wake-up"| EXT
  • Hub: the only server, on a VPS or on your own computer behind Cloudflare Tunnel or Tailscale Funnel. It keeps the registry and every agent's inbox, in a single SQLite file.
  • Runner: one per machine, installed as a background service. It long-polls the hub for every agent on that machine. When a message arrives, it resumes that agent's own CLI session with the message as the prompt, and sends the final output back as the reply.
  • Sessions that can't be spawned (claude.ai cloud) wait with myco inbox wait. Agents that live elsewhere can be woken by a webhook, a Claude routine or a GitHub event instead.
  • Runners and sessions only open outbound HTTPS connections to the hub, so their machines need no public IP and no open ports.

A task from start to finish:

sequenceDiagram
  autonumber
  participant O as Orchestrator agent
  participant H as myco hub
  participant R as runner (VPS)
  participant C as Codex session
  O->>H: message send --to vps-codex --wait 15m
  H-->>R: long-poll returns the task (leased)
  R->>C: resume the same session with the task
  C-->>H: progress updates (optional)
  H-->>O: progress shows up while waiting
  C->>R: final answer
  R->>H: reply (closes the task)
  H-->>O: --wait returns the reply

If a task is pulled but never acknowledged (say, the machine went down), its lease runs out and it is delivered again; after 5 attempts it is marked failed. If the agent's CLI exits with an error, the task fails and the sender is notified.

Supported agents

Every agent below keeps its own session: each message resumes the same conversation, so context carries over. List what's installed on a machine with myco harness list.

AgentCommand myco runs--harnessSupport
Claude CodeclaudeclaudeNative: stable
Codex CLIcodexcodexNative: stable
PipipiPreset: stable
Kirokiro-acpkiroPreset: stable
Cursor CLIcursor-agentcursorPreset: experimental
Gemini CLIgeminigeminiPreset: experimental
OpenCodeopencodeopencodePreset: experimental
  • Native: a dedicated adapter. It also reads the session transcript, so myco won't interrupt a session you're typing in, and it maps runner.access (readonly / workspace / full) to the CLI's own permission flags.
  • Preset: a built-in command-line template. Experimental means it follows the CLI's documented output format but hasn't had long real-world use yet; reports welcome.
  • Kiro runs through the kiro-acp gateway: install it with uv tool install kiro-acp-gateway, with kiro-cli logged in.

Other ways to connect:

HowUse it for
Any other CLI--harness template: declare the command line and output format in the configCLIs without a preset, no code needed
Any command--harness shell: the prompt arrives on stdin, stdout is the replyScripts and small tools
Exec node--harness exec: runs each task as a shell command (allow-listed senders and commands)Remote commands, like ssh
claude.ai cloud sessionsNo runner: the session waits with myco inbox waitCloud agents you can't start from a terminal
Push-woken agentswebhook, claude_routine, github_dispatch, github_issueAgents that live elsewhere, e.g. Codex replying on GitHub. See docs/delivery.md

Docs

INSTALL.mdHub deployment, join links and per-agent setup
docs/architecture.mdConcepts, message state machine, runner behavior and code layout
docs/delivery.mdWake-up modes and enrollment for cloud sessions
docs/api.mdHTTP API
skill/myco/SKILL.mdSkill file that teaches agents how to use myco

Development

make test     # go test -race ./...
make build    # ./bin/myco
make cross    # linux/darwin × amd64/arm64

Why "myco"

myco- is the Greek root for fungus (μύκης, mykēs), as in mycology, mycelium and mycorrhiza. Under a forest floor, mycorrhizal networks (fungal threads grown together with tree roots) link the trees into what's called the "wood wide web". Nutrients and signals travel through it: when one tree is attacked by insects, its neighbours can get the warning and prepare their defences.

myco does the same for agents. It links agents on different machines into one network, and carries tasks, replies, broadcasts and files between them. Like the fungus, it stays underground: it isn't an agent and doesn't think for anyone, it only connects and delivers. It's also four letters and easy to type: myco message send ....

Roadmap

  • Hub, CLI and runner, with long-polling, leases, idempotency and allow-lists
  • Session binding, pluggable wakers, GitHub ingress
  • Join links, self-enrollment for cloud sessions, dashboard, exec nodes
  • MCP endpoint (Streamable HTTP), so ChatGPT and Claude can join as connectors
  • Orchestrator templates and scheduling policies
  • Hub federation and an admin console

If myco saves you from copy-pasting between agents, a star helps others find it.

// faq

What is myco?

Connect Claude Code, Codex and any agent CLI across machines. Agents find each other, delegate tasks and reply through one hub. Single Go binary, one-line setup.. It is open-source on GitHub.

Is myco free to use?

myco is open-source, so it is free to use.

What category does myco belong to?

myco is listed under integrations in the Claudeers registry of Claude-compatible tools.

13 views
★ 17 stars
unclaimed
updated 13 days ago

// embed badge

myco on Claudeers
[![Claudeers](https://claudeers.com/api/badge/myco.svg)](https://claudeers.com/myco)

// retro hit counter

myco hit counter
[![Hits](https://claudeers.com/api/counter/myco.svg)](https://claudeers.com/myco)

// reviews

// guestbook

0/500

// related in Integrations & Connectors

🔓

Use claude code and codex for free in the terminal, VSCode extension, and discord like OpenClaw (voice supported)

// integrationsAlishahryar1/⟨Python⟩★ 72,248◷ MIT[ claude ]
🔓

Bridge local AI coding agents (Claude Code, Cursor, Gemini CLI, Codex) to messaging platforms (Feishu/Lark, DingTalk, Slack, Telegram, Discord, LINE, WeChat…

// integrationschenhg5/⟨Go⟩★ 16,316[ claude ]
🔓

All parts of Claude Code's system prompt, 27 builtin tool descriptions, sub agent prompts (Plan/Explore/Task), utility prompts (CLAUDE.md, compact, statusli…

// integrationsPiebald-AI/⟨JavaScript⟩★ 13,191◷ MIT[ claude ]
🔓

Claude Code skill/plugin: immersive scroll-scrubbed 'fly through the world' landing pages generated with Higgsfield (Emons-style diorama flights, seamless co…

// integrationsoso95/⟨JavaScript⟩★ 11,032◷ MIT[ claude ]
→ see how myco connects across the ecosystem