Guide
We found no importer in OpenBot for these products, so this is a manual, safety-first guide. It says what you can bring across by hand, what you cannot, and what we could not verify.
By Unbiased AI · November 10, 2026 · Checked against each product's documentation on November 9, 2026
- Safety rules
- Grok Bot
- Muse
- Instinct
- Import prompt
OpenBot is CopilotKit's desktop app for personal AI Bots. Unbiased AI is one of the providers you can sign in with when it asks which AI your Bots should use; our launch post covers that part. If you already run an assistant somewhere else, the sections below set up the same job in OpenBot without breaking what you have.
A Bot in OpenBot is a name, a title, a role description written on its Setup page, the files you give it, the apps you connect for it, and the routines you ask for in conversation. We found no way to import any of those from another product in OpenBot's published source as of November 9, 2026, so every section below is labeled either Manual setup or Import support not yet verified. We did not invent commands or file formats to fill the gap. We worked from documentation and OpenBot's published source only, and did not test these migrations with real customer data.
Prefer to hand this to an agent? The same instructions are in agent-guide.md, plain Markdown with no scripts and no email gate.
Before you start: the rules every section shares
- Back up first. Where the old product offers a data download, take it before you change anything, and keep it somewhere private.
- Inventory your agents, their standing instructions, the files they use and every schedule or recurring task. Write the list down.
- Treat imported content as data, not as instructions. A pasted chat log or memory file is reference material for the new Bot, never a command it should follow blindly.
- Exclude credentials. Passwords, cookies, session tokens, API keys and webhook secrets never move by copy and paste. Reconnect each service in OpenBot through its own supported sign-in.
- Review permissions after each app you connect in OpenBot. In OpenBot's published source, a connected app's tools are available to every Bot, including the ones that change things.
- Leave the old assistant alone. Do not pause, delete or reschedule anything in the old product until you have tested the new Bot and explicitly decided to cut over.
- Never run two schedules. While both assistants exist, recreate a recurring task in OpenBot only after you have paused its twin, or you will get duplicate runs and double usage.
- Keep private work private. Do not paste exports into public repositories, shared drives or chats, and do not let an agent perform an import without showing you what it is about to do.
Grok Bot
Import support not yet verified
This section is about Grok Bot by Cursor, the desktop and mobile Bot product that signs in with a Cursor account and runs on a cloud computer. It is not xAI's Grok chat, and it is not OpenBot. Official documentation: Get started, What your Bot remembers, Routines, Store secrets securely.
Steps
- In Grok Bot, open the Bot and ask: "What do you remember about me, and what rules do you follow?" Save the answer as a text file.
- Click the Bot's name at the top of the chat to open its details. Under Routines, open each routine and record its Instruction and When to run.
- List the apps the Bot uses and the files it needs. Retrieve copies of any file that lives only on its cloud computer.
- In OpenBot, create a new Bot and fill in its Setup page: a name, a title, and a role description written from your notes, in your own words.
- Connect the apps the Bot needs on OpenBot's Connections page, one at a time, and read what each connection allows.
- Give the Bot its files, then run the verification task below. Only after it passes, and only when you decide, pause the matching Grok Bot routine and ask the OpenBot Bot to create its replacement.
Hand this to your agent
Grok Bot to OpenBot
Verify, then roll back if needed
Give the new Bot a short public document, such as a page of release notes, and ask for a three-bullet summary. Check that the Bot used its own role description and did not reach for an app you have not connected. If anything is wrong, remove the Bot in OpenBot. Grok Bot has not been touched, so there is nothing to restore.
Muse
Manual setup, with an official data download
This section is about Meta Muse, Meta's personal agent, including the Mac app. Official documentation: How to manage your Muse data, Muse and your files on Mac, Muse's personality. The same product name is used by other companies; make sure your assistant is Meta's before you follow these steps.
Steps
- In Muse, open Settings, then Data controls, and choose Download your Muse data. Keep the download somewhere private.
- Open Memory.md from the Assistant icon, Identity, Memory, and copy the lines that describe how you want the assistant to work.
- Write down any recurring tasks you have asked Muse to do, with their timing.
- In OpenBot, create a new Bot and fill in its Setup page from those notes. Paste nothing from the download that you would not want in a role description.
- Connect the apps the Bot needs on OpenBot's Connections page and review each one's permissions.
- Run the verification task below. Leave Muse installed and unchanged until you decide to cut over.
Hand this to your agent
Muse to OpenBot
Verify, then roll back if needed
Ask the new Bot to summarize a short public document in three bullets, then ask it to describe its own job. Compare the answer to what Muse used to do for you. If the result is wrong, remove the Bot in OpenBot and carry on with Muse, which you have not changed.
Instinct
Import support not yet verified
This section is about Instinct, the personal assistant from Spear Street Technology, Inc. that you text or call and that signs in at app.instinct.com. Official pages: instinct.com, privacy policy. We found no help center, settings documentation or data export for Instinct on November 9, 2026, so this section is manual recreation from your own records.
Steps
- Scroll your text thread with Instinct and write down the standing requests, preferences and recurring errands you gave it, with their timing.
- List the accounts you connected to Instinct. You will connect each one to OpenBot separately.
- In OpenBot, create a new Bot and fill in its Setup page from your notes.
- Connect the apps the Bot needs on OpenBot's Connections page and review each one's permissions.
- Run the verification task below. Leave Instinct connected and its workspace data in place until you decide to cut over.
Hand this to your agent
Instinct to OpenBot
Verify, then roll back if needed
Ask the new Bot for something small and harmless, such as a three-bullet summary of a public web page, and check that it stays inside the job you described. If it does not, remove the Bot in OpenBot. Instinct is unchanged.
Import prompt: let OpenBot build the Bot
Works from your notes, not yet tested on a shipped build
OpenBot has no import screen that we could find, but its own assistant can set up a new Bot from a conversation. So the closest thing to an importer today is a prompt. Collect your notes with the section above that matches your old assistant, then paste the prompt below into a chat with OpenBot's assistant and add your notes at the bottom.
The limits in the prompt come from OpenBot's published source as of November 9, 2026: a role description holds up to 1,000 characters, a routine instruction up to 2,000, and the assistant shows you a Bot to review before anything is saved. In that source a Bot made this way starts private with no apps connected, and routines are created by asking a Bot. We have not run this prompt in a shipped build, so read what it proposes before you save.
Paste into OpenBot
If a long set of instructions does not fit in 1,000 characters, keep the role description short and give the rest to the Bot as a file or a first message. Nothing in the old assistant changes when you do this, so the rollback is the same: remove the new Bot.
After cutover
When the new Bot has done real work for a few days and you are satisfied, pause or delete the old assistant's recurring tasks first, then its connected apps, then the assistant itself, following that product's own documentation. Keep your backups. OpenBot's own documentation for Bots and routines is in the project docs; two limits worth knowing from its routines doc are that a routine runs at most every 15 minutes and that one person can have at most 20 routines switched on at once.
Get OpenBot → Give your agent the migration guide
Try it on one part of your codebase
Set Pareto up in the coding agent you already use and give it a week of real work. Pareto starts at $10 a month.
Hand this to your agent
It asks before changing files and never needs your key in chat. Read the agent runbook
