Campfire SMS
Ask your active Claude Code session to send an SMS when the work is ready, a blocker appears, or it needs a task decision. Campfire SMS carries the alert and your reply; Claude Code keeps doing the work.
- Your existing agentYour repo, tools, and runtime
- Campfire SMSUpdates out · replies back
- Your phoneYour normal SMS inbox
Your agent
SMS OUTThe dependency upgrade passes unit tests. One integration test needs a fixture decision.
SMS INKeep the old fixture. Show me the failing assertion when I return.
RESULTOld fixture preserved. Changes and the remaining failure are documented.
Your phone
Campfire SMS: The dependency upgrade passes unit tests. One integration test needs a fixture decision.
You: Keep the old fixture. Show me the failing assertion when I return.
Campfire SMS: Old fixture preserved. Changes and the remaining failure are documented.
Specify what deserves an interruption
If Claude Code is upgrading dependencies while you step out, you probably want the outcome, not every install command. A notification rule should name the event and the information you need to decide what happens next.
| Trigger | Useful message |
|---|---|
| Done | The completed work and which checks passed. |
| Needs input | The exact choice and the agent's suggested next step. |
| Blocked | The blocker and what can continue independently. |
| Native approval required | A summary telling you to inspect the approval in Claude Code. |
Connect the Claude Code session
Use the Claude Code MCP setup to register the Campfire SMS connector with your existing environment. Check the server, restart the client, and complete the account's test flow:
claude mcp listThen have Claude Code text a harmless update, retrieve your reply, acknowledge it, and confirm by SMS. A registered MCP entry alone does not prove the agent is listening for replies.
Give it a compact notification policy
Upgrade the dependencies we discussed. Use Campfire SMS for the final result, a blocker, or a task question I need to answer. Include the relevant check result and a clear next step. Check my replies during active work and acknowledge messages after handling them. Keep routine logs and detailed diffs in the repo.
This policy works with the task context already in Claude Code. You do not need to create a separate notification project or teach another agent about your repository. The computer must stay awake and the local session must remain active.
Reply with scope, not a wall of context
“Keep the old fixture,” “only change the parser,” or “pause after this test” is enough for a session that already understands the task. Leave large files, screenshots, and detailed code review for the development environment.
Your reply is retrieved by the agent, not injected as a shell command. Claude Code retains its native tool and permission controls. If you need to inspect and interact with the session through a web or mobile interface, use the Remote Control comparison.
Check the connection before a longer run
Start with a small task. Confirm the completion alert arrives and that a reply reaches the same active agent. If delivery stops, check the bridge, computer connectivity, installation status, and message balance. If only replies fail, ask the agent whether it is checking its inbox.
A prompt is an instruction to the session. It does not install a background notification daemon, guarantee a check interval, or restart Claude Code after the process exits.
Common questions
Does this require the Claude mobile app?
No separate phone app is needed for Campfire SMS. Your normal SMS inbox handles the text exchange.
Can a completion notification include a full diff?
Use SMS for the summary and next step. Keep detailed diffs and logs in the workspace for review.
What happens when Claude Code stops running?
It cannot send updates or retrieve replies until the local runtime is available again. Campfire SMS does not wake stopped local sessions.