Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshpilot.app/llms.txt

Use this file to discover all available pages before exploring further.

History is the cockpit’s audit surface. Every proposal, every approval, every rejection, every auto-fired action, every successful write back to a source-of-truth tool — all of it is here, chronologically, filterable, and exportable.

​
The KPI strip

Events today

Events this week

Executions succeeded

Failures / reversions

​
What’s on the page

  • Audit timeline / feed — newest first, with the agent attribution, the brand, the action type, the operator who decided (or “auto” if it fired under an autonomy threshold), and the outcome.
  • Filters — by brand, domain, outcome (succeeded / failed / reverted), and actor.
  • Drill-in details — click any row to see the proposal payload, the operator’s edit (if any), the final payload sent to the source tool, and the response.

​
Why History exists

Three reasons:
  1. Accountability. You can answer “what happened on the ayurpet account last Tuesday at 3pm?” in one click.
  2. Agent feedback. Patterns of rejection or reversion feed back into the Brain, making the next round of proposals smarter.
  3. Operator confidence. When you’re new to Mesh Pilot, watching the History fill up — and seeing that nothing surprising happened — is what builds the trust to dial up autonomy.

Open History

See your audit trail.