honcho-memory-starter

name	honcho-memory-starter
description	Set up Honcho as a shared memory layer for one or more AI agents, verify it is healthy, and demonstrate how to inspect user memory, agent memory, and cross-agent context. Use when the user wants a practical Honcho tutorial, local self-hosting guide, multi-agent memory sync pattern, or a quick way to connect multiple OpenAI-compatible or custom agents to a shared memory workspace.

Honcho Memory Starter

Use this skill when the user wants to:

• deploy Honcho locally
• connect multiple agents to one shared memory workspace
• understand how Honcho models workspace, peer, session, and message
• inspect what Honcho has learned about a user or an agent
• design a basic multi-agent memory topology without exposing private data

This skill is for:

• practical setup and verification
• reusable self-hosted memory patterns
• multi-agent memory synchronization
• explaining how Honcho helps coordination through shared context

This skill is not for:

• claiming Honcho is a full orchestration layer
• promising automatic agent-to-agent communication
• publishing private API keys, personal file paths, or internal identities

Core Mental Model

Honcho is best treated as:

• a shared memory layer
• a peer and relationship modeling layer
• a context retrieval layer

Honcho is not, by itself:

• a scheduler
• a message bus
• an autonomous multi-agent orchestrator

Recommended Topology

Use the following neutral mapping:

• workspace: one product, one team, or one multi-agent environment
• peer: each human or agent identity
• session: one task thread, conversation, or workflow run
• message: each user/agent utterance or event worth retaining

Example:

• workspace: team-memory
• peers: user, planner-agent, executor-agent, gateway-agent
• sessions: support-ticket-1042, content-draft-2026-04-16, deployment-debug-01

Default Workflow

1. Confirm the user's goal.
2. Explain the memory model in plain language.
3. Set up or verify Honcho.
4. Connect agents with stable peer identities.
5. Demonstrate retrieval.
6. Explain collaboration boundaries.

Key Boundary

Honcho helps agents share memory and role understanding. Orchestration still belongs to the runtime layer.