This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
0ctx keeps sessions, checkpoints, and decisions attached to your repo so AI tools can continue work without losing project context. Local-first runtime, SQLite-backed graph, repo-first setup.
Hey Product Hunt, we built 0ctx because too many AI workflows lose context between sessions, branches, and tool switches.
0ctx keeps project memory attached to the repo itself, so the next session can continue the work instead of asking you to restate decisions, status, and intent.
What it does today:
repo-first setup with 0ctx enable
local runtime backed by SQLite
workstreams, sessions, checkpoints, and reviewed insights
retrieval for supported agent workflows through the local runtime
The current open-source path is intentionally local-first: install the CLI, enable one repo, and work normally.
We would especially love feedback on:
whether the positioning is clear
whether the setup path feels obvious
which integrations you would want next
If you try it, tell us where the setup or mental model is confusing. That is the highest-value feedback for us right now.
What does 0ctx actually do?
0ctx is persistent project memory for AI work. It keeps sessions, checkpoints, and decisions attached to the repo so the next tool or session can continue with the right context.
Why is local-first important here?
The product is built around repo-bound workflows, so local-first keeps the runtime close to the code, reduces moving parts, and makes the memory model easier to trust and reason about.
How do I start?
Install the CLI, go into the repo you work in, then run:
npm install -g @0ctx/cli
cd <repo>
0ctx enable
Is this another hosted AI IDE?
No. The core story is not a new chat surface. The core story is durable project memory attached to the repo through a local runtime.
Which integrations are supported today?
The current GA path in this repo is:
Claude Code
Factory / Droid
We are working towards making others tools part of it as well. Preview integrations are opt-in and are not the main open-source setup story.
What should I try first?
Try it in one active repo, run 0ctx enable, then use your normal agent workflow and inspect the captured workstreams, sessions, or checkpoints.
No comment highlights available yet. Please check back later!
About 0ctx on Product Hunt
“Persistent repo memory for AI coding tools”
0ctx was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #80 on the daily leaderboard. 0ctx keeps sessions, checkpoints, and decisions attached to your repo so AI tools can continue work without losing project context. Local-first runtime, SQLite-backed graph, repo-first setup.
0ctx was featured in Productivity (650.7k followers), Developer Tools (511.7k followers), Artificial Intelligence (467.3k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 306.5k products, making this a competitive space to launch in.
Who hunted 0ctx?
0ctx was hunted by Rajesh. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how 0ctx stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Rajesh
Hey Product Hunt, we built 0ctx because too many AI workflows lose context between sessions, branches, and tool switches.
0ctx keeps project memory attached to the repo itself, so the next session can continue the work instead of asking you to restate decisions, status, and intent.
What it does today:
repo-first setup with 0ctx enable
local runtime backed by SQLite
workstreams, sessions, checkpoints, and reviewed insights
retrieval for supported agent workflows through the local runtime
The current open-source path is intentionally local-first: install the CLI, enable one repo, and work normally.
We would especially love feedback on:
whether the positioning is clear
whether the setup path feels obvious
which integrations you would want next
If you try it, tell us where the setup or mental model is confusing. That is the highest-value feedback for us right now.
What does 0ctx actually do?
0ctx is persistent project memory for AI work. It keeps sessions, checkpoints, and decisions attached to the repo so the next tool or session can continue with the right context.
Why is local-first important here?
The product is built around repo-bound workflows, so local-first keeps the runtime close to the code, reduces moving parts, and makes the memory model easier to trust and reason about.
How do I start?
Install the CLI, go into the repo you work in, then run:
Is this another hosted AI IDE?
No. The core story is not a new chat surface. The core story is durable project memory attached to the repo through a local runtime.
Which integrations are supported today?
The current GA path in this repo is:
Claude Code
Factory / Droid
We are working towards making others tools part of it as well. Preview integrations are opt-in and are not the main open-source setup story.
What should I try first?
Try it in one active repo, run 0ctx enable, then use your normal agent workflow and inspect the captured workstreams, sessions, or checkpoints.