AI that rememberswhat your meetings decided
Six weeks after a planning call, someone asks what you decided, and it's buried in a chat log, a Slack thread, and a notes app that all disagree. Khint keeps every meeting as an on-device work session you can reopen, and lets your AI tools search back through them, so the decision is recalled instead of reconstructed.
The decision was made,
now nobody can find it
A product owner's hardest recall problem isn't today's meeting: it's the one from three sprints ago whose outcome just came back to bite the roadmap. The notes are scattered, the chatbot forgot the conversation, and re-deciding wastes an afternoon. Khint fixes that with its three pillars (Agents, Capture, and Memory) wired behind one palette, so each meeting leaves behind a durable, searchable on-device record instead of evaporating.
From a call weeks ago to today's ticket
Recall the decision, don't re-hold the whole meeting in your head.
Every call already became a session
You don't do anything special to remember a meeting later: you just ran a Memorysession during it. You hit Start before the call, named it “Roadmap review · Q2”, took your notes, and pressed Stop after. That session didn't vanish: Stop marks it ended, not deleted, so it's sitting on your Mac ready to reopen. How Memory works →
Three sprints later, the question comes back
“What did we actually decide about the export flow?” Normally that's twenty minutes of scrolling a chat log, a Slack thread, and a notes app that all half-remember it. Instead you reopen the roadmap session from your history and replay the entries (the raw notes, the captures, the decisions) exactly as they were logged. Nothing was rewritten out from under you.
Let your AI search the meetings for you
Don't want to hunt by hand? Khint's bundled MCP server lets Claude Desktop or Codexlist your past sessions, open a specific one, and search across their entries, read-only by default. Ask “which planning meeting covered the export deadline?” and your AI reads it straight out of your stored sessions, no copy-paste and no transcript to paste in. How integrations work →
Pull the recalled decision into today's work
Found it. Now run a saved Action: “Draft a ticket from this”, “Summarize the decision for the epic”. If you have a session active for today's work, its context rides along too, so the old decision and the current task line up in one prompt. The recall turns straight into a ticket instead of a memory you half-trust.
Old meetings never leak into a cloud
Because every session lives in a local SQLite file that never syncs to Khint's servers, your back-catalogue of meetings (including the pre-release details you can't paste into a chatbot) stays on your Mac. You get long-term recall without a growing cloud transcript you don't control. Why on-device matters →
Why not just search your chatbot history?
You can, but a chat history mixes every topic into one endless scroll, the decision that mattered gets buried under prompts, and the whole thing lives on a server you don't control. Khint keeps each meeting as its own scoped session with an explicit Start and Stop, holds a tight compacted summary rather than a raw wall of text, and stores the lot in a local Memory database. When you want to look back, you reopen the session yourself or point your AI tools at it over MCP, and because nothing was ever uploaded, even the pre-release details are still safely on your Mac.
Common questions
How does Khint remember a meeting after it's over?
Each meeting is a Khint Memory session you start before the call and stop after. While it's on, every note you type, every Action you run, and every screen capture you take is logged to that session, and Khint keeps a compacted summary of it. When you press Stop the session isn't deleted: it's marked ended and stays on your Mac. Weeks later you can reopen it and replay exactly what was captured and decided.
Can my AI assistant search across my past meetings?
Yes. Khint ships an MCP server out of the box, read-only by default. Claude Desktop, Codex (OpenAI), or any MCP client can list your past sessions, open a specific one, and search across the entries you logged, so you can ask your AI 'what did we decide about the export feature three sprints ago?' and it reads it straight from your stored sessions instead of you scrolling a transcript.
Is this screen recording like Rewind?
No. Khint has no always-on capture. It only remembers what happens inside a session you explicitly started, and only the notes you type, the Actions you run, and the captures you trigger yourself from the palette. There is no audio recording, no background screen recording, and no keystroke log. If a session was never started, there is nothing to recall.
Where are my past meetings stored?
On your Mac. Sessions and their entries live in a local SQLite database and are never synced to Khint's servers: Memory is local-only. Sign out and Khint still recalls them offline. Your past meetings aren't sitting in a chat history or a cloud transcript somewhere; they stay on-device, and Khint can't read them remotely.
Give your meetings a memory
Free with 10 AI actions and 5 captures per day. No credit card. Start a session per meeting. Recall it whenever it comes back.