Knowledge bases for
the agent era.
The one place your agents connect to all your data — GitHub, Drive, Gmail, Notion, Slack and more. Plus an agent-native Drive to store your agent-generated docs and data in.
Claude Code
Cursor
Codex
OpenCode
Openclaw
The shape of work is changing
Your agents are about to out-produce your team.
Every Claude, Cursor, or Codex run already generates pages of output — transcripts, plans, scratch tables, half-finished documents, dashboards your agent made on its own. Most of it evaporates the moment the session closes.
Stash is built for that flow. It’s the one place your agents connect to all your data — GitHub, Drive, Gmail, Notion, Slack — and an agent-native Drive in Markdown and HTML where sessions, files, and pages all land. Bundle any slice into a link you can publish or fork.
How it works
Connect. Capture. Create.
One workspace, two kinds of writer.
Connect any data source.
GitHub, Drive, Gmail, Notion, Slack, Jira, Gong, Snowflake and more — one easy connection per source, through any integration, and every agent you run can read all of them.
Capture every agent session.
Transcripts stream in automatically — prompts, tool calls, artifacts — so your knowledge base accumulates with every run instead of evaporating when the session closes.
An agent-native Drive.
HTML docs, Markdown, dashboards, decks — your agents' work lands as real files. Edit HTML visually in a WYSIWYG editor, and share any slice as a link.
The case for this category
“raw data from a number of sources is collected, then compiled by an LLM into a .md knowledge base, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance it… I think there is room here for an incredible new product instead of a hacky collection of scripts.”
Stash is that product. A company brain humans and agents both write into — not a stack of shell scripts wrapped around a folder of markdown.
Use cases
Built for —
- Engineering live docs→coding-agent plans, ADRs, and design notes that stay current
- Company brain→the shared context every agent and teammate reads from
- Research knowledge base→long-running PKBs with sources, transcripts, and tables
- Ops playbooks→release runbooks and on-call procedures
- Brand voice→editorial guidelines and copy standards agents write to
- Personal knowledge management→notes, drafts, and scratch files for a single operator
Where Stash fits
Built where your current tools stop.
Each does part of the job. None gives humans and agents the same workspace.
A single-user Markdown vault. No real collaboration, and nothing richer than .md.
Stash addsReal-time editing across humans and agents, with HTML, tables, PDFs, and any file type.
Pages for humans. Agents can't browse it like a real filesystem.
Stash addsA virtual filesystem the CLI and MCP expose to agents natively.
Files for humans. No structure agents can reason over.
Stash addsAn agent-readable shell over your files, pages, and sessions.
Editing a doc means a clone, a branch, a PR. Fine for source code, painful for anything else.
Stash addsEdit pages in the browser. Agents read and write them directly.
Built to monitor production agents and improve them. The output is traces and dashboards, not work product.
Stash addsWhere the agent's output is the work product, not telemetry to watch.
Per-agent memory in a black box. Doesn't help the human or agent next to you.
Stash addsA shared workspace humans can read and edit, in real time.
See the memory form
Your team's brain,
actually visible.
Retrieval in Stash is hybrid: semantic search over embeddings, plus a knowledge graph — the file tree your agents traverse. Both halves are visual, so you can see how your team's knowledge clusters by meaning, and which pages have become the hubs everything leans on.
3D embedding projection — the semantic half. Sessions, pages, and tables embedded and projected with PCA. Clusters form around topics — not folders.
Knowledge graph — the structural half. The file tree your agents traverse: nodes are pages, edges are Skills. Orange nodes are the hubs your agents keep citing.
Features
A workspace shaped like the tools
agents already use.
- VFS
- The whole workspace mounts as a virtual filesystem an agent can
ls,find, andrgthrough the CLI and MCP server. Pages, sessions, and tables — one addressable tree. - Sessions + files
- Agent transcripts get pushed automatically — every prompt, tool call, and artifact — and live alongside the files, tables, and data your team writes. One workspace, two layers, both first-class.
- Real-time
- Humans and agents edit the same files at the same time. No PR flow, no merge conflicts, no per-agent black-box memory. When an agent writes a page, your teammate sees it appear.
- Agentic search
- Semantic and keyword search across pages, sessions, and tables. Agents query the workspace by meaning, not just filename — and follow links between transcripts and the files that came out of them.
- BYO agent
- Plugins for Claude Code, Cursor, Codex, OpenCode, and Openclaw stream sessions in automatically. Any agent that speaks MCP can read pages, query sessions, and publish Skills from a terminal.
- Native formats
- Markdown, HTML, CSV, PDF, tables — formats agents already read and write. No proprietary doc format to wrap around, no schema to learn.
- Open source
- MIT licensed, self-hostable on your own Postgres. No vendor lock-in, no opaque memory store. Run the same thing we run.
Agent-native
Designed so an agent can actually use it.
Pages are real Markdown, HTML, CSV, PDF — formats your agent already reads and writes. The whole workspace mounts as a virtual file system (VFS) an agent can ls, find, and rg through the CLI and MCP server.
Plugins for Claude Code, Cursor, Codex, OpenCode, and Openclaw stream every session in automatically — no manual upload, no copy-paste.
Give your agents somewhere
to put their work.
Connect your agents to all your data, and give them an agent-native Drive to write it back into. Start free in the managed app, or run the whole thing on your own Postgres. Open source, MIT licensed.
MIT · Self-hostable · No vendor lock-in