History

Every request you send and every workflow you run is recorded. Nothing is uploaded: history is written into the project's local cache, on your machine only.

Open it with the History panel (Alt+5).

Two tabs

The panel has one tab per kind of run, and a filter box that applies to whichever is active:

  • Requests: one entry per executed request, for the currently selected API. Each shows the method, the path, the request name if it was a saved instance, and the resulting status.
  • Workflows: one entry per workflow run, labelled with the workflows in that batch and coloured by outcome. A batch that ran five workflows is one entry.

Entries are grouped by day, newest first, with Today and Yesterday spelled out.

Reading an entry

Selecting an entry opens it in the main area, marked read only; it's a record of something that already happened, not an editable request. You get the response as it came back (status, headers, body) and the request exactly as it was sent, with variables already resolved. That last part is what makes history useful for debugging: it shows the real URL and the real headers, so you can see which environment values were actually in play.

A workflow run opens its full report: each block with its status (passed, failed, or skipped) and the failures spelled out.

A run made with TLS verification disabled records that fact, so you can tell from history whether a response came over a verified connection. See environments.

Where it's stored

.api-craft/cache/
├── responses/<api-slug>/     # request executions
└── workflow-runs/            # workflow run reports

Both sit under .api-craft/cache/, which is gitignored: history is machine-local and never committed, so it can't leak a response body or a resolved secret into the repo. Each entry is written twice: a small summary, and a .full.json sibling with the complete payload.

Older entries are pruned automatically. How many are kept is a plan limit: on the free plan, the last 10 per API and the last 10 workflow runs.

From the CLI

Workflow run history is scriptable:

craftr workflow history              # summaries, newest first
craftr workflow history --limit 5    # just the last five
craftr workflow history <run-id>     # one run, in full

Request runs print their result directly (craftr req run … --full), so there's no separate history command for them.