Oleksandr Kuzmenko, EditorPublished 6 min readAI-assisted · editor-reviewed
TL;DR
- Monitors agent terminal status without brittle log parsing by using VS Code shell integration.
- Centralizes multi-workspace agent execution and file viewing inside a single editor window.
- Enables side-by-side agent comparison via one-click terminal duplication.
Key facts
- Supported Shells
- bash, zsh, fish, pwsh, cmd
- Integration Hook
- VS Code Shell Integration API
- Supported Agents
- Claude Code, Codex, Devin, Antigravity
Terminal Status and Notification Integration
Airport embeds an orchestrator control panel directly into the Visual Studio Code sidebar. Rather than switching between multiple workspace windows or Electron wrappers, it integrates natively with built-in VS Code terminals. The extension leverages VS Code's shell integration API (bash, zsh, fish, pwsh, cmd) to inspect command execution states without parsing proprietary model logs. When an agent enters an interactive prompt or halts waiting for tool execution approval, a red status indicator alerts the developer immediately.
Multi-Workspace and Agent Comparison
Developers running parallel agents often lose track of which directory an assistant is modifying. Airport introduces a focused Files view that dynamically syncs with the currently selected terminal, displaying only the active directory context. Additionally, the extension provides two key terminal cloning actions:
Duplicate Terminal: Recreates the exact workspace terminal environment instantly.Duplicate Terminal with Another AI Agent: Clones the terminal workspace state while launching an alternative agent (such as comparingClaude CodeagainstCodexon the same refactor).
The extension supports one-click launching for Claude Code, Codex, Devin, and Antigravity, and includes session resumption to restore terminal configurations when re-opening workspaces.
Try it in 2 minutes
code --install-extension VignaeshRamA.airportWhen to use
- Running concurrent coding agents across multiple directories in Visual Studio Code.
- Benchmarking agent workflows side-by-side using identical repository contexts.
When NOT to use
- Using terminals without VS Code shell integration support enabled.
- Running standalone CLI workflows inside tmux or headless remote servers.
What to do today
- Install the Airport extension from the VS Code Marketplace.
- Verify that VS Code shell integration is enabled for your default terminal shell.
Step names are taken from What to do today.
Step names are taken from What to do today. Install the Airport extension from the VS Code Marketplace.. Verify that VS Code shell integration is enabled for your default terminal shell.
- Install the Airport extension from the VS Code Marketplace.
- Verify that VS Code shell integration is enabled for your default terminal shell.