OmniDev
Your context. An agent that can use it.
Watch the Mac app inspect files, propose an edit and ask before running a command.
Native app recording · no narration · waiting time acceleratedInside the OmniDev buildAI agent developer.
Memory systems & backends.
I build agents that use tools, remember context and ask before they act. Here’s the software behind that work.
Explore my work I also explain what I build.Watch the Mac app inspect files, propose an edit and ask before running a command.
Native app recording · no narration · waiting time acceleratedInside the OmniDev buildFrom the memory an agent trusts to the tools it uses and the work it saves. Explore the actual interfaces here.
A recorded console walkthrough: memory graph, audited recall, reusable rules and forgetting.
Recorded sample project · on-screen explanations · no audioInside the ContextFirewall buildCompare the source page with its generated contracts, then inspect the evidence behind a tool.
Browser capture · owned demonstration catalogInside the Graft buildExplore the saved run, sandbox workspace and mobile approval queue. The tickets are fictional.
Repository capture · historical run · fictional ticketsInside the VOX buildI’m Himanshu Jha, also known as Himanshu Kumar and himanshu748.
Carrying context across sessions. Using a tool safely. Recovering from a failed action. I build across Python and TypeScript, APIs and data stores, MCP tools and user-facing products.
Memory that can changeProvenance, revisions, forgetting, and retrieval.
Actions with boundariesScoped access, approval gates, and auditable decisions.
Backends that keep their promisesPersistent state, retry-safe writes, and observable workflows.
The deployment command is stored with the instruction it came from.
flyctl deploySession 01 · instruction 01make releaseSession 01 · instruction 02—Session 02 · ready to recallInstruction 01 is current. Its source stays attached.
flyctl deployInteractive illustration · no model calls
Agent memory, evaluation and observability—explained through actual failures, source code, and the decisions that followed.
A recorded failure changed the design: graph-enforced decisions, fixed promotion gates and a robot simulation that could refuse a regression.
Testing fake-detail leakage, legitimate-detail retention and the limits of prompt-only defenses. Includes scorer corrections and held-out cases.
Tracing a multi-agent system exposed mistaken assumptions about routing, budgets and review quality. The article follows the telemetry to the fix.
From Cognee’s memory lifecycle to a reviewed context pack: provenance, conflicting facts, embedding failures and the checks around recall.
A minimal reproduction, an interpreter bug and a fix explained step by step. Recognized in DEV’s Summer Bug Smash runner-up announcement.
Agentic AI, memory infrastructure, or a backend problem you’re working through. Tell me what you have in mind.