Pin the system LLM credential

SupaCloud makes a handful of internal LLM calls on a workspace’s behalf — classifying backlog issues, generating recommendations, and judging quality. When a workspace has more than one usable model credential, you can pin which one those internal calls use instead of leaving it to automatic precedence.

Note

This is a separate choice from the model an agent run uses. It only affects SupaCloud’s own internal calls; agent tasks still pick their model the usual way.

Pin a credential

1. As a workspace owner, open Settings → Workspace.
2. Find the System credential selector. It appears only when the workspace has two or more pinnable credentials — with a single key there is nothing to choose.
3. Pick a credential, or choose Automatic to leave it to precedence. Both an API key and a connected subscription (OAuth) credential are offered.
4. Save.

With Automatic, the internal calls follow the normal credential precedence (your own API keys, then connected subscriptions, then any server key). A pinned credential overrides that precedence for the internal calls only. If a pinned credential is later removed, the workspace falls back to Automatic.

Tip

Pin a credential when you want internal calls to land on a specific provider — for example to keep classification on a cheap, fast model, or to route internal usage to a particular subscription for cost attribution.