List apps that were launched by FlowDeck, including their status and identifiers.Documentation Index
Fetch the complete documentation index at: https://flowdeck.studio/docs/llms.txt
Use this file to discover all available pages before exploring further.
Options
| Option | Short | Description |
|---|---|---|
--examples | -e | Show usage examples |
--json | -j | Output JSON/NDJSON events |
--all | -a | Show all apps, including stopped, crashed, and exited |
--prune | Validate and prune stale entries |
Status icons
Each row in the text output is prefixed with a status icon. The default mode (flowdeck apps) only lists running apps, so you’ll only see the running icon there. The other icons appear when you pass --all.
| Icon | Status | Meaning |
|---|---|---|
| 🟢 | running | App process is active |
| 🔴 | stopped | Terminated via flowdeck stop |
| 💥 | crashed | Process exited unexpectedly |
| ⚪ | exited | Process exited normally (user closed the app) |
| ⏸️ | waitingForDebugger | Launched with --wait-for-debugger, not yet attached |
| ❓ | unknown | State could not be determined |
Registry lifecycle
FlowDeck records every app it launches and keeps the entry until the registry is pruned. Stopped, crashed, and exited entries persist so you can still reference them by ID (for example, to fetch logs withflowdeck logs <app-id>).
Run flowdeck apps --prune to remove non-running entries from the registry.
JSON Output
When--json is set, apps emits an NDJSON event with type app_list. The payload includes totals and the app list under data.apps.