@quick-window-91705 I'm seeing the default python started show when attempting to edit an automation that already has files in it. Did a quick agent investigation here github.com/OpenHands/OpenHands/issues/18341. Before making AC and a PR I wanted to get your eyes on it to see if that looks correct

Ah yes this looks right, I think we need to untar the tarball for custom automations, and render those contents Performing an untar could be tricky if there is no workspace, as we don't start a conversation with a workspace immediately when editing automations Maybe for custom automations we should?

Hmm, we could only support replacing the files. Workflow would be Edit->download tarball, edit locally, upload and replace

cool sounds good to me download/upload tarball buttons make sense to me

👍