Intra-Agent Memo Scheduling
Let the agent schedule a timestamped note for its own future self — so present decisions hand off context to a later run without needing external scheduler infrastructure.
Intent & Description
🎯 Intent
Present-self has context future-self will need. Without a native memo mechanism, that context falls out of the prompt window by the next session and is gone forever.
📋 Context
The agent ticks continuously across many sessions and regularly has the thought “check back on this tomorrow” or “verify whether X resolved by Friday.” The prompt window only carries recent turns — by tomorrow, the intention has evaporated entirely.
💡 Solution
Provide a tool schedule_future_thought(when, content, intent) that appends to a persistent scheduled-thoughts queue. At each tick, drain due entries and prepend them into the next prompt as [SYSTEM: scheduled note from past-self (set <ts>, fires <when>): <content>]. Mark each fired entry so it runs exactly once. Accept ISO timestamps and relative offsets (+1h, +2d).
Real-world Use Case
- The agent runs across many ticks or sessions and present-self has context the future-self will need.
- External schedulers (cron, queues, durable workflows) are unavailable or overkill for the use case.
- Future-fire memos are small enough volume to live in the agent’s own store.
Source
Advantages
- Agent can defer action without forgetting — “I’ll check this Friday” actually fires
- Past-self can leave rich context for future-self across long gaps
- Provides native “check back on this” semantics inside the agent loop
Disadvantages
- Without expiry or dismissal, scheduled notes accumulate and waste prompt tokens
- Drift between scheduled time and actual tick time depending on tick cadence
- Obsolete future-self commitments can corrupt the agent’s sense of obligation if not cleared