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
memory-pulse
Corrections your coding agent keeps, enforced on every edit
memory-pulse is a correction that survives the session. You tell your coding agent something once, and it holds: the correction opens every later session, and the edit that walks it back is stopped before it reaches your branch. The record is a JSONL file in your own repository, so teammates and CI inherit the same decisions. Four MCP tools, about 900 tokens of definitions, and the hosted engine keeps no copy of your memory.
Hey PH —
Travis here, maker of memory-pulse.
This came from a very specific annoyance. I'd correct a value mid-session ("the timeout is 30s, not 10"), the agent would agree, and a week later the wrong number was back in a diff I now had to read. I tried memory tools, but found there were times where the agent did not obey , regardless of recall. Then TRACE (arXiv 2606.13174) put a number on it: agents re-violated over half the corrections they'd just been shown, with a memory tool installed.
So memory-pulse doesn't just store corrections, it enforces them. `remember` writes one line to .memory-pulse/events.jsonl in your repo. Every session opens with a brief of what you already decided. Before each Edit, Write or apply_patch, a guard checks the change against what you retired and blocks it with the reason. 1.7ms p95, zero false blocks across 931 real edits so far. Your memory stays in your repo — we never keep a copy.
Try it in Claude Code: /plugin marketplace add t-crew/memory-pulse (Codex, Cursor and any MCP client work too). The client is one file, MIT, zero dependencies. Free tier, no account needed.
The feedback I want most: tell me what it blocks that it shouldn't.
About memory-pulse on Product Hunt
“Corrections your coding agent keeps, enforced on every edit”
memory-pulse was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #16 on the daily leaderboard. memory-pulse is a correction that survives the session. You tell your coding agent something once, and it holds: the correction opens every later session, and the edit that walks it back is stopped before it reaches your branch. The record is a JSONL file in your own repository, so teammates and CI inherit the same decisions. Four MCP tools, about 900 tokens of definitions, and the hosted engine keeps no copy of your memory.
On the analytics side, memory-pulse competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how memory-pulse performed against the three products that launched closest to it on the same day.
Who hunted memory-pulse?
memory-pulse was hunted by travis crew. 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 memory-pulse including community comment highlights and product details, visit the product overview.
travis crew