Mcelium

What one session learns, the others know.

Mcelium links your team's Claude sessions. When one session makes a decision, finds something out, or changes something others rely on, the sessions that need it hear about it mid-task. Nobody has to stop and sync.

Dana Pricing specClaude

We're dropping the free tier. Update the spec: Starter becomes $9 a month with a 14-day trial.

✻Done. The free tier is out of the spec, and Starter is now $9 a month with a 14-day trial.

mcelium shared a decision

Free tier removed. Starter is $9 a month, 14-day trial.

Sent to 1 session that relies on pricing: Omer

Reply to Claude…
Omer Launch emailClaude

Draft the launch email for Thursday.

mcelium 1 decision from Dana affects this draft

The free tier is gone. Starter is $9 a month with a 14-day trial.

Your draft offers a free plan in paragraph 2.

✻Dana dropped the free tier, so I've rewritten paragraph 2 before going on:

Start on the free plan, no card needed.
Try Starter free for 14 days, then $9 a month.

✻ Writing the rest of the email…

Dana's session settles a pricing decision. Omer's session is mid-draft, gets the decision, and fixes the email. Nobody sent a Slack message.

Share context, not just code.

When several people work with Claude at once, each session builds up context the others never see. Mcelium passes along the parts that matter.

How it works

  1. 1

    Connect your sessions

    Each teammate links their Claude session to your team's Mcelium space. It takes one step.

  2. 2

    Mcelium keeps track

    It notes what each session decides, learns and changes, and what each one relies on to do its work.

  3. 3

    Only relevant context arrives

    A session hears about something only when it affects the task in front of it. Everything else stays quiet.

When two sessions disagree, it stops and asks.

Mcelium never quietly overrides a decision. If two sessions head in directions that can't both be true, Claude pauses and shows you both sides.

Noa Pricing FAQClaude

Add an FAQ entry saying Starter includes 3 seats.

mcelium conflicts with a decision from Dana

Dana's spec says Starter includes 1 seat.

Both can't be true as written.

✻I've paused before writing this. How do you want to go on?

  1. Ask Dana first
  2. Follow Dana's spec (1 seat)
  3. Write it with 3 seats anyway

Code

For code: Git without the push and pull.

In Claude Code, Mcelium reads each edit as code, not text: which functions, types and endpoints you changed, and which ones you rely on. When your agent changes something another agent depends on, that agent adapts mid-task, before anyone sees a broken build.

Dana ~/shop-app claude
> rename getUser to fetchUser and make it async
⏺ Update(src/api/users.ts)
⎿ Updated src/api/users.ts with 2 additions and 2 removals
12 - export function getUser(id: string): User {
12 + export async function fetchUser(id: string) {
13 - return db.users.find(id)
13 + return await db.users.find(id)
⏺ PostToolUse hook mcelium
⎿ Shared: users.getUser renamed to fetchUser, now async
Sent to 1 session that uses it: Omer
⏺ Done. getUser is now fetchUser and returns a Promise.
>
⏵⏵ accept edits on
Omer ~/shop-app claude
> add a profile page that lists the user's orders
⏺ Write(src/pages/Profile.tsx)
⎿ Wrote 48 lines to src/pages/Profile.tsx
⏺ mcelium 1 change from Dana affects this task
⎿ users.getUser is now users.fetchUser (async)
You call it in Profile.tsx:14 and OrderList.tsx:31
⏺ Dana renamed getUser. Updating my calls before I continue.
⏺ Update(src/pages/Profile.tsx)
14 - const user = getUser(id)
14 + const user = await fetchUser(id)
✻ Updating OrderList.tsx… (esc to interrupt)
⏵⏵ accept edits on

Dana's agent renames a function. Omer's agent is mid-task, gets the change, and fixes its own calls. Neither of them pulled.

When two code changes collide, it asks.

Mcelium never merges code silently. If two people change the same function in ways that can't both work, the agents pause and show you exactly what's going on.

Omer ~/shop-app claude
> drop the id param from fetchUser, read it from the session
⏺ mcelium Noa is changing fetchUser too
⎿ Noa added a second parameter, options.
Your change removes id. Both can't land as written.
⏺ I've paused before editing. How do you want to go on?
❯ 1. Message Noa first
2. Keep Noa's signature and adapt my change
3. Continue anyway
Dana ~/shop-app claude
> /mcelium status
⏺ mcelium shop-app, 3 sessions live
Dana (you) src/api/users.ts, src/api/orders.ts
Omer src/pages/Profile.tsx uses fetchUser
Noa src/api/users.ts same file as you
Changes you shared today: 6. Delivered to others: 2.

See who's touching what.

Type /mcelium status in any session to see what each teammate's agent is working on and where your work overlaps. Git stays underneath as the safety net.