Show HN: Palmier – bridge your AI agents and your phone
Posted by caihongxu 7 hours ago
Hi HN — I built Palmier.
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.
Comments
Comment by meetmodi 39 minutes ago
Comment by t_messinis 1 hour ago
Comment by Bridgexapi 20 minutes ago
once you give something the ability to send messages or trigger actions, it’s not just read access anymore, it’s execution on your behalf
it looks simple from the outside, but there’s usually a lot of hidden behavior underneath (routing, timing, provider handling, etc)
so the question becomes less about access and more about how controlled and observable that execution actually is
curious if you’re thinking about exposing that layer, or keeping it abstracted away
Comment by dhruv3006 2 hours ago
Comment by arjunthazhath 4 hours ago