7 posts tagged with "agents"

edit: yeah we built the thing in this post. still mad about the problem though.

support has had a memory-backed agent running for like three months. works. incidents retained. deploy region flips retained. recall in prod is actually correct. rare, I know.

then ML wanders over. "hey can we get JSONL for a fine-tune."

what goes in the zip file?

chat export. messages[]. maybe someone regex'd out the system prompt. no memory IDs. no "fact A got superseded on Feb 3." no link to the document chunk anyone actually trusted.

you fine-tune. model comes back confident. cites jack shit. confidently wrong about a deploy region you fixed in the bank six weeks ago.

you open the memory UI. bank was right. dataset was fiction.

that's not "the LLM hallucinated." that's two teams shipping different religions and nobody noticed until after the GPU invoice.

— Anurag Atulya

We're entering an era where AI agents write code proposals, pitch decks, articles, architecture docs — all of it. Fast. Plausible. Confident.

And that's exactly why taste is what will matter — in engineering and in business, for founders and for teams, technical or not.

Not taste as in "I prefer minimal UI." Taste as in: this is good, this is bad, this will survive, this will rot — before you can fully explain why.

That feeling has a name people use interchangeably: intuition. I think intuition is taste. Same thing. Gut feel earned the hard way.

Atulya started as memory infrastructure for agents and teams. But a durable brain needs more than storage and retrieval. It also needs safe memory evolution. That is why Atulya now supports Git-like memory repos with branches, commits, rollback, and fork-to-bank workflows.

Agent forget. That core problem.

Not dramatic failure. Quiet one. Agent help Anurag refactor module today. Tomorrow — same agent, same repo — ask about that module. Agent say "I don't have context for that." Like nothing happened.

Worse: agent make change. Confident. No memory of constraint set three sessions ago. Break thing. No warning. Just breakage.

Agent remember fact. "Anurag reviewed PR #88." Good.

Agent remember another fact. "anurag@company.com approved deploy." Good.

Agent asked: "What did Anurag do this week?" Agent say: "I found one PR review. Nothing else."

Wrong. Two facts. Same person. Agent did not know. Looked like two separate entities. Completely unrelated.

This is entity fragmentation. Not edge case. Default state of any system that stores facts without resolving who they are about.

Give any MCP client structured long-term memory: retain, recall, reflect, and mental models. One Docker command for local stack, or Atulya Cloud over HTTPS.

CrewAI's built-in memory works inside one kickoff(). When the process exits, context is gone. atulya-crewai implements CrewAI's Storage interface on top of Atulya banks so knowledge compounds across runs.