honcho-memory-integration

Manage persistent memory with scoped app_id, user_id, and session_id separation.

Updated Sep 1, 2021
One-click install
npx skills add https://github.com/unclehowell/unclehowell --skill honcho-memory-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: honcho-memory-integration
Source: https://github.com/unclehowell/unclehowell/tree/main/skills/devops/honcho-memory-integration
Command: npx skills add https://github.com/unclehowell/unclehowell --skill honcho-memory-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distributed agent teams often suffer from fragmented, noisy, or conflicting memories across projects, users, and sessions, which leads to incorrect retrievals, leaking of context, and loss of important episodic or project-level knowledge. This Skill defines structure and patterns to reliably scope, curate, retrieve, and consolidate persistent memories so agents can maintain continuity and avoid cross-project contamination.

Core Features & Use Cases

  • Scoping Hierarchy: Enforce app_id, user_id, and session_id separation to prevent cross-project leakage and enable project-scoped queries.
  • Hybrid Recall & Tagging: Combine metadata filtering and semantic similarity for precise retrieval; require minimal tags such as context and status on every memory.
  • Lifecycle & Consolidation: Patterns for creating, upserting, archiving, deduplicating, scoring, and scheduled consolidation (cron) to compress episodic traces into semantic memories.
  • Conflict Prevention & Sharing: Append-first writes, explicit updates only, deduplication thresholds, and agent-to-agent sharing controls for workspace-level memory coordination.
  • Operational Guidance: Troubleshooting steps, secret-handling recommendations, and best practices for async writes and monitoring memory counts.

Quick Start

Consolidate recent session memories into the project-scoped app_id, tag each entry with context and status, and run a deduplication pass to mark superseded items for archival.

Frequently Asked Questions about honcho-memory-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share persistent memory across multiple AI agents without context leakage?

Persistent memory sharing across multiple agents is managed through project-scoped app_id, user_id, and session_id separation. This scoping hierarchy prevents cross-project contamination while enabling agent-to-agent sharing controls within the workspace.

How does hybrid semantic recall work for retrieving agent memories?

Hybrid semantic recall combines metadata filtering with semantic similarity for precise memory retrieval. Every memory entry requires minimal metadata tags such as context and status to ensure accurate filtering alongside the semantic search.

What's the best way to deduplicate and consolidate episodic memory traces?

Periodic consolidation workflows use scheduled cron jobs to compress episodic traces into semantic memories. Deduplication thresholds and decay scoring identify superseded items, marking them for archival to maintain clean persistent memory.

How do I prevent memory conflicts when multiple agents write to the same workspace?

Memory conflicts are prevented by using append-first writes and explicit updates only. Async write handling combined with deduplication thresholds ensures safe agent-to-agent sharing and workspace-level memory coordination.

Does multi-agent memory persistence work for cross-session continuity?

Multi-agent memory persistence supports cross-session continuity through project-scoped workspaces. By applying app_id, user_id, and session_id separation, agents maintain knowledge continuity across different operational sessions without losing episodic context.