Think of Preflight as a checklist before a flight. It helps your agent check the request before takeoff. SayWhat turns your rough instructions into a plan; Codex uses that plan to do the work.
1. Get your setup prompt
- Have the Codex desktop app or Codex CLI installed and signed in. CLI means the version you use in a terminal.
- After buying SayWhat, open your setup email or visit Account → Setup.
- Copy the full setup prompt and its activation code. The prompt tells Codex how to install SayWhat.
Your activation code is like a one-use ticket. It links the install to your license. Get a fresh code if it expires or has already been used.
2. Paste the prompt into Codex
- Open a local task in the Codex desktop app, or start Codex CLI in a terminal.
- Paste the full setup prompt and send it. If Codex asks which agent to set up, choose Codex.
- Let Codex activate the install and add the SayWhat connection and instructions. Review any requests to change your local settings.
- Wait for SayWhat connected, with results for Adapter, Activation, Preflight, and Health check.
Setup saves a license token, which works like a key. Keep it on your computer and out of shared project files. Codex should not print it in chat.
3. Restart and check
- Restart Codex and open a new local task. This lets it load the new tools and instructions.
- Send this check:
Run SayWhat Preflight for “add a hello comment” with targetAgent codex. Show the receipt only; do not edit any files.
Look for a saywhat_preflight call and a SayWhat.foo PreFlight receipt. The receipt is a short summary of the request SayWhat prepared. On your next coding task, Codex should run this check before it edits files.
What does setup add?
- A skill: an instruction sheet that tells Codex when to use SayWhat.
- An MCP connection: a standard way for agents to use tools. It acts like a cable between Codex and SayWhat.
- A Preflight rule: instructions in
~/.codex/AGENTS.mdthat tell Codex to run SayWhat before coding.
The connection settings go in ~/.codex/config.toml. Setup should add SayWhat while keeping your other settings. For details, see OpenAI’s MCP guide.
Common problems
- Code expired or already used: get a new prompt from Account → Setup.
- Tool is missing: restart Codex and open a new task. Ask it to check that the SayWhat MCP server is enabled and can start. The local adapter needs Node.js and the server file named in its settings.
- Codex skips Preflight: ask it to run
saywhat_preflightdirectly. Have it check that the skill and Preflight rule are loaded. If only one project has trouble, check for conflicting project instructions. - License check fails: ask Codex to check the saved token without showing it. Check your account to see whether the install was revoked.
- Setup stops before it finishes: ask Codex which step failed. Use the manual Codex install guide to add the connection, skill, and Preflight rule. Merge the instructions with your existing files.
- Using cloud Codex: this guide covers installs on your computer. For cloud tasks, use the web compiler and paste the plan into your agent.
Still stuck? Contact us with the step that failed and its error message. Leave out activation codes and license tokens.
