Draft and send are separate rows
Create draft writes into Gmail's drafts and stops there. Send email exists for the times the reply really is finished, and it renders the message and waits for you to type yes.
IntegrationsGmail
Answer the emailfrom the app you're in
Turn what you selected into a draft or a sent reply, and pull the thread you're answering into your work session so the agent writing it knows what was said.
SoonGmail is rolling out while Google finishes verifying the restricted scopes it needs. The card in the app shows the same word until it lands, and the other five integrations are unaffected.
KhintPalette
Sprint 24
/
Gmail
Two ways to write it, and only one of them sends
Email is the one integration where a mistake is public and permanent, so the two writes are separate rows. Create draft never sends, which makes it the one to leave on. Send email stops to show you the message first.
The one integration
built around a refusal
Everything else here is about removing a trip. This one is about not sending something you didn't read, which is why the rows, the defaults and the confirmation are shaped the way they are.
Send emailwriteWhat went out is in your session
A draft or a sent reply is logged as a session entry once Gmail confirms, so the next agent runs knowing the customer was answered, and so does your AI client reading over MCP.
Or draft it at the end of a workflow
Create Gmail draft is a workflow step, so a triage workflow can file the ticket and leave the reply waiting in your drafts. Sending is deliberately not something a workflow does on its own.
Reading is off until you turn it on
Pull thread and Search are unchecked by default, Khint never reads in the background, and Gmail is deliberately excluded from Knowledge: there's no local index of your mailbox.
GmailPausedNothing leaves
without you reading it
There's no silent send, no setting that removes the confirmation, and nothing scheduled. If you want zero risk at all, leave only Create draft switched on.
Security and privacySend renders the message and waits for a typed yes
No silent send, and no setting that disables the prompt
Create draft writes to drafts and stops
OAuth on Google's own page: Khint never sees a password
The token lives in your OS keychain
Reads only when you press a row, never in the background
Your mail is never indexed by Knowledge
Pause keeps the connection, Forget revokes it
Connect Gmail in about a minute
OAuth in your browser. There's no password and no app-specific token to paste anywhere.
Turn Gmail on in Khint's Integrations page
Your browser opens on Google's own sign-in. Khint never sees your password: the sign-in happens on Google's page and comes back as a token.
Approve the access it asks for
Reading mail, creating drafts and sending email. The card shows your address once you're done.
Use it from the palette
Cmd+Shift+K. Send email and Create draft are on by default; Pull thread and Search are a checkbox away on the same card.
Confirm before anything leaves
Send email always shows a preview and asks you to type yes. There's no way to send silently, and no setting that removes the confirmation.
- If drafting or sending fails on a connection made before the compose permission shipped, use Forget credentials on the card and connect once more to grant it. Create Gmail draft is also available as a workflow step.
The rest of Khint
An integration is where work comes in and goes out. These three are what happens in between.
Common questions about Gmail and Khint
Why does the Gmail card say Soon?
Because the Google verification for the restricted scopes Gmail needs is still in review. Until it completes, the integration is held behind a flag in release builds rather than shipped half-working. Nothing else in Khint is affected, and the card flips itself on when verification lands.
Can Khint send an email without me seeing it?
No. Send email always renders the message and waits for you to type yes. There's no silent path, no setting to disable the confirmation, and nothing scheduled. If you want zero risk at all, leave only Create draft switched on: it writes into Gmail's drafts and stops.
Does Khint store my email?
No. A pulled thread lands in your local Memory session, which lives in a SQLite file on your Mac and is never synced to our servers. Gmail is also deliberately excluded from Knowledge, so there's no local full-text index of your mailbox either.
What permissions does it ask for?
Reading mail, creating drafts and sending email, granted through Google's own consent screen. The token is stored in your operating system's keychain, and Forget credentials on the card revokes it.
Drafting fails on my connection. What happened?
That's almost always a connection made before the compose permission shipped: the older token simply doesn't carry it. Use Forget credentials on the Gmail card, then connect once more, and the new consent screen grants it.
Write the reply where you read the question
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.