Installation

Codex release candidate

Add the private marketplace and install the candidate:

1. Sign in to Integrity in the browser window that opens.
2. Choose Create new for a first connection, or Reconnect to select an existing connection group you own and intentionally want to join. Confirm the displayed target and give the connection a name.
3. Approve access, then tell your agent which workspace to use.

You can rename the connection later in Settings → Coding agents.

Separately registered clients that choose Create new have independent connection groups. Rename or revoke a group from Settings → Coding agents. Revocation disconnects all clients deliberately reconnected to that group, while other independent groups remain active. Leases and receipts keep their existing owners. After cancellation, expiry, or a stale target, start a fresh login and review the choices again.

A timed-out or interrupted change tells your agent whether it was not saved, not started, or has an unknown saved state. If the state is unknown, the change may already have been saved. Ask your agent to follow the error's recovery guidance. When the tool supports safe replay, retrying the unchanged original request avoids applying the change twice. For other operations, check the saved state before retrying. Keep recovery separate from a new edit.

MCP server address:

Cursor

Use one production Integrity MCP connection in Cursor. The local plugin setup below provides the Integrity skills and the connection together. It requires access to the production release candidate installed in the Codex section above; it is a local installation, not a Cursor Marketplace listing.

Install the local plugin

1. Locate your installed production integrity@irsiks package. With the default Codex home, it is under ~/.codex/plugins/cache/irsiks/integrity/<version>. On Windows, ~ is your user profile folder. Use the installed production version, not the integrity-dev package.
2. Create ~/.cursor/plugins/local/integrity. Copy the package's skills, references, lib, scripts, hooks, assets, and .cursor-plugin folders into it. Leave the original package unchanged. Codex SessionStart cleanup hooks stay in hooks/codex-hooks.json and are not used by Cursor. Cursor loads hooks/cursor-hooks.json through .cursor-plugin/plugin.json. Authentication is completed separately in Cursor.
3. If you copied .cursor-plugin from the package, keep that plugin.json. Otherwise create .cursor-plugin/plugin.json with the following contents. Set version to the production package version you copied.

{
  "name": "integrity",
  "version": "<installed-production-version>",
  "description": "Integrity skills and production MCP connection",
  "author": { "name": "IRSIKS Integrity" },
  "skills": "./skills/",
  "mcpServers": "./mcp.json",
  "hooks": "./hooks/cursor-hooks.json",
  "logo": "./assets/irsiks.svg"
}

4. Create mcp.json at the plugin root, beside the skills folder:

{
  "mcpServers": {
    "integrity": {
      "url": "https://integrity.irsiks.com/api/integrity/mcp"
    }
  }
}

5. Back up your existing Cursor MCP configuration. Remove a duplicate Integrity entry pointing to the same production address from ~/.cursor/mcp.json or the project's .cursor/mcp.json, preserving other servers. Keep the plugin as the single source of this connection. Remove or disable integrity-dev unless you are deliberately testing the development environment.
6. Run Developer: Reload Window from Cursor's Command Palette, or restart Cursor. Open Customize → Plugins and confirm Integrity is present. Under Customize → MCPs, enable the plugin's Integrity connection and authenticate if prompted. Complete Integrity's browser consent flow and select your workspace in the agent conversation.

If your organization restricts local plugins, an administrator must allow local plugin imports. See Cursor's local plugin instructions. When updating this local copy, use the new production package's matching folders and version, then reload Cursor and start a fresh chat.

Verify the connection

Start a fresh Cursor chat and ask:

A connected indicator alone does not prove that tools loaded. Confirm that Cursor shows available Integrity tools and that the agent completes a real read in your selected workspace. An empty result can be valid; an unavailable tool or authorization error means the check has not passed.

If Cursor shows 0 tools

Check that the plugin files are in the folder shown above and that only one enabled source defines the production connection. Reload the window, authenticate if prompted, and repeat the read check in a fresh chat. Reinstalling a plugin without reloading may leave the previous tool catalogue in use.

