Expand description
The local socket any agent can use to reach a running Cellix. One line in, one line
out: comments, take (comments, then clear them), threads, take-threads (those an
agent hasn’t seen), reply <id> <author> then a tab and the text, or open <path>.
It’s a Unix socket where there are those, and elsewhere a port on 127.0.0.1 behind a token,
as loopback describes. Agents call cellix, so only this crate tells the two apart.
Modules§
- hook
cellix hook <kind>: what Claude Code’s hooks call. Nothing here may disturb the agent, so with no Cellix running every kind quietly does nothing but keep its checkpoints.- ide
- The server Claude Code connects to when it treats Cellix as its IDE: MCP over a local WebSocket, announced by a lock file. Claude Code hasn’t published this protocol, so it follows what its VS Code extension does.
Structs§
- Agent
Event - What an agent is doing, as its hooks report it.
- Server
- The running server. Dropping it removes the socket file, and the plans kept beside it.
- TestRun
- A test command an agent ran.
Enums§
- Agent
State - Decision
- The reviewer’s answer to a plan.
- Request
- Requests that need the app itself, drained on its next tick.
- Transport
- How agents reach a Cellix.
Functions§
- request
- Sends one request to the Cellix serving
root. - request_
with request, over the transport given.- socket_
path - One socket per workspace, in a directory only this user can enter.
- start
- Binds the workspace socket. Fails if another Cellix already serves this workspace.
- start_
with start, over the transport given.
Type Aliases§
- Shared
Comments - Comments shared between the app and the socket thread.