Command-line tools¶
Use the CLI to create a project, manage migrations, run the server, and inspect application health. Start with the first-project tutorial for a tested sequence with PostgreSQL and authenticated requests.
Choose a task:
| Task | Where to start |
|---|---|
| Create, migrate, and serve an app | CLI workflows |
| Inspect models or run quality tools | Development tools |
| Find exact arguments, flags, and parser defaults | Generated CLI reference |
| Configure database and application settings | Settings reference |
| Check production readiness | Doctor |
| Operate ordinary background tasks | Tasks |
| Run durable workers | Durable Operations |
| Explore optional AI commands | Experimental AI commands |
Global output flags go before the command:
--quiet suppresses non-error Aksara UI output, not subprocess output or Uvicorn
logs. --plain disables Rich rendering and animation. --no-color and
--force-color control terminal colors.
Exit status depends on the command. Click reports invalid arguments as exit 2; Doctor has its own policy-specific exit codes. Do not assume a universal configuration/database/migration error-code table, or that a zero exit proves application health. Use each command's documented checks.