How do I authorize Tempreon in Codex?

Once Tempreon is registered by any method, Codex triggers an OAuth flow on first connect. A browser window opens with the Tempreon consent screen where you sign in, review the requested scopes, and approve; Codex then stores the access token locally and reuses it every session. From the CLI you can start this manually by running codex mcp login tempreon.

Where does Codex keep its MCP settings, and how do I add Tempreon?

Codex reads MCP servers from ~/.codex/config.toml for all installs on the machine, or a project-local .codex/config.toml to scope it to one trusted project. All three Codex surfaces — the ChatGPT desktop app, IDE extension, and CLI — read the same file. The most reliable path is to open ~/.codex/config.toml, add an [mcp_servers.tempreon] block with your URL, save, then fully quit Codex with Cmd-Q and reopen. You can also run codex mcp add tempreon --url followed by your Tempreon URL to write the same block from the terminal.

I can't find the Codex app on my Mac anymore — where did it go?

OpenAI folded the standalone Codex Mac app into the ChatGPT desktop app in July 2026, so there is no separate Codex application to open. Launch the ChatGPT desktop app and use Codex from there. Your MCP configuration is unaffected, since every Codex surface reads the same ~/.codex/config.toml file.

Codex (ChatGPT) Setup — Docs

Overview

Codex is OpenAI's coding-agent product, available in the ChatGPT desktop app, as an IDE extension (VS Code, Cursor, and similar), and as a CLI. All three share the same MCP configuration surface — once you connect Tempreon, your Codex session sees your Core Imprint, Knowledge Vault, preferences, and project context, the same intelligence layer your Claude tools use.

Codex supports remote MCP servers over OAuth. There are several equivalent ways to register Tempreon; pick the one that matches your install.

Desktop naming (as of August 2026): OpenAI folded the standalone Codex Mac app into the ChatGPT desktop app in July 2026. If you're looking for a separate "Codex" application on your Mac and can't find it, open the ChatGPT desktop app — that's where Codex lives now. The config file and every step below are unchanged.

Prerequisites

A current Codex install — the ChatGPT desktop app, IDE extension, or CLI (run codex --version to confirm)
A Tempreon account with at least one available Bridge slot (check your Bridges dashboard)
A working default browser on the machine running Codex — the OAuth flow opens one

Step-by-Step Setup

1. Get Your Connection Details

Log into Tempreon and navigate to the Bridges section of your dashboard to find your MCP server URL. The URL ends in /mcp.

2. Add to Your MCP Configuration

Codex reads MCP server configurations from ~/.codex/config.toml (global) or a project-local .codex/config.toml. All three Codex surfaces — the ChatGPT desktop app, IDE extension, and CLI — read the same file. Pick whichever method matches your install; the resulting configuration is identical.

Project-local config only loads for projects you've marked as trusted, so if a .codex/config.toml seems to be ignored, check the project's trust setting before anything else.

Method A — Edit `~/.codex/config.toml` directly (recommended)

This is the most reliable path. Open ~/.codex/config.toml in your editor (create it if it doesn't exist) and add:

[mcp_servers.tempreon]
url = "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"

Save. Fully quit Codex (Cmd-Q on Mac, not just close the window) and reopen. Tempreon will appear in your MCP servers list.

Tip: Use ~/.codex/config.toml to make Tempreon available across every Codex install on this machine. Use a project-local .codex/config.toml to scope it to a single project.

Method B — Codex IDE Extension

In the Codex extension's settings panel, choose MCP settings → Open config.toml. The extension opens the same file as Method A. Add the [mcp_servers.tempreon] block above, save, and reload the extension. The IDE Extension is the most convenient path if you're already working inside VS Code, Cursor, or a similar editor.

Method C — One CLI command

From a terminal, register and authorize Tempreon without opening an editor:

codex mcp add tempreon --url https://api.tempreon.com/functions/v1/tempreon-mcp/mcp
codex mcp login tempreon

This writes the same [mcp_servers.tempreon] block to ~/.codex/config.toml. Confirm with codex mcp list.

Method D — Desktop app GUI

In the ChatGPT desktop app, open Settings → MCP servers → Add server and fill in the form. The app writes the same [mcp_servers.tempreon] block to ~/.codex/config.toml for you.

If the Add server form flickers or the OAuth window closes immediately, the form may have failed to persist before triggering OAuth. Fall back to Method A (edit ~/.codex/config.toml directly) — the verified workaround from our 2026-05-06 validation. The same TOML block applies; the app picks it up on next launch.

3. Authorize the Connection

Once Tempreon is registered (any method), Codex triggers an OAuth flow on first connect. From the CLI you can also kick this off manually:

codex mcp login tempreon

A browser window opens with the Tempreon consent screen. Sign in if prompted, review the requested scopes, and approve. The window closes; Codex stores the access token locally and reuses it on every future session.

4. Verify the Connection

Open the MCP servers list in your Codex surface (desktop app Settings, IDE extension panel, or codex mcp list from the CLI). Tempreon should appear as Connected. Start a new session and ask:

"What Tempreon tools do you have access to?"

If Codex lists Tempreon's tools, the Bridge is working.

Developer-Specific Features

Codex with Tempreon is particularly powerful for developers because:

Architecture decisions persist. Tell Codex to remember a technical decision in one session and it surfaces automatically the next time you're working in the same area — across the desktop app, IDE extension, and CLI.
Project context carries over. Domain-scoped knowledge means Codex knows the difference between your work projects and your personal projects without you re-explaining.
Session bootstrap is automatic. Tempreon surfaces the right context at session start — what you've decided before, who you've talked to, which projects are active — so Codex picks up where the last session left off.
Task management is integrated. Capture tasks from inside the terminal or editor without context-switching to a separate tool.

Try Saying...

"Pull up what I've been working on in [project name]" — Loads project context into the session
"What did I decide about the auth service architecture last week?" — Searches your Knowledge Vault from the terminal or editor
"Save this design note as a spec document" — Stores a file in your File Vault tagged for cross-session retrieval
"What tasks do I have queued for [project]?" — Reads your personal task queue without leaving Codex

Common Issues

Problem	Solution
Desktop app's Add server form flickers, OAuth window closes, Tempreon never appears	Use Method A (edit `~/.codex/config.toml` directly). Save, fully Cmd-Q the app, reopen.
Can't find a separate Codex app on your Mac	Codex moved into the ChatGPT desktop app in July 2026. Open that instead — your config carries over.
A project-local `.codex/config.toml` seems to be ignored	Codex only loads project-scoped config for projects you've marked trusted. Trust the project, or use the global `~/.codex/config.toml`.
OAuth completes but Tempreon disconnects after a few minutes	Connector cache stickiness. Fully delete and re-add the Tempreon connector (not just disconnect/reconnect) to refresh the tool list.
Tools list doesn't update after a Tempreon-side change	Codex caches the tool list per connector. Disconnect, fully restart Codex, re-add as a new connector to bust the cache.
`codex mcp login` reports "unknown command"	Update Codex — older versions had reconnect-loop bugs around v0.125.0.
Browser doesn't open during `codex mcp login`	Codex prints the auth URL on the terminal — copy it into your browser manually.

For more help, see Troubleshooting Connections.