War Room v0.17+ exposes an "Open in editor" button in the channel header (added via PR #1). The current implementation only detects editor CLIs on macOS — it looks for bundled CLI paths under /Applications/. On Linux we should detect the same editors via the standard ways they install:
- VS Code:
code on PATH (snap, deb, AppImage, manual)
- Cursor:
cursor on PATH or ~/.local/bin/cursor
- Windsurf:
windsurf on PATH
- Zed:
zed on PATH
- Antigravity: confirm install path
File to extend: app/api/fs/open-editor/route.ts (the GET endpoint that returns available editors, and the POST handler that spawns the chosen one).
Acceptance: on Linux, opening the editor menu shows whichever of the above are installed; clicking one opens the project path in that editor.
War Room v0.17+ exposes an "Open in editor" button in the channel header (added via PR #1). The current implementation only detects editor CLIs on macOS — it looks for bundled CLI paths under
/Applications/. On Linux we should detect the same editors via the standard ways they install:codeon PATH (snap, deb, AppImage, manual)cursoron PATH or~/.local/bin/cursorwindsurfon PATHzedon PATHFile to extend:
app/api/fs/open-editor/route.ts(the GET endpoint that returns available editors, and the POST handler that spawns the chosen one).Acceptance: on Linux, opening the editor menu shows whichever of the above are installed; clicking one opens the project path in that editor.