Install
Effect-native scoped capability lifecycle with a Zod-authored execute door
For a published npm release:
npm install @fungi.computer/myceliumpnpm, Yarn and Bun work the same way.
Entrypoints
Section titled “Entrypoints”@fungi.computer/mycelium@fungi.computer/mycelium/define@fungi.computer/mycelium/effect@fungi.computer/mycelium/remote@fungi.computer/mycelium/semaphore-transition@fungi.computer/mycelium/sandbox-guest@fungi.computer/mycelium/sandbox-wire@fungi.computer/mycelium/sandbox-failure@fungi.computer/mycelium/sandbox-boundary@fungi.computer/mycelium/testing@fungi.computer/mycelium/workers@fungi.computer/mycelium/mcp@fungi.computer/mycelium/sandbox
What comes with it
Section titled “What comes with it”Installing @fungi.computer/mycelium also installs @fungi.computer/cairn, @fungi.computer/forage, @fungi.computer/mule, @fungi.computer/puffball, effect, zod, acorn, @cloudflare/codemode, @modelcontextprotocol/server.
Set up
Section titled “Set up”npm install @fungi.computer/myceliumThe package ships ESM only and depends on Zod, Effect, acorn,
Cairn, Forage, and
Mule at runtime, all installed automatically. The root
entrypoint is the Promise host facade. @fungi.computer/mycelium/effect
supplies the scoped Effect API. Both produce an Effect-native Mule tool. The
./sandbox-guest, ./sandbox-wire, ./sandbox-failure, ./sandbox-boundary,
and ./semaphore-transition subpaths support a host’s sandbox adapter. A host
supplies the sandbox that actually evaluates code and enforces isolation,
external access and cancellation.