Nothing arrives on its own
Every entry got there because you added a note, dropped a file, pulled a ticket or ran an agent. There's no background writer, and the list is short enough to read in one glance for exactly that reason.
Rewind records everything. Khint only sees the text you select, when you press the shortcut.
The session on the left is the whole memory: seven entries, each one added by hand or written by a run you triggered. Watch a line of the update land and the entry it came from lights up. Nothing is selected, nothing was recorded, and there's no eighth entry you can't see.
Khint's memory is a work session you open and close by hand. It holds the entries you put in, compacts them, and hands that summary to your next prompt. All of it stays in a SQLite file on your Mac.
Every entry got there because you added a note, dropped a file, pulled a ticket or ran an agent. There's no background writer, and the list is short enough to read in one glance for exactly that reason.
The privacy default isn't a setting buried in a pane, it's the shape of the product: no key press, no run. Stop the session and its context goes idle without deleting anything.
Sessions, their entries and the Knowledge index are local and stay local. Signing in syncs your Packs and the metadata of your history; the bodies of what you ran never leave the device.
Khint ships a standalone MCP server over stdio. Claude Desktop and Codex get the session you chose to keep, and nothing else: four ways to read it, one to append to it, and a notification every time they do.
Rewind's whole product is the feature Khint refuses to build, so this is the honest half of the comparison: what's off by default, what is never on at all, and the bill on each side.
Security and privacyThis isn't a feature gap. It's a different bet on what a memory should be allowed to see in the first place.
The memory is a session you open and close by hand. It holds what you added, compacts it into the short context your next prompt reads, and stays in a SQLite file on your Mac.
Rewind's bet is total recall: every window, every meeting, recorded and queryable afterwards. It's the feature Khint refuses to build, so there are questions Rewind answers that Khint never will.
Capture, storage, AI access, MCP, pricing. Including the rows where Rewind simply knows more than Khint ever will.
Same product, four other lenses. Each page is the honest version, including what Khint doesn't do.
A launcher with AI bolted on, against a palette that was an AI tool from day one.
Khint vs CleanShot XBoth read your screen. Only one can then act on what it read.
Khint vs GranolaNotes for the meeting, against context for the whole week around it.
Khint vs Apple IntelligenceFree and already installed, against your own prompts wired to your tools.
No. Khint never records the screen ambiently. The only time pixels are read is when you trigger OCR from the palette: that's a one-shot capture, and the screenshot isn't stored after text is extracted. There's no continuous recording, no audio capture, and no keystroke logging.
No. Khint is action-driven, not always-on. Rewind's pitch is total recall: it records every window and every meeting, then lets you rewind through your day. Khint's pitch is the opposite: only the text you select is processed, and only when you press the shortcut. The Memory pillar adds your active work session's compact context into AI prompts, but it doesn't record your screen or your audio.
Locally first. Your Khint history, your packs and your Memory sessions all live in a SQLite file on your Mac. If you sign in, your history and your packs also sync to a Supabase Postgres database, encrypted at rest and reachable only through our service key; Memory sessions never sync at all. Nothing else leaves the device unless you run an agent, which sends the text you gave it to the model.
No, and that's by design. Rewind is built for that: it indexes everything you see and hear. Khint only knows about what you put into a Memory session, plus your action history. If you want a passive total-recall search, Rewind is a better fit. If you want a clean, intentional record of work sessions you explicitly start and stop, Khint fits better.
No. Khint doesn't sell user data, and our inference providers' API terms prohibit training on customer inputs and outputs. We don't run any fine-tunes ourselves. Sub-processors are Anthropic and OpenAI (inference), Groq (voice dictation), Clerk (auth), Supabase (sync), Stripe (billing) and DigitalOcean (hosting). The privacy policy lists them all.
The active work session's summary is prepended to every AI action prompt. Free, and no always-on capture, ever.