Codex & Claude Code

1. Take independent instructions with you

Desktop Settings → Portable tools and mobile account sheet → Portable tools open the catalog. Source actions include Use in your own tools on desktop and Export flow, Export agent, Export coding brief or Export handoff brief on mobile.

Choose a destination, preview, then copy or save/share the exact artifact. Independent is the default. Imports need review and the destination’s own credentials and configuration. Sublime-connected is opt-in for flow exports to n8n; it requires configured Sublime credentials and Sublime usage and billing apply. Exporting or sharing does not activate, execute, deliver successfully, or verify the artifact.

2. Give an external client read-only meeting context

First follow key setup and visibility rules. Supply SUBLIME_API_KEY securely in the environment of the process launching your client. A shell export does not automatically reach an already running desktop application.

Codex

Add this to ~/.codex/config.toml, or use the CLI command below. Check codex mcp list and /mcp. See official Codex MCP documentation.

[mcp_servers.sublime]
url = "https://www.trysublime.io/api/mcp"
bearer_token_env_var = "SUBLIME_API_KEY"

codex mcp add sublime --url https://www.trysublime.io/api/mcp --bearer-token-env-var SUBLIME_API_KEY
codex mcp list

Claude Code

Use this project .mcp.json, retaining the environment placeholder. Review the project trust prompt, then check claude mcp list and /mcp. See official Claude Code MCP documentation.

{
  "mcpServers": {
    "sublime": {
      "type": "http",
      "url": "https://www.trysublime.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${SUBLIME_API_KEY}"
      }
    }
  }
}

claude mcp list

If tools are missing, check process environment, key expiry/revocation, owner access and workspace opt-in. This API-key setup does not use an OAuth login. The examples are source/CLI-help validated; live named-client compatibility remains unverified. The meeting transport has separate SDK route-test evidence.

3. Pair Sublime’s local coding runtime

Desktop Settings → Coding → Connect Codex or Connect Claude Code pairs a local project for Sublime execution. Choose project selects a local directory; Open CLI sign-in opens authentication. Sublime checks installed CLI authentication and validates the project remote. Recovery commands are codex login status and claude auth status --json. The Sublime Claude runner requires Claude Code 2.1.251 or newer; this is a runner requirement.

Paired execution requires taskTools access. Essentials portable export and meeting retrieval do not grant execution. Importing instructions or configuring meeting MCP does not pair a runtime.