Install Loop in Codex

Before you start

• Update Codex to the current version.

• Use a Loop account with access to at least one Project.

• Confirm that your organization allows the Patronage plugin marketplace.

Install Loop

Run these commands in your shell to add the Patronage marketplace, install Loop, and start browser authentication.

codex plugin marketplace add patronage/loop-plugin --ref main

codex plugin add patronage-loop@loop-plugin

codex mcp login patronage-loop

1. 01

   Open Plugins

   In Codex, open the plugin marketplace and add patronage/loop-plugin if the Patronage marketplace is not already listed.

2. 02

   Install Loop

   Open Patronage Loop and install patronage-loop@loop-plugin. The plugin adds the Loop skill and remote connection together.

3. 03

   Authenticate

   The login command opens browser authentication. In Codex Desktop, choose Authenticate when prompted.

Connect your Loop account

1. 01

   Sign in to Loop

   Continue in the browser with the Loop account your team invited.

2. 02

   Choose a Project

   If you can access several Projects, choose the one this connection should use. Loop selects your only accessible Project automatically.

3. 03

   Review the connection

   Confirm the requesting application, selected Project, and requested access, then choose Allow connection.

Verify the connection

Ask the agent: “Show me the marketing Projects available in Loop and tell me which one is active.” Setup is complete when the response lists your accessible Projects and names the active one.

Confirm the active Project before asking the agent to run a workflow or prepare a change.

Revoke access

Sign in at https://loop.patronage.com/admin/profile and open Agent Connections. Find this connection and choose Revoke. Loop denies its next request. You can reconnect later through the same browser authorization flow.

How Codex connects

The plugin supplies the Loop endpoint and reviewed OAuth client identity. Codex selects an available loopback callback port for each sign-in, so no setup script, fixed callback-port preference, or API key is required.

Troubleshooting

• The browser does not open

  Run codex mcp login patronage-loop, then complete the browser flow.

• Authentication fails

  Update Codex and retry the browser flow. Do not replace browser authentication with a copied key.

• You signed out but the connection still appears in Loop

  codex mcp logout patronage-loop clears local credentials. Revoke the Agent Connection in Loop when you need to stop it server-side.