Keep coding-agent sessions attached to worktrees inside VS Code
At a glance
Almas Akchabayev built Deck to keep his Claude Code and Codex sessions in persistent VS Code tabs grouped by Git worktree. This workflow is listed under coding-agents, git-worktrees, terminal-sessions, vscode.
He ran the agents across multiple worktrees and built a repository-worktree-terminal tree inside VS Code. Deck opens each tmux-backed terminal as an editor tab, letting him switch tabs or worktrees and reconnect to ongoing work without moving to a separate terminal application.
How it went
At the time of the post, he said he had used the extension daily for about a month.
Worth knowing
The reported setup requires VS Code 1.110 or later and tmux 3.1 or later. Agent status and automatic session resume in that version supported Claude Code and Codex.
Save ideas in this browser. Upvotes count across the board.
A Lobsters-linked write-up: isolate Claude Code/Codex-style harnesses on a cheap Hetzner VPS with named users (vikki/clara/…), tmux sessions, a shared bot GitHub account, and disposable machines so yolo-mode stays off your laptop.
Agent Standup (OSS, local) turns Claude Code, Codex, Mistral Vibe, and Cowork sessions into a live stand-up: desks, screen-share of real commands/diffs, voices, replay + recap; `npx @double_geste/agent-standup --open`; VS Code/Cursor extension and Claude Code plugin. Free; optional Halloween character pack from €2.
SDK + stdio MCP server run agent()/parallel()/pipeline() scripts that fan out to Claude Code, Codex, OpenCode, or pi via ACP, with journaling, resume, and git-worktree isolation.
Native macOS app orchestrates official Claude Code, Codex and Grok CLIs as a role-based crew (lead/builder/reviewer/docs/auditor/on-call) on your Mac or VPS with schedules, one-click risky-command approvals (Telegram too), and server screen/browser/terminals—no Bandito cloud for your code.