Run log

Every run has a live run log. Click a run in the Runs list of the Zaprex app to expand its log, or open the Runs tab in your Zaprex dashboard.

What you see

• status: each lifecycle change (queued, starting, running, …).
• step: what Zaprex is doing ("Running the test suite", "Fixing sum.mjs").
• tool: commands it ran, with exit code and output (for example $ npm test → exit 1, FAIL …).
• diff: the change, file by file.
• model: which model answered (see Models).
• message: what Zaprex said in the chat.

The Runs table also shows each run's task, repository, start time, minutes and pull request.

Live, and redacted

Events stream while the run is going. Before anything is stored or shown, a secret scanner redacts credential-like values, so tokens never land in the log, PR text or notifications.

Without a repository

If no repository is connected, the last step says "No repository connected: changes stay in the run log", and the diff is your result.