managing-shared-memory
Configure and audit Union Street Honcho-backed memory, profile memory namespaces, memory sync, traces, anchors, and shared institutional memory. Use when agents forget context, memory is collapsed, or memory boundaries need design.
- License 许可
- MIT
- 最近更新
- 2026-05-20
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- managing-shared-memory
- license
- MIT
- description
- Configure and audit Union Street Honcho-backed memory, profile memory namespaces, memory sync, traces, anchors, and shared institutional memory. Use when agents forget context, memory is collapsed, or memory boundaries need design.
- compatibility
- Requires Union Street local v1 with Postgres, pgvector, uv, and Honcho memory config.
02 资源文件 1
- 参考文档references/memory-config.yaml930 B
03 SKILL.md 正文
Managing Shared Memory
Memory is core infrastructure. Local JSONL is a durable log, but Honcho-backed memory peering is the supported v1 behavior.
Checks
- Run
bun run us doctor; Postgres, pgvector, and uv must pass. - Inspect the profile pack:
memory.providershould usually behoncho.memory.peerProfileshould be the agent id.sharedNamespacesshould includeinstitutionaland relevantgroup:<department>.
- Query runtime state with
bun run us runtime status <agent>. - Inspect memory events through runtime/API or profile JSONL when debugging.
Rules
- Never collapse many agents into one workspace unless explicitly designing shared memory.
- Keep departmental shared namespaces scoped.
- Preserve trace/session ids when writing memory so Lash runs remain reconstructable.
- If remote sync fails, look for
sync-outbox.jsonlbefore assuming memory vanished.
Reference Config
Use references/memory-config.yaml for profile-scoped Honcho memory shape.
04 同仓库更多 Skills
understanding-pulse
Configure and explain Union Street pulse heartbeats, recurring self-checks, pulse cadence, and pulse instructions. Use when agents should periodically wake up and inspect work.
token-accounting
Inspect, configure, and reason about Union Street token usage, model accounting modes, free providers, and usage records. Use when debugging cost, throughput, or token-heavy fleet behavior.
setting-agent-schedules
Configure Union Street agent schedules, cron jobs, due runs, scheduler ticks, and scheduled prompts. Use when creating recurring agent work beyond pulse.
managing-union-street
Manage a Union Street agent fleet from outside Union Street. Use when configuring, auditing, onboarding, repairing, or operating Union Street agents, fleets, plugins, memory, Lash delegation, schedules, webhooks, messaging, environments, or performance.
managing-agent-environments
Configure Union Street agent runtime environments, local host mode, workspace scope, secrets, and future Docker/Kubernetes/cloud sandbox targets. Use when changing where agents run.
installing-plugins
Install, inspect, grant, and debug Union Street plugins that bundle skills, MCP servers, CLI guidance, custom tools, apps, or runtime providers. Use when adding plugins to agents or departments.