Campfire SMS
An active Codex session connected to Campfire SMS can send SMS updates when you ask it to. Define the events that matter, then test a notification and a reply before relying on it.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe test run finished: 218 passed, 1 failed in the date parser.
SMS INInvestigate the date-parser failure. Keep the API unchanged.
RESULTFound the timezone edge case. Fix and regression test ready.
Your phone
Campfire SMS: The test run finished: 218 passed, 1 failed in the date parser.
You: Investigate the date-parser failure. Keep the API unchanged.
Campfire SMS: Found the timezone edge case. Fix and regression test ready.
Choose events, not a stream of terminal output
A useful phone notification gives you the result and the next decision. Ask for a text when a task finishes, an investigation reaches a conclusion, or the agent needs a clarification. Skip individual commands and ordinary progress chatter.
| Event | What the text should contain |
|---|---|
| Work ready for review | What changed, validation result, and where the diff is. |
| A blocker | What failed, what was tried, and the decision needed. |
| Scope changes | The new issue and whether it fits the agreed task. |
| Routine progress | Keep it in the workspace unless you requested a timed update. |
Connect the session that should send updates
Follow the Codex SMS setup in the same environment where the task runs. The connection is a tool your active agent uses; it is not an automatic watcher for every Codex process or terminal tab.
codex mcp listAfter checking the MCP entry, ask Codex to send a test notification and confirm a reply. Repeat that check if you switch computers or reinstall the connector.
Use a notification brief
Run the agreed tests and investigate failures within the existing scope. Use Campfire SMS to send one short text when you have a final result, need a decision, or cannot continue. Include the test result and next step. Check replies during the task and acknowledge handled messages. Do not text command-by-command progress.
For a long task, you can request a specific milestone update. Phrase it as an instruction to the agent. Campfire SMS installation does not create a timer, hook, or background monitor by itself.
Keep the reply useful
A completion alert is more useful when you can answer it. Text “add coverage for the empty case,” “stop after the tests,” or “leave the patch ready for review.” Codex retrieves the reply through the same bridge and evaluates it against the task's scope and permissions.
Native permission prompts still need the approval path Codex provides. A notification that says the agent needs a restricted action is a reason to inspect that request, not proof that replying “yes” grants permission.
If the text never arrives
Check that Codex is still active, opened the bridge, and was told to send the update. Confirm the computer is awake and online, the installation is valid, and your account has messages available. Ask for a short manual test from the session.
If you received the alert but Codex missed your reply, inspect whether it checked the message queue. Outbound delivery and inbound retrieval are separate steps. The connection troubleshooting guide covers recovery.
Common questions
Does Campfire SMS watch every Codex task automatically?
No. Tell the active agent when to use its messaging tools. Installation alone does not add task hooks, a scheduler, or a monitor.
Can I receive the notification without mobile data?
The text exchange uses cellular SMS service. The computer running Codex still needs internet access.
Can I reply to a notification?
Yes, when the active connected agent checks for replies. Confirm that round trip in the same session before leaving your desk.