Type what you want done,Khint plans it and runs it
Saved AI actions are perfect for the work you repeat. But half of a product day is one-offs: this paragraph, this thread, this ask, right now. Khint's palette opens on an idea bar: describe the task in plain words, review the plan it proposes, and run it on your selected text, in any app, with one keystroke to get there.
The action you need
doesn't exist yet
You built actions for the recurring work: notes to ticket, polish the PRD, draft the status update. Then a request arrives sideways, and the honest options used to be a chatbot tab with three copy-pastes, or stopping to write and save a prompt for something you might never do twice. The idea bar is the third option: the palette's first input is a free-form “Your idea” field, focused the moment the window opens. Type the ask once, in your words, and Khint turns it into concrete steps built from your agents and your connected tools, with a preview standing between you and anything actually happening.
From a sentence to a filed ticket
Handling an unstructured bug report you never prepared an action for.
Select the text and open the palette
A stakeholder pings you a rambling paragraph about a login problem, mid-sprint, and you have no saved action for “rambling paragraph to bug report”. Select the text and hit Cmd+Shift+K: the palette opens with the idea bar already focused, waiting on “Tell Khint what to do…”.
Type the ask in plain words
“Rewrite this as a proper bug report and create it in Jira.” Press Enter. Khint plans the task against what you actually have: the agents in your active pack, plus the tools you connected on the MCP page. Planning is free, and your selected text is never sent to the planner, only your instruction is.
Read the plan before anything runs
Khint previews the steps: draft the bug report, then create the issue in Jira. Under the plan, an On:line quotes the start of the text it will run on, so you can confirm you grabbed the right thing. If part of your ask isn't possible, the preview says so instead of quietly skipping it. Nothing runs without your go.
Confirm, pick the details, watch it run
You confirm, choose the Jira project and issue type from the same pickers the palette's Jira commands use, and the plan executes: each AI step counts as one action from your daily quota, the issue is created, and its key lands on your clipboard with an on-screen confirmation. From selection to filed ticket without opening a browser tab.
Keep the winners
The next time you open the palette, Khint offers to save the run. One click turns the drafting step into a real, editable Action and the whole sequence into a workflow in your active pack. The one-off you improvised today becomes the named command you run tomorrow, no prompt writing involved.
What a plan looks like
Illustrative examples: the idea you type, and the steps Khint previews before you confirm.
The preview is the contract. Every plan lists its steps, quotes the text it will run on, and names anything from your ask it couldn't satisfy, before a single step executes or a single action of quota is spent. A tool-ending plan finishes by copying the created ticket key or page link to your clipboard, so the proof of work is already under Cmd+V.
One-off today, workflow tomorrow
The idea bar and the workflow builder are two doors into the same system. The builder is for processes you already know you repeat: you describe them once on the Agents page and design the result deliberately. The idea bar is for the task in front of you right now, and it only asks you to invest after the work succeeded: the save offer turns a good improvisation into named Actions and a reusable workflow, in your pack, editable like anything you built by hand. Either way you end up in the same place, a palette that speaks your process. If the ask is specifically about filing tickets, the dedicated Jira palette commands are there too.
Common questions
Does typing an idea use up my daily actions?
Planning is free. When you press Enter on an idea, Khint works out the steps and shows you the plan without touching your daily quota. Only when you confirm and the plan runs does each AI step count as one action, exactly like running a saved action would. Because the preview lists every step before you commit, you always know what a run will cost before you spend anything.
What does Khint send in order to plan my task?
Only your instruction. The text you selected is never sent to the planner: Khint plans from the words you typed plus the names of your saved agents and connected tools, and your selection is only used once you confirm and the steps actually run. The preview shows an excerpt of that text under 'On:', so you can check you grabbed the right thing before anything happens. Each typed instruction also passes the same server-side security validation as a saved action prompt.
What can a plan actually do?
A plan combines AI steps that transform your selected text with, optionally, one finishing write in a tool you have connected on the MCP page: create a Jira or Linear issue, create a Confluence page, post to a Slack channel, or draft a Gmail email. When the plan ends in a tool, the created key or link is copied to your clipboard. And if part of your ask is something Khint cannot do, the preview says so plainly instead of silently dropping it.
Do I have to re-type the same idea every day?
No. After a run succeeds, the next time you open the palette Khint offers to save it: one click turns the AI steps into real, editable Actions and the whole sequence into a workflow in your active pack, ready to run by name from then on. An idea that only needed a single AI step is saved as a single Action. For recurring processes you want to design deliberately, the workflow builder covers that side.
Say it once, ship it
Free with 10 AI actions and 5 captures per day. No credit card. The idea bar is waiting behind one shortcut.