Arindam1729
Forms Are Not Dead, Static Forms Are Overused
Vercel Analytics Alternative When You Outgrow the Free Tier
I built a local dashboard to inspect Claude Code sessions, tokens, and costs
Show HN: Cc-Lens, Open Source Analytics Dashboard for Claude Code
We ran 21 MCP database tasks on Claude Sonnet 4.6
GPT-5.3 Codex vs. Claude Opus 4.6
Using AI for Code Reviews: What Works, What Doesn't, and Why
Notes after testing OpenAI's Codex App on real execution tasks
We Cut Token Usage by 83% and Still Hit 90%+ Retrieval Precision
This usually isn’t a model or tooling problem. The agents have access to the right systems, data, and policies.
What’s missing is decision context.
Most enterprise systems record outcomes, not reasoning. They store that a discount was approved or a ticket was escalated, but not why it happened. The context lives in Slack threads, meetings, or individual memory.
I was thinking about this again after reading Jaya Gupta’s article on context graphs, which describes the same gap. A context graph treats decisions as first-class data by recording the inputs considered, rules evaluated, exceptions applied, approvals taken, and the final outcome, and linking those traces to entities like accounts, tickets, policies, agents, and humans.
This gap is manageable when humans run workflows because people reconstruct context from experience. It becomes a hard limit once agents start acting inside workflows. Without access to prior decision reasoning, agents treat similar cases as unrelated and repeatedly re-solve the same edge cases.
What’s interesting is that this isn’t something existing systems of record are positioned to fix. CRMs, ERPs, and warehouses store state before or after decisions, not the decision process itself. Agent orchestration layers, by contrast, sit directly in the execution path and can capture decision traces as they happen.
At scale, agent reliability depends less on model intelligence and more on whether past decisions are actually remembered.
The Next Enterprise Platform Isn't Data-Driven, It's Context-Driven
AI's trillion-dollar opportunity: Context graphs
Gemini 3 vs. GPT-5.2: Detailed Coding Comparison
Feel Free to try it and let me know!
Agent Knowledge Needs More Than Just RAG
When people talk about “knowledge for agents,” it almost always collapses into RAG. But knowledge can, and should—be treated as a first-class runtime tool, not just a context filler.In most implementations, knowledge lives in a vector database. Agents query it through a search_knowledge tool, often hybrid (keyword + semantic) with re-ranking. That’s essentially “Agentic RAG,” and it works well...
Failing to Understand the Exponential, Again
Everyone's trying vectors and graphs for AI memory. We went back to SQL
When we first started building with LLMs, the gap was obvious: they could reason well in the moment, but forgot everything as soon as the conversation moved on.You could tell an agent, “I don’t like coffee,” and three steps later it would suggest espresso again. It wasn’t broken logic, it was missing memory.Over the past few years, people have tried a bunch of ways to fix it:1. Prompt stuffing...
It now has 35+ AI Agents, including:
- Starter agent templates
- Complex agentic workflows
- MCP-powered agents
- RAG examples
- Multiple Agentic frameworks
Thanks, everyone, for supporting this.
Show HN: Memori – Open-Source Memory Engine for AI Agents
https://github.com/GibsonAI/memori
Hey HN! I'm Arindam, part of the team behind Memori (https://memori.gibsonai.com/).Memori adds a stateful memory engine to AI agents, enabling them to stay consistent, recall past work, and improve over time. With Memori, agents don’t lose track of multi-step workflows, repeat tool calls, or forget user preferences. Instead, they build up human-like memory that makes them more reliable and...
We built a live scoreboard for developers. Now 1k+ devs are competing on it
Replit Agent deleted a $1M SaaS startup's production DB
Jason Lemkin was 9 days into building a SaaS product using Replit’s new AI agent. It had rewritten core pages, improved UX, and shipped fast. He called it a “$1M product.”Then he added a code freeze.The agent ignored it and deleted the entire production database.Why?1. No environment separation. Dev, staging, and prod looked identical to the agent.2. No human in the loop. It executed dangerous...