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.
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, which is sharing the memory and typed correctness across agents.
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.
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.
This seems especially useful when agents need to work across multiple repositories and share context or artifacts between them. Really interesting idea.
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.
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?
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.
This is great, always wannt a personalized second brian for my work, rather than my notion and pay for the subscription
Yes!! Planning to open source this as well!
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, which is sharing the memory and typed correctness across agents.
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!
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.
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.
This seems especially useful when agents need to work across multiple repositories and share context or artifacts between them. Really interesting idea.
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.
Also noticed you are a developer/founder from Japan! I'm visiting Tokyo this week!!!
[dead]