Does one setup cover the Codex CLI, IDE extension and app?

Yes. All three read ~/.codex/config.toml, so the server and its sign-in are shared. A per-project .codex/config.toml also works in trusted projects.

Has FishOut been tested with Codex?

Yes. On 19 October 2026, Codex CLI 0.163.0 registered itself with FishOut using its client metadata document, completed sign-in and consent, and called list_organizations, list_projects, list_keywords, list_mentions and get_daily_brief against production, plus a saved view it created and deleted.

Which ChatGPT plans include Codex?

OpenAI lists Codex in ChatGPT Free, Go, Plus, Pro, Business, Edu and Enterprise, with features varying by plan. FishOut’s server is on every FishOut plan, including Free.

Can Codex run this every morning?

Through Codex scheduled tasks, created in ChatGPT on the web or in the app, where your plan allows. Or let FishOut do the scheduled part: the Daily brief and alerts run without any agent, and Codex reads them when you ask.

Will Codex post replies for me?

No. FishOut has no posting tool. Codex can request a draft (from Plus), and you post it from your own account.

MCP · CLI, IDE and app

Connect FishOut to OpenAI Codex (MCP Setup)

Codex keeps MCP servers in one file that its CLI, IDE extension and desktop app all read, so you set FishOut up once. A remote server is two lines of TOML, and codex mcp login does the OAuth.

Tested with Codex CLI 0.163.0 on 19 October 2026

Start free Read the MCP docs

Setup steps checked against Codex's own documentation on 20 October 2026.

[01] CONNECT IT/ SETUP

Add FishOut to Codex

https://mcp.fishout.ai/mcp, on every plan.

Add the server

From a terminal, codex mcp add writes the entry for you. It lands in ~/.codex/config.toml, which the CLI, the IDE extension and the app share.

bash

codex mcp add fishout --url https://mcp.fishout.ai/mcp

Or write the TOML yourself

The same thing by hand. A .codex/config.toml inside a repository works too, but Codex only loads it in projects you have marked as trusted.

~/.codex/config.toml

[mcp_servers.fishout]
url = "https://mcp.fishout.ai/mcp"

Codex does not prompt on its own: run the login command, finish the sign-in in your browser, pick the organization and projects, and approve. codex mcp logout fishout removes the stored credentials.

bash

codex mcp login fishout

Or use an API key

For a CI job, name the environment variable that holds a FishOut key. Codex sends it as a bearer token and tries it before OAuth.

~/.codex/config.toml

[mcp_servers.fishout]
url = "https://mcp.fishout.ai/mcp"
bearer_token_env_var = "FISHOUT_API_KEY"

Check it worked. Type /mcp in the Codex TUI to list active servers; fishout should be there with its tools. Then ask how many mentions came in yesterday before asking for anything that writes.

[02] WORTH KNOWING FIRST/ LIMITS

Before it bites

Stated before you hit them.

A server that is configured but not signed in can still connect without credentials, and every call then fails with 401. If tools error, run codex mcp login fishout before anything else.

Project-level .codex/config.toml is ignored in untrusted projects — the usual reason a teammate “has the file but not the tools”.

Tool calls time out after 60 seconds by default (tool_timeout_sec). FishOut’s read tools answered in under a quarter of a second in our run, so this only bites a client-side stall.

In our 19 October run, Codex kept all 115 tools behind its tool search and found the right ones by name. An allow list still makes its choices faster and safer.

A tighter tool set. enabled_tools is an allow list; disabled_tools is applied after it. This keeps Codex to reading, and asks before anything else.

~/.codex/config.toml

[mcp_servers.fishout]
url = "https://mcp.fishout.ai/mcp"
enabled_tools = [
  "list_mentions",
  "count_mentions",
  "get_mention",
  "get_inbox_counts",
  "get_daily_brief",
  "get_insights",
  "list_keywords",
  "list_labels",
]
default_tools_approval_mode = "prompt"

[03] WHAT IT LOOKS LIKE/ CODEX

A question in Codex

Invented brands; a real call.

Codex · terminalfishout · mcp

Read this week’s FishOut mentions labelled Has a problem and turn the real bugs into a TODO list in BUGS.md.

list_mentionsread-onlyarguments

{
  "filter": {
    "labels": [
      "has-a-problem"
    ],
    "from": "2026-10-13T00:00:00Z",
    "minRelevance": 50
  },
  "limit": 20
}

get_mentionread-onlyarguments

{
  "mentionId": "mnt_…"
}

quarry-apps/mobileissue #3011d

Webhook retries fire twice when the first call times out

Reply nowHas a problem

r/webdevkettle_and_bit3d

Their dashboard logs me out every 10 minutes on Safari

Reply, carefullyHas a problemComplaint

Wrote BUGS.md with two items: duplicate webhook retries on timeout (one GitHub report with a repro) and Safari sessions expiring early (one Reddit post, two agreeing replies). Seven other matches were usage questions, not bugs, so I left them out.

[04] WATCH ANY PLATFORM/ SAME SERVER

What Codex can ask about

Every platform on your plan.

[05] ON A SCHEDULE/ CODEX

Codex’s scheduler

Codex calls these scheduled tasks. They are created in ChatGPT on the web or in the desktop app — not from the CLI — with daily, weekly or RRULE schedules, and availability depends on your plan and workspace. Its docs say web tasks can use connected tools; check that FishOut is available to the task before relying on it.

Or let FishOut keep the clock

Alerts and the Daily brief run on FishOut’s side, with no agent involved, and agent rules act on every mention as it is triaged. The scheduled job then only has to do the judging.

[06] WHERE YOU APPROVE IT/ SETTINGS