claudeers.
// MCP Servers

sense-of-time

Your AI knows the time. But it can't FEEL the time. A temporal context layer for LLM agents: Claude Code hook + desktop band, MCP server planned. Stores when…

// MCP Servers[ api ][ desktop ][ claude ]#claude#mcp-servers◷ MIT$open-sourceupdated 21 days ago
Actively maintained
95/100
last commit 23 days ago
last release none
releases 0
open issues 0

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up sense-of-time (claude-plugin project) into my current project.
Found on https://claudeers.com/sense-of-time
Repo: https://github.com/moddest-lab/sense-of-time
Homepage/docs: —
Detected install method: claude-plugin → /plugin install sense-of-time@moddest-lab/sense-of-time
Category: mcp-servers. Platforms: api, desktop.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
active; community-verified: false. Confirm the source before running anything.
// or install directly (claude-plugin)
/plugin marketplace add moddest-lab/sense-of-time
/plugin install sense-of-time@moddest-lab/sense-of-time
// or clone
git clone https://github.com/moddest-lab/sense-of-time

// compatibility

Platformsapi, desktop
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageHTML

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

sense-of-time

Your AI knows the time. But it can't FEEL the time.

An LLM knows what time it is, but a three-second pause and a three-week pause look identical to it: the next line of the transcript. sense-of-time gives a Claude Code session a sense of time with its user: how long you were away, which block of today's work you are in, when a greeting or a recap is due and when silence is. It stores only timestamps, never message content.

Status: early and changing daily. Today it is a Claude Code UserPromptSubmit hook plus a desktop band mod, both on your own machine. It does not run in claude.ai chat or in Claude Code cloud sessions. An MCP server for other hosts is planned. MIT licensed.

Install

Requirements: Python 3.11+ on your PATH, Claude Code on Windows, macOS or Linux.

  1. Clone this repo somewhere permanent, for example ~/sense-of-time.
  2. Open ~/.claude/settings.json and add the hook. Use the absolute path to your clone, with forward slashes:
{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python",
            "args": ["/absolute/path/to/sense-of-time/sot_hook.py"],
            "timeout": 10
          }
        ]
      }
    ]
  }
}

If settings.json already has other keys, add hooks next to them. If it already has a hooks block, add UserPromptSubmit inside it.

  1. Start a new Claude Code session (hooks load at session start) and send any prompt. Then check that an event was recorded:
cat ~/.sense-of-time/events.jsonl
  1. Ask Claude what time it is. It should answer from the hook context without calling any tool.

What it does

Before every prompt, the hook appends one event and injects one line of context such as:

[sense-of-time] It is Friday 22:25 (+07:00), late night. The user's previous
message was 12h 38m ago. This session: turn 2, 14m. Guidance: tone concise,
depth light. The user is resuming this conversation after 12h 38m, last active
Friday morning; a one-sentence opener acknowledging the gap is appropriate, once.

Rules in the test build. The hook states the situation; Claude writes the opener in its own words.

Gap since your previous message, in any chat:

GapOpener
under 30 minnone, "continuing"
30 min to 1 ha light greeting phrase
1 to 6 hbrief welcome back, ready to continue
3 h or more, past midnight since, no sleepgreeting, and a check whether you want to continue
6 h or more, no sleepone sentence bridging then to now, pointing at the last unresolved thing; no greeting ceremony
a night's sleep: 3 h or more spanning 03:00, or 6 h or more past midnighta greeting for the time of day, two or three sentences: the gap, a recap of yesterday's work only, then either "let's continue" (your message carries a task) or a question about what to pick up (it does not)

The recap is scoped by time, not by the whole chat: every prompt carries a [sense-of-time] It is Saturday 22:31 line, so the hook can name the exact markers that bracket the previous day's work in this conversation and tell Claude to ignore everything before them. A new chat gets no recap, because it holds none of that work.

"New day" follows you, not the calendar: 21:00 to 02:00 straight through is one day; sleeping 02:00 to 06:00, or 22:00 to 03:00, starts a new one.

Continuous activity, across chats, with no break over 30 min (each once):

Active forMessage
over 3 hit has been 3 hours, still want to continue?
over 6 hshort recap of the day's progress and a reminder to rest
over 10 hanother reminder to rest

Clock, first message in the window that day:

TimeMessage
start between 04:00 and 06:00, nothing since midnightgreeting noting the very early hour
00:00 to 02:00reminder that it is past midnight
02:00 to 04:00reminder that morning is near

Late night (22:00 to 03:00) also sets tone concise and depth light. Thresholds live at the top of sot_hook.py.

What is stored

One JSON line per prompt in ~/.sense-of-time/events.jsonl:

{"ts": "2026-10-23T22:29:32+07:00", "session_id": "e936...", "char_count": 38, "tier": 0}

No prompt text, ever. Events older than 90 days are ignored. Delete the file to forget everything.

Test

python sot_hook.py --selftest

Uninstall

Remove the UserPromptSubmit block from settings.json and delete ~/.sense-of-time/.

Feedback we need

Note the moments, with the time, where:

  • Claude should have acknowledged the gap or the hour and did not.
  • Claude mentioned time and it felt unnecessary or annoying.
  • The opener wording felt off.

Those moments decide the thresholds for the next version.

// faq

What is sense-of-time?

Your AI knows the time. But it can't FEEL the time. A temporal context layer for LLM agents: Claude Code hook + desktop band, MCP server planned. Stores when, never what.. It is open-source on GitHub.

Is sense-of-time free to use?

sense-of-time is open-source under the MIT license, so it is free to use.

What category does sense-of-time belong to?

sense-of-time is listed under mcp-servers in the Claudeers registry of Claude-compatible tools.

10 views
★ 17 stars
unclaimed
updated 21 days ago

// embed badge

sense-of-time on Claudeers
[![Claudeers](https://claudeers.com/api/badge/sense-of-time.svg)](https://claudeers.com/sense-of-time)

// retro hit counter

sense-of-time hit counter
[![Hits](https://claudeers.com/api/counter/sense-of-time.svg)](https://claudeers.com/sense-of-time)

// reviews

// guestbook

0/500

// related in MCP Servers

🔓

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete…

// mcp-serversf/⟨HTML⟩★ 177,810◷ NOASSERTION[ claude ]
🔓

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io

// mcp-serversfarion1231/⟨Rust⟩★ 155,814◷ MIT[ claude ]
🔓

🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman

// mcp-serversJuliusBrussee/⟨JavaScript⟩★ 117,780◷ MIT[ claude ]
🔓

An open-source AI agent that brings the power of Gemini directly into your terminal.

// mcp-serversgoogle-gemini/⟨TypeScript⟩★ 108,744◷ Apache-2.0[ claude ]
→ see how sense-of-time connects across the ecosystem