Providers page

Use the Providers page to connect the model services Guildhall can use for planning, implementation, review, and gates.

For each provider, the page shows:

Detection: whether the service found a usable CLI auth file, API key, or reachable local-model endpoint.
Verification: a verifiedAt marker after a successful test.
Credential action: connect, paste an API key, test, or disconnect.
Provider choice: which configured provider Guildhall prefers by default, with room for a project override when needed.

Provider paths the service exposes today

Claude — OAuth (via Claude Code CLI) or API key.
Codex (ChatGPT) — Codex CLI tokens.
Anthropic-compatible APIs — Anthropic itself and Anthropic-shaped hosted endpoints.
OpenAI-compatible APIs — OpenAI itself and OpenAI-shaped hosted endpoints.
Local OpenAI-compatible servers — usually llama.cpp or LM Studio, but conceptually just another OpenAI-compatible endpoint running on your machine.

Where credentials live

Machine-scoped provider credentials: ~/.guildhall/providers.yaml.
OAuth-managed credentials:
- ~/.claude/.credentials.json
- ~/.codex/auth.json
Machine-wide default: preferredProvider in ~/.guildhall/config.yaml.
Optional project override: preferredProvider in ./.guildhall/config.yaml only when one project truly needs different behavior.

The page only reveals credentials that are explicitly in config — it will never log or display a hidden system credential.

Environment variables that override credential sources.
Providers subsystem for the client-side details.