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 buildI’m Himanshu Jha. I build AI integrations and developer tools, then turn the code, failures and lessons into guides developers can use.
Watch the buildsWatch the Mac app inspect files, propose an edit and ask before running a command.
Native app recording · no narration · waiting time acceleratedInside the OmniDev buildThe software behind my writing. Watch the workflow, inspect the interface, then follow the implementation.
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 buildAgent 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.
I also publish as Himanshu Kumar and use the handle himanshu748. My route into developer relations is through building. I work on agent memory, MCP tools, and backend systems, then explain the decisions in public.
I’m interested in helping developer-tool teams turn product knowledge into useful docs, technical articles, sample apps, and demos.
Start with a real questionGive the reader a reason to care before introducing the API.
Make the example inspectableShow the code, the output, and the limits.
Leave a useful next stepA command to run, a repo to explore, or a question worth testing.
Developer education, technical content, sample apps, and demos. Tell me what you want developers to understand.