Agents: Session scoping

[stevencl]

In the recent study one participant started a local workspace session. Once they were done with that they started working on a cloud repo but reused the session. As a result, while the agent was able to read and write to the cloud repo, the file list was not updated with the new context. This meant that it was difficult for the participant to see new files that were created or browse the files that had been modified. Also, the agent committed directly to main, rather than creating a PR.

[vs-code-engineering]

Hi @stevencl. As a member of the team, you can help us triage this issue by referring to https://github.com/microsoft/vscode-copilot/wiki/Copilot-Inbox-Tracker and assigning an owner directly.

[bamurtaugh]

Thanks for filing this! Do you have more details (i.e. a screenshot(s) or example steps) on how they started work on a cloud repo but reused a different session?