File a Jira issuefrom wherever you are
Select text in any app, hit the palette, and Khint writes the issue and files it. The other direction works too: pull an issue, your active sprint or a JQL search into the work session your agents already read.
Six rows in the palette,
three of them on by default
Connecting Jira does not add a Jira window to Khint. It adds rows to the launcher you already open with a shortcut, and you pick which ones you want to see. Reads land in your active Memory session so the next agent runs with that context; writes go straight to your site.
Reads, into your session
- Pull issue: fetch an issue by key into the active session
- Active sprint: your board's current sprint, issue by issue
- Search: a JQL query, written for you from plain English if you want
- Nothing pulled is sent anywhere. It lands in the local session
Writes, into the tool
- Create issue: the selected text becomes a written issue in your project
- Add comment: post what you selected on an existing issue
- Change status: move an issue along its workflow, To Do to Done
- Every write picks its target before the model runs, so cancelling costs nothing
Connect Jira in about two minutes
A personal API token, your email and your site. Nothing to install in Jira, no admin approval, no OAuth app to register.
Create an API token
Go to id.atlassian.com, open Security, then API tokens, and create one. Copy it — Atlassian shows it once.
Open Integrations in Khint and turn Atlassian on
Enter your Atlassian email, the token, and your site (mycorp.atlassian.net), then Save. The token goes into your operating system's keychain, not into a config file.
Open the palette and use a row
Cmd+Shift+K. Create issue and Change status are on by default. Pull issue, Active sprint, Search and Add comment are one checkbox away on the same card.
Watch it land in your session
Everything you pull or create is logged into the active Memory session, so the agent you run next already knows about it.
The same credential connects Confluence — one card, both tools. And once Jira is connected, Knowledge can keep a local full-text index of your issues so agents can search them without a pull.
What it is allowed to do
An integration that writes into your team's tracker has to be explicit about its limits. These are Jira's.
Your credentials, your machine
The token lives in your operating system's keychain and the REST calls go from your Mac straight to your Atlassian site. Khint's backend never sees your token and never proxies a Jira call.
It acts as you, and only where you can
A personal API token carries your own permissions. Khint reaches exactly the projects and issues your account can already open, so there is no access model to configure and none to get wrong.
The target is picked before the model runs
Create issue asks for the project, Add comment asks for the issue, Change status asks for the transition, all before a single token is spent. Cancelling at the picker costs nothing.
A landed write is never reported as a failure
The Memory entry is written after Jira confirms, best-effort. If that logging fails the issue still exists and the run still says so, because a ticket that reports failed invites a duplicate.
Pause keeps the credentials
Turning the card off pauses the integration: the rows leave the palette and workflows stop using it, but the token stays. Forget credentials is a separate, two-click button.
Jira Cloud, token only
Cloud sites with a personal API token. Server and Data Center are not supported, and OAuth is deliberately not built until someone asks for it.
Common questions about Jira and Khint
Do I need a Jira admin to install anything?
No. You create a personal API token on your own Atlassian account and paste it into Khint. Nothing is installed into the Jira site, no app is registered, and no admin has to approve anything. The token carries your permissions, so Khint reaches exactly what you can already open.
Does my Jira data go through Khint's servers?
No. The token is stored in your operating system's keychain and every REST call goes from your Mac straight to your Atlassian site. What you pull lands in a local Memory session, which is never synced. If an agent then rewrites that text, only the text you gave it reaches the model, exactly as with any other action.
What does a Jira write cost?
The Jira call itself is free. What costs is the writing: when the row hands your selected text to an agent to turn it into an issue title and description, that is one normal agent run against your monthly credits. Pulls make no AI call at all, so they are free, and so is picking a project or an issue.
Can I use Jira inside a workflow rather than as a single row?
Yes. Create issue and Add comment are also steps a workflow can take, so a chain can clean up your notes, file the issue and post the link to Slack in one press. A parallel step can even write to Jira, Slack and Confluence at the same time from the same running text.
Can Claude Desktop see my Jira through Khint?
Indirectly, and only what you pulled. Anything a Jira row pulled into your active session is part of the context Claude Desktop or Codex read over MCP. Khint does not expose a Jira tool to those clients: they read your session, not your tracker.
Which Jira does this work with?
Jira Cloud, with a personal API token. Server and Data Center are out of scope, and OAuth was deliberately deferred rather than half-built. Your site is the part before /jira in your Jira URL, for example mycorp.atlassian.net.
Stop retyping your own notes into Jira
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.