Repository navigation
Agents app: When I get an error notification in the app, I can't tell which session it belongs to or whether this is blocking something from proceeding. #308291
Description
Activity
Sandeep Somavarapu (@sandy081) Don Jayamanne (@DonJayamanne) in this specific error case, do we need to make sure that however CLI sessions are started, that MCP server config is resolved with the correct workspace folder?
I agree we should have a better way of associating errors with the offending session, but it also seems like the above error shouldn't happen 😄
This is happening because the MCP server configuration is pointing to a workspace folder variable, which might not be constant for a Copilot CLI session. Don Jayamanne (@DonJayamanne) how can we prevent this from happening?
Connor Peet (@connor4312) not sure whats going on here, in Copilot CLI, we resolve MCP only when we start a session/send a message and that happens when the user is in the chat input view.
Are there other code paths where MCP in core tries to resolve some variables?The specific error may have been fixed, but the general problem (missing context) is a different issue.
Expected:
Upon expanding the error toast notification, I would see a name for which session it's impacting OR a button to go to the session that the error came from? OR information on whether this is blocking a session or is a passive error.
Actual:
There's an error code and name, but I have no idea if I need to act on this or what it's related to. Where do I need to open a folder?