Use OpenLatch from your agent

Let your agent work with OpenLatch for you: read your agents and their execution graph, your Autonomy Zones and intent policies, your anomalies and Asks, and draft a policy with you. Your agent signs in as you and acts with your role, and every change it makes is recorded in the audit trail as you. Install the OpenLatch plugin, which brings the MCP server and the OpenLatch skills, or connect the MCP server alone.

What the marketplace installs

The OpenLatch marketplace is the public GitHub repository OpenLatch/openlatch-plugins. It serves one plugin to every client, and the plugin packages everything your agent needs: the connection to the MCP server at https://app.openlatch.ai/mcp, and four skills that teach your agent the steps your team follows with the OpenLatch tools. The plugin and its skills share one version, and your client takes each new version from the marketplace.

Skill	What it teaches
openlatch	The core concepts, which tool to use when, and the connection and version checks
openlatch-triage	Reading and answering anomalies and Asks
openlatch-agents	Working with the agent record: ownership, sessions, zone assignment and the organization tree
openlatch-autonomy-zones	Authoring, editing and restoring an intent policy with you, from a brief to a ratified policy

Every tool the plugin gives your agent, with what it can read or change and its parameters, is listed in the MCP tools reference.

Plugin or MCP server only

Choose the route that fits your client and your constraints.

	Plugin	MCP server only
Gives	The MCP tools (MCP tools reference) and the four skills (openlatch, openlatch-triage, openlatch-agents, openlatch-autonomy-zones) that teach your agent OpenLatch’s words and the steps your team follows, with a connection and version check	The MCP tools, with no plugin package to update: the tools live on the server, so a connected agent sees the server’s current tool list. In ChatGPT, refresh the plugin to pull new tools
Costs	A client with plugin support and a marketplace you may add; new plugin versions to take from the marketplace	No OpenLatch skill: your agent works from the tool descriptions alone. Skills, if you want them, are added and updated separately (Add the skills on their own)
Fits	Most readers	A client without plugin support, a workstation where marketplaces are blocked, a team that writes its own skills

Either route connects your agent through OAuth as you: it acts with your role, and every change it makes is recorded in the audit trail as you. The plugin already carries the MCP server, so connect one route, not both. Either route reaches only app.openlatch.ai, and ChatGPT and claude.ai call it from the vendor’s cloud, not from your workstation; see OpenAI’s custom MCP server guide and Claude’s custom connectors page.

The consent page

When your agent first calls OpenLatch, your browser opens the consent page at /oauth/consent. It reads Connect followed by the client’s name, with a badge under it: Verified client, or Unverified client when the client registered itself. Choose the organization, then read the line Acts with your role ({role}). Returns to {host}. Choose Connect to let the agent act, or Cancel to refuse.

Install from the marketplace

Choose your client. Each tab follows the same five steps: add the marketplace, install the plugin, sign in, check, then update or remove it.

Claude Code

1. Add the marketplace and install the plugin from it:

   /plugin marketplace add OpenLatch/openlatch-plugins
   /plugin install openlatch@openlatch

   Claude Code asks you to review the plugin and choose a scope before it installs. See Discover and install plugins.

2. Sign in. The first time your agent calls OpenLatch, your browser opens. Sign in, choose the organization the agent works in, and choose Connect.

3. Check. Ask your agent to check its OpenLatch connection. The openlatch skill calls whoami and compares its version with the published one.

4. Update. Update the marketplace to pick up a new plugin version:

   /plugin marketplace update openlatch

   Marketplace auto-update is off until you turn it on: run /plugin, go to the Marketplaces tab, select the marketplace and choose Enable auto-update.

5. Remove. Uninstall the plugin:

   /plugin uninstall openlatch@openlatch

Codex

1. Add the marketplace from your terminal:

   codex plugin marketplace add OpenLatch/openlatch-plugins

   In the Codex app, a workspace admin imports the marketplace instead; see Roll it out to a team.

2. Install the plugin. In Codex CLI, open the plugin browser:

   /plugins

   Open the OpenLatch tab, select the plugin and install it, then start a new session. In the Codex app, open the Plugins tab, open the plugin, select the plus button, connect the MCP server if prompted, then start a new chat. See Plugins in ChatGPT and Codex.

