Codex + Cuiar
Codex checks the admin panel at 2 a.m.
- ~/.codex/config.toml
- OAuth, or a key from a variable
- Works with codex exec
Codex already runs your tests at night. Some checks live in a web admin panel or a vendor dashboard, behind a login.
Add Cuiar to config.toml, and codex exec can open those pages in your Admin workspace, read the failures and file the issues. The Codex CLI, the IDE extension and the ChatGPT desktop app read the same file.
Setup
Two lines of TOML and one sign-in.
Codex runs on your computer, next to the Cuiar app.
- 1
Add the server
Or run
codex mcp add cuiar --url https://mcp.cuiar.com/mcp.~/.codex/config.toml [mcp_servers.cuiar] url = "https://mcp.cuiar.com/mcp" - 2
Sign in
codex mcp login cuiar - 3
Give long tasks time
A
run_taskcall can take minutes. The default tool timeout is 60 seconds.~/.codex/config.toml [mcp_servers.cuiar] url = "https://mcp.cuiar.com/mcp" tool_timeout_sec = 600 - 4
Run it
codex exec "With the Cuiar tools, open the failed-jobs page in my Admin workspace and list the new failures"
Other ways to connect
A key for cron
Cron cannot open a browser for OAuth. Put a key with the
mcpscope in a variable, and Codex sends it as a Bearer token.~/.codex/config.toml [mcp_servers.cuiar] url = "https://mcp.cuiar.com/mcp" bearer_token_env_var = "CUIAR_MCP_KEY"Local stdio
Or run
codex mcp add cuiar -- cuiar mcp.~/.codex/config.toml [mcp_servers.cuiar] command = "cuiar" args = ["mcp"]The CLI from Codex's shell
Codex can also run
cuiarcommands. If the sandbox blocks their network calls, allow the network for the workspace-write sandbox, or use MCP.~/.codex/config.toml [sandbox_workspace_write] network_access = true
Route
MCP needs no hole in the sandbox.
The MCP route needs no network rule in Codex's sandbox. The same config.toml serves the CLI, the IDE extension and the ChatGPT desktop app.
- Remote MCPmcp.cuiar.com/mcp
- Best fit
- OAuth with
codex mcp login, orbearer_token_env_varfor cron. - Local MCPcuiar mcp
- Works
command = "cuiar"withargs = ["mcp"].- CLIcuiar exec
- Works
cuiar exec --jsonin the shell. The sandbox can block its network calls.- Routineson a schedule
- Works
- Codex Scheduled tasks in the ChatGPT app, a cron line with
codex exec, or a Cuiar routine without Codex.
Example tasks
Jobs for codex exec
01
Check a PR preview
codex exec "Read the preview URL from the PR description, open it with the Cuiar tools, sign up with a test email and list any broken page or console error."02
Sum up an incident
“Check the status pages of our four providers and the error dashboard in my Ops workspace. Write a short incident summary to ops/status.md.”
Codex runs
cuiar run --workspace ops.03
Export data for a migration
cuiar run --workspace admin --folder ./migration/data "Export all customers as CSV from the admin panel"Codex then writes the import script for that file.
04
Read vendor changelogs
cuiar --odyssey --permission read-only "Collect the release notes since our pinned versions for these six SDKs and list the breaking changes"Odyssey is on Pro and Team.
cuiar tasks cloud <id>keeps it going while the laptop sleeps.05
File nightly failures
0 2 * * * codex exec "With the Cuiar tools, open the failed-jobs page in my Admin workspace and file one GitHub issue per new failure"A crontab line. It needs the key route.
Good to know
- ChatGPT on the web
- It does not read
config.toml. Add Cuiar there as a plugin; the ChatGPT page has the steps. - Sandbox
codex execruns read-only by default. Add--sandbox workspace-writewhen the job writes files.
Templates to run from Codex
All templatesEach template page shows the run_task or create_routine call to give Codex.
Engineering
Run a smoke test on staging after each deploy
Sign-in, key pages and main actions checked in the browser, with a screenshot of each failure.
On an event: When a new staging deploy finishes- Vercel
- Any website
EngineeringAsks first
Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
You start it: When you start it- GitHub
Engineering
List pull requests that wait for review
Open PRs across your repos with age, reviewers and CI status, the oldest first.
On a schedule: Every weekday at 10:00- GitHub
Engineering
Compare staging with production before a release
Text, layout and console differences page by page, with the ones that look like bugs marked.
You start it: When you start it- Any website
- Google Docs
EngineeringAsks first
Draft status page updates during an incident
A clear update from the incident channel and your monitors, posted to your status page after you approve it.
You start it: When you start it- SSlack
- Datadog
- Any status page
Data
Pull tables from PDFs into a spreadsheet
Each matching table from your PDFs and scans in one sheet, with numbers as numbers and the page noted.
You start it: When you start it- Google Drive
- Google Sheets
More agents
All AI agentsClaude CodeRemote MCPTest real flows from the terminal
CursorRemote MCPCheck localhost in a real tab
Grok BuildRemote MCPAccessibility and QA passes on staging
Kimi K3Remote MCPListings and supplier data into CSV
ChatGPTRemote MCPErrands from a chat, with your OK on each click
OpenAI dotsCLIAn always-on dot, through your own computer
Start on the Free plan.
The MCP server, the vault and unlimited routines are free. Steps that your own agent takes use no Cuiar credits.