Summary
When clicking a toast notification, toasty brings the Windows Terminal window to focus, but it doesn't switch to the specific tab where the AI agent (e.g., Claude Code) was running. If you have multiple terminal tabs open, you have to manually find the right one.
Current behavior
- Claude Code finishes a task in Tab 3
- Toast notification appears
- Click the toast
- Windows Terminal comes to focus, but stays on whatever tab was last active (e.g., Tab 1)
Desired behavior
Clicking the toast should switch to the specific tab where the Claude/AI session is running.
Implementation ideas
- Windows Terminal supports the
wt.exe command with -w (window) and --target flags, but targeting a specific tab by process is tricky
- Could potentially save the tab ID or use keyboard simulation (Ctrl+Alt+[number]) if the tab index could be determined
- Windows Terminal exposes some info via the
WT_SESSION environment variable that might help identify the session
Environment
- Windows 11
- Windows Terminal with multiple tabs
- Toasty v0.5
Summary
When clicking a toast notification, toasty brings the Windows Terminal window to focus, but it doesn't switch to the specific tab where the AI agent (e.g., Claude Code) was running. If you have multiple terminal tabs open, you have to manually find the right one.
Current behavior
Desired behavior
Clicking the toast should switch to the specific tab where the Claude/AI session is running.
Implementation ideas
wt.execommand with-w(window) and--targetflags, but targeting a specific tab by process is trickyWT_SESSIONenvironment variable that might help identify the sessionEnvironment