Skip to content

refactor(an-bot-team): drop the vendor prefix, bring our own icon, and let the package see its own tools - #149

Merged
MyPrototypeWhat merged 1 commit into
MiniMax-AI:mainfrom
antianqi:feat/a-bot-team-rename
Nov 18, 2026
Merged

MyPrototypeWhat merged 1 commit into
MiniMax-AI:mainfrom
antianqi:feat/a-bot-team-rename

Conversation

@antianqi

@antianqi antianqi commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

refactor(an-bot-team): drop the vendor prefix, bring our own icon, and let the package see its own tools

This package is not the official MiniMax Bot, and it should not look like one. Three things change here.

1. The name

The package is now an-bot-team. The directory, the manifest name, package.json, the MCP
server name, the /mcp route and the two READMEs all carry the new name, and the
version moves to 1.1.0.

This renames the package, so the listing and the install path change. If you would
rather keep the old name and take only the icon, say so and I will split it.

2. The icon

The icon this package carried was the official package's file, byte for byte - the
same blob. A package that is not the official product should not wear the official
product's face, so it carries its own now: three octopuses in three forms - the glass
one, the gold one and the pixel one - in a small pyramid on a deep teal field. The
shapes are the skins the package itself ships in miniapp/client/skins, so the icon
and the avatars a user picks in the panel are one family. The glass octopus sits on
top and the other two below: one chief Bot and its members.

3. The package could not recognize its own tools

Four places in the package still carried the name of the plugin it was built from:

  • miniapp/node/engine.mjs checked for mcp__minimax-bot-pro__, while the package's
    MCP server is registered under the package name - so isPluginTool() never recognized
    the package's own tools, and the group rule at engine.mjs:847 treated them as
    foreign tools and cut them off;
  • miniapp/node/strings.mjs told the model that its tools come from an MCP server
    named after the plugin - a server that does not exist in this package;
  • miniapp/client/app.js recognized team tools by the same wrong name;
  • miniapp/client/core.js used it as the key of the page preferences.

The builder now writes the identity of the package everywhere it is written: the
manifest, package.json, the MCP server name, the route, the tool prefix the engine
recognizes, the prompt tags the relay guard matches, the strings that name the
product, and the panel title. The engine now checks for mcp__an-bot-team__ against a
server named an-bot-team.

Two guards keep it that way. The build fails when a file of the package - generated
or hand-written - carries a minimax- prefix (the Host's own .minimax-plugin
directory excepted), and it fails when a file calls the product MiniMax Bot.

The MIT attribution to the MiniMax Bot Mini App stays in the README and in the
LICENSE, where it belongs.

Checks

  • npm run validate - this package: 0 errors, 1 warning (ENTRY_STDOUT in
    miniapp/node/memory-bridge.mjs, the helper's own output channel - unchanged)
  • npm run check - 92/92
  • node --test plugins/antianqi/an-bot-team/tests/chat-delete-atomicity.test.mjs - 2/2

Both guards were falsified before this pull request: a minimax- prefix in the
plugin source and one in the package README each make the build fail, and the build
is green again after the restore.

…d let the package see its own tools

This package is not the official MiniMax Bot, and it should not look like one. Three things change here.

## 1. The name

The package is now `an-bot-team`. The directory, the manifest name, package.json, the MCP
server name, the `/mcp` route and the two READMEs all carry the new name, and the
version moves to 1.1.0.

This renames the package, so the listing and the install path change. If you would
rather keep the old name and take only the icon, say so and I will split it.

## 2. The icon

The icon this package carried was the official package's file, byte for byte - the
same blob. A package that is not the official product should not wear the official
product's face, so it carries its own now: three octopuses in three forms - the glass
one, the gold one and the pixel one - in a small pyramid on a deep teal field. The
shapes are the skins the package itself ships in `miniapp/client/skins`, so the icon
and the avatars a user picks in the panel are one family. The glass octopus sits on
top and the other two below: one chief Bot and its members.

## 3. The package could not recognize its own tools

Four places in the package still carried the name of the plugin it was built from:

- `miniapp/node/engine.mjs` checked for `mcp__minimax-bot-pro__`, while the package's
  MCP server is registered under the package name - so `isPluginTool()` never recognized
  the package's own tools, and the group rule at engine.mjs:847 treated them as
  foreign tools and cut them off;
- `miniapp/node/strings.mjs` told the model that its tools come from an MCP server
  named after the plugin - a server that does not exist in this package;
- `miniapp/client/app.js` recognized team tools by the same wrong name;
- `miniapp/client/core.js` used it as the key of the page preferences.

The builder now writes the identity of the package everywhere it is written: the
manifest, package.json, the MCP server name, the route, the tool prefix the engine
recognizes, the prompt tags the relay guard matches, the strings that name the
product, and the panel title. The engine now checks for `mcp__an-bot-team__` against a
server named `an-bot-team`.

Two guards keep it that way. The build fails when a file of the package - generated
or hand-written - carries a `minimax-` prefix (the Host's own `.minimax-plugin`
directory excepted), and it fails when a file calls the product `MiniMax Bot`.

The MIT attribution to the MiniMax Bot Mini App stays in the README and in the
LICENSE, where it belongs.

## Checks

- `npm run validate` - this package: 0 errors, 1 warning (`ENTRY_STDOUT` in
  `miniapp/node/memory-bridge.mjs`, the helper's own output channel - unchanged)
- `npm run check` - 92/92
- `node --test plugins/antianqi/an-bot-team/tests/chat-delete-atomicity.test.mjs` - 2/2

Both guards were falsified before this pull request: a `minimax-` prefix in the
plugin source and one in the package README each make the build fail, and the build
is green again after the restore.
@antianqi
antianqi force-pushed the feat/a-bot-team-rename branch from 395a856 to 65ac76b Compare November 18, 2026 11:48
@antianqi antianqi changed the title refactor(a-bot-team): drop the vendor prefix, bring our own icon, and let the package see its own tools refactor(an-bot-team): drop the vendor prefix, bring our own icon, and let the package see its own tools Nov 18, 2026
@MyPrototypeWhat
MyPrototypeWhat merged commit cfcaa0f into MiniMax-AI:main Nov 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants