Skip to main content
The predev CLI brings the full pre.dev agent to your terminal. Run it in any project directory and you get the same agent chat and slash commands as the web workspace — except the agent reads and edits the files in that folder directly.
Works on macOS and Linux (Apple Silicon, ARM64, and x64). The installer puts everything under ~/.predev, adds predev to your PATH, and keeps itself up to date — you never run the installer again.

​
First run

1

Install

Restart your shell (or source your rc file) so predev is on your PATH.
2

Run predev in a project directory

The current directory becomes the agent’s workspace. You can also pass an opening prompt directly: predev "add dark mode to the settings page".
3

Log in via your browser

On first launch the CLI opens your browser to pre.dev. Sign in (or pick your account), approve, and return to the terminal — the CLI picks up your session automatically. Your credential is stored locally in ~/.predev/auth.json; you won’t need to log in again on that machine. Run /login anytime to switch accounts.
4

Pick up your project

The CLI links each directory to a pre.dev project. The first launch in a folder creates one; every launch after that resumes it — chat history, sessions, and settings included. Pass --new to start a fresh project for the same folder.If the folder already contains code, the CLI detects it and offers to reverse-engineer the codebase into your project’s architecture before you start. See Work on an Existing Repo.

​
What you can do

Everything runs through the chat input. Type / to open the command palette — see the full command reference.

Chat on local code

Ask questions, request changes, debug — the agent reads and edits the files in your working directory.

Run sprints

/sprint <feature> builds a feature end to end in a parallel session while you keep working.

Fork parallel sessions

/fork <task> spins a task off into an isolated session — run several at once from the fleet bar.

Reverse-engineer a repo

/reverse maps an existing codebase into your project’s architecture graph.

Project views in the terminal

/kanban, /roadmap, and /arch render the Kanban board, roadmap, and architecture graph right in your terminal.

Credits and models

/balance shows remaining credits; /model, /effort, and /pro control which models do the work.

​
CLI or web?

Both clients share the same projects, sessions, and data — you can start in one and continue in the other.
The CLI and web stay in sync. A sprint started in the terminal shows up in the web workspace, and if a run is live from the web, the CLI reflects it instead of starting a competing run.

​
Staying up to date

The install one-liner is a one-time bootstrap. After that, the predev launcher checks for new releases in the background and installs them automatically — every launch runs the newest installed version. New versions land in ~/.predev/versions/ and downloads are checksum-verified.

​
Next steps

Command reference

Every slash command, grouped by what it does.

Work on an existing repo

Point pre.dev at a codebase you already have.

Coding Agent

How pre.dev’s agents plan, build, and verify.

Integrations

MCP servers, skills, and OAuth services — all manageable from the CLI.