Unable to change target branch for Cloud Agent VS Code? #181799
Unanswered
albertkun
asked this question in
Copilot Conversations
Replies: 1 comment 1 reply
-
|
@albertkun bro, thats the issue after the recent update, You didn’t miss any VS Code setting this is a real behavior change in Copilot Cloud / Coding Agents, and right now it’s by design, not a bug you can toggle away. After the update Cloud Agents do not run inside VS Code workspace anymore. They run in an isolated GitHub-hosted environment what you can do is go to the agents page, 1. Go to: https://github.com/copilot . let me know if you face any problem. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
VS Code
Body
Before the 1.0.7 November update, sending a task to the agent would default to the current branch. However, after this update everything defaults to the
mainbranch which is ruining my workflow because I have multiple branches in development andmainis for latest stable builds. I am aware of the https://github.com/copilot 's GUI here:Where I can select the
branchand theagent, but this is very inconvenient.I am so confused as to why in VS Code those critical options don't exist or why this behavior was changed. I tried writing an extension to send the branch I'm working on to the agent during coding sessions, but that still doesn't work.
Did I miss any changes where I make those settings in the latest VS Code? If not, is there any suggestions or am I stuck just using the GUI for agent tasks to target the
branchI'm working on?Beta Was this translation helpful? Give feedback.
All reactions