Troubleshooting

Most provider issues are configuration problems rather than code problems: the wrong endpoint, a missing local key, or using the blocking transport path in the wrong place.

Common failure buckets

• HTTP errors: verify base URL, endpoint, auth header behavior, and model name.
• Local key mismatch: duplicating a provider asset creates a new GUID and requires a new local key entry.
• Ollama offline: verify the local service is running and the model is pulled.
• Runtime stalls: prefer the coroutine request path instead of the blocking editor path.

Security reality

Keys are intentionally local and not serialized into asset files, but they are not encrypted at rest. The docs should continue to frame this as convenience storage rather than as hardened credential management.

Custom JSON caveat

The Custom JSON provider is intentionally flexible and correspondingly less strongly typed. If parsing fails, check the response shape your endpoint actually returns rather than assuming it matches the fallback text extraction rules.