@repo-prism/dispatch
v1.10.0
Published
Prism Dispatch — jobs, memory, drivers, and start-my-day briefings for agents
Readme
@repo-prism/dispatch
Prism Dispatch: jobs, memories, host-connector discovery, and start-my-day briefings.
The MCP server (@repo-prism/mcp-server) is the only surface that calls this
package. @repo-prism/core must not import it. Intelligence analysis stays on
Core; Dispatch is a second façade for teammate workflow.
State lives under .prism/dispatch/ (gitignored). This package makes no
network calls and stores no third-party credentials (ADR-0049). Connectors
belong to the agent window: host-connectors.ts reads Cursor and Claude Code
plugin and MCP manifests to learn which exist — names and capabilities only,
never tokens — and fill-contract.ts turns that into the sections
start_my_day asks the host agent to fill with its own tools.
Workers run in a detached child process per job. Placement is checkout-first
(ADR-0045): by default the worker edits the user's own checkout and leaves
changes uncommitted ("commit it" stages only the job's files); an isolated
worktree + job branch + commit-on-finish is the explicit or
parallel-collision path. The backend matches the host (ADR-0044): a Cursor
SDK agent in Cursor (browser login via init, ADR-0038), or the claude CLI
in Claude Code (the machine's existing sign-in — detection, never a pasted
key). Live activity and finished/failed results are stored under
.prism/dispatch/runs/ and spoken through list_jobs / start-my-day
(ADR-0040). Default parallel cap is one job. Job agents do not attach Prism
MCP; Prism worktrees symlink the host node_modules (ADR-0041).
