AI agent forgets user preferences every session. This fixes it
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
I build AI agents for work and kept hitting the same issue: a user corrects the agent, the session ends, and the correction is gone. Next session, same correction. I tracked it across our users and the average preference gets re-corrected 4+ times before people just give up. Existing solutions don't really solve this. Memory layers store raw conversation logs. RAG retrieves documents. Neither extracts what the user actually wants as a structured, persistent preference. So I built pref0. It does one thing: extracts structured preferences from user corrections and compounds confidence across sessions. How it works in practice. Say you're building a customer support agent:Session 1: User says "always escalate billing issues to a human, don't try to resolve them." pref0 extracts billing_issues: escalate_to_human, confidence 0.55.Session 4: User flags a billing ticket the agent tried to auto-resolve. pref0 reinforces the preference. Confidence hits 0.85.Session 7: A billing issue comes in. The agent routes it to a human without being told. No correction needed.Now multiply that across hundreds of users. Each one teaching your agent slightly different things. pref0 maintains a structured profile per user (or team, or org) that your agent reads before every response.The API is intentionally minimal. Two endpoints: POST /track: send conversation history after a session. pref0 extracts preferences automatically. GET /profiles/{user_id}: fetch learned preferences before the agent responds.A few design decisions: > Explicit corrections ("don't do X") score higher than implied preferences. Stronger signal. > Preferences are hierarchical: user > team > org. New team members inherit org conventions on day one. > Confidence decays over time so stale preferences don't stick forever.This isn't a replacement for memory. Memory stores what happened. pref0 learns what the user wants. You can run both side by side.Works with LangChain, CrewAI, Vercel AI SDK, or raw API calls. Free tier available -> https://pref0.com/docsWould love feedback on the approach, especially from anyone building agents with repeat users.
HN · launched Feb 7, 2026 · 6 upvotes (top 72%) · 0 views
Niche: ai agent memory infrastructure · 358 launches, 15 in the last 7 days ▼ -35% · Explore this niche →
Category and tags
- Horizontal
- Agent / copilot
- Developer
- AI-native
- Hobby / open-source project
Visit website ↗ Source listing ↗
More like this: all 358 launches in ai agent memory infrastructure →
Could you build this?
Yes Tracking and persisting user corrections across sessions is a standard CRUD and context-injection layer on top of an LLM agent.
Discussion
No comments on this launch.
Competitors
Other products that read as similar to this one : 174 launches clear the similarity bar, closest 8 shown.
Attention rank: #145 of 175 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 99 days after the earliest competitor.
- Agent Memory · ph · 2026-10-10 · 1 upvotes · similarity 0.44
- Rudel – Claude Code Session Analytics · hn · 2026-03-12 · 144 upvotes · similarity 0.41
- Mirrors: Fix recurring AI agent mistakes with real-time guidance · yc · 2026-10-30 · 21 upvotes · similarity 0.41
- AI Stalemate · ph · 2026-11-09 · 2 upvotes · similarity 0.41
- Bilinc · ph · 2026-10-20 · 3 upvotes · similarity 0.40
- Feedback Bench by Enterpret · ph · 2026-10-07 · 8 upvotes · similarity 0.40
- Polign: Corrective Recall for Agents · ph · 2026-09-23 · 2 upvotes · similarity 0.39
- Memograph CLI- A tool to diagnose 'memory failures' in AI agents · hn · 2026-02-25 · 6 upvotes · similarity 0.39
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.