About

I love building products in the open data space and envision an internet without silos.

Badges

Buddy System
Buddy System
Bright Idea 💡
Bright Idea 💡
Contributor
Contributor
Gemologist
Gemologist
View all badges

Maker History

  • AI Context Flow
    AI Context FlowOne context & memory that works across all your AIs.
    Nov 2025
  • 🎉
    Joined Product HuntOctober 9th, 2025

Forums

How are you giving your AI tools memory? We compared 5 methods

Most of us now use 2 4 AI tools, and every one of them starts from zero. We put together an honest comparison of the 5 common ways to build an AI second brain :

  1. Markdown files: free and portable, but lots of copy-paste

  2. Local files (CLAUDE.md, rules files): best for coding agents

  3. ChatGPT / Claude / Gemini Projects: easiest if you use one assistant

  4. Drive / GitHub connectors: good for large archives

  5. A portable memory layer over MCP, which is what we build with AI Context Flow

Projects is enough if you only use one assistant. Whereas a memory layer helps iwhen you switch between models, share context with a team, or run workflows (n8n, agent teams) that need to read and write the same memory.

•

3d ago

Is the European welfare system too generous to employees and too hard on startups/employers?

This is a current hot topic on Twitter.

A particular guy was complaining about too generous employee care system in Netherlands.
(I am not Dutch, so I do not know the exact rules, but as for me, no system is completely fair to anybody.)
I know that without written rules, either employees or employers can exploit it.

How agencies are using AI Context Flow to keep 10+ client voices separate

Hey PH
One use case keeps coming up with agencies, so we wrote it up properly so others can reuse the template.
The problem: an agency runs 10 clients through ChatGPT, Claude and Gemini. Every writer pastes a different version of the style guide, two clients end up in the same thread, and freelancers take their prompts with them when they leave. The result is voice bleed: Client A's copy starts sounding like Client B.
How teams are solving it with AI Context Flow:
One memory bucket per client: voice rules, audience, banned terms, on-brand and rejected examples, compliance limits
Shared buckets: contributor and viewer roles, an activity log of who changed what, and version restore
The MCP server: the same client voice in Claude, ChatGPT, Cursor, Copilot, Windsurf and headless agents. The AI pulls only the relevant context and writes client feedback back to the bucket
Full playbook, including a copyable voice-bucket checklist: https://plurality.network/blogs/...
If you run an agency or a multi-brand content team, I'd love to know how you handle client voices today, and what's still breaking, maybe we could make a custom built setup done-for-you. lmk below

View more