Publish, append, comment, pull
The space and page pickers list your 20 most recently modified pages, so filing rarely means going to look for an id. A pull makes no AI call at all, so reading a page into your session is free.
Turn the notes you just took into a published page, add a decision to the end of a living document, or pull a page into your work session so the next agent writes with it in hand.
Confluence is where a decision goes to be found again, which makes it the tool people skip when they're busy. These four rows remove the trip, and Create page and Append to page are the two that are on out of the box.
Publishing is easy. Adding to a page somebody else is editing is the operation that can destroy work, and it's the one this integration spends its care on.
The space and page pickers list your 20 most recently modified pages, so filing rarely means going to look for an id. A pull makes no AI call at all, so reading a page into your session is free.
Publishing logs a session entry once Confluence confirms, so the agent you run next writes knowing the page exists, and your AI client reading over MCP sees it too.
Create page is a workflow step, including as one branch of a parallel step: one press can file the Jira ticket, publish the page and post the Slack update from the same running text.
Turning Atlassian off hides both tools' rows and keeps the token for an instant reconnect. Forget credentials is the separate, deliberate clear.
Confluence has no append and no partial update, so adding a paragraph is a read then a write one version up. Every rule below exists because that shape is the one that can go wrong.
Security and privacyIt's the same Atlassian card as Jira. If you've already connected Jira, Confluence is already on.
At id.atlassian.com, open Security, then API tokens. The same token covers Jira and Confluence: one credential, one card in Khint.
Your Atlassian email, the token, and your site (mycorp.atlassian.net). The token goes into your operating system's keychain.
Create page and Append to page are on by default. Pull page and Comment on page are a checkbox away on the same card.
Select your notes anywhere, hit Cmd+Shift+K, choose Create page, then pick the space. Khint writes the page and logs it to your active session.
An integration is where work comes in and goes out. These three are what happens in between.
No. Both live behind one Atlassian card in Khint and one API token. Connecting either connects both, and the palette then shows a Jira section and a Confluence section with their own rows, each of which you can hide.
Yes, in the sense that it won't overwrite them. Confluence offers no append and no partial update, so Khint reads the page and writes it back one version up. That version acts as a lock: if the page moved while you were writing, the write fails with a clear message instead of replacing their edit. Retry and it appends to the new version.
No. The existing storage markup is copied through raw and only your new content is escaped. Nothing parses or regenerates the body that was already there, so macros, tables, layouts and attachments come out unchanged. Khint deliberately doesn't offer any flow where a model rewrites existing page content.
Yes. Create page asks for the space and then, optionally, a parent page, and the picker lists the 20 most recently modified pages of that space so you rarely have to go looking for an id.
Only if you switch Knowledge on for Confluence, and then only on your own Mac, in a local full-text index that never reaches our servers. Without it, a page exists in Khint just as long as the Memory session you pulled it into, which is also local.
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.