The AI is in Word and Teams,the ticket is in Jira
Microsoft 365 Copilot is a per-seat licence your IT team assigns, and it runs inside the Microsoft apps: Word, Excel, PowerPoint, Outlook, Teams. A product owner’s day ends somewhere else, in a Jira ticket, a Confluence page, a Slack thread, a screenshot of a staging bug. Khint is the layer above all of them: select any text in any app, press one shortcut, and the result lands in the tracker instead of in another document.
Two assistants,
two territories
Copilot is strongest on Microsoft content: the document you are writing, the mail you are answering, the meeting you were in. The other half of the job is not Microsoft content. It is a refinement thread in Jira, a spec in Confluence, a customer message in Slack, a screen someone shared for four seconds. Khint covers that half: an agent is a prompt you saved once, it runs on whatever text you have selected, and the integrations put the answer in the tool your team actually reads.
A real workflow run: the notes leave the app they were written in and the last step posts the result into a channel other people are already reading.
A refinement session, filed before the next call
Thursday, 40 minutes of refinement in Teams, three things to file afterwards.
Leave the notes where the meeting left them
The notes are wherever you took them: a Teams chat, a OneNote page, a Word doc, a Confluence draft. You do not move them anywhere. Start a Memory session first and call it after the epic you are refining. Every agent you run gets logged to it, Khint keeps a compact running summary, and that summary rides along on the next agent so you stop restating the same product context ten times a day.
Select the text, press one shortcut
Highlight the block of notes and press Cmd+Shift+K. The palette opens over whatever app you are in and lists the agents in your active pack. Pick “Notes to tickets” and the rewritten version comes back in place. No prompt written yet? In Agents, type one line describing what you want and press Generate: Khint drafts the prompt, and Improve refines it later without you starting over.
The bug that arrived as a screenshot
Someone drops a screenshot of a stack trace, and the error string is an image. Khint's Capture rows handle it from the same shortcut: Extract text drags a region and puts the text on your clipboard, and Capture & ask opens a short conversation about what is on screen. Nobody retypes an error message off a picture, and nothing about the flow depends on the app the screenshot came from.
File it as a real ticket, fields and all
Connect Atlassian and the palette gains a Jira Create issue row. Khint reads the project first, drafts the issue with its summary, description, type and the fields your project marks required, then shows you one editable card. You change what you want and confirm, and the issue is created with its key and link coming back to you. The write only happens after you press the button, so a cancelled draft costs nothing.
Save the pass as a workflow
Once the sequence works, it becomes one press. A workflow chains up to five steps in series: agent steps that draft, then an integration step that writes. Its Starts from setting decides what it reads (your selection, your clipboard, a capture, a document, or your voice), and it can carry its own keyboard shortcut. Next Thursday the whole pass is that one key.
From the notes to the channel, in one run
Up to five steps in series, and each step’s result becomes the input of the next.
The running text is what moves between steps: the agent's draft feeds the Jira write, and the Jira write's receipt (the issue key and its link) is what the Slack post announces. Swap the destinations for yours, a Confluence page for the write-up, a Linear issue for the engineering side, a Notion page for the decision log. The run panel shows each step ticking over with the line it produced, so you can see what landed without opening the tool.
Where each one runs
Not a scorecard of models, a map of territory.
With Khint
- Runs on any text you select, in any app on macOS or Windows: a tracker, a browser, a chat window, a terminal.
- The instruction is a saved agent you reuse, grouped into packs and reachable from one shortcut.
- Writes into Jira, Confluence, Linear, Notion, Slack and Gmail, so the answer lands as a real ticket, page or message.
- Reads a screenshot when the input is a picture, through Capture.
- You download it and it works. No seat to assign, and Memory sessions stay in a local database on your machine.
With Microsoft 365 Copilot
- Runs inside the Microsoft apps: Word, Excel, PowerPoint, Outlook and Teams.
- A paid per-user licence on top of an eligible Microsoft 365 subscription, assigned by whoever manages your tenant.
- Strongest on Microsoft content: the file you are in, the thread you are answering, the meeting you attended.
- Work that is not a Microsoft file or a Teams meeting reaches it the way it reaches any assistant, by copy-paste.
- The output stays a document or a message in the suite, and filing it in the tracker is still your job.
What Khint does not claim
The honest edges, so the comparison is worth reading.
It does not live inside Word
Khint has no cursor in your document and does not suggest as you type. Hand it a file and it gives back an edited copy, leaving the original untouched.
It reads what you hand it
An agent sees the text you selected, or the document you picked, plus your session summary if that agent has the option ticked. It does not watch your screen or your mailbox.
Your Microsoft files are not indexed
Knowledge, the local index, covers Jira, Confluence, Notion and Linear. It is a copy on your own machine, and nothing about your OneDrive or SharePoint is in it.
Every write is deliberate
An integration step shows the draft on a card before it creates anything, and Super Khint puts a Run button on each proposed action. Nothing is filed while you are looking away.
You do not have to pick one
If your company pays for Copilot, keep it for the work it was built for: the deck, the long document, the mail thread, the meeting you missed. Khint is not trying to be a better assistant inside Word. It covers the part of the loop that never enters Office, turning what you have on screen into a filed ticket, a published page or a posted update without a copy-paste round trip. The two sit on the same machine, and Khint's privacy model is the one thing worth checking with your security team first: agents only see what you select, and Memory never leaves your device.
Common questions
Is Khint a replacement for Microsoft 365 Copilot?
No, and it is not sold as one. Copilot runs inside the Microsoft apps and is licensed per user on top of a Microsoft 365 subscription; it is at its best on the document, the mail thread or the meeting you are already in. Khint runs above every app on your Mac or PC: you select text anywhere, press one shortcut, and a saved agent transforms it. Most product owners who use both keep Copilot for the long Office work and use Khint for the twenty small passes a day that end in Jira, Confluence, Linear, Notion or Slack.
What does Khint add if my company already pays for Copilot?
Three things the suite is not positioned to do. First, reach: an agent runs on selected text in any application, including your tracker, your browser and the chat windows where half of a product owner's input arrives. Second, filing: connect Atlassian, Linear, Notion, Slack or Gmail and the palette can create the issue, append the page or post the message itself, with the draft shown on a card before anything is written. Third, repeatability: the instruction is saved as an agent and shared as a pack, so a team writes tickets the same way instead of each person improvising a prompt.
Can Khint create the Jira ticket itself, or does it just draft the text?
It creates it. Khint reads the project first to learn its issue types, its people, its priorities and the custom fields it marks required, then drafts the issue and shows you one editable card. You adjust the summary, the type or a field and confirm; the issue is created and its key and link come back as the result. Because the card is shown before the call, cancelling costs nothing, and a required field your project enforces is asked for on the card rather than surfacing as a failed request afterwards.
Where does my text go, and is any of it stored?
An agent only ever sees the text you selected, plus the compacted summary of your active Memory session when that agent has the option ticked. Memory sessions and the local Knowledge index live in a SQLite database on your own machine and are never synced to Khint's servers. Any agent can be set to redact emails, phone numbers and similar identifiers before the text reaches the AI, and if your team prefers to run on its own account you can bring your own Anthropic or OpenAI API key.
Does Khint work on Windows, or is it Mac only?
Both. Khint is a menu-bar app for macOS and Windows, and the core loop is identical on each: select text, press Cmd+Shift+K (Ctrl+Shift+K on Windows), run an agent, get the result back in place or written into a connected tool. Screen capture works on both as well, with its own region selector on Windows. A few extras, such as the PowerPoint diagram companion, are macOS only for now.
Keep Copilot, add the half it does not cover
Free with 300 credits a month, about 10 AI actions a day. No credit card, no seat to assign, no IT ticket to raise.