Issue connecting to container using remote containers extension vscode

[GuyMitchy]

Whether i am running Agent Zero on windows or in my wsl ubuntu configured environment, i am running into an issue where the files created by the agent are not accessible through the vs code interface. I have Remote containers extension installed and can connect to the container in wsl, but none of the new files created in the container appear in the explorer. In the windows environment the workspace for the container is not found and i cant connect remotely.

This program is killer by the way.

Cheers

[dwidge]

Hi normally they show up in ./work_dir when the agent writes to ~/
What path is the agent writing to?

[GuyMitchy]

Hi. Thanks for your help.

Aha. It is writing to root/. Vs code is connected to the container at root/agent-zero/.

[dwidge]

If you add a file testfile.txt to ./work_dir using vscode does it show up in one of these dirs in the container?

ls /root/agent-zero
ls /root
ls ~
find / -name 'testfile.txt'

[GuyMitchy]

Yes thank you.

Didn't realise the files were accessible in ./work_dir. I was connected to the container in another vsc window to access the files. They were being written in the parent directory of the container connection so they weren't being shared. The indent on docker explorer is so shallow i didn't notice lol.

Thanks for your help