[TODO] MemoryMaxx Patch Porting — upstream refactor blockers #9

Open
opened 2026-05-19 19:12:15 -04:00 by hermes-admin · 0 comments
Collaborator

Context

Patches for MemoryMaxx (kv_cache, checkpointing, inbox_watcher, etc.) were written against monolithic run_agent.py v0.13.0. Upstream has since refactored into modules (agent/conversation_loop.py, etc.), breaking the patch locations.

Status

See PORTING_PLAN.md in the repo root for the full patch-to-upstream location map.

Open Items

  • PATCH 1 (kv_cache): Session ID metadata insertion point moved
  • PATCH 2 (checkpointing): Proactive checkpoint triggers need new locations
  • PATCH 3 (inbox_watcher): Wiki filing inbox watcher
  • Verify honcho-self-hosted skill works against current upstream
  • Update source_baseline/ reference to point to the right upstream baseline

Assignee: j7
Labels: enhancement, memory, upstream

## Context Patches for MemoryMaxx (kv_cache, checkpointing, inbox_watcher, etc.) were written against monolithic `run_agent.py` v0.13.0. Upstream has since refactored into modules (`agent/conversation_loop.py`, etc.), breaking the patch locations. ## Status See `PORTING_PLAN.md` in the repo root for the full patch-to-upstream location map. ## Open Items - [ ] PATCH 1 (kv_cache): Session ID metadata insertion point moved - [ ] PATCH 2 (checkpointing): Proactive checkpoint triggers need new locations - [ ] PATCH 3 (inbox_watcher): Wiki filing inbox watcher - [ ] Verify honcho-self-hosted skill works against current upstream - [ ] Update `source_baseline/` reference to point to the right upstream baseline **Assignee:** j7 **Labels:** enhancement, memory, upstream
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
san/hermes-agent-local#9
No description provided.