Back to browse
GitHub Repository

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.

8 starsTypeScript

Palmier – bridge your AI agents and your phone

by caihongxu·Apr 21, 2026·7 points·8 comments

AI Analysis

●●●BangerZero to OneShip ItSolve My Problem

Phone as both agent remote and agent tool — genuinely new infrastructure for local AI.

Strengths
  • Two-way bridge is novel: phone controls agents AND agents access phone capabilities
  • MCP server integration means agents can call phone tools as native MCP endpoints
  • No API keys or GCP setup required for basic phone-to-agent communication
Weaknesses
  • Requires Node.js 24+ which is still bleeding-edge for many production environments
  • Agent CLI support limited to 15+ tools — gaps for custom or proprietary agents
Target Audience

Developers running AI agents locally who need mobile access and control

Similar To

OpenClaw · Continue · Cline

Post Description

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.

Similar Projects

Developer Tools●●Solid

Built two remote tools for coding agents (one in a night)

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.

Niche GemSolve My Problem
Geddydukes
104mo ago
Developer Tools●●Solid

AgenticMail – Email, SMS, and multi-agent coordination for AI agents

Hands-off: each agent gets its own mailbox, phone number, inbox and API key, and the project bundles a local Stalwart mail server in Docker plus Gmail-relay or custom-domain outbound with DKIM/SPF/DMARC. Concrete safety features (outbound scanning to catch API keys/PII) and Google Voice SMS extraction for verification codes are genuinely useful and uncommon together. If you want to prototype agents that actually talk to people/services this is a focused, pragmatic stack — but expect telephony fiddliness and compliance trade-offs in real deployments.

WizardryNiche Gem
agenticmail
213mo ago