JSON-RPC methods & notifications
Generated from crates/versionx-daemon/src/protocol.rs.
The versiond daemon speaks JSON-RPC 2.0 over a per-user local socket (Unix Domain Socket on Linux/macOS; named pipe on Windows). Messages are length-prefixed (4-byte BE) with a maximum frame size of 2 MiB. See JSON-RPC daemon for the transport overview and framing details.
Methods
| Constant | Method name | Description |
|---|---|---|
BUMP_PROPOSE | bump.propose | |
PING | ping | |
SERVER_INFO | server.info | |
SHUTDOWN | server.shutdown | |
SUBSCRIBE | subscribe | |
UNSUBSCRIBE | unsubscribe | |
WORKSPACE_GRAPH | workspace.graph | |
WORKSPACE_LIST | workspace.list | |
WORKSPACE_STATUS | workspace.status |
Notifications
| Constant | Notification name | Description |
|---|---|---|
LOG | log | |
PROGRESS | progress | |
SHUTTING_DOWN | server.shutting_down | |
WORKSPACE_CHANGED | workspace.changed |
Error codes
Standard JSON-RPC 2.0 error codes (-32700 parse error, -32600 invalid request, -32601 method not found, -32602 invalid params, -32603 internal error) apply. Application-level codes are reserved in the -32000..=-32099 range. Current in-use codes:
| Code | Meaning |
|---|---|
-32001 | Shutting down. |
-32002 | Busy. |
-32003 | Workspace failed. |
See also
- JSON-RPC daemon — transport and framing detail.
- HTTP API — the same surface over HTTP.
- MCP server overview — the agent-facing layer on top of the daemon.