Meet Fumu in 60 seconds. Watch the intro

How it works

Ask once. It plans, delegates, checks and reports.

Every request becomes a task that is never lost. Fumu plans it, hands each step to a specialist, pauses for your approval when it should, and shows you exactly what it did.

The life of a request

Seven steps, from message to report.

  1. Step 1

    Listen

    A message arrives from Telegram, the web console or a schedule you set. It becomes a task, linked to the conversation it came from.

  2. Step 2

    Understand

    Fumu works out what kind of request it is: a quick answer, a routine it already knows, or something new that needs a plan.

  3. Step 3

    Plan

    It brings in what it remembers about you, then writes a short plan, with each step handed to the right specialist.

  4. Step 4

    Do

    Each specialist works through its step and checks the result. Every action is checked against your rules first.

  5. Step 5

    Ask

    A step above the trust you have given pauses the task and sends you an approval card. It waits until you answer.

  6. Step 6

    Check

    Fumu checks the result against what you asked for, tries again if a step failed, and remembers what it learned.

  7. Step 7

    Report

    The answer comes back where you asked, with a full record of what was done and what you approved.

Who does the work

One assistant and its specialists.

You only ever talk to Fumu. Behind it, each specialist handles one area and can only do what that job needs.

  • Fumu

    Plans, delegates and checks the result. It is the one you talk to, and it never takes a risky action itself.

  • Specialists

    One per area: Coding, Inbox, Research, Content, Support and more. Each one can only use what its job needs.

  • Helpers

    One tidies memory overnight, one double-checks risky plans before you are asked, and one turns "every Monday" into a reminder.

Reliability

Built for errands that take days.

Real work involves waiting: for a reply, an approval or a Monday morning. Fumu never loses track of a task while it waits.

  • Long waits

    Waiting days for a reply or an approval is normal. The task picks up exactly where it stopped.

  • Interruptions

    If something restarts halfway through, the task carries on from its last step.

  • Exactly once

    An email is never sent twice and a payment is never made twice, even when a step is retried.

Memory

It remembers why it believes something.

Every memory has a source and a timestamp, so Fumu can explain why it believes something, and forget it when you ask.

  • The task at hand

    What it is working on right now and how far it has got.

    Until the task is done

  • Conversations

    Your chat history, wherever you talk to it.

    Kept, summarised as it grows

  • Past work

    What Fumu did, how it went, and what you thought of it.

    Kept

  • Facts about you

    "Never book before 10am." "Prefers aisle seats."

    Until changed or deleted

  • Your documents

    Notes, docs, emails and PDFs you have shared.

    As long as you keep them

  • Routines

    Ways of working that went well, ready to reuse.

    Kept and improved

Each agent only remembers what its job needs: the Coding agent never sees your finances. Ask "what do you know about my car?", then "forget that", and it is gone.

Accountability

Every task can be explained afterwards.

  • A full record

    Every reply links to the steps it took, the actions it ran and the approvals you gave.

  • Budgets

    Set a spending limit per capability, and get a short daily report of what it cost.

  • Quality checks

    Real requests are re-run before every change to make sure answers stay as good as before.

Watch a request run.

The showcase follows one real task, from an issue link to a pull request waiting for approval.

See the showcase