An error on screen,a filed bug a shortcut later
A stack trace in Slack, a crash dialog in a tester's screenshot, and the bug never gets filed because retyping forty lines is nobody's job. Khint captures the error off the screen, shapes it into a real bug report with a reusable AI action, and files it to Jira from the same keyboard shortcut.
The bug that never
made it to the board
Errors arrive as pictures: a screenshotted console, a red dialog, a photo of someone else's laptop. To file them you squint at the image, retype the trace, guess at the steps, and remember to add the build number, so half of them never get filed at all, and the other half land as “it broke, see screenshot”. Khint closes that gap with its three pillars (Capture, Agents, and Memory) wired together behind one palette, so the error on screen becomes a structured ticket without ever being retyped.
Screenshot to ticket, step by step
Clearing the bug channel on a Tuesday morning.
Open a triage session
Before you start clearing the bug channel, start a Memory session: call it “Tuesday triage”. Every captured error and every ticket you file is logged to it, and Khint keeps a compact running summary that rides along on each AI Action, so by the third bug the model already knows the build, the area, and what you have already filed. How Memory works →
Capture the error off the screen
A developer drops a stack trace in Slack; a tester pastes a screenshot of a crash dialog. Hit Cmd+Shift+K and run Extract text: draw a box around the error and the text lands on your clipboard: no retyping a forty-line trace. For an image you can't select, Capture & ask opens a Vision chat so you can pull the relevant lines out of the picture. How Capture works →
Turn the raw error into a bug report
In Agents, save an Action like “Error to bug ticket”. No prompt yet? Type a description and press Generate: Khint drafts one that returns a clear title, steps to reproduce, expected vs actual, and the environment line a developer always asks for. Or clone the Support Desk starter pack. Select the captured text, hit the shortcut, run it, and the structured report is pasted back in place.
File it where the team works
With Atlassian connected, the palette's Jira Create issue row opens the bug in your project straight from the structured text: one issue per run, so each filing is deliberate. On Linear, the Create issue row does the same. The new ticket key comes back so you can drop the link wherever the conversation started. How integrations work →
Keep the thread tidy
Chain your “Error to bug ticket” Action and the Jira create step into one Workflow so “captured error → filed bug” is a single keystroke after the capture. Because every step is logged to the triage session, the end of the morning leaves you a clean list of what was filed, not a scroll of half-remembered screenshots.
From a forty-line trace to a ticket a dev can pick up
The shape of the report is yours to set: this is one example of what an Action might return.
The fields above are just an example: the judgment lives entirely in the prompt you save, so a team that always wants a repro link, a team that needs a severity, and a team with a compliance note each get the bug template they asked for. Tighten it over time with Improve, or clone the Support Desk starter pack from the Agents page rather than writing from scratch.
Why not just paste the screenshot into a chatbot?
You can, and for the tenth bug of the morning you'll re-explain your bug template every chat, get a different shape each time, and copy the result into Jira by hand. Khint removes the round-trips: the capture is one shortcut, the bug-report Action is saved once and reused on every error, Memory carries the build and product context into each report, and the Atlassian and Linear rows file the ticket where the team will actually see it. It also pairs with the way you already turn raw notes into work: see meeting notes to a Jira ticket and requirements from screenshots.
Common questions
How does Khint read an error message off the screen?
Capture lives in the palette (Cmd+Shift+K). Extract text draws a region around the error (a stack trace, a red toast, a crash dialog), runs OCR, and drops the recognised text on your clipboard, with a small confirmation in the overlay HUD. If the error is a screenshot you can't select (a console image pasted in chat, a photo of a colleague's screen), Capture & ask opens a short Vision chat about the picture so you can pull out the relevant lines. Either way the raw error becomes text you can act on, without retyping it.
Does the screenshot get uploaded anywhere?
OCR and the Vision chat send the captured image to Khint's vision endpoint to turn it into text: that is the one call needed to read the picture. After that, the AI Action that shapes the ticket only ever sees the text you selected, plus the compacted summary of your active Memory session if you opted in. Memory sessions live in a local SQLite database on your Mac and are never synced to Khint's servers, and your Jira credentials sit in your OS keychain. Nothing else about your screen leaves the device silently.
Can Khint file the bug straight into Jira?
Yes. Connect Atlassian once with your email, an API token, and your cloud domain, and the palette gains a Jira Create issue row. Run it on the structured bug text and Khint opens the issue in your project: one issue per run, so nothing is filed silently. If your team runs on Linear instead, the Create issue row does the same there. Both log the new ticket into your active Memory session so the triage pass keeps a record.
Do I have to write the bug-report prompt myself?
No. In the Action editor, type a one-line description like "turn this raw error into a bug report with title, steps to reproduce, expected vs actual, and environment" and press Generate: Khint drafts the prompt; press Improve later to tighten it in place. Khint also ships a Support Desk starter pack you can browse and clone from the Agents page, which gives you a working triage Action to adapt.
File your next bug from a screenshot
Free with 10 AI actions and 5 captures per day. No credit card. Capture once, file the ticket without retyping a line.