Each change comes back as a live preview of your own site, before anything merges[1]. Letter opens the pull request when asked[2], and in one sample run the change was reviewing the change · fixed what the review found[3].
[1] https://letter.dev “Each change comes back as a live preview of your own site, before anything merges.”
[2] https://letter.dev “Letter posts what changed to Slack, and opens the pull request when asked.”
[3] https://letter.dev “**~/website** $ letterpress › add a page comparing us with Rippling for teams of 5 to 50 reading the site · planning the page building in a sandbox reviewing the change · fixed what the review found changed 3 files · app/compare/rippling/page.tsx ✓ pull request opened ·…”
Uses frontier coding agents to solve growth engineering problems across your website[1]. It reads your site and opens its first pull request[2]. Frontier and fine-tuned small models break each request into brand and voice problems, then check the work against brand evals[3].
[1] https://letter.dev “[Start onboarding](https://letter.dev/start)$`npm i -g @letterstory/letterpress` Forward-thinking companies build on Letter ## Letterpress-1 uses frontier coding agents to solve growth engineering problems across your website.”
[2] https://letter.dev/pricing “Letterpress-1 reads your site and opens its first pull request.”
[3] https://letter.dev “Frontier and fine-tuned small models break each request into brand and voice problems, then check the work against brand evals.”
https://ask.letter.dev/how-does-letter-access-our-repository
https://ask.letter.dev/how-does-letter-decide-what-to-build
https://ask.letter.dev/how-does-letter-handle-our-data
https://ask.letter.dev/how-does-letter-get-set-up
All questions: https://ask.letter.dev/
Anything else: https://lettervisit.com/transact/letter.dev?q=<question>