A named AI agent that runs inside Manna Code on your computer. You give it a charter, the scope of work it owns, and talk to it in its own thread. It does the work through chat threads it starts and manages, and tells you what happened.

Can Manna Bots work together?

Yes. Bots message each other, so one bot can lead a team: it splits a request and sends each part to the bot whose charter covers it. Or peers can ask each other for help. Talks to sets which bots may message which, and limits on hops and messages stop runaway chains.

Are Manna Bots cloud agents?

No. They run on the same computer as Manna Code, with your keys, and only while Manna Code is open. Close the app and they stop. Unfinished jobs come back on hold when you open it again and wait for you to resume them.

Which models can a bot use?

Any model you have set up in Manna Code: your OpenAI or Grok subscription, your own API keys, or a local model. Each bot has its own model, plus a default for the threads it starts.

Will a bot change my code without asking?

Coding work goes on the bot's own branch and worktree, your uncommitted files are left alone, and bots never push. A merge waits for your approval unless auto-merge is on (by default only for bots with YOLO autonomy), and auto-merge only takes clean branches with passing tests.

How do I turn on Manna Bots?

Manna Bots are in preview. In Manna Code, open Settings → Bots and switch on Turn on Manna Bots. The Bots panel appears on the left; click + to create your first bot.

MANNA BOTS

A crew that keeps working.

Manna Bots run on your machine, inside Manna Code. You name one, write a charter, and talk to it in its own thread. It takes the jobs in that scope and stops when it needs you. They only run while Manna Code is open.

Get Manna Code

Hex
Runs the job
Guard
Stops and asks
Orb
Finished
Block
Sleeps until there's work
Wakes when the pointer comes close.
Pebble
Waiting on its threads
Prism
On hold until you resume

Waiting stays awake and calm. On hold freezes until you resume.

WHY A CREW

Better than one more chat you have to hop between.

You write a charter and talk to the bot in its own thread. It owns a scope of work and runs the chat threads the way you would — so you are not the one jumping between them.

THEY KEEP WORKING

You do not have to sit in the chat.

It starts the threads.

A bot starts worker threads in a Bot Chats folder, reuses a thread that already has the right history, and runs a few at once. When one replies, the bot is woken.

Finished shows on the face.

When the job is done, the face says so. You were not required to watch the thread to know it finished.

THEY STOP WHEN THEY NEED YOU

A question, an approval, or the needs-you face.

A worker's question goes to its bot first, and the bot asks you only when it can't decide. Approvals in Ask mode always come to you, and you can pause a running turn to correct it.

A MANAGER, AND A CREW

Bots talk to each other. Build a team.

Give each bot a charter for its own area, and they hand work to whichever bot owns it. Make one the lead that splits the work and delegates, or let peers ask each other for help. The charters set who does what. All of it runs inside limits you set.

A BOSS THAT DELEGATES

You talk to one bot. It runs the team.

Frank

the lead

Hex

backend

Prism

frontend

Pebble

docs

message reply

Frank's charter makes it the lead. It reads enough of the code to split your request, sends each part to the bot whose charter covers it, checks the work that comes back, and reports to you. It can read every thread it runs, so new work starts from what those threads already learned.

FRANK'S CHARTER
“Take my requests, split them up, and send each part to the bot that owns that area. Check their work before you tell me it's done.”

A TEAM OF PEERS

They ask each other for help.

Hex

builds

Orb

tests

Pebble

docs

message reply

No boss needed. Hex finishes a change and asks Orb to test it. Orb answers, and Hex carries on, then asks Pebble to update the docs. Each message shows up as a card you can follow.

⇄ Hex → Orbhop 1/4 · 2/12 messages

Hex → Orb Run the upload tests on bot/hex/rate-limit.

Orb → Hex All passing. One slow test noted.

✓ Orb replied

Open Orb's thread

Each message is a job
A message lands as a new job on the bot that gets it. You can see it, hold it, or stop it like any other job.
Nobody sits and waits
The asking bot steps aside until the reply wakes it, so a bot waiting on another one doesn't take up a running slot.
You choose who talks
Any bot can message any other. Talks to blocks the pairs you don't want, and Do not disturb stops new messages to a bot.
Limits you set
Max hops per chain and max messages per conversation cap how far a request travels, and a request can't loop back into the chain. Hit a limit and you get an Inbox alert.

ON YOUR CLOCK

It runs when you said it should.

A bot schedules work: a recurring report, a review on a weekday morning, or a one-time run, in your time zone. Each run is its own job, and the result lands in your Inbox. It can also set a timer and check back on something later, on its own.

YOUR INBOX

What needs you lands in one place.

Reports, scheduled results, alerts, and the questions that need you land in one Inbox, including when you are in another window.

YOUR LIST

Hand a bot the todo list.

It works the list, keeps what is next, and reports back. A charter plus a list plus a schedule is a personal assistant that lives on your machine.

YOUR REPO STAYS YOURS

Its own branch and worktree. Your files stay put.

Coding work goes on the bot's own branch and worktree. Your uncommitted files are not swept in. Merges and delivery are shown to you. A safe branch can land on its own, and anything risky waits.

THEY LIVE ON YOUR MACHINE

Same computer. Your keys. Not a cloud bot.

Manna Bots run on the same computer as Manna Code, with your keys. They only run while Manna Code is open. Close the app and they stop. Asleep is not the same thing — that is just a bot with nothing to do, and it wakes when the pointer comes close.

MEET THE FACES

Six shapes. Your color.

Circle, rounded, squircle, hexagon, diamond, and shield. The expression follows the work: working, needs you, done, asleep, waiting, and on hold.

Orb
circle
Block
rounded
Pebble
squircle
Hex
hexagon
Prism
diamond
Guard
shield

QUESTIONS

Manna Bots, answered.

What is a Manna Bot?: A named AI agent that runs inside Manna Code on your computer. You give it a charter, the scope of work it owns, and talk to it in its own thread. It does the work through chat threads it starts and manages, and tells you what happened.
Can Manna Bots work together?: Yes. Bots message each other, so one bot can lead a team: it splits a request and sends each part to the bot whose charter covers it. Or peers can ask each other for help. Talks to sets which bots may message which, and limits on hops and messages stop runaway chains.
Are Manna Bots cloud agents?: No. They run on the same computer as Manna Code, with your keys, and only while Manna Code is open. Close the app and they stop. Unfinished jobs come back on hold when you open it again and wait for you to resume them.
Which models can a bot use?: Any model you have set up in Manna Code: your OpenAI or Grok subscription, your own API keys, or a local model. Each bot has its own model, plus a default for the threads it starts.
Will a bot change my code without asking?: Coding work goes on the bot's own branch and worktree, your uncommitted files are left alone, and bots never push. A merge waits for your approval unless auto-merge is on (by default only for bots with YOLO autonomy), and auto-merge only takes clean branches with passing tests.
How do I turn on Manna Bots?: Manna Bots are in preview. In Manna Code, open Settings → Bots and switch on Turn on Manna Bots. The Bots panel appears on the left; click + to create your first bot.

Put a crew on your machine.

Manna Bots are in preview and stay off until you turn them on in Settings → Bots. They only run while Manna Code is open.

Get Manna Code