Meet Fumu in 60 seconds. Watch the intro

Design notes

Fumu grows one skill at a time

Everything Fumu can do is a capability you can add, pause or remove. New ones arrive with no access, and earn trust the same way as everything else.

Fumu celebrating with sparkles around it, on a burgundy background.

The most important decision in Fumu’s design is a simple one: everything Fumu can do in the outside world is a capability. Email, calendars, code, research, the web: each is a separate skill that can be added, paused or removed without touching anything else.

Fumu itself stays small and focused on the things that should never change: understanding what you want, planning, remembering, asking for approval and keeping a record. Adding “pay my electricity bill” or “book a haircut” should never mean rebuilding the assistant.

Actions, specialists and routines

A capability can bring three kinds of building block:

  • Actions: single things it can do, such as opening a pull request or finding a meeting slot. Each one has a clear risk level.
  • Specialists: agents that know one area of your work, such as coding, your inbox or support.
  • Routines: multi-step jobs Fumu can run again, such as a weekly bill check.

Each capability says up front what it needs to read and change. That list is what Fumu checks every action against.

The right skill, at the right time

A growing list of skills creates its own problem: offered hundreds of options, an assistant picks the wrong one. Fumu avoids that by only considering the handful of skills that fit the request in front of it. The answer stays focused, and it keeps working well as the list grows.

Easy to add, careful to trust

Adding a capability is easy. Trusting it is a separate step:

  1. It arrives with no access. Nothing happens until you approve what it asks for.
  2. It is kept apart. Each capability runs on its own, with no way into the others.
  3. It never changes silently. Updates need your approval, like the first install.
  4. It starts cautious. Like everything else, it drafts and asks before it acts, until you raise its autonomy.

Packs anyone can use

A capability pack bundles a skill with sensible defaults: what it may do without asking, what it must always ask about, and the checks it must pass. A pack built for one business works for any other, unchanged.

That is how Fumu grows: one skill at a time, each one earning its place.

Fumu with its pink shades pushed up, thinking, on a burgundy background.

Design notes

Why Fumu asks before it acts

An agent that can send email as you is only useful if you trust it. Here is how Fumu earns that trust one capability at a time, instead of asking for all of it on day one.

Fumu dozing with its shades on, waiting, on a burgundy background.

Design notes

A task that can wait three days

Real errands involve waiting: for a reply, an approval or a Monday morning. Fumu is built so that waiting never loses work, and a retry never does anything twice.

Fumu peeking over its pink shades with a knowing look, on a burgundy background.

Brand

Reading Fumu's face

Fumu has nine moods and one rule: its face only changes when a task changes state. Here is what each one tells you at a glance.

See Fumu at work.

Watch the 60-second intro, follow a real run from issue to pull request, and ask for a live walkthrough.

See the showcase