Claude Sonnet 4.5
Meeting Recap
Turns a recording into decisions and to-dos
Knows
MeetingsRecap template.pdf
Can
Writes notesMemory
Agents for product managers
Make your own AI agents for your notes
Make an agent for every job.
Set up an agent once for the job you do every week with a quarter of notes: how it should write, the model it answers with, the folders and files it reads first and the tools it may use. Pick it from the title of any chat in the middle of planning and it already knows the brief.
Instructions, a model, knowledge and tools, set once for every chat with it
One agent can answer with Claude and another with GPT, from the keys you added
Folders stay up to date, and files take PDFs, pictures and text, 20 of up to 20 MB
Each tool is a switch, and a tool that is off is never used, even when you ask
A locked note and anything in Recently Deleted never reach an agent
Synced with your settings, so the agents on the laptop are on the phone too
Brief it once
Write how it should work the way you would brief a person. It follows that in every chat you have with it.
Its own model and files
Claude for one agent and GPT for another, each with the folders, notes and PDFs it should read first.
Pick it from the title
Switch any chat to an agent from its title, on the laptop or the phone. Its face stays with its chats.
Tools are switches
Web search, writing notes, filing them, images and memory each have one. A tool that is off is never used.
A face that shows its work
It watches while you type, thinks and reads while it works, and hops when the answer is in.
On every device
Agents sync with your settings, with their faces, files and order, so the phone has the same team.
Ideas
Six Agents Worth Making First
Each one is a few lines of instructions, a model and the notes it should know. Settings has examples to start from, and every new agent comes with a face of its own.
Outcomes
Three things that stop living in your head
Not a feature list. What changes when six meetings a day land somewhere that can answer back.
The follow ups are in your head until the next call pushes them out.
Get the follow ups out of the meeting
Record, then ask for what you agreed and who owes what, before the next call starts.
Someone asks why it was built that way and the doc is called Untitled.
Answer why we built it that way
Search by the decision, not the doc title, and get the note that explains it.
Ten customer calls, ten transcripts, and no time to read them.
Turn ten customer calls into one theme
Ask what came up repeatedly across a folder of interviews and get it summarised.
A quarter
What that looks like for product managers
Three points in a planning cycle where the app changes the work.
01
Discovery
Record every call into one folder and let search do the pattern finding.
02
Spec writing
Draft in the note where the research lives and link to the decisions it depends on.
03
Planning
Ask for a summary of everything you captured about an area this quarter.
The rest of the app
What Else Grape Does
Every part of the app is built around the same idea: keep what you write, and hand it back when you need it.
Leave with the notes written.
Customer calls, specs, decisions and the reason behind them in one searchable library, so the context does not live in your head or in a chat thread.