Hermes Agent SMS Integration: Twilio Text Message Agent Setup
Connect Hermes Agent to SMS with Twilio so trusted phone numbers can trigger short requests, alerts, and fallback workflows.
Quick answer
SMS is best for short, urgent, low-context workflows: alerts, approvals, status checks, and fallback commands. Use stricter limits than chat apps because SMS has weaker identity and formatting.
Managed cloud · API costs included · No gateway maintenance
Best for
Teams that already coordinate in this chat platform and want Hermes where work is discussed.
Operational alerts and status reports that should reach people without opening a terminal.
Approval workflows where Hermes drafts the action but a human confirms it in chat.
Project-specific agents that need a narrow channel boundary rather than one global bot everywhere.
Features
- ✓SMS gateway access for chat-based Hermes requests
- ✓Allowlisted users, rooms, groups, or contacts before broader rollout
- ✓Tool-backed answers using the same Hermes skills and MCP servers available from the CLI
- ✓Delivery target for cron reports, incident summaries, approval prompts, and project updates
- ✓Profile and credential boundaries so each channel can be scoped to the right trust level
- ✓Private smoke-test flow before enabling production rooms or free-response behavior
Setup path
- 1Create or configure the SMS bot/app/account required by the platform.
- 2Store the token or credentials in the active Hermes profile, not in source control or a shared note.
- 3Run
hermes gateway setupand enable the platform adapter. - 4Restrict allowed users, rooms, groups, or contacts before the first test.
- 5Restart the gateway and send one harmless private test message.
- 6Only after the smoke test, connect project skills, cron reports, MCP tools, or team rooms.
What SMS is good for
SMS should be treated as a human-facing gateway, not the whole automation system. The chat message starts the request, but Hermes can still use files, terminal tools, MCP servers, web search, cron history, GitHub, Linear, Notion, and project-specific skills to do the real work.
- •Ask for a status summary without opening a terminal.
- •Send an incident, support, or operations request from the chat app your team already uses.
- •Receive cron reports, deployment notes, research summaries, or approval prompts in a familiar channel.
- •Keep sensitive tools scoped to trusted chats and profiles instead of exposing every capability everywhere.
Safe setup pattern
The safest rollout is always private first, group later. Configure credentials, restrict who can talk to the bot, prove one harmless request, and only then add production channels or free-response behavior.
- •Create or configure the SMS bot/app account and store credentials in the active Hermes profile environment.
- •Run
hermes gateway setupand enable only the platform you are testing. - •Allowlist one private user or test room before adding team-wide rooms.
- •Send a harmless prompt such as “reply with the active profile and enabled platform name.”
- •After the smoke test, decide whether the channel can use tools, cron reports, file access, or project-specific skills.
Common workflows
Once the gateway is stable, SMS becomes a convenient control surface for Hermes workflows that would otherwise require terminal access. The best workflows have a clear output and a clear permission boundary.
- •Incident triage: summarize the alert, inspect logs or dashboards, and post next actions back to chat.
- •Project updates: ask Hermes what changed in GitHub, Linear, or Notion and receive a concise report.
- •Approvals: let Hermes draft the action and ask for confirmation before sending, deploying, or editing anything sensitive.
- •Knowledge capture: turn a chat thread into a task, document, issue, or reusable skill.
Common setup issues
- No response in SMS — confirm the gateway is running, the platform is enabled, and the chat/contact is allowlisted.
- The bot replies in DM but not in a group — check group permissions, mention/free-response settings, and whether the gateway received the group update.
- The wrong profile or tools are active — verify the Hermes profile running the gateway and keep project-specific secrets in the correct profile.
- Messages are too long or poorly formatted — use concise prompts and route long reports to email, docs, or a file when the platform has tight message limits.
Keep building the workflow
FAQ
Can Hermes run from SMS?
Yes. SMS can be used as a Hermes messaging gateway when the platform adapter is configured and the gateway is running.
Should I enable this in a group immediately?
No. Start with a private or allowlisted test, verify behavior, then add group access only when permissions and response rules are clear.
Can the chat gateway use the same tools as the CLI?
It can use enabled Hermes tools, skills, and MCP servers for that profile. Scope tool access carefully because chat channels often have different trust levels than your terminal.
What is the safest first test?
Ask for a harmless status reply that confirms the active profile and platform. Do not start with file edits, deploys, purchases, or external sends.