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).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
OpenState
Session memory and guarded edits for AI coding agents
AI coding agents forget decisions between sessions and sometimes edit the wrong code. OpenState records actual session events; decisions, failed commands, blockers, and test outcomes; into a local project record. It restores context automatically in OpenCode, shares summaries with Claude Code and Codex through MCP, and previews structural edits before applying them. All 36 tools are free to explore; the first 30 structural applies per machine are free.
Hi Product Hunt! I'm the solo developer behind OpenState.
I built it because I use AI coding agents throughout my working day, and kept paying for the same mistakes. New sessions would re-read files we'd already investigated; context compaction would lose decisions; agents would retry failed commands or revisit rejected approaches. Sometimes an edit meant for one function would affect more code than intended.
OpenState tackles those problems from two directions:
Project memory grounded in what actually happened. It records decisions and their reasons, failed commands, blockers and test outcomes from session events. OpenCode captures and restores context automatically; Claude Code, Codex and Muse can request the project record through MCP.
Structural edits that check before they write. Find and read the relevant function, preview the change, and apply only if the target is still valid. Stale or ambiguous targets are refused rather than guessed.
In my June–September sessions, 21,372 OpenState tool calls had a 99.91% success rate. That's one developer's observed usage, not an independent study, and the site explains the evidence and limitations.
There are 36 tools, local project data, no account required to start, and 30 free structural applies per machine. Paid options are $10/month or $129 once for all 0.x releases.
I'd especially like feedback from developers using multiple coding agents: what does your agent repeatedly forget between sessions, and how are you handling that today?
“Session memory and guarded edits for AI coding agents”
OpenState was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #158 on the daily leaderboard. AI coding agents forget decisions between sessions and sometimes edit the wrong code. OpenState records actual session events; decisions, failed commands, blockers, and test outcomes; into a local project record. It restores context automatically in OpenCode, shares summaries with Claude Code and Codex through MCP, and previews structural edits before applying them. All 36 tools are free to explore; the first 30 structural applies per machine are free.
On the analytics side, OpenState competes within Productivity, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.7M followers on Product Hunt. The dashboard above tracks how OpenState performed against the three products that launched closest to it on the same day.
Who hunted OpenState?
OpenState was hunted by Mike Kuykendall. 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.
For a complete overview of OpenState including community comment highlights and product details, visit the product overview.
Hi Product Hunt! I'm the solo developer behind OpenState.
I built it because I use AI coding agents throughout my working day, and kept paying for the same mistakes. New sessions would re-read files we'd already investigated; context compaction would lose decisions; agents would retry failed commands or revisit rejected approaches. Sometimes an edit meant for one function would affect more code than intended.
OpenState tackles those problems from two directions:
Project memory grounded in what actually happened. It records decisions and their reasons, failed commands, blockers and test outcomes from session events. OpenCode captures and restores context automatically; Claude Code, Codex and Muse can request the project record through MCP.
Structural edits that check before they write. Find and read the relevant function, preview the change, and apply only if the target is still valid. Stale or ambiguous targets are refused rather than guessed.
In my June–September sessions, 21,372 OpenState tool calls had a 99.91% success rate. That's one developer's observed usage, not an independent study, and the site explains the evidence and limitations.
There are 36 tools, local project data, no account required to start, and 30 free structural applies per machine. Paid options are $10/month or $129 once for all 0.x releases.
I'd especially like feedback from developers using multiple coding agents: what does your agent repeatedly forget between sessions, and how are you handling that today?
Product: OpenState website
Source and documentation: GitHub