It writes the issue, not just files it
Your selection becomes a real title and description rather than a paste of the raw text, and the preview is shown before anything reaches Linear.
Select the bug report, the feedback or the half-sentence you just wrote, press the shortcut, and Khint drafts a title and a description and files the issue in your team. You see the preview before it goes.
Linear adds a single row, deliberately. The issue you meant to file gets lost in the trip to the browser, not in the typing, so the integration removes the trip and nothing else. What Khint adds on top is the writing.
The row is small on purpose. What makes it worth connecting is where the issue comes from, where its receipt goes, and that the same write is available to a workflow.
Your selection becomes a real title and description rather than a paste of the raw text, and the preview is shown before anything reaches Linear.
LIN-88 lands in the active Memory session once Linear confirms, so the next agent runs knowing it exists, and so does the AI client reading your session over MCP.
Create Linear issue is a workflow step too, including as a branch of a parallel step, so a triage workflow can file the issue and ping the channel from the same running text.
There's no Linear pull row. Reading happens through Knowledge: switch the source on and your issues are indexed locally for agents to search, in milliseconds and for zero credits.
A personal API key carries your own access, so there's no workspace install and nothing for an admin to grant. Khint won't transition, reassign or close anything.
Security and privacyA personal API key from your own Linear settings, then the team you file into by default.
In Linear, open Settings and create a personal API key. It carries your own access, so there's nothing for an admin to approve.
Paste the key and Save. It goes into your operating system's keychain, never into a config file on disk.
Khint fetches your teams live and you choose the one new issues land in. You can change it whenever you like from the same card.
Select text in any app, press Cmd+Shift+K, choose Create Linear ticket from selection. Khint writes the issue, shows you the preview, files it, and logs it to your session.
An integration is where work comes in and goes out. These three are what happens in between.
Because it's the one that removes a trip. Filing an issue means leaving the app you're in, finding the tab, and retyping something you already wrote; reading Linear rarely does. The read side is covered differently: switch Linear on in Knowledge and your issues are indexed locally, so an agent can search them without a palette row at all.
No. You create a personal API key in your own Linear settings and paste it into Khint. Nothing is installed into the workspace, no OAuth app is registered, and the key carries only your own access.
The Linear call is free. Drafting the title and description is one normal agent run against your monthly credits, the same as any other action. Picking the team costs nothing.
The default team is what the palette row files into, and you can change it at any time from the Linear card. Inside a workflow, the Create Linear issue step pins its own team, so different workflows can file into different teams.
Only if you switch Knowledge on for Linear, and then only in a local full-text index on your Mac that never reaches our servers. Toggling the source off, or forgetting the credentials, deletes that index immediately.
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.