Waiting for engine...
Skip to main content

Staying current with Boomi Companion: keep your AI agent up to date

· 5 min read
Carolyn Musa
Carolyn Musa
Product Manager, Developer Offerings @Boomi

An outdated Companion means your agent works from outdated Boomi guidance. Installing Companion is a one-time job. Keeping it current isn't, unless you set it up that way. Boomi Companion ships updates most weeks with new connector references, corrected platform behavior, new error patterns, tighter credential handling, etc.

That matters because Companion teaches your AI agent how Boomi actually behaves. Your agent only knows what your installed version taught it, so an old install can follow guidance that Boomi has already fixed. If Companion does something odd or unexpected, check your version first.

Setup takes about thirty seconds or less. Here's how, depending on where you run Companion.

Turn on auto-update in Claude Code​

Companion installs from a plugin marketplace in Claude Code, and the marketplace can update itself. Turn on auto-update once, and every new session picks up the latest version.

  1. Add the marketplace, if you haven't already:

    /plugin marketplace add OfficialBoomi/boomi-companion

  2. Run /plugin, select Marketplaces, and then select boomi-companion.

  3. Select Enable auto-update.

Refer to Installing Boomi Companion on Claude Code for the complete walkthrough.

Install from the Claude Cowork marketplace​

Cowork uses the same marketplace. To add it:

  1. Go to Customize > Plugins > Add marketplace
  2. Enter OfficialBoomi/boomi-companion.

Cowork installs the plugins and manages them from the Plugins panel, so you stay on the maintained version instead of a copy you grabbed once.

Refer to Installing Boomi Companion on Claude Cowork for more information.

Any other agent that supports skills​

Companion's skills follow the Agent Skills open standard, so they run on any agent that supports it. That includes GitHub Copilot (not to be confused with Microsoft Copilot), Cursor, Codex, Gemini CLI, and Google Antigravity, and the list keeps growing.

How you stay current depends on your agent. Some ship their own skill manager, some lean on GitHub's gh skill command, and some just want the folder in the right place. Most of these agents wait for you to ask instead of refreshing on their own, so outside the Claude marketplace, updating is up to you.

If your agent has its own skill manager, check its documentation. The directory layout is standard, so Companion drops in either way.

Refer to Installing Boomi Companion on non-Claude tools for the skill list and install guidance.

Read the changelogs​

Auto-update doesn't tell you what changed. To find out, check the changelog for each plugin on GitHub sorted by version.

PluginWhat it coversChangelog
bc-integrationIntegration processes, connectors, maps, profiles, EDI.CHANGELOG.md
bc-datahubData Hub models, sources, and stewardship.CHANGELOG.md
bc-bdiData Integration flows, CDC, and reverse ETL.CHANGELOG.md
bc-agentstudioAgentstudio agents, tools, and deployments.CHANGELOG.md
bc-marketplaceMarketplace recipe search and install.CHANGELOG.md

Each plugin also ships its changelog inside the skill folder. You can ask your agent what changed in the version you have, for example: "What changed in my installed version of bc-integration?"

Know the trade-offs before you fork​

Companion is open source under the BSD-2-Clause, so you're free to fork it. If you need it to behave differently in a way configuration can't reach, forking is your option.

Before you do, just know what you are taking on. A fork is frozen at the moment you make it:

  • You get no auto-updates.

  • You miss corrections when Boomi fixes platform guidance, new connector coverage, and other improvements.

  • You merge and test every upstream release yourself, and the merges get harder the longer you wait.

Plan for that maintenance up front.

Additional resources​

Use these links to go deeper, get answers, or report an issue:

Companion is only useful if its version is current. Turn on auto-update where you can, check for updates where you can’t, and skim the changelogs to see what’s new. Check out the Boomi Dev Docs for the changelog. It takes a few seconds, and your agent stays in step with Boomi.