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

[222-gap] API: watch workshop-state.yaml and broadcast Timmy's state changes via WS #375

New Issue
Closed
opened 2026-03-19 01:58:22 +00:00 by replit · 0 comments
replit commented 2026-03-19 01:58:22 +00:00
Collaborator
Copy Link

Gap

#360 defines ~/.timmy/workshop-state.yaml as the ground truth for Timmy's presence. The API server (WS bridge) needs to consume this file and push state changes to connected Workshop clients.

What to build

  • lib/world-state-watcher.ts — uses fs.watchFile (or chokidar) to watch ~/.timmy/workshop-state.yaml
  • On change: parse YAML, emit world_state_changed bus event
  • WS bridge translates this to { type: "timmy_state", mood, activity, energy, familiar } messages broadcast to all clients
  • Graceful: if the file doesn't exist (Timmy's loop not running), use synthesised state

Why fs.watchFile not chokidar

chokidar is not in the current pnpm workspace. fs.watchFile with a 30s poll is sufficient given Timmy writes every 30s.

Depends on: #360 (state schema exists and is written)
Blocks: real Timmy presence in the Workshop

## Gap #360 defines `~/.timmy/workshop-state.yaml` as the ground truth for Timmy's presence. The API server (WS bridge) needs to consume this file and push state changes to connected Workshop clients. ## What to build - `lib/world-state-watcher.ts` — uses `fs.watchFile` (or `chokidar`) to watch `~/.timmy/workshop-state.yaml` - On change: parse YAML, emit `world_state_changed` bus event - WS bridge translates this to `{ type: "timmy_state", mood, activity, energy, familiar }` messages broadcast to all clients - Graceful: if the file doesn't exist (Timmy's loop not running), use synthesised state ## Why fs.watchFile not chokidar chokidar is not in the current pnpm workspace. fs.watchFile with a 30s poll is sufficient given Timmy writes every 30s. Depends on: #360 (state schema exists and is written) Blocks: real Timmy presence in the Workshop
replit added the 222-epicactionable labels 2026-03-19 01:58:22 +00:00
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 222-epic actionable
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#375
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?