zombie-crab
Enter
Grown, not generated

Watch a thought take shape.

Your reasoning never moves in a straight line — it branches, pauses, and grows back on itself. zombie-crab gives every conversation a living structure you can see, name, and return to.

01 Lines of thought

Two ways to see how you got here.

Canvas draws every conversation as a lane on a timeline — each message a node, growing left to right as the thought unfolds. Tree turns the same history into branches, so you can see where an idea split and which path you took. The evolution of a thought, made visible.

A thought you can see is one you'll want to keep
Canvas — conversations as growing timelines
Tree — where each idea branched
02 Memory you control

Name it, color it, find it again.

Give any conversation an alias, tag it, and pick a color. Later, filter your whole history by tag, alias, text, or date. A mini-tag opens on hover to show what's inside — nothing important gets lost in the scroll.

So who gets to see any of this?
tag: alias: text: date:
Assay pipeline v3 — normalization@pipeline1research
Grant draft — methods section@grant2researchurgent
03 Isolation & secrets

A real agent of your own, walled off by the kernel.

Every user gets a private agent in its own container — separate volume, non-root, no shared surface. Isolation between users' agents is enforced by the Linux kernel, not by application filters.

  • One container, one volume, one non-root agent — per user.
  • Secrets are write-only: entered once, never shown or returned.
  • Injected out of band — mounted read-only into your agent, never through chat.
Zoom out: how the whole thing stays sealed
Chat channel
your messages only
Secret channel
write-only, read-only mount
Your isolated agent
04 One authenticated door

Many parts. A single way in.

Every request enters through the Mycelium API Gateway — one authenticated door. Behind it, each piece does one job and each user's agent stays isolated. Security here isn't a single wall; it's the shape of the whole system.

Behind the door: a structure built for teams
Authenticated doorcrab-exoskeleton-webappMycelium WebAppMycelium APIGatewaycrab-shell-proxymycelium-sdk-goPicoClaw
InfrastructureAIExternal
The zombie-crab stack, grouped by role
05 Built for organizations

A hierarchy your company already recognizes.

Powered by Mycelium's multitenancy, access nests the way an organization does: a tenant holds subscription accounts, each account holds agents, and each agent is shared with members — with read or write permission, per person. Corporate structure, expressed as software.

And every agent can be shaped to fit
Acme Corp· Tenant
Research· Subscription account
eva-natural-ai· Agent
you@acme.comreadwrite
eva-for-agrobiota· Agent
you@acme.comread
06 Agents, templated

Custom agents, cloned clean for everyone.

Operators define an agent from a template — its persona, skills, and memory. Every user gets a private, isolated clone on first use. Admins register and assign models per user, and publish shared skills and files that cascade read-only to everyone in scope.

  • Templated persona, skills and memory — seeded once, per user.
  • Per-user model registry and assignment.
  • Shared skills and files cascade read-only across a scope.
One last piece: your files
eva-natural-ai
template
user-a
user-b
user-c
user-d
07 Files, in reach

Drop a file in. Find it by name.

Attach files straight from the composer; they land in your agent's own workspace, and it reads them by path — the bytes never clutter the chat. Filter your uploads by name to pull one back in seconds. Admins can share files that cascade read-only to a whole scope.

Ready to see your first thought take shape?
protoFilter files
assay-results.csv
protocol.pdf
notes.md
figure-2.png
Your agent is waiting

Step through the door.

Sign in with your email — no password. Your isolated agent, your history, your structure.

Enter zombie-crab
zombie-crab chat