1.12.0 — Agent-native: Envelope, Prepare, Guard

Skills history and Pulse meter

Published skills have version history (view, revert, delete, compare). Edit can Update Skill with teammate instructions.

ConsoleDispatchMCP

Global jobs, Wake, and Spectrum

Jobs live under ~/.prism (ADR-0054). Legacy {repo}/.prism/dispatch/jobs.json files are migrated. The dashboard no longer drops jobs whose checkout left the registry.

ConsoleSpectrumDispatch

Skills, trees, and Impact

Skills is a first-class view: grouped Prism skills live in ~/.prism, not the repo, and Generate writes one from a brief.

ConsoleDispatchIntelligence

Job graph, sleep and wake

Focus draws an append-only job graph (Accepted → Queued → Working). Pause then resume adds a new Working node; the rail never rewinds.

ConsoleMCPDispatch

Dispatch stays a teammate

Dispatch: a worktree job started on a PR branch now carries that branch's commits. When the branch exists only on a remote (origin/<branch>), Prism bases the worktree on the remote ref instead of your current HEAD, so a review teammate sees the PR and no longer falls back to editing inline.

DispatchMCP

MCP start

MCP: npx @repo-prism/mcp-server starts again. 1.8.0 imported

MCP

Fleet Console

Pulse, Board, and List are three views of the same jobs canvas. New job is a verb on the board, not only a sentence in chat.

ConsoleWebsiteMCP

Shippable product

Dispatch is a teammate in the same prism server: queue a change from chat (start_job), watch it in the local Console, and keep connectors in the host window. Prism does not run OAuth and does not hold vendor tokens.

MCPCLIIDE

A job survives an older agent CLI

Dispatch: an agent CLI that rejects an optional flag no longer costs you the job. A Claude Code worker died at launch on unknown option '--forward-subagent-text' — a flag that only enriches the console with subagent text — before touching a file. Optional flags are now dropped on one retry, and the console says which one. Flags that carry the sandbox (--tools, --disallowedTools, --bare) are deliberately not droppable: those still fail, but the message names the flag and the upgrade instead of printing a launcher dump.

Dispatch

Checkout-first jobs, Claude Code footer, configure anything

Dispatch: 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: worktree restores the old default.

Dispatch

Claude Code workers

Dispatch: jobs run on the host's own agent CLI — a Cursor agent in Cursor, a Claude Code agent (claude -p) in Claude Code. configure → workerBackend overrides; PRISM_WORKER works too.

Dispatch

Job console, stall detection, review before land

Dispatch: each job keeps an append-only console. Ask “what is it doing” / “show me the logs” (job_logs).

Dispatch

Agent Dashboard Hub + worker OS CAs

Dispatch: 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=0 opts out.

Dispatch

Agent Dashboard Hub

Dispatch: 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=0 opts out.

Dispatch

Dispatch every code change by default

MCP: 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.

DispatchMCP

Durable Dispatch jobs (commit, checks, subagents)

Dispatch: 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.

DispatchMCP

Open-folder jobs without reloading after every publish

MCP / Dispatch: ignore Cursor’s Library/Containers sandbox as a workspace. start_job / start_my_day accept workspace (the folder the agent already has open). Recommended mcp.json sets CURSOR_WORKSPACE to ${workspaceFolder} — not a path you type.

MCP

Auto-bind Dispatch to the open chat folder

MCP / Dispatch: starting a job from chat no longer fails with fatal: not a git repository when 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 inherited GIT_DIR / GIT_WORK_TREE. Startup log: prism-mcp 1.1.6: workspace … (from mcp roots). Pin @1.1.6 or clear ~/.npm/_npx after install.

Intelligence

Calendar token refresh

Dispatch: start-my-day renews Google Calendar (and other vendor) access tokens through Prism Auth /oauth/refresh so connect lasts past the one-hour Google token. MCP logs print prism-mcp 1.1.5 on startup. npx @latest can still serve a cached tree; pin the new version or clear ~/.npm/_npx after a publish.

Dispatch

Standup start-my-day

Dispatch: start-my-day is a standup: greeting, yesterday (git + finished jobs + completed Linear), then open items on Linear/GitHub/Slack/Calendar. Linear OAuth uses a Bearer token so assigned issues actually load after connect.

Dispatch

Corporate TLS for connect

MCP: trust the OS certificate store at startup so connect Linear (and other Prism Auth grants) work behind corporate HTTPS inspection. Cursor reload no longer depends on NODE_USE_SYSTEM_CA in mcp.json. If the probe still fails, the error now includes the TLS/HTTP reason instead of a bare “unreachable.”

MCP

Connect on Cursor

MCP: skip the extra Continue elicitation on Cursor. The host advertised form elicitation then auto-returned cancel, which aborted Linear/Slack/Calendar connect before Authenticate appeared. Connect goes straight to the native Authenticate control.

MCP

Dispatch MCP

Dispatch: chat-native teammate on the same prism MCP server — start_my_day, jobs on local Cursor SDK workers, remember, configure, loopback OAuth (GitHub user, Linear, Jira, Slack mentions + tracked channels, Notion, Google Calendar). Connect goes through Prism Auth (auth.prismhq.in); Cursor shows a native Authenticate control and step list, Claude opens the auth page. Users never paste client ids. Tokens stay in the OS keychain. Local job workers sign in once via init / first start_job (Cursor.auth.login); do not put CURSOR_API_KEY in mcp.json. Jobs use a ticket or title slug (audit-issues) as the canonical id — chat never speaks job-<hex>. Each worker runs in its own process and git worktree (default one at a time; no Prism MCP on the job agent; worktrees symlink the host node_modules). Say where are we for live status and the result when a teammate finishes or fails. Google’s “hasn’t verified this app” screen for Calendar is expected until Prism Auth finishes sensitive-scope verification — click Advanced, then continue.

DispatchIntelligenceMCP

Completion program (M-053–M-063)

Proof: agent-orientation benchmark harness (bun run bench:orientation) and published methodology at /benchmarks.

Intelligence

MCP: first-index progress via MCP logging + stderr (Indexing… phase (n/total)).

CLIMCP

MCP: server instructions teach agents to call Prism from plain-language

MCP

MCP: fix initialize instructions tool name (blast_radius, not prism_blast_radius).

MCP: resolve workspace via git root (same as CLI); docs drop required --workspace.

npm packages under @repo-prism/* (cli, mcp-server, core, …)

VS Code and Cursor — the full UI in a webview panel.

What you can do with itWhat it does not do