1. AI should take initiative and act autonomously after a delay
Many commenters argued that current models only react to prompts and lack the ability to “wait then do something” on their own.
- “The missing thing is lack of the bot's initiative. It is always the human who takes initiative and writes something, then the bot makes a (perhaps) elaborate response and shuts up.” — Me
- “Claude can definitely wait 50 seconds and then do a second thing … It can either run a bash sleep 50 or use the ScheduleWakeup tool.” — StilesCrisis
- “I'm working on exactly that here!” — jv22222 (linking to a prototype)
2. Temporal awareness / scheduling is a core building block
The discussion repeatedly highlighted the need for AI to understand and use time—whether via simple delays, cron‑like jobs, or versioned chronology.
- “I can't resist the opportunity to paste some of the text I wrote … on an idea I had about adding temporal awareness to Claude.” — drsopp
- “temporal/versioned chronology is absolutely useful.” — alansaber
- “I have a Hermes agent running on VM that does this. I told it to keep an eye on prices. It created a cron job that triggers the scrapes and messages me …” — cassianoleal
3. Existing tools and prototypes already demonstrate practical implementations
Several users pointed to real‑world agents, scripts, or projects that embody proactive, time‑aware behavior, showing the concept is feasible today.
- “Oh cool. I'm working on exactly that here! https://innerloop.works/breadcrumb” — jv22222
- “Have you thought about using llm-wiki? It's pretty powerful and works well.” — rbansal2
- “I've been looking for a new cooker. I have a Hermes agent … It created a cron job …” — cassianoleal