Campfire SMS
Campfire SMS lets you answer task questions from your phone. It does not authorize restricted tools or replace native Codex and Claude Code permission approvals. For those prompts, use the approval interface your agent provides.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThis needs a production action outside the current permissions. I paused that step.
SMS INLeave the patch ready. I'll review the production request in the agent.
RESULTPatch and validation notes saved. Production step remains paused.
Your phone
Campfire SMS: This needs a production action outside the current permissions. I paused that step.
You: Leave the patch ready. I'll review the production request in the agent.
Campfire SMS: Patch and validation notes saved. Production step remains paused.
First identify what the agent is asking
| Question from the agent | What an SMS reply can do |
|---|---|
| Should I keep the existing API? | Clarify the design within the agreed task. |
| Add another regression test? | Steer already-permitted work within scope. |
| May I run a restricted command? | Discuss the request; native permission approval is still required. |
| Can I deploy or change production? | Communicate your intent; the action still needs the host's required authorization and approval path. |
A phone reply can resolve an ordinary task choice when the agent already has permission to do the work. If the action requires a native approval, the text does not satisfy that control. The agent should explain what is waiting and preserve the paused step.
Codex permission prompts
Codex has its own sandbox and approval settings. See the official sandboxing documentation for how those controls work in your environment. Connecting an SMS tool does not change the configured boundary.
Ask Codex to text a summary of a blocked request and leave the evidence ready in the workspace. Review the request through an interface that actually supports the native approval. Do not assume a remote messaging bridge or SSH window provides that capability for every Codex client.
Claude Code permission prompts
Claude Code also controls tool access in its own environment. Campfire SMS carries messages through MCP; it is not a permission-granting API. If you need a session view from another device, consult Anthropic's Remote Control documentation and its current capabilities.
For SMS, have the agent distinguish “I need your preference” from “I cannot run this action without native approval.” That makes a phone notification actionable without suggesting that the text bypasses the prompt.
Give the agent a useful stopping rule
Use Campfire SMS for task clarifications and status updates. If a tool action needs native approval, summarize the request by text and pause that action. Continue any independent work already within scope. Never treat a text reply as a new tool permission or a replacement for the host's approval process.
This lets you answer ordinary choices while leaving important actions in the place where you can inspect them. A useful SMS might say “the patch is ready; deployment is waiting for your review.”
Set up a decision loop before leaving
Connect Codex or Claude Code, then test a harmless question and reply. Specify the work the agent may do, the events it should text about, and the actions that must wait.
Keep the local host awake and the session active. Keep passwords, credentials, and sensitive data out of messages. Use the workspace for the detailed request, diff, and validation evidence.
Common questions
Does replying YES approve a restricted command?
No. A Campfire SMS reply does not replace the agent client's native permission approval.
What can I decide by SMS?
You can clarify the task, choose among permitted approaches, narrow the scope, or ask for a summary. The agent still checks scope and native permissions before acting.
Can the agent continue while one action waits?
It may continue independent work already authorized and allowed by its host. Give it a stopping rule for the action that needs approval.