AX plugin

The AX plugin connects your coding agent to the hosted MCP tools at https://app.514.ax/mcp and adds an optional feedback prompt. You do not need to install the AX CLI.

Install

Install from the AX plugin repository. These instructions track its main channel. On Windows, use WSL; native Windows is not supported by the plugin's shell hooks.

/plugin marketplace add 514-labs/ax-plugins
/plugin install ax@ax-prod

Authenticate with AX when your client prompts, then confirm AX tools appear in your session. To connect without the plugin, use MCP install.

Feedback and opt-out

After a session in which you use AX, the plugin asks your agent to draft feedback about AX, show it to you, and send it only if you agree.

For sessions that use AX only through the ax CLI, Claude Code and Codex require the CLI to be signed in, coding-agent session reporting to be enabled, and the agent to expose its session ID to shell commands. See coding-agent session reporting. Copilot and Cursor detect CLI use through their shell hooks, without requiring CLI sign-in or session reporting.

The prompt is limited to once a day within each agent family. Claude Code and Codex share a per-user 24-hour cooldown. Copilot and Cursor share a separate local daily marker. These limits do not coordinate across the two families or across machines for the local marker.

Through the MCP feedback_send tool, feedback sends only the message text, an optional category, and any run or experiment reference IDs the agent includes. It cannot attach files or code. For CLI-only sessions, ax feedback send also sends the CLI version and OS, plus the detected agent session ID when signed in. The CLI uploads a file only when explicitly given --attach; the plugin's prompt does not request attachments. Neither channel uploads run traces or experiment YAML because a reference ID was included. Review the draft before agreeing to send it.

To disable the entire Codex plugin, add this to ~/.codex/config.toml (or a trusted project's .codex/config.toml):

[plugins."ax@ax-prod"]
enabled = false

CLI telemetry and coding-agent session reporting have separate opt-outs.

Updates

Refresh the marketplace and update the plugin in your client:

Enterprise allowlists

Add AX to your existing policy entries. Keep other approved marketplaces and servers in place.

Claude Code

Allow the repository with strictKnownMarketplaces and register it with extraKnownMarketplaces in managed settings:

{
  "strictKnownMarketplaces": [
    { "source": "github", "repo": "514-labs/ax-plugins" }
  ],
  "extraKnownMarketplaces": {
    "ax-prod": {
      "source": { "source": "github", "repo": "514-labs/ax-plugins" }
    }
  }
}

The allowlist alone does not register the marketplace. If your policy sets allowManagedHooksOnly, force-enable AX in managed settings to allow its feedback hook:

{
  "enabledPlugins": {
    "ax@ax-prod": true
  }
}

See Claude Code organization policy and managed hook policy.

Codex

When your managed requirements.toml restricts marketplace sources, add an AX source rule:

[marketplaces.allowed_sources.ax]
source = "git"
url = "https://github.com/514-labs/ax-plugins.git"

These rules apply when marketplaces.restrict_to_allowed_sources = true. If your policy also defines a plugins MCP allowlist, allow the plugin's server:

[plugins."ax@ax-prod".mcp_servers.ax]
identity.url = "https://app.514.ax/mcp"

When allow_managed_hooks_only = true, Codex skips plugin hooks. See the Codex requirements reference.

Copilot

If your enterprise selects “Registry only” for MCP access, add the AX server (https://app.514.ax/mcp) to your organization's MCP registry. Installing the plugin does not bypass that policy. See Copilot registry restrictions.

The AX plugin cannot be used in the Copilot cloud agent yet: its hosted MCP connection uses OAuth, which the cloud agent does not support. Use Copilot CLI or VS Code instead. The cloud-agent firewall host would be app.514.ax, configured under Settings → Copilot → Internet access, but allowing that host does not enable the plugin. See cloud-agent firewall settings and cloud-agent MCP configuration.

Cursor

Import the repository into a Team Marketplace using the steps in the Cursor tab. Set marketplace access for your team or organization groups, then choose the plugin's installation mode:

If your team restricts local plugin imports or MCP servers, approve the AX plugin and https://app.514.ax/mcp through your team policy. See Cursor team marketplaces.