Yukti
A browser assistant that remembers your web activity and answers questions from it.
Tagline
Your browsing, remembered.
Private memory for every tab you research.
Stop digging through history. Ask your browser.
Remember the page, search, or startup later.
Category-defining: Yukti is private browsing memory for the web.
The product is not just a chat sidebar; it indexes browsing actions into a private vector store and answers questions over your history, which is closer to personal web memory than generic search.
Alternative-to: Replace endless Chrome history digging, tab pinning, and Notion scraps with one ask box.
The strongest user pain here is retrieval, not capture. The page explicitly promises semantic recall, source citations, and live page awareness, which makes it a clear alternative to manual history management.
Pain-killer: Stop losing the one page, search, or startup you saw yesterday.
The example prompt on the page is exactly this scenario, and the product is optimized for recall of browsing moments rather than generic browsing assistance.
Primary user
Knowledge workers who do heavy web research all day, especially product managers, recruiters, founders, and analysts using Chrome
ICP #1
Technical recruiter at a high-growth startup screening roles and candidate profiles all day
Pain
They forget which candidate, job post, or resume they saw yesterday and waste time retracing tabs, search queries, and browser history.
Why this solves
Yukti can answer 'what was that startup I looked at yesterday?' or 'which candidate had React Native experience?' by recalling browsed pages semantically with citations.
ICP #2
Product manager doing competitive research and market scanning across dozens of tabs
Pain
They lose track of which competitor page, pricing doc, or feature announcement contained a specific detail they need for a meeting.
Why this solves
Yukti builds a private memory of pages, searches, and clicks, so they can ask natural-language questions instead of manually hunting through browser history.
ICP #3
Solo founder or operator comparing tools, vendors, and hiring sources across a long research session
Pain
They open too many tabs and later cannot remember where a key stat, company, or contact came from.
Why this solves
Yukti’s page-aware chat plus semantic recall gives them a fast way to reconstruct prior research from their own browsing trail without switching tools.
Strengths
- +The value proposition is immediate and memorable: "Your browsing, remembered" is strong and benefits from the concrete example question.
- +The feature set is clearly explained with scannable sections for recall, page-aware answers, privacy, BYO model, and citations.
- +The privacy and trust story is unusually explicit for this category, including scoped IDs and no passwords/payment tracking.
Weaknesses
- −The site is too developer-flavored for a mainstream user; terms like "RAG-powered," "vector store," and "Manifest V3" will scare off non-technical buyers.
- −The landing page lacks a sharp persona and use-case focus, so it feels like a general-purpose browser memory tool instead of a must-have for one audience.
- −There is no proof: no screenshots of the actual extension UI, no demo video, no testimonials, and no quantified outcome.
- −The install flow looks fiddly and manual, with "download zip," "extract," and "load unpacked," which signals friction and may reduce trust.
- −The page does not explain what gets indexed, how far back the memory goes, or how the private vector store is set up in plain language.
Fix these
- Pick one wedge persona for the homepage, likely recruiters or product/ops researchers, and rewrite the hero around that workflow.
- Replace jargon with outcome-driven copy; swap "RAG-powered" and "vector store" for "remember every page you visited and ask about it later."
- Add a 30-60 second product demo showing a real question, the recalled source, and the live page overlay.
- Show visual proof of privacy and permissions, including exactly what is captured and what is excluded.
- Reduce install friction by offering a one-click Chrome Web Store path or, if not possible, explain the manual install as a temporary beta step with reassurance.
Drop-in replacement copy
Headline
Remember what you browsed
Ask your browser about pages, searches, and clicks from your own history.
Find the thing you saw yesterday
Yukti remembers meaningful browsing moments in the background so you can recover the page, startup, or candidate you forgot. No more digging through tab soup or Chrome history.
Ask your current page in real time
Open any page and ask a question without waiting for indexing. Yukti reads the page you’re on and returns an answer with source-cited context.
Search your web history like memory
It semantically retrieves past browsing moments from your private store, so you can ask in plain English instead of guessing keywords. That means faster recall for research-heavy work.
Keep it private by design
Each user gets a private ID, and Yukti avoids password and payment fields. You can also connect your own model with Gemini, OpenAI, Groq, or Mistral.
FAQ
What exactly does Yukti capture?
Pages, searches, and clicks that look meaningful for later recall. It explicitly avoids passwords and payment fields.
How is this different from Chrome history?
Chrome history is a list of URLs. Yukti turns browsing into searchable memory with semantic recall and source-cited answers.
Can I ask about a page I’m on right now?
Yes. Yukti can answer questions about the current page in real time without waiting for background indexing.
Do I have to use your model?
No. You can bring your own setup with Gemini, OpenAI, Groq, or Mistral.
Who is this for?
People who research on the web all day: recruiters, PMs, founders, analysts, and power users who keep losing the thread across tabs.
I built Yukti because browser history is a terrible knowledge base. It remembers pages, searches, and clicks, then lets you ask questions like “what was that startup I saw yesterday?” Private. Source-cited. Lives in Chrome.
Yukti is live. A Chrome extension that quietly remembers the pages you research and answers questions from your own browsing history. No tab archaeology. No Notion scraps. Just ask and get cited answers.
Watch this happen: 1. Open a page 2. Ask Yukti about it 3. Get a sourced answer instantly It also recalls stuff you saw hours ago, not just the current tab. This is what browser memory should feel like.
Most people don’t need another AI chat. They need a better way to find the page, query, or candidate they saw yesterday. That’s why Yukti indexes meaningful browsing moments in the background and turns them into private memory.
The first people who “get” Yukti immediately say the same thing: “I lose track of candidate pages all day.” If you live in Chrome and need to remember what you saw, this is for you.
You know the drill: - 27 tabs open - vague memory of a pricing page - browser history useless Yukti turns that mess into a private searchable memory with citations.
Yukti remembers the web so you don’t have to. It captures pages, searches, and clicks in the background, then answers questions about your own browsing with source links. Built for people who research all day.
This is the exact use case I kept hearing: “Which candidate had React Native experience?” “Where did I see that startup yesterday?” Yukti finds it from your browsing trail, not from your memory.
Yukti scopes everything to a private ID that’s only yours. No password tracking. No payment fields. No creepy cross-user stuff. Just a local-feeling browser assistant that remembers what matters.
Product managers immediately understood the value. Competitive research, pricing pages, launch posts, random tabs from last week - all of it becomes askable later. That’s the wedge. That’s the product.
Angle: recruiters as the wedge
Most browser tools are built for browsing. Yukti is built for remembering. I kept hearing the same complaint from recruiters and sourcers: “I know I saw that candidate, but I can’t remember where.” They were digging through history, pinned tabs, screenshots, Slack notes, and half-finished Notion pages just to reconstruct one research session. So I built Yukti: a Chrome extension that quietly remembers meaningful browsing moments - pages, searches, clicks - and lets you ask questions about them later. Example: - Which candidate had React Native experience? - What startup did I look at yesterday? - Which job post mentioned relocation? It answers with source-cited context from your own browsing history. The interesting part is not “AI in the browser.” It’s retrieval. If you spend all day researching on the web, the bottleneck is not capture. It’s finding the thing you already saw. Would love feedback from recruiters, sourcers, and people who live in Chrome all day.
Angle: private browser memory as a category
There’s a hole in the browser stack. Chrome remembers history. Notion remembers notes. Perplexity answers questions. But none of them remember your actual browsing in a way that helps you later. That’s the space Yukti is exploring: private browser memory. It indexes meaningful browsing activity in the background, then turns it into a searchable memory you can query in plain English. You can ask about the page you’re on, or something you saw yesterday, and it answers with cited sources from your own activity. A few things I cared about while building it: - keep it private by design - don’t track passwords or payment fields - make the answers source-cited, not vague - support bring-your-own-model setups for people who want control This is still early, and I’m treating it like a wedge product, not a platform. The real question: who feels this pain hard enough that they’ll change behavior for it? If you research on the web for a living, I’d love to hear what would make this a must-have instead of a nice-to-have.
Angle: pain-killer for founders/operators
I’m convinced “I saw it somewhere on the web” is one of the most common work problems nobody has solved properly. Founders compare competitors. Operators compare vendors. PMs compare launches. Recruiters compare candidates. And then later, everyone asks the same thing: where was that page? Yukti is my attempt at fixing that. It lives in Chrome, quietly remembers pages/searches/clicks, and lets you ask about your browsing trail later. Not with generic search. With source-cited recall from your own history. The best part is the shift in behavior: - less tab hoarding - less screenshotting for later - less digging through Chrome history - less “I know I saw it, but where?” I’m especially interested in hearing from people who spend hours a day in browser research. The product is tiny, but the pain is huge. If you’re in that bucket, tell me the exact question you wish your browser could answer.
No visuals for this kit yet.
Tagline
Private memory for your browser
Description
Yukti remembers the pages, searches, and clicks you actually care about, then answers questions from your own browsing history with source-cited context. Built for recruiters, PMs, founders, and anyone who researches all day in Chrome.
Maker's first comment
I built Yukti because I was tired of browser history feeling like a junk drawer. When you spend your day researching on the web, the problem isn’t that you never saw the answer - it’s that you can’t find it again. I kept losing candidate pages, competitor pricing, random startup sites, and half-remembered searches across too many tabs. Yukti quietly remembers meaningful browsing moments and lets you ask questions about them later, with source-cited answers. It’s private by design, avoids passwords and payment fields, and supports bring-your-own-model setups if you want to use Gemini, OpenAI, Groq, or Mistral. I’m launching this early and want real feedback from people who live in Chrome all day: recruiters, PMs, founders, analysts, researchers. The biggest thing I’m looking for is the exact workflow where this becomes a no-brainer instead of a nice extra.
Pinned maker comment
I’d love feedback on the wedge. Right now Yukti is strongest for recruiters, PMs, and founders who do heavy web research - but I’m still refining the first user flow, the privacy story, and how obvious the value is in under 30 seconds.
Meta
Still losing the page you saw yesterday?
Target: recruiters, PMs, founders who research all day in Chrome. Hypothesis: they’ll click if they feel the pain of browser history being useless. Yukti remembers pages, searches, and clicks, then answers questions with cited context from your own browsing.
Google Search
Remember every page you researched
Target: people actively searching for Chrome history alternatives, browser assistants, and research tools. Hypothesis: high-intent searchers want a better recall layer, not another generic AI sidebar. Yukti turns your browsing into a private searchable memory with source-cited answers.
Reddit Promoted
If Chrome history fails you, this helps
Target: indie hackers, recruiters, PMs, and power users who spend all day in tabs. Hypothesis: Reddit users will respond to a practical tool that solves a real retrieval pain, not a flashy AI gimmick. Yukti remembers what you browsed and lets you ask about it later.
Subreddits
r/SideProject
Build story + short demo of browser memory for people who live in tabs
Rules: Show the product and the problem; keep it honest, no hard sell, and include what you learned building it
r/indiehackers
How I picked a wedge persona and why browser history is a bad memory system
Rules: Share lessons and metrics, not just a product drop; self-promo is tolerated only when the post is genuinely useful
r/microsaas
Tiny SaaS solving a specific retrieval problem for recruiters/PMs
Rules: Keep it tactical, include screenshots or a demo, and avoid hype
r/recruiting
Workflow pain post: remembering candidate pages, job posts, and searches
Rules: No spam; frame it as a tool built from a recruiter pain point and ask for workflow feedback
r/ProductManagement
Competitive research and tab overload: a memory layer for PM research
Rules: Share the problem, the workflow, and a concrete example; avoid obvious promotion and focus on utility
Communities
Post build logs, wedge experiments, and what users say verbatim. Comment on other founders’ posts daily so people recognize your name before you share Yukti.
Join discussions around productivity, research workflows, and AI in product work. Ask for very specific feedback on memory and retrieval, not generic product opinions.
Share a short workflow demo in PM channels and invite people to break it. The angle is research recall, not AI novelty.
Cold outreach template
{firstName}, I built Yukti because people who research in Chrome all day keep losing pages, searches, and candidate/competitor details. If you’re open to it, I’d love to show you how it answers questions from your own browsing history with cited sources. If it’s useful, I’d rather learn your exact workflow than pitch you anything.
Product Hunt timing
Launch on Tuesday at 12:01am PT. That gives you the full UTC day for momentum, catches US morning traffic, and hits product people, founders, and recruiters while they’re actively online and reacting to new tools.
Indie Hackers post ideas
- 01I built a browser memory assistant because Chrome history is useless
- 02How I picked recruiters as the first wedge for Yukti
- 03What people actually want from a private AI browser assistant
Competitor alternatives
Current tone of voice
Clean, slightly playful, and technical; for example, it says "Your browsing, remembered" and "quietly indexes what you do" while also using jargon like "RAG-powered" and "Manifest V3."
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique