Yes — Codex can build, launch and manage your WhatsApp campaigns in WarmySender, all in plain language, through the same 78-tool connection Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent share. You ask in the Codex terminal. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Codex is OpenAI’s coding agent and runs in your terminal, so you talk to it in the shell you already use for the rest of your pipeline. It connects with one add command and one login command; the login opens a WarmySender sign-in in your browser, so there is no key to paste. WhatsApp campaigns via Codex fit a contact list that lives in a file: Codex builds the intro-and-follow-up campaign on your business number, enrolls the list, and reports reply rates on request. The number’s ramp and first-message budget are readable, never movable.
Every "can" below stands on a real tool in the WarmySender connection. Every "cannot" is not a setting — there is simply nothing an agent can call that does it.
| Can / cannot | What that means for WhatsApp outreach |
|---|---|
| Can | Create a WhatsApp campaign on a connected number and choose the steps and waits. |
| Can | Start, pause and resume a campaign, and enroll the people you choose. |
| Can | Report on results and check the health of every connected number. |
| Cannot | Send a WhatsApp message itself — WarmySender’s scheduler paces every message with a natural pause between them. |
| Cannot | Raise the daily, first-message or hourly budget, or shorten a new number’s ramp. |
| Cannot | Connect or disconnect a WhatsApp number — that stays in the app. |
| Cannot | Fire messages in a burst — a large enrollment drains at the number’s safe pace. |
| Cannot | Read or reply to conversations — replies stay in WarmySender’s inbox, with you. |
OpenAI's coding agent registers WarmySender with one command and signs in through your browser — no key to paste.
Run both lines in your terminal; the second opens your browser to sign in to WarmySender.
codex mcp add warmysender --url https://warmysender.com/mcp
codex mcp login warmysenderPrefer a key? Create one under Settings › API Keys and choose exactly which permissions it carries, including read-only. With a key, the Codex route is: Run both lines, adding the export to your shell profile so it sticks.
Both routes reach the same workspace and stay inside the same safe limits. Every agent's steps live on the AI Agents hub.
Create a WhatsApp campaign on my business number: a short intro, then a follow-up three days later if they have not replied, and enroll this list.
Pause every WhatsApp campaign until the new number has finished ramping.
How is my WhatsApp number doing today, and how many first messages does it have left?
Show me reply rates for every WhatsApp campaign this month.
Build a WhatsApp campaign for the numbers in contacts.csv on my business number and print how many first messages the number has left today.
Codex never sends a message itself and can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits and a gradual ramp — the same protections that apply when a human clicks the buttons. Connecting and disconnecting accounts stays in the app. Account safety always wins.
Yes. Connect Codex to WarmySender and ask in plain language, in the Codex terminal — it can build, launch and manage your WhatsApp campaigns. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
OpenAI's coding agent registers WarmySender with one command and signs in through your browser — no key to paste. Run both lines in your terminal; the second opens your browser to sign in to WarmySender. The command text is: codex mcp add warmysender --url https://warmysender.com/mcp codex mcp login warmysender — the server address is https://warmysender.com/mcp. The steps are on this page under "Connect Codex", and the full install hub for every agent is at /ai-agents.
No. Nothing an agent can call moves a limit — not the daily, first-message or hourly budget, or a new number’s ramp. Codex can read where you are against a limit and tell you when a pause lifts; WarmySender’s scheduler decides what actually goes out.
No. Connecting and disconnecting accounts stays in the app on purpose — a credential should never pass through an agent or a chat log. Connect the WhatsApp number once in WarmySender; after that Codex can use it.
No. New numbers ramp up gradually and stay within a safe daily, first-message and hourly budget with a natural pause between messages, whether a person or an agent created the campaign. The agent can tell you where the number is on its ramp and when it picks up again; it cannot move it.
No. The add command registers the server address https://warmysender.com/mcp and the login command opens a browser sign-in — nothing to paste or store. Prefer a key anyway? Create one under Settings › API Keys and use the key form on the AI Agents hub.
No. Codex only writes the campaign or the setting; once it has handed that to WarmySender, the scheduler paces every WhatsApp message on its own whether or not Codex is running.
Yes. Each client registers the server and signs in on its own; they reach the same workspace and the same safe limits, and the scheduler paces every WhatsApp message exactly the same whichever agent wrote the campaign.
Last updated: 2026-09-09