State what exists
Every page on this site names the state of what it describes: shipped, planned, or not written. Saying a thing does not exist costs less than the trust spent implying it does.
The person behind Memkith
Memkith is built by one person, Saksham Bedi. The CLI beside your editor, the service that keeps what your team learns, this site and every reply to the contact address come from the same desk.
Why I started Memkith
Memkith started as a complaint. I had more than one coding agent working in one repository, and each arrived knowing nothing about what the last had worked out. I explained the same constraint 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.
So I built the layer that keeps it, beneath the agents, where it is addressed by code and follows the code’s visibility. The agents stay swappable. The memory stays put.
I write the CLI, the memories service and this site, and I read every message that reaches the contact address. If something on this site is wrong or unclear, that is the fastest way to get it fixed.
Saksham Bedi
Founder, Memkith
What I hold the work to
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. I hold the work to it too: decisions get recorded where the next person will look.