Campfire SMS
SMS is useful for brief updates and replies through your normal text inbox. A managed iMessage integration can add richer messaging features. Either channel still needs an agent runtime, task context, and a working reply path.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe test suite passes. Do you want the small cleanup included?
SMS INLeave the cleanup out. Keep the patch focused.
RESULTCleanup excluded. Patch ready in the same workspace.
Your phone
Campfire SMS: The test suite passes. Do you want the small cleanup included?
You: Leave the cleanup out. Keep the patch focused.
Campfire SMS: Cleanup excluded. Patch ready in the same workspace.
The channel and the coding workspace are separate choices
A coding agent needs files, tools, context, and a place to run. A messaging channel carries the questions and answers. You can change the phone interface without changing where the coding work happens.
With Campfire SMS, the existing agent sends updates and retrieves replies through a bridge. Your local repo is still the source of the work. A new messaging project or cloud coding workspace is not required.
Compare the short-message experience
| Question | SMS with Campfire SMS | Managed iMessage integration |
|---|---|---|
| Phone interface | The phone's normal SMS inbox with cellular SMS service. | An iMessage-capable messaging interface. |
| Typical payload | Brief task summaries and instructions. | Text and richer features supported by the provider. |
| Example agent connection | Local MCP connector to an existing coding agent. | Messaging SDK or a hosted agent template. |
| What remains necessary | An available runtime and agent message checks. | An available runtime and an inbound-message handler. |
| Permissions | The coding agent's native controls remain in effect. | The coding runtime still needs its own authorization controls. |
Photon documents a managed iMessage Codex example. Its platform overview describes richer channel features and SMS/RCS fallback. Hosted iMessage through Photon does not require maintaining your own Mac server.
Choose SMS when the decision fits in a text
“The tests pass; add one more case?” is a natural SMS exchange. So are “pause after this step,” “keep the public API,” and “send me the result.” You can answer without a separate phone app and let the existing agent continue within its task permissions.
SMS does not require mobile data for the text exchange, but it does require cellular SMS service. The computer running the agent still needs internet access. Delivery can be delayed, so keep an inspection interface available for urgent or detailed work.
Choose richer messaging when the product needs it
If you are building an application around attachments, richer conversation behavior, or multiple messaging channels, a messaging SDK and provider platform may fit that product. The setup is an application integration rather than only an extra contact method for a current coding session.
For a full code diff or terminal view, use the agent's development or remote interface. Richer messaging alone does not make a phone thread a complete coding environment.
Verify the whole conversation
Whichever route you choose, check more than an outbound alert. Send an update, reply, confirm the correct agent retrieves it, and verify it handles the reply once and sends a confirmation. Make sure the workspace and stopping point are the ones you intended.
For Campfire SMS, start with Codex setup or Claude Code setup. Keep the local runtime active. SMS is not end-to-end encrypted; use it for task summaries and keep secrets out of the thread.
Common questions
Do I need an iPhone for Campfire SMS?
No. The phone needs SMS service, so the text workflow can use an iPhone or an Android phone.
Do managed iMessage agents always need my own Mac?
No. Photon offers managed infrastructure and documents a hosted Codex example that does not need your own Mac server.
Does a messaging channel keep my coding agent running?
No. Messaging carries the exchange; compute, process availability, task state, and native permissions remain runtime responsibilities.