Let agents send/receive SMS using your old Android phone
Old Android + prepaid SIM beats Twilio for agent SMS with real phone numbers.
Run AI agents on your computer and dispatch tasks from anywhere, approve actions on the go, and let agents tap into phone capabilities like notifications, SMS, contacts, and calendar.
Phone as both agent remote and agent tool — genuinely new infrastructure for local AI.
Developers running AI agents locally who need mobile access and control
OpenClaw · Continue · Cline
Palmier bridges your AI agents and your phone.
It does two things:
1. It lets you use your phone to directly control AI agents running on your computer, from anywhere.
2. It gives your AI agents access to your phone, wherever you are — including things like push notifications, SMS, calendar, contacts, sending email, creating calendar events, location, and more.
A few details:
* Supports 15+ agent CLIs
* Supports Linux, Windows, and macOS
* What runs on your computer and your phone is fully open source
* Works out of the box — no need to set up GCP or API keys just to let agents use phone capabilities
* Your phone can act as an agent remote: start tasks, check progress, review results, and respond to requests while away from your desk
* Your phone can also act as an agent tool: agents can reach into phone capabilities directly when needed
* Optional MCP server: if you want, Palmier exposes an MCP endpoint so your agent can access phone capabilities as native MCP tools. This is optional — you can also use Palmier directly from the phone app/PWA, with those capabilities already built in
* Still in alpha stage, with bugs. Opinions and bug reports very welcome
The basic idea is that AI agents become much more useful if they can both:
* interact with the device you actually carry around all day
* be controlled when you are away from your computer
Palmier is my attempt at that bridge.
It already works with agent CLIs like Claude Code, Gemini CLI, Codex CLI, Cursor CLI, OpenClaw, and others. You can run tasks on demand, on a schedule, or in response to events.
Would especially love feedback on:
* whether this feels genuinely useful
* which phone capabilities are most valuable
* which agent CLIs I should support next
* what feels broken, awkward, or confusing
Site: https://www.palmier.me
Github:
* https://github.com/caihongxu/palmier
* https://github.com/caihongxu/palmier-android
Happy to answer questions.
Old Android + prepaid SIM beats Twilio for agent SMS with real phone numbers.
This turns agent I/O into real phone-first interactions: when a local CLI agent needs input you get an SMS/Telegram/iMessage prompt and can reply to continue the session. The multi-provider notifier plus per-session PTY state (node-pty + optional tmux + a SQLite/JSON store) is thoughtful engineering for this exact problem, and the companion T-Lite for Tailscale-only mobile SSH shows the author iterated on UX pain points instead of shipping an awkward control plane. It's not revolutionary, but it's a tidy, opinionated solution that I'd use if I had recurring headless agent runs.
One MCP endpoint gives agents real phone numbers and email—no Twilio hell.
Build SMS AI agents without managing Twilio state or human handoff logic yourself.
Seven unanswered audio alerts trigger a phone call — works through iPhone Silent Mode.
MCP server for agent comms beats wiring Twilio, SES, and LiveKit manually every time.