Unreliable locks in file editor

v0
1

Now that the locks are fixed, I wanted to highlight that I’m still getting unreliable behavior with them. My workflow is that I often lock everything, then unlock a couple files, give my prompt and have it focus on those files. Since the major update that updated the file explorer, I’ve noticed that after giving a prompt, v0 re-locks the files I’ve just unlocked. In particular, one thing that just happened was that I restored an earlier version, then I did a browser hard refresh (because sometimes the client-side state appears to be disconnected with the server-side state on the file locks and diffs), then unlocked the files I wanted to edit, then gave my prompt. I immediately noticed that v0 relocked those files, then later complained that those files were locked.

I believe the root of the issue is just inconsistency between client-side and server-side file locks. I’ve also seen the client show locks on a file that subsequently got edited by the v0 agent.

1 Like
4

Thanks for reporting, this does sound like inconsistency saving the locked state. I’ll pass it along and see what we can do

2 Likes
5

Hi @rtruxler, just checking in on your issue with the unreliable locks in the file editor. Have you found any solutions, or do you still need assistance? Let me know if that helps!

6

Hey Jacob! Thanks for checking in.

I thought I saw an issue the other day, but it turns out that when the agent is in the middle of generating, it locks all files. I would chalk that up to a weird UI quirk since I didn’t lock the files myself.

That said, the issue I reported before where the locks seem to forget their state hasn’t returned, and I think it’s been more stable lately.