Would you pilot a shared vault + hosted MCP for agent files?
Looking for pilot teams whose cloud agents lose files across chats/locally stored.
AI Asset Vault: shared durable vault + hosted MCP for agents. Save → find → promote. Seats, tokens, audit.
Reply/DM if your squad wants early access → vault.wilgott.com
For a pilot, I’d make the success criteria very concrete: can a new agent session find the right file, can two agents avoid overwriting each other, and can a human see who changed what and roll it back? Versioning, scoped permissions, retention rules, and clear handling for stale or conflicting files may matter as much as retrieval itself. A small “before and after” workflow showing the time saved and the number of lost-context incidents avoided could make the pilot easier to evaluate. How are you planning to measure pilot success?
The coordination problem you're solving is real — I've seen teams lose weeks of context when agents start fresh every session.
One thing that might resonate with your pilot users: if they're building products with AI tools (Bolt, Lovable, etc.), the codebase complexity sneaks up fast. We built SecondRead to audit those AI-generated codebases for non-technical founders — find the security holes and cost sinks before they become fires. Might be complementary if your vault users are shipping apps alongside their agent workflows.
Happy to share a free beta audit if any of your pilot teams want a second pair of eyes on their code.
Yeah, that “weeks of context gone when the next session starts cold” thing is exactly what we keep hearing.
Interesting problem with Bolt/Lovable-style shipping too. Different layer than us — we’re the place agents drop reports, release notes, summaries, and other docs into a shared vault (hosted MCP), then find them again with keyword + vector/semantic search so the next agent or teammate isn’t starting cold. You’re more codebase audit. Same kind of founder though.
Appreciate the offer — if a pilot team hits that wall I’ll send them your way. And if you’ve got people juggling a few agents / losing context between sessions, happy for you to point them at us too.
The interesting part is the shared durable layer rather than another file manager. If agents can reliably save, retrieve, and promote files across different sessions without losing context, that could solve a real coordination problem for teams using multiple agents.
Yeah! that’s exactly it. :-)
Not another file app. The useful bit is a place agents (and people) can collaborate and drop stuff across sessions so the next agent isn’t starting from a blank chat. Save → find → promote is the loop we’ve been obsessing over aand it’s shareable.
If you’re juggling a few agents on a team and want to poke at it, happy to do a quick walkthrough or just answer questions here. PM me and I can give you full access to try the Team plan (with the team features unlocked).
That’s interesting. I’d be happy to continue the conversation beyond the thread — would you be open to sharing the best email to reach you on?