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

[HIGH] Chat history is in-memory only — lost on server restart #46

New Issue
Closed
opened 2026-03-14 18:46:46 +00:00 by kimi · 0 comments
kimi commented 2026-03-14 18:46:46 +00:00
Collaborator
Copy Link

Problem

The chat history in dashboard.store.message_log is in-memory only and is lost when the server restarts:

class MessageLog:
    """In-memory chat history for the lifetime of the server process."""
    def __init__(self) -> None:
        self._entries: list[Message] = []

Impact

  • Users lose conversation context on server restart
  • Briefings generated from empty history
  • Cannot review past conversations after restart

Related

  • Issue #38: Thinking engine rumination loop
  • Issue #12: Session handoff persistence

Acceptance Criteria

  • Store chat history in SQLite (timmy.db or memory.db)
  • Load history on server startup
  • Implement retention policy (e.g., last 100 messages or 7 days)
  • Add /api/chat/history endpoint to retrieve persisted history
  • Maintain backward compatibility with existing message_log singleton
  • Tests for persistence and retrieval

Priority: HIGH 🟡

## Problem The chat history in `dashboard.store.message_log` is **in-memory only** and is lost when the server restarts: ```python class MessageLog: """In-memory chat history for the lifetime of the server process.""" def __init__(self) -> None: self._entries: list[Message] = [] ``` ## Impact - Users lose conversation context on server restart - Briefings generated from empty history - Cannot review past conversations after restart ## Related - Issue #38: Thinking engine rumination loop - Issue #12: Session handoff persistence ## Acceptance Criteria - [ ] Store chat history in SQLite (timmy.db or memory.db) - [ ] Load history on server startup - [ ] Implement retention policy (e.g., last 100 messages or 7 days) - [ ] Add `/api/chat/history` endpoint to retrieve persisted history - [ ] Maintain backward compatibility with existing `message_log` singleton - [ ] Tests for persistence and retrieval ## Priority: HIGH 🟡
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#46
Delete Branch "%!s()"

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?