What's new in 1.2

1.2 widens Kairoku from "an app with an MCP endpoint" to a workspace an agent — or a person, through the same conversation — can run end to end, plus one place to connect the outside tools every agent on it can then use.

The MCP tool catalog grows to the full lifecycle

The registry behind /api/mcp now covers project creation and settings, documents and folders, the plan, releases, dispatch and execution, and the ship/approval flow — not just the read-and-report core it shipped with. A tool that changes something a person should decide — deleting, marking Done, shipping, publishing, approving a release for execution — files an approval instead of running, and a token's kairoku:read / write / operate / admin scopes say which of the rest it can reach. See MCP.

An in-app operator

Mission Control's Details panel now has an Operator tab for an owner-scoped workspace: a conversation that calls the same registry, multi-step, with the caller's own authority. It pauses on anything approval-class exactly like an agent would, and a workspace owner can additionally require a person's sign-off before it dispatches work at all. See Operator and Mission Control.

A Connections Hub

Settings → Connections adds a second kind of row beside the GitHub/GitLab/Atlassian integrations it already had: remote MCP services — Atlassian's Rovo MCP, Linear, Sentry, context7, and any custom MCP server by URL — connected once per workspace. From then on, every machine and every dispatched run sees that connector's tools, named <connector>__<tool>, with no sign-in of their own; refreshing an expiring token is centralized, and revoking turns the next call into a tool error asking to reconnect. See Connections.

The plugin's operator skill and agent

The plugin ships a new operator skill (/kairoku:operator) and a matching subagent that drive a project through this same tool set from a terminal: create it, link its repo, plan it, dispatch the work, and ask a person to ship it. See Plugin.