Creating cloud tasks targets wrong repo

What version of the VS Code extension are you using?

0.5.19

Which IDE are you using?

VSCode

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What steps can reproduce the bug?

1. Open a folder of a repo
2. Open Codex extension
3. Create new chat
4. Select "Cloud" from "Local or Cloud" selector on bottom left
5. Provide instruction to Codex

Codex will at this point carry out the task to the best of its ability, even though, if you have not ALSO changed the repo to match the current folder, the request will appear to make zero sense whatsoever.

What is the expected behavior?

Options from best to worst

1. Repo of current folder = default repo for cloud tasks (preferred unless there is a reason it is not a good idea)
2. As soon as "cloud" is selected, show another mandatory selection window for the repo.
3. When user hits the send button after typing prompt and selecting cloud task, it asks the user if {current_repo} is the correct repo, and offers a selection window to change.

What do you see instead?

Cloud task is selected, prompt is typed and sent. codex spins up the container and gets to work. The only indication that you might not be in the right repo is the option directly under the cloud task selection that shows the repo name, but it is very easy to overlook as you are there to change the context from local to cloud, not to check which repo you are in (you opened the correct folder after all).

Additional information

I have seen that at least a warning has bene implemented for the case where you have allowed Codex to work on the task, and are about to apply the changes and it warns you that the edits were made in a different repo. It would make sense to apply this insight that the extension seems to have, BEFORE the pointless task is embarked upon :).

I have made this mistake now 3 times now I think.