aicentosAugment Code
Augment Code does not open up custom endpoints, so the model cannot be switched to aicentos — the reasoning and the alternatives
Last updated:
Augment Code is a coding plugin for VS Code / JetBrains / Vim, plus the auggie CLI. It does not support a custom Base URL and offers no BYOK: models come from the official catalog, the account must sign in through auggie auth login, and requests cannot be pointed at aicentos.
Why it cannot connect directly
- The configuration files have no fields such as
baseUrlorapiKey, and the plugin settings panel has no endpoint input box either. - The CLI recognizes only two related environment variables:
AUGMENT_SESSION_AUTH(sign-in state) andAUGMENT_DISABLE_AUTO_UPDATE(turn off auto-update). There is no variable that overrides the endpoint. --modelonly accepts names from the official model catalog (Claude, GPT, Gemini, GLM, Kimi and so on); a third-party model name is rejected.- The official docs index
docs.augmentcode.com/llms.txthas no entry for BYOK or a custom provider.
Configuration to fill in
| Field | Value |
|---|---|
| API Key | The key created in the console |
| Base URL | https://aicentos.com/v1 |
| Model | A model name from the Model Gallery in the console |
The table above lists the generic aicentos-side parameters, for use with any of the alternatives below.
Alternatives
Alternative 1: Switch to a coding agent that supports custom endpoints
Craft Agent, Gajae Code, and Oh My Pi are all terminal coding agents whose configuration accepts baseUrl directly.
Alternative 2: Stay in VS Code and change the plugin
Cline, Roo Code, and Kilo all support an OpenAI-compatible provider and can take https://aicentos.com/v1 directly.
Alternative 3: Move only the batch jobs
If your team already pays for an Augment subscription and does not want to give up its completion experience, keep the official model for everyday editing and move batch refactoring and scripted tasks to a CLI that supports custom endpoints.
Test
After switching to any of the alternative clients, first confirm connectivity with one simple prompt, then check in the console whether usage is being recorded against the new key.
Notes
- Some tutorials online write keys such as
augment.modelProvider: "openai-compatible",augment.baseUrl,augment.apiKeyEnv. They do not exist in the official configuration: writing them raises no error and has no effect, and--modelstill only accepts the official catalog. - Do not take "the config key raised no error" as "the configuration took effect". The way to verify is to ask it for the current model name and compare that against the official catalog.
- Augment's cloud index and completion have no equivalent replacement; switching clients means switching the whole workflow, so try it on a small repository first.