Keep the meeting contextloaded all day
The hard part of a meeting isn't the notes: it's carrying what was decided into everything you do next. Khint Memory holds that context for you: start a session before the call, and every AI action (and your AI tools) already know the topic, the decisions, and the open questions.
The context evaporates
the second the call ends
You leave a planning call holding ten threads in your head, then spend the afternoon re-explaining each one: to the ticket, to the email, to the chatbot you paste into. Every prompt starts cold. Khint fixes that with its three pillars (Agents, Capture, and Memory), wired together behind one palette, so the meeting's context follows you into the work instead of staying in the meeting.
One session, context that follows the meeting
From the call to the follow-ups, without re-typing what it was about.
Start a session before the call
Before the meeting begins, hit Start and name the session: call it “Sprint sync · Tue”. From here on, Khint only listens while that session is on. As you take notes it logs each entry and keeps a tight running summary in the background, so the moment the call ends the context is already written for you. How Memory works →
Capture what flashes on the shared screen
Someone screen-shares a metric, an error, or a slide you want to keep. Open the palette with Cmd+Shift+K, run Extract text, and drag over the region: the text lands on your clipboard and is logged to the session. No AI rewrite, just the raw text, captured in seconds and now part of the meeting's context. How Capture works →
Run Actions that already know the meeting
After the call, run a saved Action: “Draft the follow-up”, “Summarize for the ticket”, “Reply to that email”. Because the session is active, its compacted summary rides along on every prompt, wrapped in
<session_context>. You don't re-explain who said what: the model already has the thread of the meeting.Hand the live context to your AI tools
Want to keep working in Claude Desktop or Codex? Khint's bundled MCP server lets your AI client read the active session live, read-only by default, no copy-paste. Ask Claude to draft the spec and it already knows the meeting; any write back into the session surfaces an explicit OS notification first. How integrations work →
Stop when the meeting is wrapped
The follow-ups are sent and the tickets are filed. Hit Stop. The context closes and the next task starts on a clean slate, because Memory is about this hour's work, not your whole week. The session stays on your Mac for replay if you need to look back. Turn the same notes into action items →
Why not just keep a chatbot tab open?
You can, but a chat window forgets the meeting between prompts, so you re-paste the decisions, the constraints, and the names into every message, and the unreleased details pile up in a chat history you don't control. Khint carries the context for you: the active Memory session is attached to every Action automatically, captures you take during the call become part of it, and your AI tools read the same live session over MCP. Because Actions only ever see the text you select plus the session summary you opted into, the meeting stays on your Mac.
Common questions
How does Khint remember the context of a meeting?
Start a Khint Memory session before the call. While the session is on, every note you type, every Action you run, and every screen capture you take is logged to it, and Khint rewrites a short compacted summary in the background: who is in the room, the subject, the decisions, the open items. That summary is wrapped in <session_context> and attached to every AI Action you run afterwards, so you never re-type what the meeting was about.
Does Khint record my screen or listen to the call?
No. Khint has no always-on capture: it only listens while a Memory session is on, and it only summarizes what you type and paste during the session. There is no audio recording, no screen recording, and no keystroke log. Screen capture happens only when you trigger Extract text from the palette yourself. Press Stop and the context is closed.
Can Claude Desktop or Codex use the same meeting context?
Yes. Khint ships an MCP server out of the box, read-only by default. Claude Desktop, Codex (OpenAI), or any MCP client can ask for the active session and read the live meeting context, no copy-paste between tools. Writing a new entry back from your AI client requires an explicit OS notification, so nothing is injected silently.
Where does the meeting context live?
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 runs fully offline. Stop the session and the context is closed; past sessions stay on-device for replay. Your meeting context isn't sitting in a chat history somewhere.
Try it on your next meeting
Free with 10 AI actions and 5 captures per day. No credit card. Start a session before the call, stop it after.