You were gone a week,catch up in one sitting
The first day back is usually spent scrolling: the project channel, the thread you were @-mentioned into, the sprint board, the email chains that kept going without you. Khint pulls all of it into one work session and lets a single AI action tell you what was decided, what changed, and what is waiting on you.
The backlog of messages
is not the backlog that matters
Out of five hundred unread messages, maybe ten decide something and three are waiting on you. Reading everything to find those thirteen is how a day off costs a second day. The usual fix, skimming and hoping, is how a scope change slips past a product owner. Khint takes a third route: it sits behind one palette shortcut, and its pillars (Agents, Memory) plus its Slack, Jira, and Gmail integrations let you collect first and read a distilled version once, instead of scrolling three tools in parallel.
First morning back, in five moves
Every step runs from the same palette shortcut.
Start a catch-up session before you open anything
The instinct is to open Slack first and start scrolling. Resist it. Start a Memorysession called “Back from leave” instead. A session is a container: every pull you run in the next steps is logged into it, and Khint keeps a compacted summary of everything that lands there. You are not reading yet; you are collecting.
Drain the Slack channel without scrolling it
Open the palette with Cmd+Shift+K and run Pull channel on your project channel: Khint reads the recent messages into your session in one move. Someone @-mentioned you into a forty-reply argument? Pull thread grabs that one discussion, every reply in order. Search messages finds the conversations that name you, so nothing addressed to you hides in a channel you forgot to check.
See what moved in the sprint while you were out
From the same palette, run Active sprintin the JIRA section. The current sprint's state lands in your session next to the Slack pulls, so “what the team said” and “what the board says” sit in one place. A ticket looks suspicious? Pull issue brings in that one ticket's detail without opening a browser tab.
Sweep the email threads that kept going
Connect Gmail on the Integrations page and the palette gains Pull thread and Search rows for your inbox too. Pull the two or three threads that clearly kept moving in your absence. Same pattern as Slack: the whole exchange is read into the session, in order, instead of you reconstructing it from forty individual notifications.
Ask one Action what actually needs you
Now run a saved Action, your own “What did I miss?” prompt: list the decisions made, what changed since, and what is explicitly waiting on me. Actions read the compacted context of your active session, so the answer draws on the channel, the threads, the sprint, and the emails together. Reply where it matters (Jira Add comment, Slack Post, Gmail Create draft) from the same palette, and you are back in the room.
The catch-up session outlives the catch-up
Because everything you pulled landed in a Memory session, the digest is not the end of it. Keep the session active through your first day back and every Action you run, tightening a reply, drafting the comment that unblocks a ticket, already knows what happened while you were out. This is the same mechanism that powers work-session context on an ordinary day. And when the catch-up surfaces a decision that should have been a ticket all along, turning that Slack thread into a Jira ticket is the very next palette row.
Common questions
Do the pull rows show up in the palette automatically?
You switch them on once. Connect Slack, Atlassian, and Gmail from Khint's Integrations page, then open each card's Palette actions block: rows are grouped into reads and writes, and the read rows (Pull channel, Pull thread, Active sprint, Gmail Pull thread, the searches) are off by default so your palette stays lean. Tick the pulls you want for catch-up and they appear as palette rows under their SLACK, JIRA, and GMAIL sections. Untick them afterwards if you only want them the week you come back.
Was Khint reading my Slack and inbox while I was away?
No. Nothing runs in the background: a pull happens only at the moment you run its palette row, using your own credentials, and reads straight from that service into your machine. Slack connects with a token you paste, Atlassian with your email plus an API token, and Gmail through Google's own sign-in; all of it is stored in your operating system's keychain, not on Khint's servers. If you never trigger a row, nothing is fetched.
Where does everything I pulled end up?
In the Memory session you started for the catch-up. Every pull is logged as an entry in that session, and sessions live in a local database on your machine; they are never synced to Khint's cloud. Khint keeps a compacted running summary of the session, which is exactly what your digest Action reads. When you are caught up, end the session; it stays in your Memory history if you ever need to check what you were told.
Can I answer things from Khint too, or only read?
You can act from the same palette. The JIRA section has Add comment and Change status rows for the tickets that were waiting on you, the SLACK section has a Post row to answer the channel, and the GMAIL section has Create draft plus Send email. Sending is deliberately careful: Khint gathers the recipient and subject, shows you a preview, and only sends after you type yes to confirm, so catching up never turns into an accidental reply-all.
Take the time off, skip the re-entry tax
Free with 10 AI actions and 5 captures per day. No credit card. Slack, Jira, and Gmail connect with your own credentials, kept in your keychain.