What use cases/features are good to ship
how many times been asked for ?
https://notes.granola.ai/t/778001c4-a7c6-42cc-ad7c-4b4ed98613c0
The big highlights were this person decided to use mobile, where some of the formatting issues showed up. This is what they look like.
Thier first question was to ask about bitcoin, which replied with BITCOIN the ticker and that is, sadly, a memecoin on Ethereum.
https://notes.granola.ai/t/b12f45b2-1cb5-425c-8d22-3917705d8285-00b881l8
what I’d personally want next (prioritized roughly in order of how much it would move the needle for me as a power user):
Memory / Context Persistence (the #1 thing I kept wishing for) Right now every new session feels stateless. As soon as I want the agent to “remember what we were working on yesterday” or reference files I uploaded last week, it can’t. Giving agents long-term memory (even just per-user vector store + simple CRUD UI) would 10x the usefulness overnight. This is the single biggest thing holding back every agent framework I’ve tried. File Upload + Persistent Knowledge Base Let me drag-and-drop a folder of PDFs, Notion exports, code repos, etc., and have the agent index it once and forever have it as “my stuff.” Being able to say “referring to the docs in my folder X” or “compare this new design against the brand guidelines I uploaded” would be killer.
Multi-Agent / Team Mode (this is the moonshot) Let me spin up a “team” of specialized agents (researcher, coder, designer, PM) that can message each other and collaborate on a project. Even a baby version of this (like CrewAI but actually reliable and in your UI) would be insane. Better Task Planning Visibility When I give it a big hairy goal, show me the plan it’s making before it sprints off. Let me approve/edit/reject steps. The current “here’s what I’m about to do” preview is good—make it mandatory and richer for anything over, say, 5 steps. Reliability & Re-run Fixes When something fails halfway through a 12-step task, give me a one-click “resume and fix the part that broke” instead of starting over. Also, surface logs in a way a non-engineer can understand (“Step 4 failed because the webpage changed layout – here’s the new HTML snippet”).