Chain your agents with writes to Jira, Confluence, Linear, Notion, Slack, or Gmail. Select the text, hit your shortcut, and the routine runs through to a filed result.
Select the source text, hit ⌘⇧K, pick the workflow. Up to 5 steps run in series and end in a filed result, not a clipboard shuffle.
bump Premium €9.99 → €12.99 by Q2 · CS drafts the customer FAQ · sign off AC before ship
Runs the chain, ends with a filed ticket and a shared link.
The AI steps shape the text. A write step ships it: a Jira issue or comment, a Confluence page, comment or append, a Linear issue, a Notion page or append, a Slack post, a Gmail draft, or a hand-off to Claude.
The palette's idea bar plans a one-off workflow from your agents and connected integrations, shows you the plan before anything runs, and offers to save the good ones.
Khint previews the plan first. Nothing runs without your go.
Describe the routine, Khint drafts the chain.
Workflows keep the trigger they were made with.
Every step leaves a trace you can use.
A workflow is a chain of up to 5 work steps run in series behind a single shortcut. Each step is either one of your agents (a saved AI Action) or a write to a connected tool, and each step picks up where the previous one left off: rough notes become action items, then a formatted ticket, then a filed Jira issue. One keystroke in, one result out. Workflows have their own page in the app's sidebar, next to Agents.
A step can create a Jira issue or comment on one, create a Confluence page, comment on a page or append to one, create a Linear issue, create or append to a Notion page, post a Slack message, draft a Gmail email, or hand the running text to Claude. The AI steps shape the text; the write step ships it, and the issue key or page link it returns becomes the running text for the next step.
No. Open Generate with AI on the Workflows page and describe the routine in plain language, for example "turn my standup notes into Linear issues." Khint drafts the chain: it reuses agents you already have when they match, authors new ones where needed, and shows build notes for what it created or reused. If a step needs an integration you haven't connected yet, it flags a Connect prompt instead of guessing. You review, tweak, and save.
The palette opens with a "Your idea" input. Type what you want done ("summarize this and file it in Jira") and Khint plans it as a one-off workflow from your agents and connected integrations. You see the plan before anything runs: the steps, and the text it will run on. Confirm, it runs, and if the run was good Khint offers to save it as a real workflow you can trigger again.
Yes. Capture & ask has the same "Do this" entry as the palette: plan a workflow on a captured answer, or on a fresh capture before any chat. Save that plan and it keeps its origin, so a workflow born from a capture re-runs with a capture trigger: launching it draws a region on screen, extracts the text, and runs the steps on it.
A workflow run from the palette pastes the final text back where your cursor was. A run planned from the idea bar or a capture lands on your clipboard instead, with the created issue key or page link when the last step is a write, ready to drop into the thread you were in. Either way, every step logs into your active Memory session, so later actions can draw on what the workflow did.
Guided walkthroughs that run on this pillar, start to finish.
