#5876: docs(AGENTS): add absolute dates convention for memory files
docs
Cluster:
Memory Compaction Improvements
## Summary
Adds a new convention to the AGENTS.md template encouraging agents to always anchor relative dates to absolute ones when writing to memory files.
## Problem
Relative dates like "tomorrow", "next week", or "yesterday" become meaningless once the day passes. This leads to:
- Stale reminders that keep firing because the agent can't tell if the date has passed
- Confusing memory entries that lose context over time
- Missed events or duplicate alerts
## Solution
Add a `📅 Use Absolute Dates!` section to the Memory conventions in AGENTS.md:
```markdown
- ❌ "Demo is tomorrow"
- ✅ "Demo is tomorrow — Sunday, February 1st"
- ❌ "Meeting next Tuesday"
- ✅ "Meeting next Tuesday, February 4th"
```
## Real-world example
Discovered via a demo reminder that was stored as "Jan 30/31 - date TBC" without year context. The reminder kept firing on Jan 31st because the agent couldn't determine whether the demo had already happened.
## Changes
- `docs/reference/templates/AGENTS.md`: Added "📅 Use Absolute Dates!" section after "📝 Write It Down"
---
*Contributed from the field by [@heybeaux](https://github.com/heybeaux) and Rook ♜*
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR updates `docs/reference/templates/AGENTS.md` by adding a “Use Absolute Dates” convention in the Memory section, encouraging agents to anchor relative-date reminders (e.g., “tomorrow”) to explicit calendar dates. This aligns with the template’s broader goal of making agent memory durable across sessions and avoiding reminders that become ambiguous over time.
<h3>Confidence Score: 4/5</h3>
- This PR is safe to merge; it’s a small documentation-only change with low risk.
- The change is confined to a single docs template and introduces no code/runtime behavior changes. The only meaningful risks are minor documentation clarity/consistency issues (date format examples and heading/anchor stability).
- docs/reference/templates/AGENTS.md
<!-- greptile_other_comments_section -->
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
<details><summary><h4>Context used (3)</h4></summary>
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13))
- Context from `dashboard` - docs/reference/templates/AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=ef691cbd-a005-4c3e-998b-6fcd72f2d312))
- Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
</details>
<!-- /greptile_comment -->
Most Similar PRs
#7896: docs: enforce immediate memory persistence in AGENTS.md
by FelixFoster · 2026-02-03
77.1%
#7196: docs: Agent continuity - the 'stranger problem' and lighter approach
by sincere-arjun · 2026-02-02
74.9%
#11743: fix: remove redundant file reads from AGENTS.md template
by shogunsea · 2026-02-08
74.0%
#11761: fix(gateway): expose memory/ directory files in agents.files RPC
by advaitpaliwal · 2026-02-08
70.5%
#11457: feat: Add hybrid memory mode with auto-created daily log templates
by Undertone0809 · 2026-02-07
69.3%
#19560: docs: refactor agent workspace default location & bootstrap configu...
by ashinkuniyil · 2026-02-17
68.4%
#17624: Fix memory flush YYYY-MM-DD placeholder resolution
by grunt3714-lgtm · 2026-02-16
67.8%
#10894: Docs: fix legacy branding, add config reference, expand cron troubl...
by biv0711 · 2026-02-07
67.6%
#8900: fix: improve default memory flush prompts with urgency and specifics
by joetomasone · 2026-02-04
67.5%
#23566: Gateway:expose memory/*.md in agents.files RPC
by SepehrShapouri · 2026-02-22
67.2%