Terminal & AI Providers
Dybs.it does not bundle an AI model. It launches a compatible AI coding CLI on your computer and gives it the selected BMad workflow and project context.
The embedded terminal
The terminal is a real interactive shell inside the app. It stays available while you navigate between project views, and you can use multiple tabs for separate pieces of work.
When you start a workflow from a story, Dybs.it opens or selects the relevant terminal and launches the configured provider. Keep the terminal open while the agent is working. You can always inspect the command before continuing.
A tab without an AI agent
Not every terminal tab needs a model in it. File > New Shell Tab opens a tab that is only your own shell, in the same working directory a new tab would use. No provider is started and no command is typed for you, so you can run git, npm or a quick check beside your agents. The same action is in the Command Palette as New Shell Tab, and there is a shell button next to the + in the tab bar. The keyboard shortcut is Shift+Cmd+T on macOS and Ctrl+Shift+T elsewhere.
Choose what a new tab starts
Settings > General > Terminal has a New tab opens choice:
- AI agent (the default) starts your configured provider, which is how new tabs have always behaved.
- Plain shell makes a new tab just your shell.
This governs the plain "new tab" actions only: the + button, the New Terminal Tab menu item and its Command Palette entry. Launching a story or a workflow always starts the agent for it, whichever option you pick. New Shell Tab always opens a shell, so the dedicated shortcut never changes meaning. With Plain shell selected the + button opens the shell directly and the separate shell button is hidden.
Split the terminal
To watch two sessions at once, drag a tab onto the right or bottom edge of the terminal area. It opens in a second tab group beside or below the first, and both terminals stay live. Drag the divider between them to change how the space is shared, or double-click it to go back to an even split.
Each group keeps its own tabs and its own selected tab. The group you last clicked in is the focused one, and that is where a new tab, a workflow launch and Clear will go. Drag a tab onto the other group to move it across, and drag or close the last tab in a group to go back to a single terminal.
If you prefer the keyboard, select a tab in the tab strip and use Alt+Shift+Right or Alt+Shift+Down to move it into a second group, and Alt+Shift+Left or Alt+Shift+Up to move it back. Alt+Left and Alt+Right still reorder tabs within their own group. The split is remembered per project, so it is still there when you reopen it.
Which coding agents work
Nearly all of them. The workflow runs on any coding agent that works in a terminal and supports the BMad Method, which in practice is tens to hundreds: frontier agents like Claude Code, Codex CLI and Gemini CLI, and open-source ones like Kimi 3 and OpenCode. Which one drives the work is your choice, and you can run one agent for development and a different one for review.
A smaller set gets extra handling inside Dybs.it. Those are detected for you, Dybs.it knows how to phrase a command for them, and where the agent supports it a past session can be resumed. Anything outside that set still runs the workflow perfectly well, it just gets less help from the app around it.
The one real exception is editor-only integrations. They may be detected, but they cannot take a story file and run the develop-and-review loop, so they cannot complete the workflow at all. That is a capability limit, not a preference.
Each agent is installed separately, has to be on your command path, and is authenticated with its own vendor. A Dybs.it licence does not include agent access, API credit, or a model subscription.
Choose a provider
Open Settings to select the default provider. Where workflow-specific overrides are available, they take priority over that default. This lets you use one agent for development and another for review, for example.
If no usable provider is available, use the environment diagnostics in Settings. A provider that works in your normal terminal but is not detected may require an app restart after installation or a path correction.
Workflow launches
The main story actions map to these BMad skills:
| Story state | Workflow |
|---|---|
| Backlog | /bmad-create-story |
| Ready or In Progress | /bmad-dev-story |
| Review | /bmad-code-review |
Dybs.it adapts the launch to the selected provider. Do not depend on identical command-line text across providers: some understand BMad slash commands directly, while others receive an equivalent instruction. The story specification remains the contract for the work.
Sessions and resume
Dybs.it records launched sessions in project history. Whether a session can be resumed depends on the provider:
- Claude Code supports resuming a recorded session identifier.
- Providers without compatible session resume support start a new terminal session for the next launch.
Starting a new session does not delete the old history entry. Use Documents & History to inspect previous work.
Command Palette
Use the Command Palette from the application menu or its displayed keyboard shortcut to find BMad workflows and navigation actions. The shortcut is shown by the app for your operating system; using the menu avoids platform-specific key confusion.
Safety and troubleshooting
- Read a workflow's story or artifact path before approving destructive work.
- Commit important changes before moving between providers.
- If a command is unavailable, confirm the corresponding BMad skill is installed in the project.
- If a provider exits immediately, run it directly in a terminal to complete setup or authentication, then retry from Dybs.it.