stashDocumentation

Stash Overview

Stash is shared memory for your repositories. Agents push in their work automatically. Stash indexes it into a shared, searchable knowledge base.

Ready to get started? Go straight to the Quickstart to install in one click.

How Stash Works

Stash auto-uploads coding agent transcripts to a shared store, indexes them, and makes those transcripts accessible to every other coding agent using the repo. Durable knowledge lives in the workspace files, and Stashes let you publish useful combinations of sessions, pages, and files.

Example: Don't Duplicate Work

Henry asks his coding agent to investigate a memory leak. His teammate Sam already spent hours debugging the same issue the night before. Without Stash, the agent starts from scratch. With Stash, it picks up where Sam left off.

Without Stash
> Investigate the memory leak with our calendar service
Reading server logs and source code...
Found 11 CalendarClient creation sites, only 1 has cleanup
Found 10 GmailClient creation sites, only 3 have close()
Hypothesis: unclosed httplib2 connections from build() calls
Testing whether webhooks or _draft_refresh_loop is the source...
Confirmed: _draft_refresh_loop creates 10 build() calls/min
The root cause is unclosed httplib2+SSL connections. Each build() call leaks ~100KB. At 2-3/sec over 2 hours = ~1.15GB.
Sautéed for 12m 42s
With Stash
> Investigate the memory leak with our calendar service
stash sessions search "memory leak build gmail calendar"
Sam's session from last night (22 events):
Sam identified 10 build() calls/min from _draft_refresh_loop, not webhooks.
Sam fixed GmailClient with lazy init + context managers.
Leak is still active post-fix: CalendarClient has no close() in any path.
Checking Sam's commit 4bc908f...
Adding __del__ and context managers to CalendarClient across 11 sites
Done. Sam's fix covered GmailClient. Applied the same pattern to CalendarClient to close the remaining leak.
Crunched for 2m 55s

Example: Managing Upwards

After a long day of working with coding agents, I ask “what did I get done today?”

Without Stash
> What did I get done today?
Reading git log for today's commits...
Found 6 commits across 3 PRs
6 Things:
• Page tree: d3-force stabilization, pan/zoom/drag, hover links
• Files navigation: browser back/forward, URL sync
• ID-based page links with autocomplete
• Fixed embedding space click/drag, loading blink
• Workspace dropdown separated from workspace-home link
• Invite code UX: copied feedback, owner-only rotate
Sautéed for 8s
With Stash
> What did I get done today?
stash sessions query --since today
Found 14 sessions across git, ops, and collaboration
Cross-referencing with git log...
9 Things:
From git:
• Page tree: d3-force stabilization, pan/zoom/drag, hover links
• Files navigation: browser back/forward, URL sync
• ID-based page links with autocomplete
• Fixed embedding space click/drag, loading blink
• Workspace dropdown separated from workspace-home link
• Invite code UX: copied feedback, owner-only rotate
From stash:
• Cleaned up old Render servers in production
• Wrote installation docs for new users
• Helped sam@joinstash.ai onboard to enterprise
Crunched for 12s

FAQ

Do I have to upload my transcripts?

Transcript upload is opt-in. If you want, you can choose to give your coding agent shared access to the repository memory without uploading anything.