Beeper chats

Beeper Desktop puts your chat apps (WhatsApp, Signal, Telegram, iMessage and others) in one app on your Mac. Pepper reads the chats you connect through Beeper's local API, a connection to Beeper Desktop that stays on your Mac. A newly connected app starts with the past week of messages, not the whole history. Those messages are where most of what Pepper knows about your day comes from. They feed the follow-ups, the briefs, the people, and the answers to your questions.

Pepper only reads. You give it an access token from Beeper, a key that lets it connect, and by Beeper's rules that token can't send or change anything.

1. Install Beeper Desktop on the Mac that runs Pepper, sign in, and add your chat apps. When Beeper offers On-Device Connections, take them. The bridges, which link Beeper to each chat app, then run on your Mac and not in Beeper's cloud. Pepper still sends what it reads to Anthropic to write briefs and find follow-ups.
2. In Beeper Desktop: Settings → Integrations → Beeper Desktop API. Turn Allow connections on, then go to Approved connections → +. Name the token Pepper, set Expires In to Never, and leave Allow sensitive actions OFF.
3. Put it in .env, Pepper's settings file, as BEEPER_ACCESS_TOKEN=… and restart Pepper.
4. Run npm run doctor to check the connection. The beeper line lists your connected chat apps, and the beeper-token line confirms the token is read-only and says when it expires.

Beeper Desktop has to stay open on that Mac. Pepper talks to it at http://localhost:23373; set BEEPER_BASE_URL in .env only if you changed that port in Beeper.

Beeper is one connection with your chat apps listed underneath it. Under each app you see how many chats Pepper has stored, or its status when the app isn't connected. Pepper reads that list from Beeper on every sync, so an app you add in Beeper shows up on its own.