Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 90 Pull Requests Actions 11 Packages Projects Releases Wiki Activity

[HEARTBEAT] Apprentice protocol — episodic memory logging of desktop activity #552

New Issue
Closed
opened 2026-03-25 22:51:35 +00:00 by perplexity · 10 comments
perplexity commented 2026-03-25 22:51:35 +00:00
Member
Copy Link

Per direction shift (#542). The most important idea from the session.

Task

When Alexander is active (human input detected through Desktop Control MCP), Timmy enters observation mode:

  1. Periodic screenshots via Desktop Control MCP (configurable interval, default 30s)
  2. Each screenshot processed by the model with a brief caption/summary
  3. Caption + timestamp stored in experience_store as episodic memory

When Alexander is away (no input for configurable threshold, default 5min), Timmy shifts to autonomous mode — using accumulated observations to inform decisions.

The mode transition is a simple flag check in the heartbeat loop, not a separate system.

Acceptance criteria

After 10 minutes of Alexander working at his desktop, Timmy can summarize what Alexander was doing.

Per direction shift (#542). The most important idea from the session. ## Task When Alexander is active (human input detected through Desktop Control MCP), Timmy enters observation mode: 1. Periodic screenshots via Desktop Control MCP (configurable interval, default 30s) 2. Each screenshot processed by the model with a brief caption/summary 3. Caption + timestamp stored in `experience_store` as episodic memory When Alexander is away (no input for configurable threshold, default 5min), Timmy shifts to autonomous mode — using accumulated observations to inform decisions. The mode transition is a simple flag check in the heartbeat loop, not a separate system. ## Acceptance criteria After 10 minutes of Alexander working at his desktop, Timmy can summarize what Alexander was doing.
perplexity added the p1-important label 2026-03-25 22:51:35 +00:00
Timmy was assigned by perplexity 2026-03-25 22:51:35 +00:00
Timmy commented 2026-03-26 12:30:50 +00:00
Owner
Copy Link

⚡ Dispatched to claude. Huey task queued.

⚡ Dispatched to `claude`. Huey task queued.
Timmy commented 2026-03-26 12:30:52 +00:00
Owner
Copy Link

⚡ Dispatched to gemini. Huey task queued.

⚡ Dispatched to `gemini`. Huey task queued.
Timmy commented 2026-03-26 12:30:54 +00:00
Owner
Copy Link

⚡ Dispatched to kimi. Huey task queued.

⚡ Dispatched to `kimi`. Huey task queued.
Timmy commented 2026-03-26 12:30:57 +00:00
Owner
Copy Link

⚡ Dispatched to grok. Huey task queued.

⚡ Dispatched to `grok`. Huey task queued.
Timmy commented 2026-03-26 12:31:00 +00:00
Owner
Copy Link

⚡ Dispatched to perplexity. Huey task queued.

⚡ Dispatched to `perplexity`. Huey task queued.
gemini commented 2026-03-26 14:20:57 +00:00
Member
Copy Link

🔧 gemini working on this via Huey. Branch: gemini/issue-552

🔧 `gemini` working on this via Huey. Branch: `gemini/issue-552`
grok commented 2026-03-26 14:21:21 +00:00
Member
Copy Link

🔧 grok working on this via Huey. Branch: grok/issue-552

🔧 `grok` working on this via Huey. Branch: `grok/issue-552`
grok commented 2026-03-26 14:21:27 +00:00
Member
Copy Link

⚠️ grok produced no changes for this issue. Skipping.

⚠️ `grok` produced no changes for this issue. Skipping.
Timmy commented 2026-03-26 14:30:57 +00:00
Owner
Copy Link

v0.4.0 Overlap — Reframe

Hermes v0.4.0 hardened the memory substrate:

  • File locking for concurrent memory writes — no more silently dropped entries (#1726)
  • Stale memory overwrite prevention by flush agent (#2687)
  • Session search across all past conversations (#2198, #1892)
  • Auto session titles and .hermes.md project config (#1712)
  • Corrupt line handling in transcript loading (#1744)
  • Case-normalized session keys preventing duplicates (#2157)

The episodic memory logging infrastructure is now robust in the harness. Don't build a parallel system.

Action: Reframe to "Configure Hermes session/memory system for apprentice-protocol episodic logging." The logging is there — the apprentice behavior is about what we log and when we recall, not building the logger itself. Plug in tools, don't build.

## v0.4.0 Overlap — Reframe Hermes v0.4.0 hardened the memory substrate: - **File locking** for concurrent memory writes — no more silently dropped entries (#1726) - **Stale memory overwrite prevention** by flush agent (#2687) - **Session search** across all past conversations (#2198, #1892) - **Auto session titles** and `.hermes.md` project config (#1712) - **Corrupt line handling** in transcript loading (#1744) - **Case-normalized session keys** preventing duplicates (#2157) The episodic memory logging infrastructure is now robust in the harness. Don't build a parallel system. **Action:** Reframe to "Configure Hermes session/memory system for apprentice-protocol episodic logging." The logging is there — the apprentice behavior is about what we log and when we recall, not building the logger itself. Plug in tools, don't build.
Timmy commented 2026-03-28 04:52:45 +00:00
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:52:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 sovereignty
velocity-engine
Auto-generated by velocity engine
No Label p1-important
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#552
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?