AI text processing thatstays on your Mac

A native macOS menu-bar app, not another browser tab. Khint processes the text you select in place (in Notes, Slack, Jira, a doc) from one shortcut, and keeps your prompts, sessions and captures in a local database on the device. Only the selection itself is ever sent for processing.

For product owners and business analysts. macOS and Windows, menu-bar app. Local-first storage, no background recording.

Native beats
a tab you have to babysit

Most AI text tools ask you to leave your work: copy the paragraph, find the browser tab, paste it into a chat window, copy the answer back. Khint inverts that. It runs as a macOS menu-bar app behind one palette shortcut, and its three pillars (Agents, Capture, and Memory) are built so your prompts, your session context, and your capture history all sit locally on the device. The result is a local-first workflow: your data stays put, and only the text you highlight is sent to the model.

What runs on your Mac, and what leaves it

Five points between your keyboard and the model.

  1. It lives in your menu bar, not a browser tab

    Khint sits in the macOS menu bar and opens with one shortcut: Cmd+Shift+K. There's no web app to keep open, no tab to hunt for. Select text anywhere, summon the palette, pick an agent, and Khint pastes the result straight back into the app you were already in. The tool comes to your text instead of you carrying your text to the tool.

  2. The transform happens in place, across every app

    Because Khint pastes into the frontmost window, the same action works in Apple Notes, the Slack desktop app, a Notion doc, or a Jira description in your browser. A product owner can tighten a rough requirement in Notes, then switch to Confluence and clean a page: one keyboard reflex, no copy-into-a-chatbot round trip and no context switch out of the app where the work lives.

  3. Your prompts and sessions stay on the device

    The agents and Packs you build, your Memory sessions, and your run history all live in a local SQLite file on your Mac. Memory is local-only (it is never synced to Khint's servers), so the compacted context that rides along with an agent to save you re-explaining yourself is data that never leaves the machine.

  4. Capture reads the screen without a background recorder

    Capture turns anything on screen (a screenshot pasted in chat, a PDF, an error dialog) into selectable text. On macOS it fires only when you ask, using the system's own screenshot UI rather than an always-on capture API, and drops the extracted text on your clipboard. Nothing is recorded in the background; the capture is a deliberate gesture you trigger from the palette.

  5. Only the selection leaves, and nothing is kept

    The payload for any agent is the text you highlighted, and nothing else on screen. Khint's backend passes it to the model and stores none of it: the result comes back, the bodies of your history stay on the device. Your files, clipboard history and other windows are never read. See the full security posture →

Local-first, still honest about the model

Local-first doesn't mean the model itself runs on your laptop: the language work is done by Claude over the network. What Khint keeps local is the part that piles up over time: the prompts you refine, the Memory of what you've been working on, and the text you capture. When you connect integrations like Atlassian or Linear, writes go one item at a time and each push is explicit, so a refined ticket reaches Jira from anywhere only when you say so. If confidentiality is your first concern, the privacy-first walkthrough spells out exactly what does and doesn't leave the device.

Common questions

Does Khint run the AI model locally on my Mac?

No, and it's worth being precise. The language model behind an agent is Claude, reached over the network, not a model running on your Mac. What's local is everything around it: your prompts (agents and Packs), your Memory sessions, your capture history, and your action history all live in a local SQLite database on the device. Each run sends only the text you selected to the model and pastes the result back. So the workflow and your data stay on your machine even though the model itself is in the cloud.

Which Mac apps does it work inside?

Any app where you can select text. Khint lives in the menu bar and pastes results into whatever window is frontmost, so the same shortcut cleans up a paragraph in Apple Notes, rewrites a message in the Slack desktop app, or tightens a description in a Jira or Confluence tab in your browser. You never move the text into a separate chatbot window: it's processed in place. Khint ships for macOS and Windows.

Do I need an internet connection to use it?

Your on-device parts work offline: Memory sessions, stored Packs and agents, and your local history are all readable without a connection. AI agents and Capture (OCR) need a connection because the model that transforms or reads the text runs in the cloud. When you're offline you can still start a session and organize your prompts; the AI step resumes the moment you're back online.

Can I run AI agents on my own API key?

Yes, with bring-your-own-key, which comes with Khint Lifetime. Add an Anthropic (Claude) or OpenAI key in Settings and it's stored in the macOS Keychain; runs then go on your key and stop counting against your monthly credits. The call still travels through Khint's backend rather than leaving your Mac for the provider directly. Prefer the default? The managed proxy works out of the box and still only ever receives the text you selected, plus, if you opted in, a short compacted summary of your active Memory session.

Text processing that lives where you work

Free with 300 credits a month, about 10 AI actions a day. No credit card. Native menu-bar app, local-first storage.