Campfire SMS
Guides / Local agents

How to get SMS notifications from your coding agent

Connect Campfire SMS to your coding agent, test two-way texting, and ask for useful task updates.

This guide covers a running local agent. For a text that starts a cloud Bot run while your PC is off, use Grok Bot webhook wake.

When a coding task takes longer than a few minutes, you may want a text when it finishes or needs your input. Campfire SMS’s local connector connects your verified phone to an already-running coding agent. You use your usual SMS app to receive short updates and send instructions back.

What you need before you start

Have a supported coding agent installed on the computer that will do the work, a phone that can receive SMS, Node.js 18+ with npx, and Python 3.12+ for the local connector. Your computer needs internet access and must remain awake with the agent active. Your phone needs cellular SMS service; mobile data is not required for the text exchange.

Campfire SMS carries messages. It does not run a separate coding model or automatically watch every task on your computer.

1. Connect your phone and computer

Follow local-agent setup and verify your phone number. Copy the temporary installation command shown by Campfire SMS and run it on the computer where you use your agent. It has this form:

npx -y @campfiresms/setup XXXX-XXXX

XXXX-XXXX is a placeholder, not a working code. Use the command from your account; it is single use and expires after ten minutes. The installer registers the connector with the supported local agents it finds and stores the installation credential locally. Open or restart your agent afterward.

The install guide covers the complete setup flow and removal instructions.

For the tool-level workflow, see MCP SMS notifications and human replies.

2. Test both directions

Follow the setup test: send the test message, then reply TEST from your verified phone. Wait for the setup confirmation before relying on task updates. Receiving a text proves only one direction works; the reply checks the return path too.

3. Tell your agent when to text you

Give the agent a concrete task and describe which events deserve a message. For example, adapt this prompt to your repository:

Investigate the failing tests and fix the issue within the scope we've discussed. Use Campfire SMS to send a short update when you have a result, hit a blocker, or need clarification. Check for my replies while you work. Keep updates brief and close the bridge when we're finished.

This asks the agent to use the connection for that task. The local connector does not wake an arbitrarily idle agent, so sending a text to a stopped session is not a reliable way to restart work.

Use a focused rule for build completion texts, PR notifications, or questions that need your input. If you need a future notification after the session ends, compare agent notifications and scheduled reminders.

What an update can look like

The following is an illustrative exchange, not a recorded test result:

Agent: The test failure comes from date parsing. I have a fix and am running the suite.
You: Include a regression case for an empty date.
Agent: Added the case. The suite passes. Changes are ready for your review.

Text is useful for progress and short clarifications. Review detailed diffs in your coding environment. SMS replies do not replace native runtime approvals or grant the agent additional permissions.

If no update arrives

SMS delivery can be delayed. Keep passwords and sensitive material out of texts: SMS is not end-to-end encrypted. For account or delivery help, contact support.

Try it on one bounded task

Start with a small fix or test run, confirm the round trip, then try a longer session. Read how to monitor an agent away from your desk for a task handoff you can adapt.