- Removed in 2.0Dispatch: jobs work in your own checkout by default and leave edits uncommitted — no surprise branches or commits. Ask for a branch (or run a second job alongside) and it takes a worktree; a dirty tree asks first; the review subtracts what was already yours. “Commit it” commits only the job's files.
configure→placement: worktreerestores the old default. - Removed in 2.0Dispatch:
configureaccepts standing preferences (preference: "standup: terse") applied to standup presentation; unknown setting keys are kept as preferences loudly instead of vanishing. - Removed in 2.0Hub:
prism-hub statuslineprints live job state for Claude Code's statusLine footer (--setupprints the settings block). The jobs board gains a per-job Console with subagent work indented;job_logsmarks subagent lines. - Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.15: workspace ….@repo-prism/dispatch@1.1.15,@repo-prism/dispatch-hub@1.1.15, and@repo-prism/mcp-server@1.1.15.
Changelog
What’s new.
Older releases, page 2 of 4.
Legacy
1.x releases
- Removed in 2.0Dispatch: jobs run on the host's own agent CLI — a Cursor agent in Cursor, a Claude Code agent (
claude -p) in Claude Code.configure→workerBackendoverrides;PRISM_WORKERworks too. - Removed in 2.0Dispatch: Claude workers reuse the machine's existing Claude Code sign-in.
prism initchecks theclaudeCLI and says what to run — never asks for a key. - Removed in 2.0Dispatch: same contract on both backends: own worktree, no shell, no MCP, console (
job_logs), stall detection, Prism-side commit + checks, review before land. Resume continues the Claude session. - Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.14: workspace ….@repo-prism/dispatch@1.1.14,@repo-prism/dispatch-hub@1.1.14, and@repo-prism/mcp-server@1.1.14.
- Removed in 2.0Dispatch: each job keeps an append-only console. Ask “what is it doing” / “show me the logs” (
job_logs). - Removed in 2.0Dispatch: a live worker that goes quiet is stalled — chat says no activity for N minutes and offers resume or cancel.
- Removed in 2.0Dispatch: finishing is not landing. Prism still commits the job branch and runs checks; a job that changed files returns ready for your review. Nothing is merged or pushed for you.
- Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.13: workspace ….@repo-prism/dispatch@1.1.13,@repo-prism/dispatch-hub@1.1.13, and@repo-prism/mcp-server@1.1.13.
- Removed in 2.0Dispatch: a local jobs board watches every registered repo, lists parallel teammates, and fires a desktop notification (plus a Cursor toast) when one finishes. Open Prism: Open Agent Dashboard or
http://127.0.0.1:17330/.PRISM_HUB=0opts out. - Removed in 2.0Dispatch: job workers trust OS certificate stores so they can reach Cursor behind HTTPS interception. A failed network call is spoken as a network error, not the SDK's "Network request failed".
- Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.12: workspace ….@repo-prism/dispatch@1.1.12,@repo-prism/dispatch-hub@1.1.12, and@repo-prism/mcp-server@1.1.12.
- Removed in 2.0Dispatch: a local jobs board watches every registered repo, lists parallel teammates, and fires a desktop notification (plus a Cursor toast) when one finishes. Open Prism: Open Agent Dashboard or
http://127.0.0.1:17330/.PRISM_HUB=0opts out. - Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.11: workspace ….@repo-prism/dispatch@1.1.11,@repo-prism/dispatch-hub@1.1.11, and@repo-prism/mcp-server@1.1.11.
- Removed in 2.0MCP: a request to change the repo (
fix that issue,make this work like that) starts a teammate without a ticket, PRD, or the words “start working on”. The agent writes the PRD itself. “Do it now” / “right here” keeps the edit inline. Combined with 1.1.9: finished jobs still commit, run typecheck/test, and may use in-process subagents. - Removed in 2.0Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.10: workspace ….@repo-prism/dispatch@1.1.10and@repo-prism/mcp-server@1.1.10.
- Removed in 2.0Dispatch: when a teammate stops, Prism commits the job branch and runs typecheck/test. Empty work says “produced no reviewable change”; summaries cannot cite files that were never written. Write-ups under
.prism/dispatch/notes/ship with the commit. - Removed in 2.0Dispatch: in-process subagents (
task) are on; host fan-out stays off. Jobs are admitted on free memory (defaultmaxJobs4). Orphan worktrees with no unmerged commits are pruned. - Removed in 2.0MCP: describing work is enough to start a job — no “start working on” phrase. The agent announces what it will start first. Local checkouts no longer hop to npm. Keep
@latest; hop on the next Cursor/MCP start. Logs:prism-mcp 1.1.9: workspace ….@repo-prism/dispatch@1.1.9and@repo-prism/mcp-server@1.1.9.
- Removed in 2.0MCP / Dispatch: ignore Cursor’s
Library/Containerssandbox as a workspace.start_job/start_my_dayacceptworkspace(the folder the agent already has open). Recommended mcp.json setsCURSOR_WORKSPACEto${workspaceFolder}— not a path you type. - Updates: at startup the server checks npm and hops to a newer
@repo-prism/mcp-serverwhennpx @latestis stale. Keep@latestin mcp.json. A running session cannot swap mid-chat; the next Cursor/MCP start picks up the publish.
- Removed in 2.0MCP / Dispatch: starting a job from chat no longer fails with
fatal: not a git repositorywhen the MCP process was launched from the editor user folder. After initialize, Prism asks the client for MCP roots and rebinds Intelligence + Dispatch to the open folder. Git child processes ignore inheritedGIT_DIR/GIT_WORK_TREE. Startup log:prism-mcp 1.1.6: workspace … (from mcp roots). Pin@1.1.6or clear~/.npm/_npxafter install.
- Removed in 2.0Dispatch: start-my-day renews Google Calendar (and other vendor) access tokens through Prism Auth
/oauth/refreshso connect lasts past the one-hour Google token. MCP logs printprism-mcp 1.1.5on startup.npx @latestcan still serve a cached tree; pin the new version or clear~/.npm/_npxafter a publish.