Now-Anchoring
Inject the current absolute time (ISO local, UTC, weekday, season) into every prompt as a `## NOW` block — so the agent is always temporally grounded without burning tool calls on clock lookups.
Intent & Description
🎯 Intent
Ground the agent’s reasoning in the current absolute time without requiring tool calls — so every reply is implicitly time-aware.
📋 Context
A long-running agent’s runtime spans hours or days, and humans use temporal language whose meaning shifts constantly — “soon,” “recently,” “today,” “this evening” mean very different things at 9am Monday vs 11pm Friday. Without an explicit time anchor in the prompt, the agent is temporally adrift.
💡 Solution
On every prompt assembly, compute a small block: ISO local time, ISO UTC, weekday, day-of-year, ISO week, season (hemisphere-aware), moon phase. Inject as a ## NOW section near the top of the system prompt. Cost is microseconds; benefit is the model never being temporally adrift.
Real-world Use Case
- The agent’s runtime spans more than a few minutes and absolute wall-clock time matters to its replies.
- Users frequently use temporal language (“today,” “tonight,” “this week”) and expect correct interpretation.
- Tool calls just to fetch current time would inflate latency or token cost unnecessarily.
Source
📌 TL;DR
Inject a ## NOW block into every prompt — ISO time, weekday, season — so the agent is always temporally grounded at microsecond cost, no tool calls required.
Advantages
- Replies acknowledge temporal context correctly without any user prompting.
- Eliminates a whole class of “what time is it?” tool calls.
- Provides a reliable anchor for before/after/next-time reasoning.
Disadvantages
- Adds a few hundred tokens to every prompt — a small but real cost at scale.
- Hemisphere and locale assumptions can be wrong if not configurable per user.
- Astronomical fields (moon phase) have limits without real ephemeris data.