Skip to content
Docs

basemodo logs

Follow an App's Logs live, or print its last lines with --lines.

Terminal window
basemodo logs [OPTIONS]

Logs are what the App's processes print and what its builds print, kept 7 days. Without --lines or --after the CLI follows them until interrupted; an agent gets the latest 100 lines and a cursor, and follows by asking again with --after.

Arguments

  • --app <APP>: The App whose Logs to read. Default: the one named after the current folder.
  • --lines <N>: Print the last N lines and stop, instead of following.
  • --after <CURSOR>: Print the lines after this cursor (from an earlier --json answer) and stop.

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

Examples

Follow the Logs of the App of this folder (Ctrl-C to stop):

Terminal window
basemodo logs

Print the last 50 lines and stop:

Terminal window
basemodo logs --lines 50

Print what is new since an earlier answer:

Terminal window
basemodo logs --after <cursor> --json

Output

With --json, it prints {"lines": [{"at", "source", "deploy", "message"}], "cursor", "retention_days"}; while following, one JSON line per log line.

From an agent

The local MCP serves it as the tool logs. 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), lines (number), after (text). It answers what the command prints with --json.

Explained in