Campfire SMS
What happens when you text Grok Bot
With webhook wake configured, Campfire SMS queues the incoming text and sends a wake event to Grok. Its cloud routine retrieves your message through the hosted MCP, handles the instruction, and can send an SMS reply. Your PC can be off while that cloud routine runs.
Follow the Grok Bot webhook walkthrough to connect the tools and test a real text and reply.
How local-agent connections differ
A running Codex, Grok Build, Claude Code, OpenCode, or other compatible agent can send an update and retrieve your SMS reply through MCP or the HTTP API. The local computer must stay awake and online, and the agent must check for messages. The local connector does not start stopped sessions.
Hosted service or DIY bridge?
Campfire SMS operates the SMS gateway, phone enrollment, authenticated message queue, and routing between your phone and the configured agent. Grok webhook wake is configured through your account.
With a DIY SMS bridge, you operate the provider account, webhook endpoint, credential storage, inbound routing, and connection to the agent. An outbound SMS script can send an alert; receiving a reply and starting agent work require those additional pieces.
Your agent provides its own model, tools, project access, and task execution. SMS instructions stay within its existing permissions; native approvals remain in the agent’s environment.
See setup options, pricing, or the comparison of alerts, SMS replies, and wake.