Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Bot import
People coming from Grok Bot (or from an app that already imported their Grok Bot agents) bring their agents
over in one step: an export file (.zip) on this computer becomes bots and group chats with their
instructions, avatars, skills, routines, memories and workspace files. Chats aren't copied; the export
keeps what matters in them as memories.
Flow
- The user adds the export skill to an agent in Grok Bot. The skill is
host/src/import/export-skill.md(EXPORT_SKILL); the desktop app copies it (+ → Import bots… → Copy export skill, host methodimportSkill) andcodync-host import --skillprints it. - They ask that agent "Export my agents for Codync". It writes
~/Downloads/codync-export-<date>.zip. - They choose the file: desktop + → Import bots… (
app:pickExportopens the dialog in the main process and returns a path), orcodync-host import <file>(--dry-runlists it,--only a,bpicks agents). Both callpreviewImportthenimportBotswith the path; both methods are loopback only (LOCAL_ONLY), since the path is on this computer.
Phones and the terminal UI have no import screen: the export file is on the computer, and the CLI covers the terminal.
Formats (host/src/import/manifest.rs)
| Manifest | format |
Written by |
|---|---|---|
codync-import.json |
codync-bot-import |
Codync's export skill |
openbot-import.json |
openbot-agent-import |
Other apps' Grok Bot export agents |
openbot-transfer.json |
openbot-instance-transfer |
Those apps' own transfer files (agents, memories, sections) |
The three share one shape (agents with key, name, title, description, avatar, skills,
routines, memories, files; optional channels). version above 1 is refused. A manifest inside one
top-level folder is found too. An agent, group or routine that doesn't check out is left out with a
warning; the rest imports.
What each part becomes (host/src/import/mod.rs)
- Bot:
createBotwith defaults;description= title, then instructions. A transfer file'sprovideris kept when that agent runs on this computer, else the bot gets the default agent and a warning; its model isn't (other apps' model ids aren't ACP ids). Colors and shapes cycle through the avatar choices. - Avatar:
setIconforbot:<id>; needs the computer signed in, else a warning and the default face. - Skills: each folder becomes a skill of that bot's own (
add_custom_skillwritten by the bot, on for it only), with the folder's other files besideSKILL.md. - Routines: schedules map to cron, interval or one-time triggers (
schedule.rs) in the routine's time zone (else this computer's). - Memories: into the bot's
MEMORY.mdas imported facts, through the same path as the old memory move (chat::memory::add_facts): checked, capped, the rest intoearlier.md. The count reported is what was written. - Workspace files: copied to
imported/in the bot's workspace. - Group chats: a group of the imported members; its routines and memories go to its lead (or first member), since Codync keeps them per bot. A group whose bots already share one (two channels of the same members, or one the user made) isn't made again: a warning says it joins that group.
A bot whose skills or files fail is deleted again with the skills and imported/ files it got; the others
carry on. Import counts as bots_imported in analytics (source and counts only).
Safety (host/src/import/archive.rs)
Entries are listed before anything is read: at most 5,000 entries and 500 MB inflated. Paths that leave the
archive and links are skipped; so are .env*, *private*key*, nested archives, .git and node_modules
(reported back), and Mac zip noise (silently). Every manifest path of an agent must sit in
agents/<key>/, and keys are lowercase letters, digits and hyphens.