Campfire SMS
For short updates and instructions, add SMS to your existing Codex environment. For terminal commands, large diffs, or native permission prompts, use an interface that exposes the development session.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe bug is isolated to timezone conversion. Expand coverage to DST?
SMS INYes. Include the spring transition, then stop for review.
RESULTDST case added. Patch ready; no deployment performed.
Your phone
Campfire SMS: The bug is isolated to timezone conversion. Expand coverage to DST?
You: Yes. Include the spring transition, then stop for review.
Campfire SMS: DST case added. Patch ready; no deployment performed.
Start with the workspace you want to keep
Remote access is useful when it reaches the code, credentials, and tools you already prepared. If Codex is working in your existing repository, connecting that session can be less work than creating a separate hosted agent and recreating its environment.
Campfire SMS adds messaging to an active local Codex workflow. Your account manages the phone and connected computer; the repository stays where Codex already works.
Compare ways to reach Codex
| Method | Use it for | What you set up |
|---|---|---|
| Campfire SMS | Brief task updates, questions, and steering by SMS. | Phone verification and MCP in the existing agent environment. |
| SSH | Terminal access and command-line inspection. | A reachable host, authentication, and a terminal client. |
| Remote desktop | The full desktop, editor, and visual review. | A desktop connection and a device that can use it comfortably. |
| Photon + Render template | A separately hosted Codex agent contacted through iMessage. | A Render deployment, Photon setup, and Codex authentication. |
Photon documents its hosted route in the Codex-on-Render walkthrough. That is a useful option when you want a separate hosted runtime. SMS to your existing agent is useful when the current runtime already has what the task needs.
Set up the SMS route
Follow Codex SMS setup on the computer or VM doing the work. Keep that host awake and connected. Ask Codex to open the bridge, text you, retrieve a harmless reply, acknowledge it, and send a confirmation.
Test from the phone before you leave. Do not treat a server appearing in the MCP list as evidence that the session will check messages throughout a long task.
Hand off a bounded task
Investigate the timezone bug in this repo. Keep changes limited to parsing and tests. Text me through Campfire SMS when you need a task choice or have a result ready. Check replies while active. Leave the patch for review and retain all native approval requirements.
A good handoff includes the permitted work, expected evidence, and stopping point. The agent already has the project context, so your SMS can be a short correction or decision instead of a new project brief.
Keep an interface for work that needs inspection
SMS is useful for “add the DST case” and “leave the patch ready.” It is not a file browser or a full terminal. Review code and native approval requests in the interface that runs Codex.
The local SMS bridge does not wake a stopped session. If you need a text to start cloud work while your PC is off, see the separate Grok Bot webhook-wake setup. That cloud workflow has its own runtime and configuration.
Common questions
Can I use Codex from my phone without SSH?
For short SMS instructions and updates, yes, while the connected agent remains active and checks replies. Full terminal access and native approvals require another interface.
Do I have to move my repository to a hosted agent?
No. The Campfire SMS local connector works with Codex in its existing environment. Install it wherever that agent runs.
Will this work while my workstation is asleep?
No. A local Codex session needs an awake, online host. SMS does not provide compute or restart its process.