Loading latest release… · MIT licensed

The intelligence layer beneath
your projects and team

Capture what your team learns. Turn it into skills your agents follow. Evolve them as your code does.

Works with Claude Code · Cursor · Codex · Copilot · Gemini · Windsurf
Mycelial network of roots beneath the forest floor, with glowing sage threads
Mycorrhizal network The underground systems that connect trees in a forest.
One command

Install in sixty seconds

One install, any agent. Myco auto-detects the coding agents you already use and installs hooks for each.

~/your-project
$curl -fsSL https://myco.sh/install.sh | sh installed @goondocks/myco daemon binary linked to ~/.myco/bin $cd your-project && myco init detected agents: claude-code (hooks, mcp, skills) cursor (hooks, skills) · codex (optional) daemon started on :7337 dashboard → http://localhost:7337
PowerShell
PS>irm https://myco.sh/install.ps1 | iex installed @goondocks/myco PS>cd your-project ; myco init
~/your-project
$npm install -g @goondocks/myco + @goondocks/myco added 1 package in 3s $myco init
Requires Node 22+ and at least one supported coding agent. Quickstart
What it does

Memory is table stakes — Myco goes further.

Three things, working together beneath the surface of every session — so your agents get smarter as your team does.

01 · Capture

Every session, deposited as spores.

Rich multi-agent local data collection — your prompts, tools, agent summaries, plans, screenshots. Browse and search semantically via a local daemon. Agents access via local MCP.

prompts tool calls plans screenshots
02 · Curate

Repeated patterns become skills.

Myco's intelligence agent surveys your vault for procedural patterns with cross-session evidence, drafts a SKILL.md, runs it through quality gates, and — with your nod — promotes it to .agents/skills/.

survey approve generate evolve
03 · Connect

A shared mycelium, across the team.

Teammates' agents contribute and share project intelligence, synchronized automatically through a Cloudflare-backed worker. Cloud MCP exposes the same knowledge to managed agents beyond your laptop.

team sync cloud mcp collective
Local dashboard

A quiet command deck for your mycelium.

Myco ships a local web dashboard. Configure providers, approve skill candidates, monitor session pods, and tail daemon logs — all on localhost, all yours.

  • 01

    Session pods

    Live view of every concurrent agent thread on your machine — spore events, wisdom extractions, stability signals. Click any pod to walk its full activity trail.

  • 02

    Skills & candidates

    Approve or dismiss auto-generated skill candidates. Every change is recorded as lineage — what was in generation N, and why it's different in N+1.

  • 03

    Power-aware daemon

    Four states — active, idle, sleep, deep-sleep — so Myco costs nothing on idle laptops and wakes instantly when you sit back down.

localhost:7337/dashboard
Myco dashboard showing session pods, stats, and a mycelial network graph
Skill lifecycle

From spore to skill — automatically.

Every session deposits spores. Myco digests them, proposes plans, and — with your nod — promotes them into skills your agents follow on the next run.

Step 01Agent

Survey

Myco's agent scans spores, sessions, and plans for procedural patterns with cross-session evidence. One-off observations don't qualify.

myco:survey≥ 0.7 conf
Step 02Human

Approve

Candidates land in the Skills dashboard with rationale and confidence scores. You stay in the loop on what becomes canon for your project.

skills / candidateshuman-in-loop
Step 03Agent

Generate

A SKILL.md is drafted from the source material, staged, and passed through quality gates before being promoted to .agents/skills/.

.agents/skills/gen 1
Step 04Agent

Evolve

As your code evolves, so do your skills. Drift is detected, stale content rewritten, oversized skills split, outdated skills retired — with full lineage.

lineage recordedgen N+1
Day 01

New teammates ship correctly

Skills install once to the .agents/skills/ standard and symlink into each agent's native directory — so every teammate works the way your best session did.

Every run

Agents stop repeating mistakes

Your project's standard of excellence gets enforced, not just documented. The happy path becomes the default path.

Over time

Knowledge compounds

Skills rewrite themselves as the code does. Every generation records rationale, content snapshot, and source IDs — a complete audit trail.

Cortex

The brain of Myco — context, instructions, and a map of your code.

Cortex is where everything Myco knows about this project becomes context your agent can use — an operating brief written from your team's accumulated knowledge, plus a living map of the codebase your agent can navigate before opening a single file.

  • Operating instructions, written for this project — auto-generated from your spores, sessions, and plans. Surfaced at session start so agents arrive oriented, refreshed as the project evolves.
  • Anatomy on every Read — Canopy injects exports, imports, and top comment before each file opens. Most reads end early because the summary already answered.
  • Project map + behavior search — one MCP call returns the directory shape and golden paths; another finds files by what they do, not what they're named.
  • Cortex command deck — the dashboard tab where you read the brief, browse the index, regenerate the map, and watch token-savings tick up.
Canopy guide MCP tools →
Cortex brief · canopy · search
01
Operating brief
Session start · auto-written
## Stack & conventions - TypeScript strict, no any - Test with Vitest ## Active work - Canopy Phase 1 integration
02
Read injection · canopy
PreToolUse · automatic
exports Daemon, runDaemon imports ./capture, ./mcp // Owns daemon lifecycle …
03
myco_cortex · myco_search
MCP · on demand
"where does session capture happen?" → capture/transcript-miner.ts → capture/buffer.ts
Team sync

A shared vault, without a backend.

Every teammate's agents benefit from the collective intelligence. Runs on Cloudflare's free tier for small teams. Local databases remain the source of truth — the cloud store is a queryable mirror.

  • Automatic backfill — every spore, session, plan, and graph edge syncs in the background.
  • Fanned-out search — queries hit local and team databases in parallel and merge by relevance.
  • Machine-identity attribution — results are tagged with who said what, so nothing is anonymised.
  • Cloud MCP endpoint — expose your team's knowledge to managed agents and N8N automations.
Team sync guide Cloud MCP →
Mycelium · team connected · 4 nodes
node · 01 chris_a7b3c2 synced
node · 02 dana_4f21d8 synced
node · 03 riley_e0912a syncing · 12
managed cloud mcp bearer · rotated
worker · cf
myco-sync
D1 · Vectorize · KV
Works with your agent

Drop Myco beneath the agent you already use.

Hooks-based integration. No wrappers, no forked CLIs — the agent keeps its voice, Myco captures its surface.

cc
Claude Code
hooks · mcp · skills
Full support
cs
Cursor
hooks · skills
Full support
cx
Codex
hooks · .agents/
Full support
vs
VS Code Copilot
hooks · .agents/
Full support
gm
Gemini CLI
hooks · .agents/
Full support
ws
Windsurf
hooks · skills
Hooks + skills
oc
OpenCode
hooks · .agents/
Full support
pi
Pi
hooks · skills
Full support
Docs

Dig in.

Nine guides cover everything from your first myco init to running a Collective across dozens of projects.

Local-first · MIT licensed

Install once. Let the forest floor do the rest.

Myco runs entirely on your machine by default — no account, no vendor lock-in. Layer team sync and a Collective on top when you're ready.

Get started Star on GitHub