Build with Buni
Use Buni, the assistant in the canvas, to answer questions, plan changes, build and fix flows, and undo what it changed.
Buni is the assistant built into the canvas. Describe what your flow should do and Buni builds it; ask how something works and it answers; point it at a broken node and it fixes it. Every change Buni makes lands on the canvas where you can see it, and you can undo it.
Some parts of the Buni panel, such as docking it beside the canvas and task-by-task builds, are rolling out gradually and may not appear in your workspace yet.
Open Buni
Select the Buni button on the canvas (its tooltip reads Chat with Buni). The panel opens over the right side of the canvas. On a wide screen you can select Dock beside the canvas to keep it open next to your flow, and Float over the canvas to undock it.
Buni also appears where something needs fixing: when the canvas reports validation problems, select Fix with Buni and it opens with those problems already described.
Choose a mode
The mode picker in the message box decides whether Buni may change your flow.
| Mode | What Buni does |
|---|---|
| Just ask | "I'll answer without changing anything." Use it for questions about your flow or about Buni.ai. |
| Build it | "I'll make the changes for you." Buni edits the canvas directly. |
| Plan first | "I'll write a plan for you to approve." Nothing changes until you approve the plan. |
Use Plan first for large or risky changes, such as rebuilding a section or changing a flow that is already live.
Build or change a flow
Write what the flow should do, in plain language. Useful things to include:
- who the users are and which channel they use,
- the steps in order, and what to collect at each,
- which systems it calls and what to do if they fail,
- rules such as limits, confirmations or opening hours.
Build a USSD airtime top-up: ask for the phone number, then the amount
(between 1 and 500), confirm both, then call our top-up API. If the API
fails, say the service is busy and offer to try again.While Buni works, its progress shows in the panel and the nodes appear on the canvas. When it finishes, a summary card says what changed, for example "Done — I made 5 changes.", with the steps it added, changed or removed. Select Show me on the canvas to highlight them.
Point Buni at specific nodes
Select one or more nodes on the canvas before you send a message. They appear as chips above the message box, and Buni works on those nodes. Remove a chip to leave that node out.
Attach files
Select Attach file to include a requirements document, API description or screenshot. Accepted types are .txt, .pdf, .doc, .docx, .jpg, .jpeg, .png, .gif and .webp. Where your browser supports it, Dictate message lets you speak instead of typing.
Approve a plan
In Plan first, Buni replies with a plan card: the steps it intends to take and what they will change on the canvas. Choose:
| Button | What happens |
|---|---|
| Looks good — build it | Buni builds the plan as written. If the plan removes existing nodes, this button reads Remove and rebuild. |
| Change something | Tell Buni what to change; it writes a new plan. |
| Explain more | Ask about the plan before deciding. |
If the plan arrives as a plain message instead of a card, the same choices appear as replies: Start implementation, Revise plan and Ask a question.
Answer Buni's questions
When a request leaves out something Buni needs, it asks before it builds. The questions dock above the message box, one at a time, headed "Before I build this", with a count such as 1 of 3. Pick an option or answer in your own words, then Continue, or Submit on the last one. Skip this question leaves one to Buni, and Stop asking — decide the rest for me (or Esc) skips the rest.
Steer while it works
You do not have to wait for Buni to finish. Type a message while it is working and send it; Buni picks it up at its next step and adjusts, for example "use Hubtel, not MTN" or "skip the confirmation screen". Work already applied stays on the canvas, and Buni corrects it from there.
To stop, select Stop generating. Pause operation and Resume operation hold a long run and pick it up again.
Bigger builds, one task at a time
For a large request, Buni may split the work into tasks and show a task list with its progress. From the list you can:
- turn on Check with me after each task before sending, so Buni pauses after every task for you to look,
- Pause after this task, then Continue with task N or Finish the rest,
- Stop and keep what's done,
- Undo from task N to roll back that task and everything after it.
Undo Buni's changes
Every run is a single undo step. Select Undo these changes on the summary card, or press ⌘Z / Ctrl + Z on the canvas. If a teammate edited the flow while Buni was working, Buni warns that "This also undoes changes your teammates made while I was working." and asks you to confirm with Undo anyway or Keep them.
Undo from the card is not available after you reload the page, or once a newer change has replaced this one. Use version history to go back further.
Other settings
- Model and thinking effort. Choose a provider, or Auto, and an effort of High (deep reasoning), Medium (balanced) or Low (fastest).
- Also write documentation. When on, Buni also updates the project's Documentation tab after building or fixing the flow.
- Chats. Start a new chat begins a fresh conversation; Recent chats lists earlier ones, with Search your chats.
What Buni can see
Buni works from your current flow, your project type and settings, the nodes you selected, the files you attach and the conversation so far. Do not paste secrets into the chat; store them as credentials and let Buni reference them by name.
Review what Buni builds and test it in the simulator before you publish. Buni's changes only reach users when you publish.