Campfire SMS
Claude Code Remote Control connects a local session to Anthropic's web and mobile interfaces. Campfire SMS adds short updates and replies through cellular SMS. Choose a session view when you need it, and texting when a brief exchange is enough.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe frontend build passes. Should I add the small-screen layout fix too?
SMS INKeep this change to the build issue. Leave the layout fix for later.
RESULTScope kept to the build fix. Diff ready for review.
Your phone
Campfire SMS: The frontend build passes. Should I add the small-screen layout fix too?
You: Keep this change to the build issue. Leave the layout fix for later.
Campfire SMS: Scope kept to the build fix. Diff ready for review.
An existing session does not need a new home
Claude Code already knows your local repository, tools, and task. Campfire SMS adds phone contact to that environment. You verify your phone and register MCP, then keep using Claude Code where you already work.
Anthropic's native Remote Control can also preserve local context. The difference to evaluate is how you want to interact from your phone, rather than whether you can keep your repository.
Compare the phone interfaces
| Question | Claude Code Remote Control | Campfire SMS |
|---|---|---|
| Phone interface | claude.ai/code or the Claude mobile app. | Your normal SMS inbox. |
| Interaction | A connected view of the local session. | Short messages the active agent sends and retrieves. |
| Existing local tools | The local environment stays available. | The same agent continues using its existing tools. |
| Connection | A running local process and internet access. | An active local agent, internet on the host, and SMS service on the phone. |
| Native permissions | Use the approval controls available in Claude Code. | SMS does not replace Claude Code's native approvals. |
Anthropic explains the native feature in its Remote Control documentation. Availability and organization settings can affect that route; check the current requirements there.
Try native Remote Control for a session view
Follow Anthropic's setup in your existing repository. Its CLI entry point is:
claude remote-controlUse the documented connection flow to open the session from your other device. This route is useful when you want more of the conversation and development context visible on the phone.
Try SMS for a short decision loop
Use Claude Code SMS setup, then ask the active agent to send a test question and retrieve your reply. Confirm that it acknowledges the handled message and responds.
Finish the build fix in this repo. Use Campfire SMS for task questions, blockers, and the final result. Check my replies while working. Keep detailed diffs here and preserve the current scope and native permission controls.
This is useful when you want to answer “keep it small” from your ordinary inbox and let the agent continue the work it already understands.
Keep the host running
Both local workflows depend on the computer running Claude Code. Anthropic's documentation says the local process must remain running for Remote Control. The Campfire SMS route also needs an active agent that checks its message queue.
Texting does not provide a terminal, start a stopped local process, or make native permission prompts disappear. Decide what work may continue and where it should stop before leaving the desk.
Common questions
Is Campfire SMS a replacement for Claude Code Remote Control?
It is an SMS option for short messages, not a complete session interface. Use Remote Control when the web or mobile view better fits the work.
Can both use my existing local repository?
Yes. Native Remote Control preserves the local environment, and Campfire SMS connects to your existing agent through MCP.
Can I handle native Claude Code permissions through SMS?
No. A Campfire SMS reply is a task message. Native permission requests remain subject to Claude Code's approval controls.