I have a few quick questions: 1.

make test

seems to write to

~/.openhands

instead of staying isolated. Is that expected? Also, if I set

OPENHANDS_PERSISTENCE_DIR

to work around that, one test fails (

test_work_dir_and_persistence_dir_are_different

). 2. I was thinking about opening a PR to add devcontainer support to the CLI repo, similar to the GUI repo. But I'm not 100% sure it's a good idea, since it might push new contributors toward a clunkier setup (testing/using the CLI from the VS Code terminal, I'm not sure it works well there). Would appreciate a yes/no on this one. 3. I also wanted to add podman support in

openhands serve

(also handling rootful/rootless+selinux cases for both docker and podman, where possible). Would it be ok to add it as a separate command, something like

openhands serve-new

? I'm not sure how good it is going to be, and I don't want to risk breaking

serve

.

Hey, thanks @little-architect-38123! My opinion: 1. that is not expected, we’d appreciate a fix if you can make one 2. i don’t have a super-strong opinion about this, I think you assessed the pros and cons well, and the other con is maintainability — we’d need to make sure that the devcontainer remains up to date 3. the proper way to add podman support would probably be to add a PodmanWorkspace to OpenHands/software-agent-sdk, like the ApptainerWorkspace I think. We might want to check if

openhands serve

works well with the apptainer workspace as well, we haven’t tried that yet IIRC

1. OK, I'll submit a quick fix for that, and also a few other test issues tomorrow. 2. A devcontainer that only installs

uv

should be pretty low maintenance. I'll test the CLI in the vscode terminal and think a bit more about it. 3. I'll wait then. If this takes a while, podman support can still be added using the docker-compatible socket.