aftersight¶
Observability infrastructure for self-improving agents.
An agent cannot improve on a run it cannot read. Aftersight writes every run into the repository as plain files, so the agent can read its own history with the tools it already has.
Those files are readable by a person and machine-readable by a client. An agent uses its normal file and shell tools to diagnose one failed run, find recurring failures and inspect exact model or tool inputs and outputs.
Then ask:
Read
.runs/NAVIGATE.mdand find out why the latest run failed.
There is no account, API key, service or initialization step. Aftersight itself makes no network requests, and payload redaction is enabled by default.
Where to go next¶
- Why aftersight exists explains the local, agent-native design.
- Quickstart records a first run.
- Frameworks covers OpenTelemetry and framework setup.
- Navigating runs contains the search workflow.
- Run folder format documents every generated file.
Local durability
Aftersight can run in production, but local filesystem data may disappear with an ephemeral, replaced or failed host. Use durable storage or another telemetry export path when the run history must survive the host.