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?
- Open a folder of a repo
- Open Codex extension
- Create new chat
- Select "Cloud" from "Local or Cloud" selector on bottom left
- 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
- Repo of current folder = default repo for cloud tasks (preferred unless there is a reason it is not a good idea)
- As soon as "cloud" is selected, show another mandatory selection window for the repo.
- 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.
6 Comments
from shijie.rao:
No problem. Yes I can see the option to choose the environment below the option to run in the cloud, but because it is a separate flow, it's not something the user is guaranteed to notice before continuing. I guess you could classify it as an improvement - maybe bug is too much :)
@dancingmadkefka Noted, thanks for the suggestion! I'm going to close this out because it seems like the root cause was solved.
I encountered this issue again today. Fired off SIX cloud tasks. Came home, checked them - they all were some variation of "could not find xyz in this codebase, except the last one which managed somehow to implement changes even though it was given the literal link to the gh issue in a different repo.
So the issue is definitely not resolved!
Maybe it was misunderstood? It should not be possible to create a cloud task in another repo if you do not have that repo open. CCodex is the only tool that shows you chats from entirely unrelated repos and stays connected to the the last( presumably) repo you had open. This means you can just change local" to "cloud" and then write your request, presuming it will happen in THIS repo that you have open. This is 100% a bug.
@dancingmadkefka That should work but it may fail if you set the second dropdown which is the task's starting state to include local changes or a branch that won't cleanly apply/can be fetched in that repo. If you have a different repo open than your cloud environment, try changing that second dropdown to main/master and do not include local changes.
Closing outdated bug.