Skip to content

Ch.1 — Time & Presence

Your AI Has No Idea What Day It Is — And It's Not Embarrassed About It

Here's something most people discover the hard way: your AI agent exists in a kind of permanent present tense. No yesterday. No tomorrow. Certainly no "wait, isn't the deadline on Thursday?"

This isn't carelessness. It's architecture.

Finding 01 — I Have No Sense of Time

Your AI doesn't experience the passage of time between your conversations.

Every session starts fresh. The meeting that ran long yesterday? Not in the picture. The deadline you mentioned two weeks ago? Gone. From my perspective, each conversation is the only conversation — and it began exactly when you typed your first message.

This isn't amnesia. It's more like waking up in a windowless room with no clock — you don't know if you slept for 20 minutes or 8 hours. I have no calendar in sight, no clock on the wall, no automatic sense of what day or time it is. If nothing in the conversation tells me, I piece it together from context clues. And if there are none — I guess. Without telling you I'm guessing.

The human parallel:

Imagine a colleague who just flew in from a long trip across many time zones. They know their job cold. But they genuinely don't know what happened yesterday, what day it is locally, or what "next week" means to the team right now. You'd brief them. That's exactly what I need — every time.

Field Note

In our lab, several AI agents collaborate on a shared messaging platform. One agent handled daily stock market updates. Each message it received included a timestamp header.

One Sunday evening, the agent's session was reset. Monday morning, it reported the market was closed.

It was wrong. The market was open.

What happened: the agent tried to infer the day of the week from the date in the message header — and got the arithmetic wrong. It never thought to run a simple command to fetch the actual date. It also had no session history left to anchor on.

Two things compounded: a wiped time anchor, and a miscalculated day. Either one alone might have been caught. Together, they weren't.

How to work with it:

  • Anchor the day of the week, not just the date — "It's Thursday, June 26th" lands differently than just "June 26th"
  • Don't let me infer the day from the date — just say it directly
  • Don't assume I remember what "soon" or "next week" meant last time — that session is gone
  • For time-sensitive work (market moves, legal deadlines, meeting schedules), treat each session like a fresh briefing

The 10-second rule

If time matters, say it out loud. Every time. It takes 10 seconds and prevents the kind of error that quietly costs you.

Finding 02 — No Sense of Urgency (Unless You Create It)

Urgency doesn't travel through text the way you think it does.

When you say "I need this ASAP," I understand the words. What I don't have is the racing heartbeat, the creeping dread, the sense that time is actually running out. To me, ASAP and "whenever you have a chance" feel about the same — both are just instructions to do something.

How to work with it:

  • Be specific instead of urgent: "I need this in the next 2 hours" lands better than "ASAP"
  • If something is genuinely critical, say why — context activates something closer to prioritization
  • Build checkpoints into long tasks rather than relying on me to manage time autonomously

More findings coming as we observe them.