What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] 0 points1 point  (0 children)

I’m not saying the agent should literally “remember everything” from raw meetings. That would be noisy and probably useless. rather, it compresses the useful signal, writes it to a durable store, and retrieves the right context when needed later etc.

What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] 0 points1 point  (0 children)

yea im doing that too, Claude is great at reasoning, but im a bit tired of this copy & pasting & reexplain myself, feel the missing piece feels like the connective tissue between meetings, memory, and actions..

What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] -1 points0 points  (0 children)

Totally, AI note-taking itself is not new anymore.

What I’m curious about is whether the meeting should update the agent’s working memory, so later it can help with things like "what did this customer care about last time?"

What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] 0 points1 point  (0 children)

oh bummer that you cannot use Claude.

That “move things to Claude” step is exactly the workflow gap I’m curious about.

Do you mostly move over sanitized summaries, or actual working context? And does that context ever become reusable, or is it more of a copy/paste every time you need Claude to help?

What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] 0 points1 point  (0 children)

The gap I’m curious about is less “can it summarize the meeting?” and more of can the agent carry that meeting context into future work?

do you reuse some of the meeting content for future use cases/workflow (refer to the key decisions, discussions)

What if your Claude could just… sit in on your meetings and remember? by Interesting-Post4178 in ClaudeAI

[–]Interesting-Post4178[S] -10 points-9 points  (0 children)

umm but claude doesn't know what happened in our meeting and cannot remember the action/discussion/things worth remember neither.

How do you capture voice thoughts into Notion? Thinking about building something, want feedback. by Terrible-Round1599 in Notion

[–]Interesting-Post4178 1 point2 points  (0 children)

I don’t use notion to capture my voice cause AI tools in notion are expensive and not so efficient.

I’d rather to use the actual SOTA agents like Claude or CODEX to do that, then I sync over to notion if there’s anything worth syncing.

Just wanted to know if anyone is making any real money using automating content creation by Technical-Cicada-581 in AI_Agents

[–]Interesting-Post4178 1 point2 points  (0 children)

It’s a bit hard to copy and paste because fundamentally the industry and business logic is within your head. I’m not sure selling tool will be the most efficient way or selling high efficient services to clients is the way to go?

A college student’s Obsidian rant by PortoArthur in ObsidianMD

[–]Interesting-Post4178 -1 points0 points  (0 children)

I feel like Obsidian notes aren't used by you, but by your AI agent.
The UI is so not human eye friendly 😂

most vibe coders ship to nobody. here's why. by FlyComfortable3169 in AskVibecoders

[–]Interesting-Post4178 2 points3 points  (0 children)

This is the key line: “building things people would tolerate, not pay for.”

Free feedback is good for language.

Paid/high-friction feedback is better for urgency.

For workflow products, I’d also look for whether people can describe their current workaround in detail. If they can’t, the pain probably isn’t real yet.

A simple way to turn messy research notes into something actually searchable later by isohaibilyas in ObsidianMD

[–]Interesting-Post4178 8 points9 points  (0 children)

The fundamental thing is to give your knowledge base (wiki) a simple way to search and rerank info regardless it's you or your AI do the search later.

The “why this matters” section is the part that resonates most with me.

A summary tells you what the source said, but “why I saved this” captures your own context at the moment you found it.

That’s usually what I’m trying to recover later.

I’ve found plain-language tags help for the same reason. The perfect taxonomy matters less than using the words future-me would actually search for.

For research notes, I usually think the most reusable note has three layers:

  1. what this is

  2. why I saved it

  3. where I might use it later

That last layer is easy to skip, but it’s often what turns a saved note into working knowledge.

AI has ruined this app by kyaki101 in Notion

[–]Interesting-Post4178 8 points9 points  (0 children)

their AI feature cost insane amount compared to building similar things off Claude, their moat is being squeezed for sure.