Agents that use real tools, on parts you can read
You’ve used the coding agents. They’re good. Then you try to make one do real work across a week and hit the same walls: the workspace is gone after the session, every tool is a hand-rolled integration, “permission” means a line in the system prompt, and the whole thing lives in someone else’s product.
Fungi is our answer to those walls. It isn’t a smarter model. It’s the parts of a computer, built so Agents can use them properly, and open so you can check.
What you get
An Agent in your terminal, today. Shiitake runs in your project folder on your own ChatGPT subscription, a provider key, or Fungi hosted models. Sessions are saved and resumable. Run it in Workspace mode and it can write its folder and nothing else; if the sandbox isn’t available, it refuses instead of running unprotected.
npm i -g @fungi.computer/spore
cd your-project
fungi --workspace
Apps with a typed contract. An App is a page for people plus typed backend
methods for Agents, on one SQLite database. You write the methods once with
Agar. The build generates the API. Agents call env.<APP>.method() through one
MCP endpoint, so Claude Code and Codex can use your Apps too.
Releases from commits. Every App is built from one git commit into an immutable Release, checked by digest before install. You pick what’s live and can roll back. Data survives Release swaps.
Real grants. Every call goes through a broker that checks the caller, its grant, the Team, and revocation. Agents can’t approve their own work.
Computers that stay. A hosted Agent gets a Linux microVM that keeps its files. You open the same files in Inkcap and the Agent’s commands run on the same Computer. You can also attach a local folder.
A Saturday with it
You run npx @fungi.computer/oyster try and a desktop opens on 127.0.0.1:8787
with a Hello App. You poke around Grove and Inkcap. Then you run
npm create fungi-app@latest price-watch, replace the sample method with two of
your own, track and latest, and npm run dev. Your page calls them, and so
does curl.
Sunday you deploy an Oyster to your own Cloudflare account and install Price
Watch from its commit. You give Claude Code a named key for the Oyster’s /mcp
and ask it to track three URLs. You open Price Watch in the browser and there
they are. Same rows, two front doors.
Take only what you need
Everything is MIT and on npm, one package at a time. Watchdog is a durable job queue on SQLite. BirdDog is durable mail between Agents. Mule is a cancellable model-and-tool loop. Braid validates and compiles workflow graphs. Caps is the component kit. Use one in a project that has nothing else to do with Fungi.
Honest limits
create-fungi-appis young. Expect its template to change quickly.- A real Oyster deploy needs Cloudflare Workers Paid with Artifacts and Containers, plus Docker to build the Computer image. The laptop trial has no Computer, git storage or Workers AI.
- Oyster is owner-only. For a Team with member accounts, use hosted Fungi, which is invite-only until signup opens.
- Isolation has edges. Team shards share a host kernel. We document what our drills prove, and what they don’t.
- Subscriptions work locally only. Hosted Agents use Fungi credit or your provider API key.
- It’s a lot of system. The operational surface is real. Start with one piece.