GlinkBot documentation

Move from Grok Bot

GlinkBot setup and usage guidance.

GlinkBot is an open-source alternative to Grok Bot, with no tie to xAI. You can bring each of your Grok Bot Bots over, with its instructions, skills, routines, memories and the list of apps it used. It takes a few minutes per Bot, and nothing changes in Grok Bot.

Grok Bot has no export button. So GlinkBot gives you a message to send to each Bot, the Bot writes down its own setup, and GlinkBot reads what it wrote.

What comes over

From each Grok Bot BotIn GlinkBot
Name, title and descriptionA new bot with that name. If you already have a bot with the name, the new one gets a number after it.
Instructions (its role, job and lasting rules)The bot's instructions, up to 24 KB.
Skills, with their full textThe bot's skills, up to 30 per bot. Each one is switched on, unless a safety check keeps it off (see below).
Routines on a scheduleRoutines in the same time zone, paused, up to 50 per bot.
Routines that start on an event (Slack, GitHub, email, a webhook) or whose schedule can't be readSaved as a note in the bot's memory, memory/grok-bot-event-routines.md, with their trigger and full instruction, so you can set each one up again.
What it remembers, and what it knows about youThe bot's memory (MEMORY.md), under Notes from Grok Bot.
Connected apps and MCP serversListed as apps to connect again. Where the Bot gave a remote MCP server's https address, GlinkBot keeps that address with any key taken out.

What doesn't come over

Before you start

Move a Bot, step by step

1. Open Move from Grok Bot

In GlinkBot, open Settings → Import & export and choose Move from Grok Bot. You can also type grok in the Settings search.

A new install shows a Move from Grok Bot popup once, after your first chat. Let's start opens the same thing. If you chose Not now, it stays in Settings → Import & export.

2. Send your Bot the message

Choose Copy the message, then paste it into your Bot's chat in Grok Bot and send it. Do this once per Bot.

The message asks the Bot to write its whole setup as one file named grok-bot-export-<its name>.json: in your Downloads folder if it can write to your computer, otherwise attached to its reply, or as a JSON block in the reply. It also asks the Bot to change nothing, to leave out keys and passwords, and to say what it couldn't read instead of guessing.

If the setup is too long for one message, the Bot splits it into several parts. Bring back all of them: GlinkBot puts them together.

3. Bring back what it wrote

Any of these works:

Then choose Continue.

4. Check what would come over

What would come over shows each Bot with its number of skills, routines, memories and routines saved as notes, and says:

Choose Back to bring back a different reply, or Import.

5. Import

Each Bot becomes a bot in your sidebar, and GlinkBot opens the first one. The report names each Bot (Bramble is here, for a Bot called Bramble) with what came over. If one Bot can't be added, the others still are.

Choose Move another Bot for the next one, or Done.

After you import

  1. Choose the bot's engine and model in the bot's settings, if it should not use your default.
  2. Turn routines on. Turn each one off in Grok Bot first, then on in GlinkBot, so it doesn't run twice.
  3. Set up event routines again from the note in the bot's memory (memory/grok-bot-event-routines.md). You can ask the bot to do it: for example, "set up the routines in your Grok Bot notes".
  4. Connect apps again under Connected apps.
  5. Check skills that stayed off. A safety check keeps a skill off when its text has a long base64-looking blob, pipes a download straight into a shell (curl | sh), or has invisible Unicode characters. Read it, then switch it on in the bot's skills if you trust it.
  6. Add files the bot needs to its folder.

What GlinkBot reads on your computer

Only while Move from Grok Bot is open in the desktop app, and only when your bots live on this computer:

It never opens Grok Bot's sign-in files, cookies or chats. A file you drop on the dialog is read by the dialog only: it is not attached to the chat behind it.

When something goes wrong

GlinkBot saysWhat to do
That doesn't look like what your Bot writes.Copy the Bot's whole reply, or choose the file it made.
Your Bot's reply looks cut off.Ask the Bot to send the rest as another message in the same shape, then paste both.
That's larger than 4 MB.Ask the Bot to split it into several messages.
This has passwords or keys in it, so nothing was read.Ask the Bot to write it again without them.
This was written for a newer GlinkBot.Update GlinkBot, then try again.
This couldn't be turned into a bot.Ask the Bot to write it again.
Already hereThat Bot was moved before. Delete the moved bot first if you want to move it again.

Not the same as Backups

Settings → Import & export → Import backup restores a GlinkBot backup (an encrypted .ombbackup file) and replaces everything in that installation. It does not read Grok Bot files: use Move from Grok Bot for those.

GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.