Skip to content

Commit e213662

Browse files
authored
Update readme.md
1 parent dec9e9b commit e213662

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

readme.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,11 @@
1616
1717
</div>
1818

19+
<br>
20+
<div align="center">
21+
<img src="docs/hero_mechs_combined.gif" width="920" alt="AgingBench: an agent ages across sessions (left), shown across the four aging mechanisms — compression, interference, revision, maintenance (right).">
22+
</div>
23+
1924
## Overview
2025

2126
Long-lived AI agents are increasingly deployed as persistent operational systems, yet they are still evaluated like freshly initialized models. Day-one benchmarks miss a basic systems question: *how long does an agent remain reliable after deployment?* Even when model weights are frozen, an agent's effective state keeps changing as it compresses interaction history, retrieves from a growing memory store, revises facts after updates, and undergoes routine maintenance. Reliability is therefore a lifespan property of the full agent harness, not a snapshot property of the base model.
@@ -24,10 +29,6 @@ Long-lived AI agents are increasingly deployed as persistent operational systems
2429

2530
We are committed to actively maintaining this repository as a foundation for ALE research and engineering, and welcome contributions from the community.
2631

27-
<div align="center">
28-
<img src="docs/hero_mechs_combined.gif" width="820" alt="AgingBench: an agent ages across sessions (left), shown across the four aging mechanisms — compression, interference, revision, maintenance (right).">
29-
</div>
30-
3132
## 📢 Updates
3233

3334
* **v0.3.0** — Initial public release (2026-05-25). Seven core scenarios (S1–S7) across the four aging mechanisms, plus the *S8 SWE-bench-Aging* community extension. AgingCard schema v1.0.0, `agingbench` + `agingbench-lite` CLIs in a single `pip install`, behavioral-DAG telemetry-mode post-hoc trace analysis. Full log will be updated in [docs/CHANGELOG.md](docs/CHANGELOG.md).

0 commit comments

Comments
 (0)