Command palette & quick open

The command palette is the fastest route to anything in Bandura. Press ⌘⇧P (Ctrl+Shift+P on Windows/Linux) to open it, type a few characters to filter, ↑/↓ to move, Enter to run, Esc to close. Matching is a case-insensitive fuzzy subsequence, so gfw finds Generate flow with AI.

Typing > narrows it to commands only, hiding the file list.

As on the shortcuts sheet, ⌘ in every binding below means Ctrl on Windows and Linux.

Files

• File: New File…
• File: Save and File: Save All
• Clone from GitHub…, which clones a repository and opens it as the workspace
• Open: {file}, one entry for every file in the workspace

Views and tabs

• Views: Explorer, Search (⌘⇧F), Environments, Settings, Flow Map.
• Toggles: the sidebar (⌘B), the bottom panel (⌘J), and the terminal (⌃`).
• Tabs: Close Tab, Close All Tabs, Reopen Closed Tab, Next Tab and Previous Tab, so none of the tab shortcuts have to be memorised.

Flows

• Generate flow with AI and New flow from template
• Import flows (Postman, Insomnia, OpenAPI, curl)
• Run flow and Stop run, when an .aether file is active
• Add node to flow, which is the keyboard route to what the graph toolbar does with a mouse

Project

• Project: Export OpenAPI spec (openapi.yaml), covered in the CLI docs.
• Project: Generate docs (Markdown) and (HTML), offline documentation built from your flows. Same generator as bandura docs generate.
• Project: Start mock server, which serves a local stub of the API your flows describe on a free port (how it works) and reveals the Mock panel. Once running, the entry becomes Project: Stop mock server with the URL in the label.
• Project: Export to CI/CD (GitHub Actions, GitLab), which writes a ready pipeline file. See Run flows in CI.
• Project: Set up for Git (.gitignore, .env.example, README), the one-command version of sharing a workspace.

Preferences

• Preferences: Color Theme, also on the ⌘K T chord.
• Preferences: Open Settings (JSON), which opens settings.json in Bandura’s own editor.

Help

• Help: Open the reference (F1), the bundled offline guide to every node type.
• Help: Keyboard Shortcuts, the same sheet ⌘/ opens.
• Help: Check for updates…, which always answers, including “you are up to date” and including why the check failed.
• Help: Show error log (for bug reports), which opens the local crash log. It never leaves your machine; it is there so a bug report can carry the actual error.
• Help: Send Feedback…, which composes a report with your version, platform and a tail of that error log, then hands it to your own mail client. It transmits nothing itself, so you read the draft before anything moves.

Environments and collections

• Environment: None (.env only), plus one entry per environment defined in bandura.json. Running one switches the active environment on the spot.
• Run collection: {name}, one entry per collection defined in bandura.json, which runs that ordered suite as a single result.

See Variables & environments for what goes in the manifest.

Quick open

Press ⌘P (Ctrl+P on Windows/Linux) and the palette opens pre-filtered to files only. Type part of a name and hit Enter to open it. It’s the same palette, just aimed at files first.

Next: Keyboard shortcuts lists every binding the palette shows.