Zero Dependency clock time awareness for Claude Code

asakin1 pts0 comments

Ariel Sakin (@arielsakin): "Left a deploy mid-flight at 1:50 AM and went to bed.

Opened the same Claude Code session at 9:55 AM and typed "ok, something is not working."

The response opened with: "Good morning. Let me check on the overnight deploy and figure out what's broken."

Not "what's the issue?" …"

Home

Subscriptions

Chat

Activity

Explore

Profile<br>Create

Make money doing the work you believe in

Start your SubstackLearn more

For you

Ariel Sakin

4h<br>Durable Context

Left a deploy mid-flight at 1:50 AM and went to bed.<br>Opened the same Claude Code session at 9:55 AM and typed "ok, something is not working."<br>The response opened with: " Good morning. Let me check on the overnight deploy and figure out what's broken. "<br>Not "what's the issue?" Not a generic context-free answer. Good morning — because the model knew I'd been gone eight hours, not eight minutes. It went on to anchor specifics:<br>"CI succeeded at 01:55… the deploy polling ran for ~10 minutes then likely silently hung when my gcloud auth expired."

Each line a duration or wall-clock claim against actual data.<br>Claude Code has no concept of time within a session (github.com/anthropics/c…, and worse, after a context compaction it's frozen at whatever the session-start time was, sometimes hours stale.<br>The standard workaround is shelling out to date whenever the model wants to make a time-relative claim. A tax on every response.<br>The fix was gist.github.com/asakin/…: two hooks. UserPromptSubmit injects [⏱ now=… utc=… unix_ms=… session=…] into every turn, throttled to once per five minutes. SessionStart re-injects after a compaction, Zero dependencies.<br>You don't install it by hand. you don’t have to know python, or how to install hooks. Paste the gist URL into Claude Code itself and say:<br>Look at this gist and install the temporal-awareness hook into my Claude Code. Default the window to 120 seconds:

The agent reads the gist, drops the script in ~/.claude/hooks/, edits your settings.json. It installs the thing that makes itself smarter. When a native version eventually ships, ask it to delete the hooks.<br>When a feature request stalls, scratch the itch. Ten minutes to build, one prompt to install and a meaningfully different collaborator the next morning.<br>P.S: no more “go to sleep” from Claude at 10am, or sending you to lunch because you mentioned that 10 hours ago. This is probably the biggest win.

gist.github.com<br>zero-dependency time awareness for Claude Code. Injects a throttled [⏱ time] block on user prompt and on compaction. No more “good morning” when it’s already 8pm and you are still in the office.<br>zero-dependency time awareness for Claude Code. Injects a throttled [⏱ time] block on user prompt and on compaction. No more &quot;good morning&quot; when it&#39;s already 8pm and you are still in ...

May 24<br>at<br>2:56 PM

Relevant people

Log in or sign up<br>Join the most interesting and insightful discussions.

Start your SubstackSign in

Get app

This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts

claude time code morning deploy session

Related Articles