scrybe-rpc

JSON-RPC 2.0 wire protocol shared between the Scrybe CLI and the running Scrybe desktop app. Defines the request/response/error envelopes and method names; both sides import this crate so the protocol has a single source of truth.

What it does

When the desktop app is running, the CLI talks to it instead of opening files directly. That makes commands like scrybe open path/to/note.md surface in the existing GUI session as a new tab. The conversation between the two processes goes over a Unix-domain socket (named pipe on Windows) using newline-delimited JSON-RPC 2.0.

This crate is just the types and codec. It deliberately has no I/O — the client (scrybe-cli) and the server (scrybe-app) each implement their own transport on top.

Methods (Phase 1)

Method	Effect
`open(path)`	Open a tab, or force-refresh if the file is already open
`save(path)`	Save an open tab's buffer to disk; no-op if not open
`close(path)`	Close a tab; no-op if not open
`quit({ force })`	Quit the app; `force=true` skips the dirty-buffer prompt

Framing

Newline-delimited JSON. One request per line, one response per line. Multiple requests on a single connection are processed FIFO.

Socket location

~/.scrybe/sock by default. Override with the SCRYBE_SOCK environment variable.

License