Connect coding agents

The first-party Cortex integration supports Codex, Claude Code, Cursor, and GitHub Copilot CLI.

What the integration installs

Each provider-specific plugin supplies two capabilities:

• SessionStart context explains what Cortex is, when to use it, and how the installed Socra CLI expands available commands.
• A hosted MCP connection gives the agent structured Cortex tools without passing long command output through the session-start hook.

The integration does not run an inbox task automatically and does not give Cortex control over the agent host. The host continues to control tool approval, instruction precedence, filesystem access, and command execution.

Installation

Run socra cortex setup after installing Cortex and signing in through the Socra CLI. The command detects supported hosts and installs or updates the Cortex integration for each detected host. Restart the configured hosts after setup completes.

Codex, Claude Code, and GitHub Copilot CLI install Cortex through their plugin marketplace support. Cursor receives the equivalent provider files from the same remote Socra plugin repository through its local integration path.

The setup command is idempotent. Running it again updates an outdated Cortex installation and leaves a current installation unchanged.

Authorization

Each host uses its own first-party public OAuth client and Authorization Code with PKCE. The plugin contains the public client ID but no client secret. The host stores its own grant after you select and authorize a Socra Account.

The setup process does not copy the Socra CLI access token into an agent host. A current browser session can reduce the number of sign-in prompts, but each host still obtains and stores its own OAuth grant.

Custom clients

Use the custom MCP guide when the client is not installed by socra cortex setup or when your application requires a customer-owned Cloud Project and OAuth client.