Hey, thanks for the report. This is a known issue. Cloud agent environments get bound to the repo URL when they’re created, and after a rename that binding breaks. We had a similar report before: Renaming GH Repository (and org?) breaks cloud agent GH access
Your workaround with git remote set-url origin is the best option right now, but like you noticed, it only fixes local git actions inside the VM, not the server-side binding.
Unfortunately, there’s no full fix yet to bring existing agents back to life after a rename. New agents should work fine with the new repo URL.
I’ve shared this with the team. No timeline yet, but your report helps with prioritization. About sharing agent history across local/worktree/cloud, that’s a good feature request. I’d suggest making a separate thread in Feature Requests so it can get votes.
Let me know if there’s anything else.