Beeper as your message hub: Claude pulls promises out of your chats before you forget them

You have Beeper connected via MCP. Try asking it what came in for me
today: go through messages from the last 12 hours across every
network and give me a brief summary — who it's from, which network,
roughly what the message is about. Don't mark anything as read,
don't flag anything, and above all DON'T SEND ANYTHING. Just read
and summarize. If you can't connect to Beeper, tell me exactly what
error came up.

Give me an overview of my Beeper: which networks/accounts are
connected, and for each network the 10 chats with the most traffic
over the last 14 days — chat name, network, roughly how many
messages.
Split them into two groups: work and personal (estimate from the
content, put a question mark on anything uncertain). Don't read
anything aloud in detail, no quotes from private messages — just
chat names and numbers. Don't send anything.

Go through my messages from the last 24 hours across every network
via Beeper and pull out the commitments. Look for three kinds:

1. MY PROMISES — what I promised someone (“I'll send”, “I'll get
   it ready”, “I'll call”, “I'll find out”, “I'll let you know
   by…”).
2. OTHER PEOPLE'S PROMISES — what someone promised me (“I'll send
   you”, “I'll get back to you”, “I'll deliver the materials
   by…”).
3. MEETINGS AND DEADLINES — arranged meetings, calls, deadlines we
   agreed on.

For each finding, give me:
- who and whom (names from the chat),
- exactly what (one sentence),
- by when (convert “tomorrow” and “by Friday” to a specific date;
  today is [date]; if no deadline was stated, write “no deadline”),
- network and chat name,
- the exact quote you're basing this on.

Rules: exclude these chats [names of excluded chats]. Don't mistake
musing (“maybe I could…”) for a promise — only count clear
commitments. When you're not sure, put the finding in a separate
“Needs review” section instead of guessing.
Don't write anything anywhere, don't mark anything as read, and
DON'T SEND ANYTHING — just give me the summary.

MY PROMISES (3)
1. Me → Peter Novak: send the renovation quote
   By: Friday, 8/21 | WhatsApp, chat “Peter Novak”
   Quote: “sure, I'll send you the quote by Friday”
2. Me → Web team: prepare materials for the sprint review
   By: Wednesday, 8/19 | Slack, channel “project-web”
   Quote: “I'll have the materials ready by Wednesday”

OTHER PEOPLE'S PROMISES (2)
1. Jane Miller → me: deliver the landing page copy
   By: Tuesday, 8/18 | Messenger, chat “Jane Miller”
   Quote: “I'll get you the copy on Tuesday, promise”

MEETINGS AND DEADLINES (1)
1. Meeting with Mr. Smith, Thursday 8/20 at 10:00, at their office
   Messenger, chat “Mr. Smith” | “Thursday at 10 at our office?”
   → my reply: “works for me”

NEEDS REVIEW (1)
1. Tom (SMS): “I'll take a look at the flooring next week” — a
   promise with no fixed date, suggest recording it with the
   deadline “next week”.

For finding #[number], give me the whole conversation around the
quoted sentence: 10 messages before it and every message after it
up to now, with timestamps and sender names. I want to judge
whether the promise still stands, or whether someone changed or
canceled it in the meantime. Don't evaluate anything, just the
verbatim transcript. Don't send anything.

Create a new Notion database called “Promises & Commitments” with
these properties:
- Promise (title) — one sentence describing what's supposed to
  happen
- Who (select: Me, Other party)
- Other party (text) — the other person's name
- Due (date)
- Network (select: WhatsApp, Messenger, Instagram, Slack, Signal,
  LinkedIn, SMS, Telegram, Discord, Other)
- Chat (text) — the conversation's name
- Quote (text) — the exact sentence from the message
- Status (select: New, Confirmed, Done, Canceled; default New)
- Logged (created time)
Add a “Calendar” view based on the Due property, a “Overdue” view
filtered to Due in the past and Status not Done or Canceled, and
a “My promises” view filtered to Who = Me. Don't create anything
else.

Take the commitments from the last scan and prepare an entry into
the Notion database “Promises & Commitments”.

First, show me a table of the rows you're about to create, in the
database's column format. Check for duplicates: if a row with the
same other party and the same promise already exists in the
database, don't create it again — propose a deadline update instead,
if the date changed.

Wait for my approval. Only once I type “write” should you create
the rows, and then tell me exactly what you wrote, with links to
the new items. Never write anything I haven't approved, never
delete anything in the database, and DON'T SEND ANYTHING to Beeper.

Here's today's summary of commitments from my chats:

[paste the MEETINGS AND DEADLINES section from the scan output]

Propose calendar events for these on my Google Calendar: title in
the form “Name: what” (e.g., “Smith: meeting at their office”), the
correct date and time, and an all-day event for anything without a
time. Put the quote and the network it came from in each event's
description. Check for conflicts with my existing calendar and list
them. Show me the list of proposed events and only create them
after I explicitly approve.

Instead of Notion, keep my promises in a file called promises.md
in this folder. Structure: a heading for the week, with bullets
underneath in the form
- [ ] DUE | WHO WHOM | WHAT | network/chat | "quote"
Mark completed promises with a checkmark - [x], never delete them.
Take the commitments from the last scan, show me which lines you're
about to add, and append them to the right place after I approve.
Sort by due date. Don't send anything.

Daily promise check. Today is [date].
1. Go through messages via Beeper from last night onward, across
   every network except these chats: [list of excluded chats].
2. Pull out commitments (my promises, other people's promises,
   meetings) in this format: who and whom, what, due date,
   network/chat, exact quote.
3. Compare against the “Promises & Commitments” database in Notion:
   what's new, what's a duplicate, where the deadline moved.
4. Check the existing database: which promises are due today or
   overdue — list these separately as “ON FIRE”.
5. Show me a proposal of what to write and change. Only write after
   I say "write".
Don't send anything, don't delete anything, don't mark anything as
read.

From now on, when scanning for promises, work EXCLUSIVELY with
this list of chats and don't open or search any others:
[list of allowed chats — e.g. “Peter Novak (WhatsApp)”,
“project-web (Slack)”, “Mr. Smith (Messenger)”]
If completing the task would require going outside this list, stop
and tell me — never do it on your own. Confirm that you understand
the rule and repeat the list back to me.

Go through the “Promises & Commitments” database for items where
Who = Other party and Status isn't Done or Canceled, and the due
date is today or in the past. For each one, check in Beeper whether
it's since been fulfilled or the deadline moved — if so, propose a
status change.
For the rest, draft short, friendly reminders in my voice (one per
network, matched to that chat's context), referencing the original
arrangement. DON'T SEND ANYTHING — just give me the texts, I'll
send them myself from my own apps.