imux vs VS Code
对比 imux 4.1.20 与 VS Code。imux 是原生 macOS 上的终端优先多 agent 指挥中心：多 agent 终端、文件、SCM、远程、浏览器自动化与监督控制——不是完整 VS Code 扩展生态克隆。
VS Code is the default editor-first Electron IDE for many teams. Its integrated terminal is a convenience surface next to the editor — solid for quick commands, limited as a multi-agent execution deck.
imux 全面领先
按 agent 时代日常主战场打分（满分 10）。不是扩展市场人气榜，而是多 agent、原生性能、自动化与指挥中心能力。
功能对比
| 功能 | imux | Vscode Terminal |
|---|---|---|
| 多 agent 舰队（并行 CLI） | ✓ | 部分 |
| Linked Mode · Agent mesh | ✓ | ✗ |
| GPU 加速 | ✓ | ✗ |
| 原生 macOS（非 Electron） | ✓ | ✗ |
| 工作区与标签 | ✓ | 部分 |
| 分屏面板 | ✓ | ✓ |
| AI 原生设计 | ✓ | 部分 |
| 源码管理集成 | ✓ | ✓ |
| 远程文件资源管理器 | ✓ | 部分 |
| 浏览器自动化 | ✓ | 部分 |
| 监督器 · Mission Control | ✓ | ✗ |
| Socket 自动化 API | ✓ | 部分 |
| 活动通知 | ✓ | 部分 |
| 会话持久化 | ✓ | 部分 |
| 编辑器智能（LSP · 多文件编辑） | 部分 | ✓ |
| 扩展市场 | ✗ | ✓ |
为什么选择 imux？
VS Code 是成熟的 Electron IDE（LSP、调试、扩展、Remote-SSH、SCM），但集成终端是附属。imux 是面向 AI 优先 macOS 工作的终端优先指挥中心：Ghostty 级终端、多 agent 工作区、浏览器验证、远程资源管理器、通知与可脚本控制面——原生、更密，承接 agent 时代执行，而不是完整 IDE 克隆。
- Terminal-first multi-agent command center for AI-era macOS work — not an accessory terminal under an editor
- Ghostty-grade GPU terminal as a first-class surface (not a secondary panel under the editor)
- Workspace-first layout for multiple long-running agents and processes with files and Git evidence
- Built-in remote SSH explorer and browser surfaces on the same operator deck
- Socket/`icc` automation with a stable window → workspace → pane → surface model
- Native Swift/AppKit performance without Electron shell tax on multi-agent sessions
如何切换
把 imux 装成日常主战场。把 agent、长时任务、远程/浏览器证据与 Git 可见执行收进一个工作台。打开你在 VS Code 里用的同一仓库。
- 1
Install imux as the multi-agent command center
Download imux and open your project as a workspace. Put agent and long-running terminal work here; keep VS Code only for editor-first workflows you still need.
- 2
Move terminals and agents into imux
Shift builds, test suites, dev servers, and agent CLIs out of VS Code's integrated terminal into imux workspaces for visibility and notifications.
- 3
Keep agents and evidence on one surface
Use files, branch quick pick, SCM, Agent Chat, browser, and remotes in imux. Agents and Git evidence stay on the same surface while processes run.
- 4
Use remote and browser surfaces as first-class tools
Use imux remote explorer and browser panels for operator workflows that are awkward as pure editor Remote-SSH or external Chrome tabs.
- 5
Script the control plane
Automate notify, browser open, and workspace setup with the icc CLI/socket API while you stay inside the imux workbench.
常见问题
Should I replace VS Code with imux?▼
Replace the multi-agent terminal + evidence loop with imux if that is your bottleneck. imux is a terminal-first AI command center — not a claim to clone every VS Code extension, language service, or editor workflow. Terminals, files, SCM, remotes, browser automation, and supervisor control are first-class surfaces.
Doesn't VS Code already have Remote-SSH, Git, and Copilot?▼
Those are real strengths of the VS Code ecosystem. imux re-centers the product: terminal agents, long-running processes, browser evidence, remote files, and Git-visible ops are first-class workspace surfaces — with native performance instead of Electron shell tax.
Can I open the same project I used in VS Code?▼
Yes. Open the same git repository in imux. Your working tree, branches, and Git status transfer with the repo.
Does imux have an editor like VS Code?▼
imux includes in-app file viewing and editing for the operator loop, plus Agent Chat and terminal agents for larger changes. It is not positioned as a full VS Code-grade editor with the same extension ecosystem — the product center is the multi-agent command center.