Walk into the meetingalready briefed
Every page on the internet tells you what to do after the meeting. The stressful part is the fifteen minutes before it: what shipped, what slipped, what was decided last time. Khint pulls the live Jira sprint and the relevant Confluence pages into one working context, then drafts your talking points with a single AI action.
Prep is a research job,
you do it against the clock
A product owner walks into a stakeholder review needing three things: the current state of the sprint, the history of every contested decision, and a crisp line on what needs deciding today. Normally that means eight tabs, a frantic scroll through the board, and improvising the rest. Khint sits behind one palette shortcut, and its three pillars (Agents, Capture, and Memory) plus its Jira and Confluence integrations turn that scramble into a five-minute routine that ends with a written brief.
From cold start to briefed in five moves
Every step runs from the same palette shortcut.
Open a session for the meeting
Ten minutes before the steering call, start a Memory session named after it. From now on, everything you pull and every draft you run is collected and compacted into one context for that meeting, instead of living in six browser tabs you will lose track of mid-call.
Pull the live sprint state from Jira
Open the palette with Cmd+Shift+K and run Active sprint in the JIRA section: the board's current state lands in your session. Someone will ask about that one contested ticket, so run Pull issue on it too, or Search if you only remember the phrasing. No tab-hopping, no screenshotting the board.
Pull the decision that started the argument
Half of meeting prep is re-reading what was already agreed. The CONFLUENCE section's Pull page row brings the decision page or the spec into the same session, so the context your brief draws on includes what was decided last month, not just what the board says today.
Draft the brief with one Action
Type your rough agenda anywhere (three bullet points is enough), select it, and run a saved Actionlike “Write my meeting brief”. Because the Action reads your active session, the talking points it returns are grounded in the sprint status and pages you just pulled: what shipped, what slipped, what you need decided today.
Keep the same session running through the meeting
Prep and follow-up are one context, not two. When the meeting ends, the session that briefed you is the same one that turns your notes into Jira tickets or a Confluence summary, and the palette's Add comment row drops an update onto the issue everyone argued about, while the context is still warm.
The brief is a by-product of the pulling
What makes this different from asking a chatbot to “summarize my sprint” is that Khint's Memory holds the actual material: each Jira and Confluence pull is logged into the active session and compacted, so the Action that writes your brief works from the real board state, not from what you remembered to paste. The same mechanics power the after-meeting flows (sprint review summaries, status reports), and if your day is spent alternating between the two Atlassian tools, the Jira + Confluence assistant page covers the wider toolkit.
Common questions
What can Khint pull from Jira and Confluence before a meeting?
With Atlassian connected, the palette gains a JIRA section with Pull issue, Active sprint, and Search rows, and a CONFLUENCE section with Pull page. Each pull lands as an entry in your active Memory session, so the sprint board's state, the contested issue, and the decision page all sit in one place before you write a word. The pull rows are off by default to keep the palette lean. Switch on the ones you use from the Atlassian card on the Integrations page.
How does the AI know what to put in my brief?
Through Memory. While a session is active, everything you pull is compacted into a running context, and every Action you run reads that context alongside the text you selected. So when you run a brief-writing Action over your rough agenda, it is not guessing: it is drawing on the sprint status and the pages you just pulled. An Action only ever sees your selection plus that session summary; nothing else on your machine.
Do I need admin rights to connect Jira and Confluence?
No. Atlassian connects with your own email, an API token you create yourself, and your cloud domain, the same access you already have in the browser. The three values are stored in your operating system's keychain, not on Khint's servers, and every pull goes straight from your machine to Atlassian with your own credentials. If you can open the sprint board, you can pull it.
Can I prep more than one meeting at a time?
Yes: keep one Memory session per meeting or per topic. Sessions are cheap to start and stop, and you activate the one you are prepping so pulls and Actions land in the right context; switch the active session and the context switches with it. Sessions live in a local database on your machine and are never synced to the cloud, so a brief about a sensitive reorg stays where you wrote it.
Spend the fifteen minutes thinking, not scrolling
Free with 10 AI actions and 5 captures per day. No credit card. Jira and Confluence connect with your own API token, kept in your keychain.