Skip to content
Docs

basemodo status

Say whether an App is awake, asleep, starting or paused, and its latest Deploy.

Terminal window
basemodo status [OPTIONS]

An App nobody visits for 10 minutes falls asleep (unless it runs a worker); the next visit wakes it in a few seconds, never with an error. An App whose worker crash-loops, or that runs out of its memory or disk quota, is paused until it is deployed again; one whose Owner's Trial ended, until they choose a Plan. It also says what the Owner's Plan gives the App: how long its Logs and Backups are kept, and how many times a failed cron run is tried again; and what went wrong in the last day: failed Deploys, Processes that crashed or ran out of memory or disk, failed cron runs.

Arguments

  • --app <APP>: The App to look at. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Is the App of this folder up?:

Terminal window
basemodo status

The same for another App, for a script:

Terminal window
basemodo status --app lunch-rota --json

Output

With --json, it prints {"app", "state" (awake, asleep, starting, paused, or null before the first Deploy), "paused_reason" and "resume" (what resumes it; both only while paused), "latest_deploy", "public_paths", "extras": {"log_retention_days", "backup_retention_days", "cron_retries"}, "recent_errors": [{"at", "kind" (deploy_failed, crashed, crash_loop, out_of_memory, disk_full, cron_failed), "message", "deploy"}]}.

From an agent

The local MCP serves it as the tool status. It only reads, so an agent's client may run it without asking you. Its arguments are the command's, named as JSON keys: app (text). It answers what the command prints with --json.

Explained in