If tools remain unavailable, open Cursor's Output panel and select MCP Logs. Capture the error from the latest connection attempt, including any tools/list or schema-validation failure, without sharing credentials. A successful connection followed by an empty catalogue needs separate investigation; duplicate entries are not proof of the cause. See Cursor's MCP troubleshooting guide.

Claude Code

Claude Code loads the same package as a local plugin directory. It needs a package that contains .claude-plugin/plugin.json; earlier packages have no Claude Code manifest.

1. Locate your installed production integrity@irsiks package as in the Cursor section above.
2. Start Claude Code in your repository with that directory as a plugin:

3. Approve the plugin's Integrity MCP connection when Claude Code asks, complete Integrity's browser consent, and select your workspace in the conversation.

The manifest registers the lifecycle skills under the plugin namespace, for example /integrity:spec and /integrity:build, together with the production connection and a write gate. The gate selects the repository's rules for each file Claude Code edits and stops the edit until the selected rule files were read in that session. Repositories without an Integrity rule registry are unaffected.

Claude Code reads the repository's AGENTS.md through a one-line CLAUDE.md that contains only @AGENTS.md. Keep that file as it is; other content there, or a CLAUDE.local.md, hides the shared contract from Claude Code.

Verify the connection

Start a fresh Claude Code session and run the same read check as for Cursor: health and identity, your selected workspace, then the Teams you can access. Confirm that the Integrity tools are listed and that the agent completes a real read before relying on the connection.

Try it out

Once connected, ask your agent:

Include the Project name when asking about a specific Project. If you use more than one workspace, tell your agent which one to use.

After changing a plugin, connection, or server environment, start a fresh task before relying on its tool inventory. Ask the agent to confirm the selected server, environment, resource, and workspace. A development connection must not be treated as production access, and a successful login does not qualify a new application or plugin release.

Your agent uses your existing Integrity access. It asks for confirmation when an action requires it.

What to expect:

• Show my assigned Issues: your assigned work in the selected workspace.
• Latest Project update: the most recent published update for the Project you name.
• Find the spec: the specification saved to that Project, when one is available.

Change several properties

Ask your coding agent to use mutate_work_properties for up to 100 distinct Issues, Projects or Initiatives. The tool accepts routine status, priority, assignee/lead/owner, date and supported label changes within its schema. It uses one transaction, while preserving each item's permissions and stale checks. Known refused items leave eligible siblings saved. A batch that moves an Issue to a Team, Project or Phase, or a Project to its main Initiative, previews every item first. Properties in that batch wait too. Review the full preview and ask the agent to apply its one confirmation before anything saves. Document edits use their separate tool.

The response identifies saved and refused items. Ask the agent to re-read the objects for their current values. Run one bulk batch at a time.

After a lost response, ask the agent to look up the original batch with get_work_property_batch, or repeat the original request exactly. A missing lookup is unconfirmed. Repeating a batch returns its recorded refusals too; corrected refused items require a new request. For a confirmed move batch, the agent looks up or replays the original confirmation using its apply request key. Changed items need a fresh preview; independent eligible items can still save.

In-app AI retains its 16-item proposal limit, full approval summary and explicit approval/replay flow for routine properties. Move batches and batch lookup are available to connected coding agents.

Qualification and release boundary

For a release candidate, the project owner or operator verifies the exact application commit and installed plugin bytes against the configured development resource in fresh isolated sessions. The check includes the expected tool contract, real readback, safe fixture cleanup, and a recomputed promotion proof. Local tests, an existing browser tab, or a successful earlier task cannot replace that evidence.

Promotion eligibility is evidence, not permission by itself. A request or explicit standing project policy that already authorizes application deployment or plugin publication carries through the matching guarded release procedure without a second approval. The agent never infers a production target. If qualification fails or is interrupted, preserve its evidence, reconcile the same candidate, and resume through the supported workflow. Do not reinstall, switch environments, repeat an uncertain mutation, or delete retained state just to obtain a clean result.

Next step

Continue to Set up a project. That is where the repository gets Integrity's rule layout. Installation only connects the agent.