Skip to content

Search documentation

Search across every goat product

Custom providers

Connect any OpenAI-compatible endpoint, including models running on your own machine.

On this page

Hosted providers cover most cases, but goat treats any OpenAI-compatible endpoint as a first-class provider. A local runtime and a hosted API are configured the same way.

Add the provider

Give the endpoint a name. That name becomes the prefix you use to address its models.

goat provider add local --endpoint http://127.0.0.1:11434/v1
goat provider list

If the endpoint requires a key, goat prompts for it and stores it alongside your other provider credentials under ~/.goat/.

Address its models

Models from a custom provider are written as <provider>/<model>:

goat code --model local/qwen2.5-coder
goat agent add --model local/qwen2.5-coder

The prefix is what disambiguates two providers that serve a model of the same name.

Mix providers

Agents and coding sessions choose models independently. A common setup is a hosted model for an agent that answers in a channel, and a local model for coding sessions that should not leave the machine.

goat provider login anthropic
goat provider add local --endpoint http://127.0.0.1:11434/v1

Both stay available at once; nothing is switched globally.