Experimental and not an officially supported Microsoft product or service. Provided as is under the repository's MIT license, with no support or warranty. Use at your own risk. Trademark use follows the repository's trademark notice.
Bring your AI setup into a Brainstem you own
Your instructions, skills, tools and memory from another AI assistant or AI coding tool, as plain files on your device.
Install into Brainstem
curl -fsSL https://microsoft.github.io/aibast-agents-library/docs/experimental/ai-migration/ai_migration_agent.py -o ~/.brainstem/src/rapp_brainstem/agents/ai_migration_agent.py
One file, standard Python only. To remove it, delete the file. View the agent file.
How it works
- Install Brainstem. Follow the Brainstem installer. It runs on your existing GitHub Copilot plan.
- Drop in the agent. Run the install command above. It saves one file into your Brainstem's
agents/folder. No restart needed. - Say "scan", then "plan", then "apply". Scan lists what it finds, by folder and item type. Plan says what each item becomes. Apply writes a new review folder under
~/.brainstem/imports/. Apply is a dry run until you say to write. - Review and merge. Read
soul.import.mdand copy what you want into yoursoul.md. Install the generated agents when you are ready. "Undo" removes exactly what an apply added.
If your AI has custom assistants with no file export, copy their instructions into soul.import.md.
What it brings over
| In your current setup | In your Brainstem |
|---|---|
| Instructions files | A soul addition, soul.import.md, that you merge |
| Skills, subagents and commands | Generated single-file agents |
| Tool servers (MCP) | Listed as "needs a bridge", with every key removed |
| Hooks | Not carried. A Brainstem has no event hooks; rebuild one as an agent you call |
| Memory files | Memory entries, memory.import.md |
| Exported conversations | An optional read-only archive |
What stays on your device
The agent reads local files only. It skips known key and sign-in files, such as .env or auth.json, and any file that holds a private key, and it tells you each file it skipped and why. A skill or project with a word like "auth" or "session" in its name still comes over. It removes key-looking values from everything it writes. It never overwrites soul.md or an agent you already have.
When you use it through a Brainstem, its replies (names and counts, never file contents or keys) go to the model you chose, as any chat does.
How the setups compare
| Hosted AI assistant | Cloud AI coding tool | Your Brainstem | |
|---|---|---|---|
| Architecture | A web or mobile app that the provider runs | A local app or terminal tool that calls the provider's models | A small local server on your device that calls models through GitHub Copilot |
| Plugins and extensions | The provider's add-ons and connectors | Config-file plugins, skills, commands and tool servers | Single-file Python agents in your agents/ folder |
| Where your data lives | Mostly in your account with the provider | Settings and history in a folder on your device; prompts go to the provider | Soul, agents and memory as plain files on your device; prompts go to the model you choose |
| Cost model | Subscription tiers | Subscription tiers or per-token API billing | Your existing GitHub Copilot plan |
As of 2026-10-29. Pricing models change; check each provider's own pricing page.
GitHub Copilot offers models from several providers, so bringing your setup over keeps your choice of model. What you own is your setup.