Capabilities

Everything Fumu can do is a capability.

Add the ones you need, pause the ones you don't. Each one says up front what it needs, and asks before anything risky.

Packs

Five packs to start with.

Anything that reaches a customer or the public needs your approval until you raise that pack's autonomy.

Fix issues, open pull requests, review code and triage bugs.

Default: Asks before any merge or deploy.

Track competitors, summarise trends and check pricing pages.

Default: None needed: the pack only reads.

Draft LinkedIn posts, articles and changelog announcements.

Default: Always asks before publishing.

Draft replies, onboarding emails and follow-ups from your own inbox.

Default: Asks before sending, until you decide it has earned your trust.

Triage support email, answer from your docs and escalate the rest.

Default: Asks before sending; labelling is allowed.

Adding more

However a new capability is added, it follows the same approvals and the same record as everything else.

Step 1
Connect
Add a new service or tool. It arrives with no access at all.
Step 2
Approve
You see exactly what it wants to read and change, and say yes or no.
Step 3
Use
Fumu picks it up the next time a request needs it. Nothing else changes.
Step 4
Trust
Raise its autonomy when it has earned it, or switch it off at any time.

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