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.
great project.
i gave back all my electrical knowledge to my professor already.
i love the idea of infinite canva; it would have helped me in my undergrad.
i just gave it a try, i cant connect shit... due to lack of ece in my head.
Interest has risen in tandem with the popularity of LLMs. I have worked on these sorts of things as part of internal tooling.
Sometimes these strategies are used to provide LLMs with a greater understanding of your codebase to improve code generation results.
Additionally, techniques which allow humans to visualize the shape of code are being explored as engineers become less familiar with the specific implementation.
How does AgentDrive solve the edit conflict? Does user allow to modify a file just like google drive?