Every is a Love Letter.
Someone cared enough to write. Love Letter gathers every note — from your app, the App Store and your inbox — onto one desk, so each one is read, filed and answered — by you, or by your agents.
All of it on one desk, in the order it arrived.
Filter by tag, version, device, OS or source. A short on-device summary sits on top, so you know what's working and what needs attention before you open a single note.
From “it's broken” to “it's fixed”.
Everything is stored as issues and milestones in your own GitHub repository. No new service to run.
- NO. 1ReceivedThe SDK, an App Store review or an email lands as a labelled GitHub issue, with version, device and OS attached.
- NO. 2ReadApple Intelligence summarizes and translates on your device. A German note reads in English.
- NO. 3FiledAttach it to a task, give the task a priority, and slot it into a version.
- NO. 4AnsweredReply from your own address. On release day, everyone whose note was fixed gets one personal email.
Hand the mail to your agents.
A command-line tool and an AI skill let Claude Code, Codex, Cursor or any agent read, file and answer your feedback. Keep a human in the loop, or don't.
-
NO
HUMANROUTE 1Morning triageA scheduled agent reads the night's mail, links duplicates to existing tasks and files new ones. You read the summary over coffee. -
YOU
REVIEWROUTE 2Bug to pull requestAn agent takes a high-priority bug, reproduces it with the attached device, OS and version, and opens a fix for your review. -
YOU
SIGNROUTE 3Reply on releaseWhen a version ships, the agent drafts a reply to everyone whose note it fixed. You approve each one, or let it send. -
YOUR
RULESROUTE 4Your own pipelineEverything comes out as JSON, so CI, chat, cron or a dashboard can use it. You decide where a human steps in, if anywhere.


Send from anywhere. Arrives the same.
Open-source SDKs for Apple, Android and the Web write a byte-identical GitHub issue, checked against shared golden fixtures in every SDK's CI.