State what exists
Every page on this site names the state of what it describes: shipped, planned, or not written. That is a company habit before it is a design one. Saying a thing does not exist costs less than the trust spent implying it does.
The company behind the memory layer
Memkith, Inc. builds a shared memory layer for AI coding agents. This page covers where the product stands, how we work, and how to reach us. For the product itself, read the product overview.
Company at a glance
- Company
- Memkith, Inc.
- Building
- Shared memory for AI coding agents
- Contact
- saksham@memkith.com
- Hiring
- No open roles
Where the product stands
- Shipping today
- Code-scoped memory over MCP for Claude Code, Cursor, Codex, and Zed. Setup is three commands, and every mechanism is listed on the quickstart.
- Committed next
- Branch-scoped recall, more agents, and written reference documentation. Undated on purpose, with the standard of evidence stated on the roadmap.
How we work
Three working habits, each one checkable against this site and the product rather than asserted.
Keep the surface small
Setup is three commands and the CLI ships a handful more. A mechanism earns its place by removing a real problem from a team's workday, not by filling out a comparison table.
Write the reason down
The product exists because reasons kept evaporating out of closed pull requests and ended sessions. The same discipline applies to how we work: decisions get recorded where the next person will actually look.
The reason should stay with the code
Memkith started as a complaint. More than one coding agent was working in one repository, and each arrived knowing nothing about what the last had worked out. The same constraint got explained twice a week. A dead end came back a month later as a new idea.
None of that knowledge was missing. It sat in a closed pull request, a review comment nobody would search again, or a session that ended when the window closed. The code kept the fix. Nothing kept the reason.
Memkith keeps that reasoning a layer beneath the agents, where it is addressed by code and follows the code’s visibility. The agents stay swappable. The memory stays put.
Saksham Bedi
Founder, Memkith
Get in touch
Email and LinkedIn both reach us directly, and there is no support desk or separate hiring address behind either. Every route, open or not, is listed with its state on the contact page.