u/Upper-Ad-1714

Image 1 — What are these? Are they poisonous to people?
Image 2 — What are these? Are they poisonous to people?
Image 3 — What are these? Are they poisonous to people?
Image 4 — What are these? Are they poisonous to people?
▲ 94 r/Berries

What are these? Are they poisonous to people?

Found in Moraga, CA. We have two young children and I'm wondering if they are poisonous.

u/Upper-Ad-1714 — 6 days ago

My AI agent finally pushed back at me 😂

Did anyone else notice how weirdly agreeable most AI agents are? They’ll confidently do anything you ask, even when it’s a bad idea lol.

I’ve tried a bunch of memory/agent tools recently, but this is the first time an agent actually pushed back on something I asked it to do. It questioned the task, explained why it might not be the best approach, basically reminding me I already decided against this with my cursor agent . Honestly felt way more useful and human.

The project is called RoBrain.dev it’s open source, and I think the founder used to work at Vercel.

Curious if anyone else here has tried it or experimented with agents that are less “yes-man” and more opinionated?

reddit.com
u/Upper-Ad-1714 — 3 months ago
▲ 3 r/cursor

Open-source memory layer for Cursor because rules files don't capture what I rejected

I build websites for real estate agents, listing pages, lead capture forms, MLS feeds, that kind of thing. I use Cursor for most of the work and Claude Code to double-check the code before I ship. I'm not a hardcore engineer, I learn as I go.

The thing driving me crazy is .cursorrules going stale.

Rules files are fine for stable stuff like "always use Tailwind." But they're useless for the actual decisions I make during a build. Last month I spent half a day getting a property image carousel working, hit a wall with one library on mobile, and switched to a different one. Three weeks later, fresh project for another agent, Cursor confidently suggests the first library again. Same wall, same half-day.

I tried writing this into .cursorrules. Works until the next decision. Then the next one. The file grows, becomes contradictory, I forget to update it, and the agent ignores half of it anyway.

Someone pointed me at RoBrain (https://github.com/adelinamart/robrain). Open source. 

The thing that hooked me is that it captures both what I chose and what I rejected and the reason why. So next time the agent is about to suggest the autocomplete, it can flag "you already ruled this out because rural addresses got mis-corrected." That "why" is what rules files never capture.

A week in:

  • Captures decisions automatically. I don't have to remember to write anything down.
  • At session start, past decisions just show up in context. No command, no copy-paste.
  • Works across Cursor and Claude Code, so when I jump to Claude to double-check something, it already knows the decisions I made in Cursor.
  • When I change my mind on something later, it doesn't overwrite the old decision, it links them. So I can still ask "what did we land on for the carousel back in March?" and get a real answer.

Honest rough parts:

  • Setup is heavier than I expected. Docker step, plus API keys for Anthropic and an embeddings provider. Took me ~20 minutes, not 2.
  • Sometimes captures noise (a debugging step, a temporary workaround). There's a robrain review command for cleaning those up.

Has anyone else been using something similar?

u/Upper-Ad-1714 — 3 months ago