Vexoo

FORGE

Your terminal AI coding agent — wired to Vexoo's stack.

01 · Choose your install

01 · Install Forge

Two flavors. One binary.

One binary. Everything included.

Run bare Forge with the built-in provider list, or the Vexoo preset with our hosted models pre-wired. Same self-contained binary either way.

Forge ships with Vexoo's hosted models pre-wired — Mistral on Azure, Vexoo Oracle, Claude, and on-prem Vexoo-SRA. One self-contained binary, preconfigured and ready to build.

Bare install

Just Forge

Plain Forge with the built-in provider list (Anthropic, OpenAI, etc.). Pick a model, paste your own API key when prompted.

Linux / WSL
$ curl -fsSL https://forge.vexoo.ai/install | bash
Windows PowerShell
> irm https://forge.vexoo.ai/install.ps1 | iex
Recommended

Vexoo-flavored install

Recommended setup

Forge + Vexoo Preset

Forge, preconfigured with Vexoo

Ships with Vexoo's hosted models pre-configured: Mistral on Azure, Vexoo Oracle, Claude (Azure), and on-prem Vexoo-SRA. Drop in your forge.env and you're live.

Linux / WSL
$ curl -fsSL https://forge.vexoo.ai/install | bash -s -- --vexoo
Windows PowerShell
> & ([scriptblock]::Create((irm https://forge.vexoo.ai/install.ps1))) -Vexoo

Recommended for Vexoo engineers.

02 · forge.env

One file. Every model. No shell mess.

Drop your API keys into a single, locked-down env file. Forge reads it at startup.

Linux / WSL
$ mkdir -p ~/.config/forge$ nano ~/.config/forge/forge.env$ chmod 600 ~/.config/forge/forge.env
~/.config/forge/forge.env
# Anthropic — for cloud-open-models and forge-review agentsANTHROPIC_API_KEY=sk-ant-... # Azure (Mistral + Vexoo-Oracle on Cloud-Hosted-Models)AZURE_MISTRAL_API_KEY=... # Azure ClaudeAZURE_CLAUDE_API_KEY=...

Forge reads ~/.config/forge/forge.env at startup and substitutes {env:VAR} placeholders in forge.json. Shell-exported vars take precedence.

Or

Skip the file — let Forge ask you

No forge.env? No problem. Pick a model in the TUI and if its provider has no key, Forge pops an inline dialog asking for one. Works the same on a bare install or a --vexoo install. Keys land in ~/.local/share/forge/auth.json (mode 600) and survive every restart — no shell exports, no env-file edits.

No forge.env? No problem. Pick a model in the TUI and if its provider has no key, Forge pops an inline dialog asking for one. Keys land in ~/.local/share/forge/auth.json (mode 600) and survive every restart — no shell exports, no env-file edits.

03 · Reload

Activate Forge in your current terminal

Pick up the new PATH without opening a fresh window.

Linux / WSL
$ source ~/.bashrc # or: exec bash
Windows
# exit then reopen, or:> $env:Path = "$env:USERPROFILE\.forge\bin;$env:Path"

04 · Launch

Run it.

One command. Forge boots straight into your terminal.

Any shell
$ forge

05 · Removal

Reversible. Clean. Promise.

No daemons, no registry sprawl. Everything Forge writes lives under a handful of dot-dirs.

Linux / WSL
$ rm -rf ~/.forge ~/.config/forge ~/.local/share/forge ~/.cache/forge ~/.local/state/forge$ sed -i '/# forge/,+1d' ~/.bashrc
Windows PowerShell
> Remove-Item -Recurse -Force "$env:USERPROFILE\.forge","...\.config\forge","...\.local\share\forge","...\.cache\forge","...\.local\state\forge" -ErrorAction SilentlyContinue> $p = ([Environment]::GetEnvironmentVariable('Path','User') -split ';') | Where-Object { $_ -and ($_ -notmatch '\.forge\\bin$') }> [Environment]::SetEnvironmentVariable('Path', ($p -join ';'), 'User')