MammouthAI
Connect your Mammouth AI API key and import compatible models into GitHub Copilot
Chat from the VS Code sidebar.
Features
- Validate your API key and store it securely using VS Code's secret storage.
- See how many models are available to your Mammouth account.
- Add or update the Mammouth Custom Endpoint group in your active VS Code profile.
- Keep other model providers and the existing Copilot key when refreshing models.
Requirements
- Visual Studio Code 1.146.0 or later
- GitHub Copilot Chat, enabled for importing models
- A Mammouth AI API key and API credits
Installation
Install MammouthAI from the VS Code Extensions view once it is published, or
install a packaged .vsix using Extensions: Install from VSIX.... Open the
Mammouth AI activity bar icon and connect your account.
Connecting and importing models
Enter your API key in the Account view. The extension validates it using
GET https://api.mammouth.ai/v1/models and stores a valid key in VS Code's secure
secret storage (context.secrets, key mammouthai.apiKey).
Click Inject into Copilot configuration to refresh your account's models and
import those compatible with Copilot Chat into the Mammouth group
(customendpoint, chat-completions) in the active VS Code profile. Embedding and
image-generation models are excluded. Token limits come from the Mammouth catalog
when available; otherwise fallback values are used. Vision and tool calling are
enabled only when those capabilities are known.
On the first import, VS Code stores the Copilot API key separately and writes only
a reference such as ${input:chat.lm.secret.…} to chatLanguageModels.json. Later
imports update the group without creating duplicates and retain its existing key.
Use Manage Language Models to change that key. Disconnect removes the
extension's key, not the one already configured in Copilot.
Development
Development requires Node.js 22 or later and npm.
npm install
npm run compile
Press F5 in VS Code to open an Extension Development Host, then click the
Mammouth AI icon in the activity bar. The pre-launch task compiles the extension.
To rebuild automatically while developing, run the watch task from
Terminal > Run Build Task.
Project structure
src/extension.ts: extension activation and sidebar message handling.
src/mammouthApi.ts: API key validation and model retrieval.
src/copilotConfig.ts: Copilot model configuration import.
media/sidebar.html and media/sidebar.js: sidebar interface and behavior.
src/test/: extension and API tests.
package.json: extension contributions and metadata.
The {{iconUri}} placeholder in media/sidebar.html is replaced at load time by
the webview URI for media/icon.svg.
To add a command, declare its identifier and title under contributes.commands in
package.json, register it with vscode.commands.registerCommand in
src/extension.ts, and add the disposable to context.subscriptions.
Verification
npm run compile
npm test
npm run compile checks types, runs ESLint, and generates dist/extension.js.
npm test compiles and runs the tests in a VS Code environment.
To also test JSON writes and the key reference, use a disposable profile with the
test provider; no real API key is required:
profile=$(mktemp -d)
mkdir -p "$profile/extensions/mammouth-test.custom-endpoint-0.0.1"
cp src/test/fixtures/custom-endpoint/package.json "$profile/extensions/mammouth-test.custom-endpoint-0.0.1/"
MAMMOUTH_IMPORT_TEST_PROFILE="$profile" MAMMOUTH_IMPORT_TEST_VSCODE="/usr/share/code/code" npm test
Adjust the VS Code executable path for your installation.
Packaging and publishing
npm ci
npm test
npm run package:vsix
npm pack --dry-run
package:vsix builds the extension and produces a VSIX that can be installed
locally or uploaded through the Marketplace publisher management page.
The npm package contains the bundled extension; it is not installed into VS Code
automatically by npm. Publish to npm separately with npm publish if desired.
The extension is available under the MIT license. Before a public
release, confirm ownership of the Mammouth Marketplace publisher and availability
of the npm package name, and verify the extension with a real API key. The
repository and issue tracker are currently private; their links require access.
For automated Marketplace publishing, configure Trusted Publishing
instead of storing a long-lived token. Do not commit credentials.