3. Sign in. When the plugin asks you to connect, or the first time your agent calls OpenLatch, sign in in your browser and choose Connect.

4. Check. Ask your agent to check its OpenLatch connection. The openlatch skill calls whoami and compares its version with the published one.

5. Update or remove. In Codex CLI, refresh the marketplace, then reinstall the plugin from the plugin browser:

   codex plugin marketplace upgrade openlatch

   To remove the plugin, open it in the same plugin browser and uninstall it. Removing the plugin does not disconnect the MCP server, so disconnect it too where you connected it. In a workspace, your admin syncs the marketplace to publish a new version; see Roll it out to a team.

ChatGPT

The OpenLatch plugin declares an MCP server, so it is marked Desktop only: it installs and runs in the ChatGPT desktop app, not on the web. See Plugin management.

1. Have a workspace admin import the marketplace. Your admin follows Roll it out to a team.

2. In the ChatGPT desktop app, open the Plugins tab, find the plugin under your workspace’s tab and open it. Select the plus button, connect the MCP server if prompted, then start a new chat. See Plugins in ChatGPT and Codex.

3. Sign in. When ChatGPT prompts you to connect the MCP server, sign in in your browser and choose Connect.

4. Check. Ask your agent to check its OpenLatch connection. The openlatch skill calls whoami and compares its version with the published one.

5. Update or remove. Your admin syncs the marketplace to publish a new version. To remove the plugin, open it from the Plugins tab and select Uninstall plugin. The MCP connection stays until you disconnect it in ChatGPT, and a plugin your workspace installed for you may not offer the action.

claude.ai

1. In claude.ai or the desktop app, open Customize › Plugins, select Add › Add marketplace and enter OpenLatch/openlatch-plugins. See Use plugins in Claude.

2. Install the plugin. On the Plugins tab, open Discover, select the OpenLatch plugin and choose Add.

3. Sign in. The first time your agent calls OpenLatch, sign in in your browser and choose Connect.

4. Check. Ask your agent to check its OpenLatch connection. The openlatch skill calls whoami and compares its version with the published one.

5. Update or remove. Select Check for updates on the marketplace to pick up a new version. To remove the plugin, remove its marketplace: find it on the Plugins page, open its menu and select Remove.

Then ask your agent: “List my agents and tell me which ones have no zone.”

A draft is not a policy

Any policy your agent drafts for you stays a draft until you approve its ratify call, which shows you the exact sentences. Author a policy through your agent walks through it.

Roll it out to a team

In a ChatGPT or Codex workspace, an admin imports the marketplace once and every member can then install the plugin. See Plugin management for the full steps.

1. Open Admin › Plugins and select Add › Import marketplace.
2. In Source, enter https://github.com/OpenLatch/openlatch-plugins, the repository URL only. Leave Path and the branch empty, and authorize GitHub access when prompted.
3. Open the plugin and set its installation policy for each role: Available lists the plugin for members to install, and Installed puts it in their client.
4. After an OpenLatch release, open Admin › Plugins › Marketplaces, select the marketplace and choose Sync now. Otherwise it syncs daily.

Importing the marketplace does not connect anyone’s OpenLatch account: each member signs in on their own.

In a Claude Team or Enterprise organization, an owner distributes plugins through plugin marketplaces or the organization library; see Use plugins in Claude.

Add the MCP server only

To connect your agent without the plugin, add the MCP server at https://app.openlatch.ai/mcp to your client under the name openlatch. Choose your client. Each tab follows the same steps: add the server, sign in, check, then remove it.

Claude Code

1. Add the server for every project on your machine:

   claude mcp add --transport http --scope user openlatch https://app.openlatch.ai/mcp

   Without —scope user, the server serves the current project only. See Connect Claude Code to tools via MCP.

2. Sign in. In Claude Code, run /mcp, choose openlatch and follow the steps in your browser: sign in, choose the organization the agent works in, then choose Connect.

3. Check. Ask your agent to call whoami: it answers with your user and your organization.

4. Remove. Remove the server:

   claude mcp remove openlatch

Codex

1. Add the server:

   codex mcp add openlatch --url https://app.openlatch.ai/mcp

   The ChatGPT desktop app, Codex CLI and the IDE extension share this configuration. See Model Context Protocol.

