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).
When an AI agent writes to a file or calls an API, a timeout can leave it unclear whether the change happened. MELRA checks tool calls against local policy, pauses sensitive actions for approval, verifies the declared result, and keeps a redacted receipt. If a write's outcome is unknown, MELRA holds it for reconciliation instead of retrying blindly. Open-source alpha; requires Node.js 22.13+ or 23.4+.
I’m building MELRA at XAGI Labs. The current alpha runs locally and requires Node.js 22.13+ or 23.4+. In a throwaway workspace, run `npx -y @melra/cli@alpha setup`: it writes a safe local policy, prints a pasteable MCP client config, and runs readiness checks. It asks before writing the client config. I’d especially value a run through one client flow and feedback on what happens when a tool call is interrupted. Partial or failed runs are useful too. What would you need to see before trusting an agent with local tool access?
Update: the v0.3.0-alpha.14 release now has CI-smoke-checked binaries for macOS arm64, Linux x64/arm64, and Windows x64, plus the Node runtime and Python wheel.
It’s still alpha. Please try it in a throwaway workspace and tell us where setup or recovery is unclear.
Update: I’ve added a 26-second walkthrough to the gallery. It shows a verified read, an approval-gated write, and a policy-blocked command; the sample write is not executed. MELRA remains alpha and supports Node.js 22.13+ or 23.4+. If you try it, please share the client, version, OS, and where setup or recovery feels unclear. Partial results are useful too.
MELRA was submitted on Product Hunt and earned 4 upvotes and 3 comments, placing #103 on the daily leaderboard. When an AI agent writes to a file or calls an API, a timeout can leave it unclear whether the change happened. MELRA checks tool calls against local policy, pauses sensitive actions for approval, verifies the declared result, and keeps a redacted receipt. If a write's outcome is unknown, MELRA holds it for reconciliation instead of retrying blindly. Open-source alpha; requires Node.js 22.13+ or 23.4+.
MELRA was featured in Open Source (69k followers), Developer Tools (521.6k followers) and Artificial Intelligence (481.6k followers) on Product Hunt. Together, these topics include over 237.7k products, making this a competitive space to launch in.
Who hunted MELRA?
MELRA was hunted by Dheeraj S. 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 MELRA stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Dheeraj S
I’m building MELRA at XAGI Labs. The current alpha runs locally and requires Node.js 22.13+ or 23.4+. In a throwaway workspace, run `npx -y @melra/cli@alpha setup`: it writes a safe local policy, prints a pasteable MCP client config, and runs readiness checks. It asks before writing the client config. I’d especially value a run through one client flow and feedback on what happens when a tool call is interrupted. Partial or failed runs are useful too. What would you need to see before trusting an agent with local tool access?