Medium: IDE keyboard shortcuts (e.g. Ctrl+P) captured by IDE instead of TeamCode TUI terminal

[ElioNeto]

Description

When running TeamCode inside an IDE-integrated terminal (VS Code, Cursor, Windsurf, etc.), keyboard shortcuts such as Ctrl+P, Ctrl+W, Ctrl+Tab, and others are intercepted by the IDE before they reach the TeamCode TUI. This prevents users from using important TUI features.

Impact

• Ctrl+P — cannot open command palette or quick-open in TUI (IDE captures it for file search)
• Ctrl+W — cannot close tabs/splits in TUI (IDE captures it for closing editor tabs)
• Ctrl+Tab — cannot switch tabs in TUI (IDE captures it for switching editor tabs)
• Ctrl+N — cannot create new items in TUI (IDE captures it for new file)
• Many other shortcuts common to terminals and IDEs

This makes the TUI significantly harder to use inside an IDE, which is a common workflow pattern.

Root Cause

IDE-integrated terminals (VS Code integrated terminal, Cursor, Windsurf) run a "terminal" that is actually a web-based XTerm emulator. The IDE keyboard handler has higher priority for certain key combinations and never forwards them to the terminal process.

The TeamCode TUI currently has no workaround for this — users cannot rebind these shortcuts or use alternative key combinations.

Workaround

Users can:

1. Run TeamCode in a standalone terminal emulator (iTerm2, Windows Terminal, GNOME Terminal, Konsole, etc.)
2. Manually disable the conflicting IDE keyboard shortcuts in IDE settings
3. Use a different keybinding in TeamCode (not currently possible since some TUI keybindings are hardcoded)

Suggested Fix

1. Document IDE workarounds — add a section in the TUI help about running inside IDE terminals
2. Make TUI keybindings configurable — allow users to rebind shortcuts to avoid IDE conflicts
3. Detect IDE terminal environment — check for TERM_PROGRAM=vscode or similar env vars and suggest alternatives