Logs, deploys and restores from the CLI and the API
ib-apps logs prints an environment's events in a terminal, filtered with the Logs page's query language (ib-apps logs "type = action AND status >= 400" --env production), and --follow keeps printing new ones while you reproduce a problem. ib-apps deploys lists production's deploys with each build and which one is live, and ib-apps restore --at 2h shows what putting the records back two hours would change, then restores once you confirm and prints the command that undoes it.
The API has the same three: GET /v1/apps/:app/environments/:env/events (the query language, a cursor for older events and one for following), GET /v1/apps/:app/deploys (deploy tokens can read it, so CI can check the build it started) and POST /v1/apps/:app/environments/:env/restore (a preview until it's sent with apply: true, for the same people as Backups). The environment's MCP server's list_events takes a query too, and list_deploys is new.
ib-apps 0.13.0 also fixes ib-apps rollback, which 0.12.0 refused as an unknown command.
More in Logs, deploys and restores.