The built-in terminal | Bandura Docs

A real terminal in Bandura's bottom panel: your shell, full-screen programs, Ctrl+C, and an AI coding agent running beside your flows.

Bandura’s bottom panel holds a real terminal, running your own shell at the workspace root, so quick commands (git status, a stray curl, bandura run) don’t need a window switch. It is a pseudo-terminal, the same thing your system terminal gives a program, which means the shell behaves exactly as it does anywhere else.

Opening it

Press ⌃` (Ctrl+backtick) to toggle the terminal directly, or open the bottom panel (⌘J) and pick the Terminal tab. The session starts in your workspace root and survives switching to another tab in the panel.

On macOS and Linux it starts your login shell, so the PATH, aliases and version managers your profile sets up are all there. On Windows it starts PowerShell.

What works

Everything you would expect from a terminal, because your shell is the one in charge:

Your own prompt, your own history, your own Tab completion. Bandura does not imitate any of it.
Full-screen and interactive programs: vim, less, top, ssh, a Node or Python REPL, an installer that asks a question halfway through.
Colour, and programs that redraw or resize with the panel.
Ctrl+C interrupts the running command and leaves the shell up, the same as anywhere else. The Interrupt button sends exactly that.
Restart kills the session and opens a new one, for a shell that is genuinely stuck.
Copy puts your selection on the clipboard, or the whole terminal when nothing is selected.

A URL printed by a dev server or a test runner is clickable and opens in your browser.

What it is not

One session per window: there are no tabs and no splits. Bandura also does not track where one command ends and the next begins, so nothing in the app knows which command produced which output.

Run an AI coding agent next to your flows

Because it is a real terminal, a terminal-based coding agent runs in it. Install Claude Code or another agent CLI, connect Bandura’s MCP server once, and you can ask for a change and watch the canvas redraw as the file on disk changes:

npm install -g @bandura/cli
claude mcp add bandura -- bandura mcp

Then open the panel and run claude. The agent starts in your workspace root, so the flows it lists are the flows in your explorer. The full setup, including what the agent can and cannot do to your files, is in MCP server.

One thing to know before you try it: Bandura reloads a file from disk only when you have no unsaved changes in that tab. Save before you hand a flow to an agent, or the editor keeps showing your version while the agent edits another.

Stuck, or found a mistake on this page? Email [email protected]. A human reads it.