Re: the note in #C086ARSNMGA channel, and the current behavior: Automations seem to me to have different expectations by backend type: • on cloud = ephemeral sandboxes = “one-off” stuff that clones the repo and does its thing, then the sandbox is typically disposable ◦ the next run will get a new one, clone again etc ◦ seems okay for ephemeral • on local/remote VM = persistent filesystem = it gets filled up by clones of the same repos - and `.venv`s ◦ I think maybe more user-friendly would be to have a location for clones, and reuse them… 🤔 ◦ e.g.

/tmp/openhands-automations/repos

◦ alternatively, clean up the clones from last time / clean up the clone at the end of a run https://openhands-ai.slack.com/archives/C0BLWB8PQ3B/p1787253582035209?thread_ts=1787251947.036729&channel=C0BLWB8PQ3B&message_ts=1787253582.035209

I really like this idea!

alternatively, clean up the clones from last time / clean up the clone at the end of a run

Some automation here or at least making it visible inside your long running local so you can trigger a clean up on your own could be helpful