2. Sign in. Start the sign-in, then follow the steps in your browser: sign in, choose the organization the agent works in, then choose Connect.

   codex mcp login openlatch

3. Check. List your servers to see the server, then ask your agent to call whoami: it answers with your user and your organization.

   codex mcp list

4. Remove. Delete the server definition. See Codex commands.

   codex mcp remove openlatch

ChatGPT

Workspace permissions and security restrictions apply to who may add a custom MCP server: see OpenAI’s custom MCP server guide. Unlike the plugin, which installs in the desktop app only, a custom MCP server is added on the web.

1. Add the server. On ChatGPT on the web, go to Plugins, select the plus button, then Add custom MCP server. Enter a name and the server URL, https://app.openlatch.ai/mcp, choose OAuth authentication, acknowledge the risk warning, create the plugin, then install it. See OpenAI’s custom MCP server guide.

2. Sign in. When ChatGPT starts the OAuth sign-in, sign in in your browser, choose the organization the agent works in, then choose Connect.

3. Check. In the prompt box, type @ and select the plugin you installed, then ask your agent to call whoami: it answers with your user and your organization.

claude.ai

The Free plan holds one custom connector. See Get started with custom connectors using remote MCP for every step below.

1. Add the connector. Open Customize › Connectors, select + Add, then Add custom connector. Enter a name and the server URL, https://app.openlatch.ai/mcp, and select Continue. Under OAuth client, choose Use Claude’s published identity (Recommended), then select Add.

   On Team and Enterprise plans, an Owner adds it under Organization settings › Connectors, and each member finds it under Customize › Connectors and selects Connect. Adding it gives no one access to OpenLatch: each member signs in as themselves, with their own role.

2. Sign in. Select Connect, then sign in in your browser, choose the organization the agent works in, and choose Connect.

3. Check. In a conversation, select +, then Connectors, and turn the connector on. Ask your agent to call whoami: it answers with your user and your organization.

4. Remove. Open Customize › Connectors and select Remove next to the connector. An Owner removes an organization connector under Organization settings › Connectors.

A connector you add in claude.ai is also available in Claude Code when you sign in to Claude Code with your claude.ai account. See Use MCP servers from claude.ai.

Removing the server from a client does not revoke OpenLatch’s access: revoke the agent under Connected agents in your OpenLatch profile.

Add the skills on their own

If you connected the MCP server alone, you can add the four OpenLatch skills on their own, or work without them. Install them from the repository:

npx skills@1.7.4 add OpenLatch/openlatch-plugins

In claude.ai, upload each skill’s archive, <skill>.zip, from the repository’s latest release under Customize › Skills. Do not upload openlatch-plugin.zip there: it carries the MCP connection too. A manual install does not update itself: the openlatch skill tells you when a new version is out.

Troubleshooting

You see	Do this
The plugin is installed but no OpenLatch tool answers	Start a new session or chat. If the tools are still missing, the MCP server is not signed in: ask your agent to check its OpenLatch connection
The plugin does not appear in ChatGPT on the web	It is Desktop only. Open the ChatGPT desktop app
The agent suggests an update	Update with the route of your client, above
You added the server but no OpenLatch tool answers	Sign in: in Claude Code run /mcp, in Codex run codex mcp login openlatch, in claude.ai select Connect. Then start a new session or chat. In claude.ai, turn the connector on under + › Connectors; in ChatGPT, type @ and select the plugin
The consent page shows “Unverified client”	The client registered itself rather than through a published identity: connect only if you started the sign-in from a client you trust. In claude.ai, remove the connector and add it again with Use Claude’s published identity (Recommended)
OpenLatch tools appear twice	Two routes are connected. If you installed the plugin, remove the server you added by hand. In Claude Code, a claude.ai connector can also appear: run /mcp and turn it off for the current project

Working with OpenLatch is not being covered by it

Connecting your agent lets it work with OpenLatch; it does not put that agent under OpenLatch’s control. Coverage comes from the client, and the control level of each agent is stated plane by plane in Control levels.

Next steps

• Examples gives questions to ask your agent, with the tools it calls.
• Author a policy through your agent takes your agent from a brief to a ratified policy.
• The MCP tools reference lists every tool your agent can call, grouped by OpenLatch object.