Set up your second computerin one sign-in
The agents you sharpen over months are the ones you press every day, and a new laptop should not mean typing them all in again. Sign in to Khint on the second machine and your packs arrive: the prompts, the workflows, the order you put them in, and the shortcut on each one.
Two computers,
two sets of prompts
A prompt is only good after you have run it fifty times and fixed the three things it kept getting wrong. Retyping that from memory on a second machine gives you a rougher copy of it, and from that day the two drift: the version that files your tickets properly is on the laptop you left at the office. Khint keeps agents and workflows in your account, so there is one copy of each and both machines run it.
Meeting to Ticket
Product owner · from raw notes to filed work
The real palette. A pack holds your agents and workflows, and switching the active pack swaps the rows you see; it is these packs that arrive when you sign in somewhere new.
From a fresh install to your own palette
What happens on the second machine, in the order it happens.
Sign in once on each computer
Install Khint and sign in. The desktop app shows a code, you confirm it in the browser where you are already signed in, and the app keeps the session from then on. It is the same account on macOS and on Windows, so a work Mac and a home PC are two machines, not two setups. There is nothing to export from the first one.
Your packs arrive with their shortcuts
On a signed-in start Khint pulls your packs from your account: every agent with its prompt and its input source, every workflow with its steps in order, the order you dragged the rows into, and the keyboard shortcut recorded on each one. Press the same combination you press at work and the same agent runs.
Keep editing on whichever one you are sitting at
Khint pushes after a change and pulls when it starts, so an improvement you make in the agent editor on Tuesday is what the other machine runs on Wednesday. A push that could not go through, because you were offline on a train, is sent up on the next round rather than replaced by the older copy in your account. In practice, edit in one place at a time and let the other catch up.
Notice what did not come with them
Your Memory sessions are not on the new machine, and neither is the text of anything you have run: those live in a local database and stay there. Your Knowledge index of Jira, Confluence, Notion and Linear is built per machine too, so the new one fills its own copy in the background. That is a design decision, not a gap, and the next section says why.
Reconnect your tools, once per machine
Credentials are the one thing you enter again. Open Integrationson the new computer and connect Atlassian, Linear, Notion, Slack or Gmail: each is stored in that machine’s own operating-system keychain, never in your account. Which palette rows each integration shows is a per-machine choice as well. Settings then Account shows when your packs last synced.
Two ways to make the new machine yours
Both end with your agents on it. One of them ends with two copies that drift.
Rebuild it by hand
Open the old machine beside the new one and copy across.
- Retype every prompt, and lose the wording you fixed last month
- Record every shortcut again, and find the ones that now collide
- Rebuild each workflow step by step, including the filled-in Jira fields
- From here on, improve a prompt and only one machine has the improvement
Sign in
The packs are in your account, so the new machine reads them.
Download Khint Free- Agents, workflows, prompts, row order and shortcuts arrive on the first launch
- One copy of each agent, so an improvement is everywhere by the next start
- Nothing to export, nothing to import, no file to keep in a drive folder
- A pack a colleague shared with your team reaches you by the same route
What stays on the machine that made it
Four things Khint deliberately does not put in your account.
Memory sessions
Sessions, their entries and their recaps live in a local database on the machine you worked on. A session you started on the Mac is not on the PC, and Khint does not copy it to a server to make it so.
The text of your runs
History syncs as an index: what you ran and when. The input and the output stay local, so the second machine can list a run from last week without ever having held the meeting notes behind it.
Your knowledge index
The searchable local index of your Jira issues, Confluence pages, Notion pages and Linear issues is built and stored on each machine, from your own credentials. Nothing about your workspace passes through Khint to get there.
Tool credentials
Atlassian, Linear, Notion, Slack and Gmail credentials go in the keychain of the computer you entered them on. Connecting a tool is therefore a per-machine step, and revoking one machine leaves the others alone.
Why the useful half is the half that travels
An agent is a prompt you wrote: it is yours, it is short, and it is worth having on every machine you work from. A Memory session is the content of your week, the notes, the ticket bodies, the client names, and it gains nothing by sitting on a server. Khint splits along that line on purpose, which is why signing in on a new laptop gives you your whole palette and none of your material. What stays on the device covers the rest of that reasoning, and if a teammate needs your agents rather than your second machine, a shared pack is the same mechanism pointed at a colleague.
Common questions
Do my AI actions sync between my computers automatically?
Yes, as long as you are signed in on both. Khint pushes your packs to your account after a change and pulls them when it starts, so agents, workflows, their prompts and steps, the order of the rows and the keyboard shortcut on each one are the same on every machine. There is no export file and no manual import. Settings then Account shows the last time packs and history synced, so you can check a machine is up to date before you close it.
Does the text I run through Khint sync too?
No. History syncs as an index only: the action name and the timestamp, so a fresh install can show you what you have been doing. The input text and the result stay in the local database of the machine that ran them, which is why an old run opened on a second machine shows the action without the content. Memory sessions and their entries are local as well and are never sent to Khint's servers at all.
Can I use the same account on macOS and on Windows?
Yes. Khint runs on both, and one account covers both: sign in on each machine and the same packs arrive. Your agents and workflows are the same objects on either platform, so a workflow built on the Mac runs from the same shortcut on the PC. The parts that are tied to the operating system, such as where your credentials are stored, are set up once per machine.
What if I edit the same agent on both machines?
Khint pulls the copy in your account when it starts and pushes yours after you change something, so the machine you last edited on is the one that wins. Edits that have not reached your account yet are pushed up on the next round instead of being replaced by the older copy, which is what protects work done offline. The practical habit is to edit in one place at a time and let the other machine pick it up at its next start.
Do I have to reconnect Jira, Slack and Gmail on the new machine?
Yes, and that is deliberate. Integration credentials are kept in the operating-system keychain of the machine you entered them on rather than in your Khint account, so a new computer connects each tool once from the Integrations page. It takes a couple of minutes and it means signing in to Khint somewhere new never hands that session access to your work tools.
Your palette, on whichever machine you open
Free with 300 credits a month, about 10 AI actions a day. No credit card. Build an agent once and sign in wherever you work.