Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[claude] fix: auto-update Working RAM timestamp from DB activity (#1351) #1357

Closed
claude wants to merge 1 commits from claude/issue-1351 into main
pull from: claude/issue-1351
merge into: Rockachopa:main
Conversation 2 Commits 1 Files Changed 4 +182 -14
claude commented 2026-03-24 02:58:06 +00:00
Collaborator
Copy Link

Fixes #1351

Problem

Working RAM (Hot Memory) displayed stale timestamps from the static MEMORY.md file despite continuous active inference sessions. The HotMemory.read() method built its output from the database but never included a timestamp, so the displayed "Last updated" was always frozen at whatever was in the fallback file.

Solution

  • Added recall_last_activity_time() to timmy.memory.crud — queries the most recent created_at across all memories
  • Updated HotMemory.read() to include > Last updated: <timestamp> in the header when returning the DB-computed view
  • The timestamp reflects the actual last inference session, auto-updating as new memories are stored
  • Fallback to MEMORY.md file is preserved when DB is empty

Tests

Added TestHotMemoryTimestamp (3 tests): timestamp present with facts, timestamp reflects newest memory, fallback has no timestamp.

Fixes #1351 ## Problem Working RAM (Hot Memory) displayed stale timestamps from the static MEMORY.md file despite continuous active inference sessions. The `HotMemory.read()` method built its output from the database but never included a timestamp, so the displayed "Last updated" was always frozen at whatever was in the fallback file. ## Solution - Added `recall_last_activity_time()` to `timmy.memory.crud` — queries the most recent `created_at` across all memories - Updated `HotMemory.read()` to include `> Last updated: <timestamp>` in the header when returning the DB-computed view - The timestamp reflects the actual last inference session, auto-updating as new memories are stored - Fallback to MEMORY.md file is preserved when DB is empty ## Tests Added `TestHotMemoryTimestamp` (3 tests): timestamp present with facts, timestamp reflects newest memory, fallback has no timestamp.
claude added 1 commit 2026-03-24 02:58:07 +00:00
fix: auto-update Working RAM timestamp from DB activity
Some checks failed
Tests / lint (pull_request) Failing after 35s
Details
Tests / test (pull_request) Has been skipped
Details
13212b92b5 
HotMemory.read() now includes a '> Last updated:' header showing the
created_at timestamp of the most recent memory in the database. This
means the Working RAM display automatically reflects the last inference
session rather than persisting the static timestamp from MEMORY.md.

- Add recall_last_activity_time() to timmy.memory.crud
- Update HotMemory.read() to include timestamp when DB has content
- Export recall_last_activity_time from timmy.memory_system
- Add TestHotMemoryTimestamp test class (3 tests)

Fixes #1351

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Timmy commented 2026-03-24 03:00:45 +00:00
Owner
Copy Link

Merge conflict -- rebase onto main (kimi cv2 stub just landed) and force-push. Changes look good, will merge once green.

Merge conflict -- rebase onto main (kimi cv2 stub just landed) and force-push. Changes look good, will merge once green.
Timmy commented 2026-03-24 03:09:08 +00:00
Owner
Copy Link

LGTM — clean fix with tests. Has merge conflicts though. Rebase on main and I'll squash-merge.

LGTM — clean fix with tests. Has merge conflicts though. Rebase on main and I'll squash-merge.
Timmy closed this pull request 2026-03-24 03:12:02 +00:00
Some checks failed
Tests / lint (pull_request) Failing after 35s
Details
Tests / test (pull_request) Has been skipped
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1357
Delete Branch "claude/issue-1351"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?