When a terminal is moved into a new window using "Move Terminal into New Window" and then the "Create New Terminal" command (Ctrl+Shift+`) is executed from that auxiliary window, the terminal was incorrectly being created in the original main window instead of the current auxiliary window.

Problem

The issue occurred because the TerminalCommandId.New action did not consider which window context it was running in. It would always fall back to the terminal service's defaultLocation (Panel or Editor based on configuration), which targets the main window.

Solution

Modified the terminal creation logic in terminalActions.ts to:

1. Detect auxiliary window context using VS Code's built-in IsAuxiliaryWindowContext context key
2. Target the current auxiliary window by setting the terminal location to the active editor group in that window using editorGroupToColumn(editorGroupsService, editorGroupsService.activeGroup)
3. Preserve existing behavior for main windows and when explicit locations are already specified

Changes

• Added imports for IContextKeyService and IsAuxiliaryWindowContext
• Added auxiliary window detection logic in the TerminalCommandId.New action handler
• When in an auxiliary window and no explicit location is provided, the terminal is now created in that window's editor area

The fix is minimal and conservative - it only changes behavior for auxiliary windows and only when no explicit location is specified, ensuring no regressions in existing functionality.

Fixes #259000.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.