Stash — Shared Memory for Coding Agents

Practical Notes

• Designed for team-scale memory: multiple agents feed one shared workspace
• Self-host option via docker compose -f docker-compose.prod.yml up -d (per README)
• GitHub stars/forks (verified): see Source & Thanks

Stash is useful when “tribal knowledge” becomes your bottleneck:

• One engineer already solved a build issue, but others keep re-solving it.
• Agents generate great notes in transcripts, but the information is lost after the run.
• A long-running agent session becomes faster when it can query prior decisions.

A practical playbook:

1. Start by capturing only the runs you want shared (opt-in).
2. Create one workspace per repo or per product area (keep scope tight).
3. Promote durable facts into the wiki (decisions, commands, common fixes), and let noisy transcripts expire.

This turns agent usage into an asset: later runs start with more context and fewer repeated questions.

FAQ

Q: What is Stash? A: A shared memory/workspace for coding agent session knowledge, accessible via CLI.

Q: Can I self-host it? A: Yes — the README includes a docker compose production file for self-hosting.

Q: How do I keep it clean? A: Keep scope per repo/team, opt in transcripts, and promote durable facts into the wiki.