Campfire SMS
Campfire SMS connects your verified phone to an active Codex session through MCP. Codex keeps using its current workspace and tools; you get short updates and can send instructions back.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe parser fix is ready. Should I add coverage for empty input?
SMS INYes, add the empty-input case and rerun the tests.
RESULTAdded. Tests pass; the diff is ready in your repo.
Your phone
Campfire SMS: The parser fix is ready. Should I add coverage for empty input?
You: Yes, add the empty-input case and rerun the tests.
Campfire SMS: Added. Tests pass; the diff is ready in your repo.
Add texting to the Codex you already use
You have a repository open, Codex understands the task, and your development tools are set up. Leaving your desk should not mean rebuilding that environment inside another agent app. Campfire SMS adds a messaging connection to that workflow.
The work remains on the computer or VM running Codex. There is no Campfire SMS project to create, repository to import, or second coding model to configure. You still create a Campfire SMS account, verify your phone, and connect the computer once.
Connect Codex to SMS
You need a verified Campfire SMS account, Node.js 18+, Python 3.12+, and the computer where your agent already works. Start with local-agent setup. Copy the one-time command from your account:
npx -y @campfiresms/setup YOUR_INSTALLATION_CODEYOUR_INSTALLATION_CODE is a placeholder. Your actual command is single use and expires after ten minutes. Setup saves the device credential in your user profile; you do not need to put it in your repository.
Setup registers a detected Codex CLI. Open or restart Codex in the repository you already use, then check the connection:
codex mcp listIf Codex was not detected, register the local STDIO command printed by setup in your client's MCP settings. Codex's official MCP guide explains the command and settings options.
On Linux or a VM, follow the virtual-environment instructions before installing. Run setup as the same user who runs the agent.
Test a reply before leaving your desk
- Complete the account's SMS test and reply TEST.
- Ask Codex to open its Campfire SMS bridge and text a harmless question.
- Reply from your verified phone and have Codex retrieve the message.
- Ask it to acknowledge the handled message and send a short confirmation.
A text reaching your phone proves outbound delivery. Codex responding to your reply proves the working return path.
Give Codex a task and a texting rule
Fix the parser issue in this repo. Use Campfire SMS to text me when you need a task clarification or have a result ready. Check my replies during the task and acknowledge messages after handling them. Keep working within the permissions and scope we already agreed.
Useful replies include “add a regression case,” “keep the public API unchanged,” and “leave the changes ready for review.” Detailed diffs and native approval prompts remain in Codex. Keep the host awake, online, and the agent active; installing MCP alone does not schedule reply checks or start stopped sessions.
Common questions
Does this run Codex on my phone?
No. Codex runs in its existing environment. Your phone sends and receives SMS instructions and summaries.
Do I have to create a new project?
No Campfire SMS project or code import is required. Connect your computer and use Codex in the repository you already work in.
Can I approve Codex permission prompts by text?
Campfire SMS carries task instructions, not native permission approvals. Codex's approval controls still apply. Read the phone approvals guide for the distinction.