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
MorrowCache
Skip the chat call when the question is the same
MorrowCache is a drop-in OpenAI-compatible proxy. Change baseURL—keep your model and API keys. Agents rephrase until done; each try is a full chat bill. Reuse cached completions when a same-intent judge matches (cloud Jev or local Kev/Laya)—not cosine alone. Demo: 2817ms → 423ms on a paraphrase HIT. Fail-open on judge errors. Freshness refuses stale "latest" hits. Streaming & tools bypass. npx @kushalicious/jevcache@latest start · morrowcache.vercel.app/agent-setup
Hey PH 👋 I'm Kushal, maker of MorrowCache.
The pain: same user question, different wording—or an agent that rephrases until the answer "looks done"—and you pay for every chat completion again. Vector-ish caches miss paraphrases or merge the wrong prompts.
MorrowCache is a local OpenAI-compatible proxy. Point your client at http://127.0.0.1:8080/v1, keep your upstream model. Before calling the model, a same-intent adjudicator (TypeSafe Jev by default, or local Kev/Laya) decides whether to reuse the cached answer. Not "similar text" as the only signal.
What I'd call out upfront:
• Fail-open — if the judge errors, the real model still runs
• Freshness — time-sensitive asks can refuse a stale HIT
• Streaming + tool calls bypass the cache (by design in v0)
Quick try (~5 min, Node 22.5+):
npx @kushalicious/jevcache@latest start
Demo with no real API key:
MOCK_UPSTREAM=1 npx @kushalicious/jevcache@latest start --demo
Then send a prompt + a paraphrase → expect MISS then HIT (X-Jevcache headers or /stats).
Easiest in Cursor / Claude Code: copy the setup prompt from
https://morrowcache.vercel.app/a...
Recorded pair on the site: 2817ms MISS → 423ms HIT at intent 0.94 — one example, not a guarantee for every workload.
I'd love feedback from anyone running agents or support bots: where would same-intent caching help, and where would you never trust it? Happy to dig into architecture in the comments.
About MorrowCache on Product Hunt
“Skip the chat call when the question is the same”
MorrowCache was submitted on Product Hunt and earned 1 upvotes and 1 comments, placing #108 on the daily leaderboard. MorrowCache is a drop-in OpenAI-compatible proxy. Change baseURL—keep your model and API keys. Agents rephrase until done; each try is a full chat bill. Reuse cached completions when a same-intent judge matches (cloud Jev or local Kev/Laya)—not cosine alone. Demo: 2817ms → 423ms on a paraphrase HIT. Fail-open on judge errors. Freshness refuses stale "latest" hits. Streaming & tools bypass. npx @kushalicious/jevcache@latest start · morrowcache.vercel.app/agent-setup
On the analytics side, MorrowCache competes within Open Source, Developer Tools and GitHub — topics that collectively have 630.7k followers on Product Hunt. The dashboard above tracks how MorrowCache performed against the three products that launched closest to it on the same day.
Who hunted MorrowCache?
MorrowCache was hunted by Kushal 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.
For a complete overview of MorrowCache including community comment highlights and product details, visit the product overview.
Kushal S