Repository navigation
refactor(an-bot-team): drop the vendor prefix, bring our own icon, and let the package see its own tools - #149
Merged
Conversation
…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
force-pushed
the
feat/a-bot-team-rename
branch
from
November 18, 2026 11:48
395a856 to
65ac76b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 MCPserver name, the
/mcproute and the two READMEs all carry the new name, and theversion 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 iconand 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.mjschecked formcp__minimax-bot-pro__, while the package'sMCP server is registered under the package name - so
isPluginTool()never recognizedthe package's own tools, and the group rule at engine.mjs:847 treated them as
foreign tools and cut them off;
miniapp/node/strings.mjstold the model that its tools come from an MCP servernamed after the plugin - a server that does not exist in this package;
miniapp/client/app.jsrecognized team tools by the same wrong name;miniapp/client/core.jsused 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 aserver 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-plugindirectory 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_STDOUTinminiapp/node/memory-bridge.mjs, the helper's own output channel - unchanged)npm run check- 92/92node --test plugins/antianqi/an-bot-team/tests/chat-delete-atomicity.test.mjs- 2/2Both guards were falsified before this pull request: a
minimax-prefix in theplugin source and one in the package README each make the build fail, and the build
is green again after the restore.