4 ms·

Show HN: AgentDrive – persistent, versioned file storage for AI agents

6 points by tokencanopy 17d ago

We’re opening the private beta for AgentDrive, a persistent file/workspace layer for AI agents. AgentDrive gives agents: - Versioned artifacts and folders - Hosted MCP access for coding agents - Direct upload sessions for larger files - Share links and controlled public publishing - Workspace-scoped authorization and auditability - Many supported file formats such as MD, HTML, JSON, images, videos, and even spreadsheets The MCP surface is intentionally narrow and reviewed rather than exposing the entire storage API. It’s a private beta, so some features are deliberately out of scope for now. See more details: https://tokencanopy.com/products/agentdrive https://tokencanopy.com/products/agentdrive Try the beta: https://app.tokencanopy.com/drive/ https://app.tokencanopy.com/drive/ For MCP clients: claude mcp add --transport http --scope user agentdrive https://drive.mcp.tokencanopy.com/mcp claude mcp login agentdrive codex mcp add agentdrive --url https://drive.mcp.tokencanopy.com/mcp codex mcp login agentdrive A public API/SDK integration experience is on the roadmap so that you can use AgentDrive in your product, but it is not available as a beta user interface today. We’d especially appreciate feedback on: 1. Was connecting and using AgentDrive through MCP clear? 2. Which tools or storage primitives are missing? 3. What would be the first workflow you ask your agents do with AgentDrive? Open source repo is also on the roadmap so that you can host it on your own infrastructure! Sign up at tokencanopy.com for more future updates. Any feedback or feature requests can be sent to support@team.tokencanopy.com. You can reach out to me directly at josh@tokencanopy.com I'd love to personally connect with more founders and developers who are building in the coding agent infra space: https://github.com/jiashuoz https://github.com/jiashuoz

smapira 17d ago
This seems especially useful when agents need to work across multiple repositories and share context or artifacts between them. Really interesting idea.
- tokencanopy 17d ago
  Thanks!! We also have some interesting use cases such as powering coding agents working on different hardware platforms and share files, documents, or reports in a central drive.
- tokencanopy 17d ago
  Also noticed you are a developer/founder from Japan! I'm visiting Tokyo this week!!!
  - smapira 15d ago
    That’s awesome! It’s been pretty rainy in Tokyo lately, but I hope you have a great time here. Would be great to meet up if we get the chance!
anuptalwalkar 17d ago
A few questions - Are these read only? how do you relay ownership? If a rogue agent goes and deletes files for example, how would the system treats that error? I recently open sourced Recall https://github.com/Polign/recall https://github.com/Polign/recall, which is sharing the memory and typed correctness across agents.
- tokencanopy 17d ago
  AgentDrive provides upload APIs so any agents can upload files to the drive. Everything is a soft delete. Every edit and update results in a new snapshot of the file (version). Your project looks cool! AgentDrive itself isn't a memory system - it's a cloud-based file system that can be managed by agents. In other words, you can build a memory system on top of AgentDrive. Open source is also on the roadmap!
  - anuptalwalkar 17d ago
    Thanks for the reply. would that be against some GDPR policy, not that should be a concern in the beginning, but something to think about 'wipeouts'. I struggled with deletion and clean ups a lot and found that is the hardest part to solve of it all.
    - tokencanopy 17d ago
      we support garbage collection jobs that periodically scan and delete objects; we will also provide an option for users to delete the files in trash, which results in permanent deletion. This is fairly common in file systems and mostly an already solved problem.
Jzuckerman 16d ago
[dead]
XUEYANZ 16d ago
MCP makes the agent integration nice and smooth. How does AgentDrive solve the edit conflict? Does user allow to modify a file just like google drive?
- tokencanopy 16d ago
  Currently we delegate the conflict resolution to the agent itself. Every update results in a new snapshot (version). If there's a conflict, then API returns an error code, which the agent can use and compare its file against the latest version. There's definitely a more native way to support file conflict resolution, which will be a future improvement. For example, something like the API returns conflict information upon file upload.
AlexPF99 16d ago
This is great, always wannt a personalized second brian for my work, rather than my notion and pay for the subscription
- tokencanopy 16d ago
  Yes!! Planning to open source this as well!
deleted 16d ago
[deleted]
p32929 15d ago
[flagged]

6 points by tokencanopy 17d ago

smapira 17d ago

This seems especially useful when agents need to work across multiple repositories and share context or artifacts between them. Really interesting idea.

tokencanopy 17d ago
Thanks!! We also have some interesting use cases such as powering coding agents working on different hardware platforms and share files, documents, or reports in a central drive.
tokencanopy 17d ago
Also noticed you are a developer/founder from Japan! I'm visiting Tokyo this week!!!
- smapira 15d ago
  That’s awesome! It’s been pretty rainy in Tokyo lately, but I hope you have a great time here. Would be great to meet up if we get the chance!

anuptalwalkar 17d ago

A few questions - Are these read only? how do you relay ownership? If a rogue agent goes and deletes files for example, how would the system treats that error? I recently open sourced Recall https://github.com/Polign/recall https://github.com/Polign/recall, which is sharing the memory and typed correctness across agents.

tokencanopy 17d ago
AgentDrive provides upload APIs so any agents can upload files to the drive. Everything is a soft delete. Every edit and update results in a new snapshot of the file (version). Your project looks cool! AgentDrive itself isn't a memory system - it's a cloud-based file system that can be managed by agents. In other words, you can build a memory system on top of AgentDrive. Open source is also on the roadmap!
- anuptalwalkar 17d ago
  Thanks for the reply. would that be against some GDPR policy, not that should be a concern in the beginning, but something to think about 'wipeouts'. I struggled with deletion and clean ups a lot and found that is the hardest part to solve of it all.
  - tokencanopy 17d ago
    we support garbage collection jobs that periodically scan and delete objects; we will also provide an option for users to delete the files in trash, which results in permanent deletion. This is fairly common in file systems and mostly an already solved problem.

Jzuckerman 16d ago

[dead]

XUEYANZ 16d ago

MCP makes the agent integration nice and smooth. How does AgentDrive solve the edit conflict? Does user allow to modify a file just like google drive?

tokencanopy 16d ago
Currently we delegate the conflict resolution to the agent itself. Every update results in a new snapshot (version). If there's a conflict, then API returns an error code, which the agent can use and compare its file against the latest version. There's definitely a more native way to support file conflict resolution, which will be a future improvement. For example, something like the API returns conflict information upon file upload.

AlexPF99 16d ago

This is great, always wannt a personalized second brian for my work, rather than my notion and pay for the subscription

tokencanopy 16d ago
Yes!! Planning to open source this as well!

deleted 16d ago

[deleted]

p32929 15d ago

[flagged]