A Slack thread becomesa filed Jira ticket
The bug got reported in a thread. The scope call got argued out in another. By the time you go to log it, half the detail has scrolled away. Khint pulls the whole Slack discussion in, turns it into a clean ticket with one AI action, and files it in Jira, without you ever leaving the keyboard.
The decision happened in Slack,
the ticket has to happen somewhere else
Product owners and analysts live in threads. A regression gets spotted, three people pile on with repro steps, someone decides it is a P1, and then it stalls, because turning that conversation into a proper Jira issue means scrolling back, copy-pasting fragments, and rewriting them into something a developer can act on. Khint collapses that gap. It sits behind one palette shortcut, and its three pillars (Agents, Capture, and Memory) plus its Slack and Jira integrations let the ticket be written where the discussion already is.
From thread to ticket in five moves
Every step runs from the same palette shortcut.
Pull the whole thread, not a screenshot of it
A bug report or a scope decision rarely lives in one message: it is buried across a dozen replies. Open the palette with Cmd+Shift+K, run the Pull thread row in the SLACK section, and Khint reads the entire discussion into your workspace. With a Memory session open, that thread is logged as session context, so the next step sees every reply in order.
Let an Action turn the chatter into a ticket
Run a reusable Action(your own “Write a bug ticket” prompt, or one cloned from a starter pack) over the pulled thread. Scattered messages become a clear title, a description with steps to reproduce, and acceptance criteria. Because the Action reads your active session, it already knows which product area the thread belongs to.
File it in Jira from the same palette
Connect Atlassian on the Integrations page and the palette gains a JIRA section. Run Create issue and the formatted ticket is filed straight to your project. One issue per run, so what lands in Jira is exactly what you reviewed. No browser tab, no re-typing what the thread already said.
Post the ticket back so the thread gets closure
The same SLACK section has a Postrow. Drop the new ticket reference back into the channel so everyone who was arguing in the thread knows it is captured and where it now lives. The loop closes where the conversation started, and nobody has to ask “did anyone log this?”
Save the repeat as a Workflow
Once the format-then-file rhythm feels routine, chain it. A Workflow strings up to five steps in series (the ticket-writing Action, a Jira Create issue step, and a Slack Post step), so after you pull a thread, one launch runs the whole hand-off instead of three separate clicks.
Context follows the ticket
The reason a pulled thread becomes a good ticket and not a wall of quotes is Memory. Start a session for the feature you are shepherding and every pull, every Action, and every filed issue rides on the same compacted context, so a bug logged from a Slack thread inherits the epic you have been grooming rather than starting from zero. Prefer to keep the same reasoning for a Linear-based team? Drafting Linear issues works the same way, and writing to Jira from anywhere covers the case where the source is any app, not just Slack.
Common questions
How does Khint get the Slack thread in the first place?
Connect Slack once from the MCP page by pasting a token, and the palette gains a SLACK section with Pull thread, Pull channel, Post, and Search messages rows. Pull thread reads the whole discussion (every reply, in order) into Khint instead of you copy-pasting messages one at a time. If a Memory session is active, the pulled thread is also logged there, so the Action that writes your ticket sees the full context and not just the last message you happened to select.
Does it just dump the raw Slack messages into the ticket?
Only if you want it to. The Create flow runs the pulled thread through a reusable Action first, so a scattered back-and-forth becomes a clean title, a description, and acceptance criteria before anything lands in Jira. Because the Action can read your active Memory session, the ticket inherits the product area you have been working in rather than starting cold from a wall of chat.
Can I search Slack for the right thread, not just pull one I have open?
Yes. The palette's SLACK section includes Search messages, so you can find the discussion by keyword without leaving your keyboard. Search needs a Slack user token (the xoxp- kind); a bot token is rejected with a not_allowed_token_type error, so if search returns nothing check which token you pasted. Every Slack row is individually hideable from the Slack card on the MCP page, so you can show only the ones you use.
Where do my Slack and Jira credentials live?
Locally. Slack connects with a pasted token and Atlassian with your email, an API token, and your cloud domain, all stored in your operating system's keychain, not on Khint's servers. Both integrations are local-only: the Slack read and the Jira Create call go straight from your Mac to those services with your own tokens, one action per run, so nothing is filed or posted silently in the background.
Stop losing tickets to the scroll
Free with 10 AI actions and 5 captures per day. No credit card. Connect Slack and Jira with your own tokens, kept in your keychain.