Type an idea into the palette and Khint plans it from your own agents and connected tools. You see the plan before anything runs. Keep the run that worked and it becomes a reusable agent or workflow.
Khint drafts the steps from the agents in your active pack and the tools you have connected, then shows them to you. Nothing runs until you confirm, and anything it could not cover is listed rather than quietly dropped.
Khint previews the plan first. Nothing runs without your go.
The palette opens on the idea bar, focused and empty.
With the palette open, dictation fills the idea bar.
Capture & ask has the same "Do this" entry.
A planned run is a one-off: nothing is saved unless it worked and you say so. Then Khint writes the steps out as real agents and a real workflow with its own shortcut, so the second time is one keystroke. Go deeper: Workflows →
A saved plan keeps the trigger of the surface it was born on: planned in the palette it re-runs on your selection, planned from a capture it re-runs from a region on screen, planned on a file it asks for the next file.
Planning is separate from running on purpose: the plan is free, the run is the part that acts.
Steps, the text they will run on, and anything Khint could not cover, all shown before you confirm. Esc walks away.
The planner only sees your sentence, your agent names and which tools you connected. The text you selected is never sent to it.
Resolving a plan never spends credits, so cancelling costs nothing. Only the AI steps you run are billed, one action's worth each.
Khint never infers an intent from a question you asked. The idea bar is the only place you describe work, and it is always an explicit Enter.
The palette opens on a "Your idea" input. Type what you want done in plain language, for example "summarize this and file it in Jira", and press Enter. Khint turns the sentence into a plan: a short chain of steps built from your own agents and the tools you have connected. You see the plan before anything runs, confirm it, and it runs.
No, and that is the point. The idea bar is the way in for work you have not set up yet: Khint writes the steps for this run. If the result was good it offers to save them, so the throwaway run becomes a reusable agent or workflow you can trigger by shortcut afterwards. You end up with a library you described rather than one you assembled.
The agents in your active pack, plus the write actions of the integrations you have connected: create a Jira issue, create a Confluence page, create a Linear issue, create a Notion page, post to Slack, draft a Gmail email. Anything it cannot cover with those is reported in the plan as unmet instead of being quietly dropped, so you never discover a missing step mid-run.
Yes. With the palette open, holding your dictation shortcut sends the transcript to the idea bar instead of pasting it into the app behind. The text is filled in, never fired: you read back what Khint heard and press Enter yourself. Nothing is ever planned from words nobody has seen.
Yes. Capture & ask carries the same entry point: a "Do this" button on an answer, or on a fresh capture before any chat. Khint plans on what it read from the screen, runs the steps live in the thread, and puts the created issue key or page link on your clipboard. A plan born from a capture keeps that origin when you save it, so re-running it starts with a region capture.
The run does; the planning does not. Your selected text is never sent to the planner: it only ever sees the sentence you typed, your agent names, and which tools you have connected. The plan card then shows you the text the run will actually work on before you confirm.
Planning is free and never spends credits, so a plan you cancel costs nothing. Running it costs what the same work would cost as a normal run: one action's worth of your monthly credits per AI step, and nothing extra for the steps that write to your tools.
A chat gives you text to copy. The idea bar gives you the work done: it runs on the text you are already looking at, in your own agents, and it can end by filing the ticket or publishing the page. It also stays separate from search on purpose: the search box filters the actions you have saved, the idea bar describes work you have not saved yet, and intent is never guessed from a question you asked a capture.
Guided walkthroughs that run on this pillar, start to finish.
Jira