The project list command lists all projects in your current organization along with their deployed stages, deployment status, and monthly costs. Use it to review projects in your organization, see deployed and undeployed stage counts, spot in-progress or errored stages, and compare current and previous month costs.
Usage
The command requires no arguments. You must be logged in to Stacktape, and the output reflects the organization your CLI session is scoped to. Run whoami to verify which organization you're authenticated against.
Output
The project list command prints a summary table followed by per-project detail. The summary table includes these columns:
| Column | Description |
|---|---|
| Project | The project name. |
| Stages | Total stage count with deployed count in parentheses — e.g. 3 (2 deployed). |
| In Progress | Number of stages with a deployment currently running. |
| Errored | Number of stages in an error state. |
| This Month | Aggregated cost across all stages for the current month. |
| Prev Month | Aggregated cost across all stages for the previous month. |
Projects are sorted by most recent stage activity first, then alphabetically by name. Costs use the currency code returned with stage cost data; when no current-month currency code is present, the command falls back to USD.
CI and agent usage
In CI pipelines or when consumed by AI coding agents, pass --agent to get machine-readable JSONL output instead of the interactive table. The --output-format flag provides finer control over formatting.
List projects as JSONL for scripting:
Use plain text output (no colors or animations):
Flags reference
stacktape project listCLI options-h, --helpstringShow Help
If provided, the command will not execute and will instead print help information.
--log-level"info" | "debug" | "error"Log Level
The level of logs to print to the console.
info: Basic information about the operation.error: Only errors.debug: Detailed information for debugging.
--quietbooleanQuiet
Hide progress, banners, success messages and hints. Command output, warnings and errors are still printed.
Examples
Check all projects and their cost at a glance:
Pipe JSONL output into jq for scripting:
Suppress info-level CLI log messages, showing only errors from the CLI framework itself:
Related commands
project create— create a new project in the current organization.org list— list organizations accessible with your current user.whoami— verify which user and organization your CLI session is scoped to.