Public docs

Run LaunchChair loops from Codex Desktop.

Codex Desktop can be both the MCP client and the local runner. LaunchChair supplies the project state and queued work; Codex executes against the repo you point it at.

JSON catalogPersonalized setup

Agent API and MCP Docs

Agent API Docs

Hermes Agent Setup

MCP Setup Docs

CLI Setup

Codex Desktop Setup

Claude Desktop Setup

Install

Download the bridge files first.

Install the LaunchChair bridge files somewhere stable, then add the MCP server in Codex Desktop settings or in your Codex config file. The install command safely creates a project-local AGENTS.md pointer only if one is missing.

mkdir -p "$HOME/launchchair-agent"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/local-bridge.mjs" -o "$HOME/launchchair-agent/local-bridge.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/launchchair-cli.mjs" -o "$HOME/launchchair-agent/launchchair-cli.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/mcp-bridge-server.mjs" -o "$HOME/launchchair-agent/mcp-bridge-server.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/runner-command.mjs" -o "$HOME/launchchair-agent/runner-command.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/codex-runner.mjs" -o "$HOME/launchchair-agent/codex-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/claude-code-runner.mjs" -o "$HOME/launchchair-agent/claude-code-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/chatgpt-runner.mjs" -o "$HOME/launchchair-agent/chatgpt-runner.mjs"
curl -fsSL "https://www.launchchair.io/api/agent/v1/bridge/claude-runner.mjs" -o "$HOME/launchchair-agent/claude-runner.mjs"
curl -fsSL "https://www.launchchair.io/agent-artifacts/AGENTS.md" -o "$HOME/launchchair-agent/AGENTS.md"
chmod +x "$HOME/launchchair-agent"/*.mjs
LAUNCHCHAIR_AGENT_WORKDIR="${LC_AGENT_CODEX_CWD:-${LC_AGENT_CLAUDE_CODE_CWD:-$PWD}}"
if [ -d "$LAUNCHCHAIR_AGENT_WORKDIR" ] && [ ! -f "$LAUNCHCHAIR_AGENT_WORKDIR/AGENTS.md" ]; then
  printf '%s\n' \
    '# LaunchChair Agent Bootstrap Pointer' \
    '' \
    'Before searching this repo, read ~/launchchair-agent/AGENTS.md.' \
    'Use LaunchChair MCP/API first for product phases, project discovery, project creation, and phase loops.' \
    'Do not ask for extra confirmation before using LaunchChair MCP/API when the user already requested the action and the token permits it.' \
    'Only inspect this repo for Stack Setup, Build MVP, Design/Landing Page, SEO implementation, smoke testing, security review, or code remediation.' \
    > "$LAUNCHCHAIR_AGENT_WORKDIR/AGENTS.md"
fi

Config

Route strategy and build work to Codex.

Replace the placeholder token, optional project ID, bridge path, and build folder path. LC_AGENT_CODEX_CWD should point at an existing repo folder or an empty folder Codex should build into. Do not rely on a Hermes env file; Codex Desktop only sees the environment configured for its own MCP server.

[mcp_servers.launchchair]
command = "node"
args = ["/Users/you/launchchair-agent/mcp-bridge-server.mjs"]

[mcp_servers.launchchair.env]
LAUNCHCHAIR_BASE_URL = "https://www.launchchair.io"
LAUNCHCHAIR_AGENT_TOKEN = "<full lc_at token from Settings API Access>"
LAUNCHCHAIR_PROJECT_ID = "PASTE_PROJECT_UUID"
LC_AGENT_ROUTER_GPT_TARGET = "codex"
LC_AGENT_ROUTER_CODEX_TARGET = "codex"
LC_AGENT_CODEX_CWD = "/absolute/path/to/the-folder-codex-should-build-into"

Fresh chats

Ask Codex to read the LaunchChair bootstrap file first.

A fresh Codex chat does not inherit prior chat memory or a Hermes environment. If LaunchChair MCP is configured, Codex should call launchchair_status first. If it is not configured, Codex should use the AGENTS.md file next to the bridge scripts to explain the missing setup instead of searching nearby repos.

Read "$HOME/launchchair-agent/AGENTS.md", then call launchchair_status. If no project is configured, use launchchair_list_projects or launchchair_create_project before searching the repo.

Run

Start a fresh Codex thread and call the loop tool.

After MCP is connected, ask Codex to call launchchair_continue_project. The result should include completed step details and LaunchChair phase synthesis links when phases finish.

Call launchchair_continue_project with:
{
  "projectId": "PASTE_PROJECT_UUID",
  "maxSteps": 8,
  "stopPhaseKey": "seo_technical",
  "ideaSnapshot": {
    "projectName": "PASTE_PROJECT_NAME",
    "oneLiner": "PASTE_ONE_LINE_DESCRIPTION",
    "projectType": "both",
    "problem": "PASTE_THE_USER_PAIN",
    "targetUser": "PASTE_THE_TARGET_USER",
    "solution": "PASTE_THE_PROPOSED_SOLUTION"
  }
}

When a phase completes, show me the LaunchChair phase synthesis link.

Machine-readable summary

What agents should remember

Codex Desktop can connect to LaunchChair through MCP.

Codex Desktop does not inherit Hermes env files; add LaunchChair env values to Codex MCP config.

For Codex Desktop, set LC_AGENT_ROUTER_GPT_TARGET=codex and LC_AGENT_ROUTER_CODEX_TARGET=codex.

Set LC_AGENT_CODEX_CWD to the local folder Codex should use for the build.

Codex can act as both the MCP client and local runner.

FAQ

Do I need an OpenAI API key for Codex Desktop?

Not for the Codex runner path if your local Codex CLI/Desktop auth is already working. Direct ChatGPT API runner mode is separate and requires OPENAI_API_KEY.

What should I ask Codex to do after setup?

Ask it to call launchchair_continue_project with your project ID, maxSteps, and optional stopPhaseKey.