Airport: Manage Multiple AI Agent Terminals Happily ✈️

A developer built Airport, a free open-source VS Code extension that manages and monitors multiple AI coding agents side by side in VS Code's own terminals. The extension uses a sidebar with live status icons (needs you, working, done), notifications, terminal duplication with a different agent, and session resume, hooking into VS Code's shell integration API to infer agent status rather than parsing agent-specific output. It began as a standalone Electron desktop app before being rebuilt as a native VS Code extension.

AI coding agents have changed the way I develop software. Instead of one assistant helping with one task at a time, I increasingly found myself running multiple agents in parallel — Claude Code, Codex, Devin, Antigravity, and others, each working on a different project or task. And that's when I ran into a problem I wasn't expecting: managing the agents was becoming harder than using them. My workflow quickly turned into something like this: VS Code terminals are great, but once you're running agents across multiple projects and workspaces, they all start looking identical. The question I kept asking myself was: "Which files is this agent actually working on?" The agent knows its workspace — but connecting agent → workspace → files → terminal meant constantly jumping between windows just to piece it together. That's what led me to build Airport. Airport is a VS Code extension for managing and monitoring multiple AI coding agents, side by side, in VS Code's own terminals. A dedicated sidebar lists every agent terminal in one place, with a live status icon: 🔴 Needs you — blocked on a question or permission prompt 🟡 Working — thinking or running a tool 🟢 Done — finished its turn, idle Instead of alt-tabbing to check state, you only switch to the terminals that actually need you. Beyond status tracking, Airport also gives you: Duplicate Terminal with Another AI Agent — clone a terminal's workspace context but start a different agent in it, handy for comparing how Claude Code vs. Codex handles the same task Notifications the moment a terminal needs your input Session resume — reopen your workspace and pick up your previous terminals where you left off Airport hooks into VS Code's shell integration API to watch terminal output and infer agent status, rather than parsing agent-specific output formats. That's also why status detection needs a shell with shell integration support bash, zsh, fish, pwsh, cmd all work — without it, the terminal still runs fine, it just won't show a status light. It actually started life as a standalone Electron desktop app before I rebuilt it as a native VS Code extension. A separate window for terminal management stopped making sense once VS Code already had terminals I wanted to reuse directly. The name comes from the idea of an airport control tower controlling multiple terminals — multiple things happening at once, and you need a simple way to see what's happening, where, and what needs your attention right now. ✈️ Agents are taking off. Airport is the control tower. Free and open source: Marketplace : https://marketplace.visualstudio.com/items?itemName=VignaeshRamA.airport https://marketplace.visualstudio.com/items?itemName=VignaeshRamA.airport GitHub : https://github.com/vignaesh01/airport-vscode https://github.com/vignaesh01/airport-vscode I'd love to hear from developers already running multiple AI coding agents — how are you managing them today? Multiple terminals, separate VS Code windows, tmux, something else? This is still early, and I'm figuring out where this workflow goes. As agents get more capable, I think the developer experience shifts from "I am coding with an AI assistant" to "I am orchestrating multiple AI agents." That means we need better tools for managing the agents themselves — not just better agents. That's the problem I'm exploring with Airport. vscode ai aicoding codingagents claudecode codex developertools opensource