Terminal Sessions – VSCode extension for tmux terminals that survive restarts Terminal Sessions, a new VSCode extension, wraps every terminal in a tmux session that survives full editor restarts, crashes, and reboots, with first-class awareness of AI coding agents including Claude Code, Codex, Antigravity (agy), and Grok (xAI). The extension shows live agent state, context usage, cost, and past conversations in the sidebar, and supports macOS, Linux, Remote-SSH, and Remote-WSL, but not native Windows without WSL or SSH. Persistent terminal sessions for Cursor and VS Code, with first-class awareness of your AI coding agents — Claude Code, Codex, Antigravity agy , and Grok xAI . Terminals survive full editor restart, organized per workspace, and the sidebar shows live agent state: working/tool/waiting, context usage, cost, last user and assistant messages. Browse, read, name, resume, and clean up every past conversation on your machine, across all four agents. Every terminal is wrapped in a tmux session whose server runs independent of the editor. Quit Cursor, reboot the window, crash the renderer: Claude Code, dev servers, REPLs, migrations, SSH sessions keep running. Reopen the workspace and everything is where you left it. | Platform | tmux backend | Notifications | Click-to-focus on notif | Status | |---|---|---|---|---| macOS local | Native | macOS Notification Center + modal alert | Yes osascript / terminal-notifier | Full support | Linux local | Native | notify-send libnotify + optional zenity modal | Yes zenity | Full support | Remote-SSH / Remote-WSL | Native tmux on the remote | IPC-forwarded VS Code toast or modal in the local Cursor window | Yes via VS Code API | Full support | Windows native | Not supported — needs WSL or Remote-SSH | Falls back to VS Code toast | No | Requires WSL or SSH | Windows users:tmux does not run natively on Windows. The extension works normally on: WSL— install the extension in the WSL-Remote window, install tmux in WSL sudo apt install tmux Remote-SSH— connect to a Linux/macOS host, install the extension on the remote sideNative Windows PowerShell, cmd, Git Bash is not supported. Remote-SSH / Remote-WSL users:you do NOT need to install terminal-notifier or libnotify on the remote machine. The extension detects the remote extension host via vscode.env.remoteName and routes notifications through the VS Code API, which forwards them to your local Cursor UI automatically. The Show terminal button on waiting alerts still works across the IPC bridge. VS Code's built-in terminal.integrated.persistentSessionReviveProcess only survives window reloads, not full app quits. Child processes always die when the editor fully restarts. This extension solves it by wrapping each terminal in a tmux session whose server daemon is independent of the editor process. Three moving pieces, each independent, composed to give you a persistent and observable terminal layer. 1. tmux as the process keeper. Every persistent terminal you open is actually tmux attach-session against a named session on a tmux server that runs outside of Cursor. Quit Cursor, reboot the window, crash the renderer: the shells and anything they spawned Claude Code, npm run dev , a migration, a long SSH keep running in the tmux server. When you reopen the workspace, the extension offers to re-attach. Sessions are named ts-