Hey everyone, we're now in the final week of the AppSumo campaign, so I wanted to check back in here and open things up.

I've been getting a lot of the same questions in DMs and comments, so let me address the most common ones:

"How hard is the MCP setup?" It takes less than 5 minutes. Full setup guide here: https://docs.plurality.network/t...

"Which tier should I get?" $59 if you're a solo builder. $149 if you're a power user who lives in AI tools daily. $339 if you have a team and want shared context across everyone.

You can now store unlimited context for AI, but without structure, your memories quickly become a messy pile of information that you have no idea how to work with. We've been there too.
So, we've been heads-down building, and Memory Studio now has a Notion-style editor: with version history, rich formatting, enhanced file understanding, markdown support and more.

Here's what's we shipped:

We're in the middle of setting up an affiliate program for AI Context Flow and I wanted to get some feedback from the community here:
- what makes you want to promote a product? (commissions, category or being a power user yourself?)
- what do you expect from the product team to provide you?
- is it something that would interest you if you aren't a professional content creator already?
Curious to hear the thoughts from other founders and people in the community

OpenAI just made AI memory automatic.
The problem? you can no longer fully audit what it remembers about you.

Dreaming V3 (launched June 4) doesn't ask you to save memories anymore. It runs in the background, reads across years of your conversations, and synthesizes a profile of you, and automatically updating as your life changes.
It remembered your Singapore trip was in the future. Now it knows you went. You didn't tell it that. It figured it out.

The audit trail problem: TechTimes reported the update "limits" what users can actually see. You used to have a list of saved memories you could read and delete. Now you have a synthesized profile that's broader than that list, and you can only partially inspect it.
A CHI 2026 study called it the "personalization-convenience paradox": the feature users value most is also the one they can least control.

Okay this one's fun to share.

Ever wish you could just tell your AI exactly what to remember and what to skip, instead of hoping it figures it out on its own? Just give it instructions like you would give an intern: check that folder, use that info, forget about this part.

That's basically what we built with the @aicf handle. It's a custom instruction system baked right into AI Context Flow, you just add it to your prompt and tell it exactly what context to pull.

Made a quick tutorial walking through 3 examples we actually use ourselves:

We've just launched our affiliate program, and as one of our early supporters, we wanted to invite people in this forum first.

How it works: you refer someone, they subscribe, you earn 20% of their payment every month for a full year.

Some quick math: refer just 10 users every month, and by the end of year one you could have earned:

Saw this Reddit post today and it hit so close to home.

I've had this exact conversation multiple times. AI Memory is a topic that people get instantly. There are many people who have open-sourced basic AI memory layers and published their own GitHub repos.

Hey PH community

We're in the middle of our AppSumo launch for AI Context Flow, and I wanted to start a real conversation here rather than just drop a link.

The problem we're solving: most people using AI tools daily are paying what I call an "AI context tax", the time spent re-explaining your project, background, and goals every single session, to every single tool.

ChatGPT doesn't know who you are. Claude doesn't know who you are. Gemini doesn't know who you are. And if you're jumping between them (like most power users are), you're paying that tax multiple times a day.

Prompt Optimization was one of the first features we shipped in AI Context Flow.

We've grown a lot since then, evolving into a universal memory hub, but a big chunk of our userbase originally came for prompt optimization, and still loves it as a core part of their workflow.

The feedback we kept hearing was consistent: "I like the fast, one-click optimization, but sometimes I need more control."

More control over how the prompt gets optimized. More control over how context gets pulled in.