Bourdon is live on Product Hunt today — free, self-host forever:
pip install bourdon
npx @getbourdon/mcp-server
🔗 producthunt.com/products/bou…
🔗 bourdon.ai
Come tell us we're wrong about memory. We'll be in the thread all day.
16 agent integrations ship in the box — Claude Code, Codex, Cursor, Copilot, Windsurf's Cascade, Hermes…
Best part: every agent that built Bourdon had a hand in its OWN connection — the tools it federates wired themselves in. Receipts: bourdon.ai/credits
Comber is live. Point it at a URL and it explores your app like a real user — every click, every reachable state — and files what broke with a repro, screenshot, and trace. No test scripts, no selectors. npx comber check <your-url> runs free with your Anthropic key.
[comber-hero-demo.gif] codecomber.io/from/x
We've been running our whole agent fleet on this. bourdon v0.10.0 turns shadcn/improve backlogs into shared cross-agent memory — any agent can answer "what's executable in repo X right now, and what's blocking it" without ever opening repo X. 🐝
shadcn's improve gives every repo a self-contained, executable plan backlog. We loved the format so much we made it our fleet's handoff standard — then taught our agents to share it.
bourdon v0.10.0 ships `bourdon improve sync`: point it at any improve-format plans/ directory and the backlog gets federated into cross-agent memory. Every agent in your fleet can answer "what's executable in repo X right now — and what's blocking it" without opening repo X. Wire it to a session-end hook and the answer is never stale.
Built on top of shadcn/improve (MIT) — complementing it, not forking it. Thanks @shadcn 🐝
Replying to @nicoloboschi
Hindsight solves within-agent recall better than anything on BEAM 10m. We're tackling the between-agent layer — federating memory across a swarm without a centralized brain.
That's Continuo (open source, MIT, v0.0.7). Would love to explore an integration path if you're open to it. Feels like a stack that doesn't exist yet.
Replying to @uselockai
I like that. Structure matters more than search. And yes I think those are structured different by nature (raw state vs. a decision).
Replying to @nicoloboschi
Very interesting. I will be checking this out immediately.
Read the thesis: continuo.cloud
Code: github.com/getcontinuo/conti…
Most-wanted: adapters for Cursor + Cline, integration of the
recognition runtime into a real agent's response loop, and honest
falsification attempts.
Recognition first.
Continuo isn't competing with @mem0ai @zep_ai @letta_inc — those
frameworks solve representation + retrieval really well.
Continuo is the *runtime timing layer* that can sit on top of any of
them. Mem0's store + Continuo's timing = memory that feels like a
mind, not a database.


