Claude Sonnet 4.5
Meeting Recap
Turns a recording into decisions and to-dos
Knows
MeetingsRecap template.pdf
Can
Writes notesMemory
Agents for project 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 project file: 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 an hour before a steering meeting 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.
Deliverables
Three things that stop falling through the gap
Not a feature list. What changes when the meeting, the actions and the risks live in one place.
The actions get written up an hour after the meeting, from memory.
Actions written while people are still talking
Record the meeting and ask for the decisions and owners as soon as it ends.
The status update means reopening every note from the week.
Status updates from your own notes
Ask what moved this week across a project folder and get a summary you can send.
The decision is in the notes, the task in the tracker, the file in email.
Nothing falls through the gap between tools
Checklists, notes, attachments and transcripts all live in the same note.
A sprint
What that looks like for project managers
Three points in a cycle where the app closes a gap.
01
Weekly meeting
Record it, get the transcript, ask for the action list and tick items off in the note.
02
Risk review
Keep a note per risk, linked to the meetings where it moved.
03
Reporting
Ask for a status summary built from this week and export it.
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.
Do not also transcribe it.
Record the standup, get the actions out of the transcript, and keep every risk, decision and follow up in a library you can search by meaning.