S17: spike before editors in the swarm (about a day) #41

New issue

Open

opened 2026-10-02 05:20:26 +00:00 by jhgaylor · 0 comments

jhgaylor commented

2026-10-02 05:20:26 +00:00

Owner

Depends on: #36 (only its connection and preview numbers; it can start now)
Blocks: #42, #43

Swarm track: editors. Zoom into the swarm and land in someone's editor: a VS Code started on the pane's machine (M27), or the editor they already have open, followed from the browser (M28). This spike answers what those need first.

Claude Code's IDE protocol:
- how Claude Code finds an IDE (lockfiles in ~/.claude/ide/), how it connects (MCP over a WebSocket, and its auth token), and which tools it calls (openDiff, diagnostics, selection, open editors);
- can illogicald register as an IDE itself, so that Claude Code's diff approvals and questions arrive as attention reasons (#38) with no editor open?
- what happens when a real IDE and illogicald are registered at once.
Extensions on remote machines: with VS Code and Cursor over Remote-SSH and in dev containers, does a workspace extension run on the remote host and reach the local illogicald socket there? Check the same for Zed's remote development and for nvim on the machine.
What an editor can report cheaply: active file, cursor and selection, visible range, diagnostics counts, debugger state and unsaved buffers, from the VS Code API and from nvim's autocmds.
- Measure event rates while typing, and the debouncing needed to stay under M23's summary budget.
openvscode-server or code-server:
- licence and extension marketplace (Open VSX) for each;
- memory per instance and cold start on geek and in a wisp sandbox;
- does it run inside a browser block (M6a) with no auth of its own, behind the daemon's access checks?
Follow-mode rendering: Monaco in the page (bundle size, theming next to the terminal), or a lighter read-only code view?

Output: a short write-up in spikes/s17-editors/, with a go/no-go on illogicald as a Claude Code IDE, which server goes in M27, and the editor event schema for M28.

**Depends on:** #36 (only its connection and preview numbers; it can start now) **Blocks:** #42, #43 *Swarm track: editors. Zoom into the swarm and land in someone's editor: a VS Code started on the pane's machine (M27), or the editor they already have open, followed from the browser (M28). This spike answers what those need first.* -------- - **Claude Code's IDE protocol:** - how Claude Code finds an IDE (lockfiles in `~/.claude/ide/`), how it connects (MCP over a WebSocket, and its auth token), and which tools it calls (`openDiff`, diagnostics, selection, open editors); - can illogicald register as an IDE itself, so that Claude Code's diff approvals and questions arrive as attention reasons (#38) with no editor open? - what happens when a real IDE and illogicald are registered at once. - **Extensions on remote machines:** with VS Code and Cursor over Remote-SSH and in dev containers, does a workspace extension run on the remote host and reach the local `illogicald` socket there? Check the same for Zed's remote development and for nvim on the machine. - **What an editor can report cheaply:** active file, cursor and selection, visible range, diagnostics counts, debugger state and unsaved buffers, from the VS Code API and from nvim's autocmds. - Measure event rates while typing, and the debouncing needed to stay under M23's summary budget. - **openvscode-server or code-server:** - licence and extension marketplace (Open VSX) for each; - memory per instance and cold start on geek and in a wisp sandbox; - does it run inside a browser block (M6a) with no auth of its own, behind the daemon's access checks? - **Follow-mode rendering:** Monaco in the page (bundle size, theming next to the terminal), or a lighter read-only code view? **Output:** a short write-up in `spikes/s17-editors/`, with a go/no-go on illogicald as a Claude Code IDE, which server goes in M27, and the editor event schema for M28.

jhgaylor added the

spike

swarm

labels

2026-10-02 05:20:26 +00:00

jhgaylor referenced this issue

2026-10-02 05:20:27 +00:00

M27: VS Code blocks (an editor on any pane's machine) #42

jhgaylor referenced this issue

2026-10-02 05:20:27 +00:00

M28: your editor in the swarm (presence, follow mode, IDE attention) #43