Your browser opens, you sign in, and you pick which account to connect. The token is stored in your OS keyring.
The consent screen has up to three checkboxes — for your datasets, for managing people on the account, and for author mode. Building, changing, publishing and sharing apps works without any of them. Tick what you need now or later, from Account → Connections, without reconnecting. See what you’re granting.
> Have Gaia build an event planning app using the Excel file in this folder
Codex imports the workbook, walks the contract conversation with you, then runs the build pipeline. When the harness needs a decision it presents the options as a numbered list in chat — reply with the number or the option name and it continues.
Note the “Have Gaia” at the front. The first message has to name the product or Codex will just answer it itself, without ever calling the connector — see Say “Gaia” in your first message.
Then keep talking. The app is in context now, so follow-ups don’t need to name it:
> add a probability column to the deals table> publish it
build takes 90–180 seconds and a chat turn can take over a minute. If your client doesn’t send a progress token, the connector hands the wait back after about 50 seconds with outcome:"running" rather than risk the call being abandoned.That is not a failure. The right response is a status call, which Codex should make on its own.
Never ask Codex to run the build again to check on it. The first build is still running server-side, so a second start isn’t a retry — it creates duplicate work someone has to clear by hand. The same goes for re-sending a chat message.
Same connector, same tools, same harness — only the client’s interface differs:
Claude Code
Codex
Add the server
claude mcp add --transport http
codex mcp add --url
Sign in
/mcp → Authenticate
codex mcp login gainable
Forwarding harness questions
AskUserQuestion picker
Numbered list in chat
Build progress
Live task list
Plain-text stage updates
The connector is an MCP server, not a shell command, so there are no per-command approval rules to configure. Codex asks once when a tool is first used, and that’s it.
