Copilot insert command to terminal doesnt successfully activate terminal

[cwebster-99]

When Copilot prompts a terminal command if you choose to insert in terminal the terminal doesn't activate via auto activate command first

We had to create a terminal first for activation command to run and then insert from copilot once the terminal was set

cc/ @eleanorjboyd

[karthiknadig]

This is the issue that shellStartupis designed to solve.

[cwebster-99]

Since command is the default setting and supports all shells is there something we can do to make this experience more reliable on the Copilot side if not from our activation side. shellStartup could be made the default but I think I prefer it as command since it doesn't require editing files and covers more shell types

[karthiknadig]

@DonJayamanne is working on copilot tools to make Copilot use the right commands when running Python.

[DonJayamanne]

s working on copilot tools to make Copilot use the right commands when running Python.

This has been completed in this iteration.

[eleanorjboyd]

my understanding at this point is that users who want to have the environment activated before copilot commands are run will need to set their activation type to "shellStartup" as that will setup their env before executing the copilot terminal action. This is the behavior we support currently and therefore I am going to close this issue