Skip to main content
Type / in the chat input to open the command palette. Keep typing to filter, use ↑/↓ to move, Enter to run, Esc to dismiss. Commands that take arguments (like /sprint and /fork) keep the composer open so you can type the rest.

Building

/sprint example

The sprint opens as a new tab in the fleet bar and builds in an isolated session while you keep chatting in main. Your /effort and /model settings apply and persist per project.

Sessions

/fork example

The fork runs in parallel in its own tab — you stay in your current session. Prefixing any message with >> does the same thing:
Forked sessions work in isolated git worktrees, so parallel sessions never trample each other’s changes. Open sessions persist: quit the CLI and relaunch, and your tabs come back.

Project

/kanban, /roadmap, and /arch render right in the terminal — press Esc to return to chat. They show the same project data as the web workspace. /reverse runs in the background (typically a few minutes) and you can keep chatting while it maps your codebase into the architecture graph. See Work on an Existing Repo for the full flow.

Setup

Skills and MCP servers are account-level — anything you configure in the CLI applies across your projects, in the CLI and on the web. OAuth integrations are managed from the web workspace. See Integrations.

Launch flags

Flags you can pass to predev itself: