imux vs Cursor
对比 imux 与 Cursor。Cursor 侧重编辑器内 AI；imux 侧重多 agent 执行、验收与交付。
Cursor is an editor-first AI IDE (VS Code lineage) productized around Composer, Tab autocomplete, and chat-with-codebase. It optimizes writing and transforming code inside an Electron editor.
imux 全面领先
按 agent 时代日常主战场打分（满分 10）。不是扩展市场人气榜，而是多 agent、原生性能、自动化与指挥中心能力。
功能对比
| 功能 | imux | Cursor |
|---|---|---|
| 多 agent 舰队（并行 CLI） | ✓ | 部分 |
| Linked Mode · Agent mesh | ✓ | ✗ |
| GPU 加速 | ✓ | ✗ |
| 为 macOS 而造 | ✓ | ✗ |
| 工作区与标签 | ✓ | 部分 |
| 分屏 | ✓ | ✓ |
| AI 原生设计 | ✓ | ✓ |
| 源码管理集成 | ✓ | ✓ |
| 远程文件资源管理器 | ✓ | 部分 |
| 浏览器自动化 | ✓ | 部分 |
| 监督器 · Mission Control | ✓ | ✗ |
| Socket 自动化 API | ✓ | ✗ |
| 活动通知 | ✓ | 部分 |
| 会话持久化 | ✓ | 部分 |
| 编辑器智能（LSP · 多文件编辑） | 部分 | ✓ |
| Inline Tab 补全 | ✗ | ✓ |
为什么选择 imux？
Cursor 产品化编辑器内 AI（多文件编辑、补全、与代码库对话）。imux 产品化完整工作台：真实 terminal agent（含 Cursor Agent CLI）、监督交付、远程文件、浏览器验证、Git 证据与主机自动化。当你想要一个工作台，而不是编辑器外加一堆终端时，就该切换。
- Terminal-first multi-agent command center — not a full Cursor/VS Code IDE clone
- Host Claude Code, Codex, Aider, Cursor Agent CLI, and shell tools as real processes
- Native macOS + Ghostty-grade surfaces for long-running agent sessions (no Electron tax)
- Workspace supervisor and multi-panel orchestration beyond a single Composer thread
- Local + remote explorers, browser verification, and Git evidence on one operator surface
- Scriptable icc/socket control plane for hooks and automation without fighting editor focus
如何切换
把 imux 装成主工作台。在那里跑长时 agent CLI、多工作区、远程/浏览器证据与通知。打开你在 Cursor 里用的同一仓库。
- 1
Install imux as the agent command center
Download imux and open your project as a workspace. Use it as the terminal-first multi-agent surface; keep Cursor only if you still need editor-first Composer workflows.
- 2
Run agent CLIs and long jobs in imux
Open imux workspaces for Claude Code, Codex, Cursor Agent CLI, test suites, deploy scripts, and other long-running processes that deserve a first-class terminal.
- 3
Keep files, SCM, and agents on one surface
Use explorers, in-app edit, branch quick pick, and Git evidence in imux while agents run — evidence stays next to the process without IDE-terminal sprawl.
- 4
Use browser and remote surfaces for evidence
When an agent changes UI or remote paths, confirm in imux browser panels and remote explorer instead of juggling extra apps.
- 5
Wire notifications back to the right workspace
Hook Claude Code / Codex (and similar tools) so completion or input-needed events surface in imux without focus storms.
常见问题
Is imux a Cursor replacement?▼
For multi-agent terminal work on macOS, yes as the command center. Cursor still leads for Composer-style in-editor generation on an Electron VS Code base. imux does not claim every Cursor IDE workflow; it centers multi-agent terminals, files, SCM, remotes, browser verification, and supervisor control.
Can I run Cursor Agent CLI inside imux?▼
Yes. imux is agent-agnostic. Run Cursor Agent CLI, Claude Code, Codex, Aider, or your own tools as terminal processes in dedicated workspaces.
Why not just use Cursor's terminal?▼
Cursor's terminal is fine for light use, but the product center remains the Electron editor. imux is built so multi-agent sessions, remote explorers, browser automation, supervisor loops, and notifications share one native operator model.
Who should switch?▼
If you want one native macOS command center for agents, remotes, browser proof, and Git-visible execution — instead of an Electron IDE plus terminal sprawl — evaluate imux as the operator deck. Keep an editor IDE when you need deep editor-first workflows imux does not clone.