jpmschweitzerandClaude
50d0143afc
`bin/clide` gains the single-word shortcuts CLAUDE.md's tier 2 spells out: open, active, insert, replace-selection, save. Each maps the flat positional argv into the canonical editor.* IPC shape. Insert and replace-selection accept a lone `-` to read text from stdin so piping works (`pbpaste | clide replace-selection -`). `clide tail --events` is the subscribe mode. Same socket as the request side; the client just reads + filters events. --filter SUBSYSTEM or SUBSYSTEM:ID narrows the stream. Exits cleanly on SIGINT. defaultSocketPath() now respects CLIDE_SOCKET_PATH before XDG — the existing override callers always had this up their sleeve (via XDG_RUNTIME_DIR manipulation) but making it explicit unblocks parallel test runs where each test needs its own daemon socket. The new end-to-end CLI suite does exactly that: 5 tests spin up real daemon subprocesses and exercise the shortcut surface through the live IPC stack. 74 core tests pass; round-trip verified by hand (open README.md → insert → tail --events captures editor.opened / edited / selection-changed / saved). Co-Authored-By: Claude <noreply@anthropic.com>
clide
A Flutter desktop IDE for Claude Code. Markdown-first content, pql-powered queries, canvas and graph surfaces, a Go sidecar handling PTYs / subprocesses / git / pql. Claude drives the UI through a clide CLI.
Currently pre-v2.0, scaffolding. The north-star design lives in docs/initial-plan.md; architectural decisions are captured in docs/ADRs/. The Python Textual v1.2.0 implementation is archived under legacy/ for reference.
Three surfaces, one tool
app/— Flutter desktop application (Linux / macOS; Windows is a stretch).sidecar/— Go sidecar/CLI, single binary with two modes:clide <subcommand>(one-shot for Claude) andclide --daemon(long-running sidecar for the app). Owns PTYs, subprocesses, file watchers, git, pql invocations.pql— external supporter tool. clide wraps it for every query surface; never re-implements it.
Why the rebuild?
The Python Textual implementation (legacy/) proved the pane model but capped at terminal-only rendering. A short-lived experiment (claudian, April 2026) explored an Obsidian-plugin approach and was abandoned because Obsidian is Electron, and the user's history with terminal-in-Electron ruled that host out.
Flutter desktop resolves both constraints: native Skia rendering avoids Electron's failure modes, xterm.dart gives us a solid terminal surface, and the pane model can be rebuilt natively. The Obsidian ideas worth keeping (canvas, graph) fold in; everything else (vault concept, inline query tables, plugin ecosystem inheritance) doesn't.
Status
No build yet beyond the repo scaffold. Tier 0 acceptance: sidecar daemon runs, Flutter app connects, empty IDE shell appears with placeholders.
License
MIT. See LICENSE.