Simplify Credentials UX

[Torantulino]

Context

We have implemented a quick patch to switch to the new credentials system across all blocks. The current UX is non-intuitive and needs immediate improvement to prevent it from blocking beta testers.

Current Issues

1. Missing Default Behaviour

Problem: No credential is selected by default, even when there's only one valid option in the system.

2. Confusing AI Block Provider Credential Selection

Problem: Users must manually select credentials for their chosen LLM provider without clear guidance on which credential to choose for which provider. Even if we had this guidance the user shouldn't need to have to do this.

3. Poor Error Handling

Problem: No feedback when credential selection is needed.

---

New UX Flow

System Level Keys (i.e. The API keys supplied by AutoGPT)

• Should not be visible to the user at all. i.e. on the Profile page or Credentials Dropdown
• Should work silently in the background when no user keys are present
• When a user has a system level key for the selected provider it should just be used, and the credentials field should be hidden.

When a user has a System Level Key

• Don't display credential field at all on the block

• Display the Add New API Key button on the Settings page, next to to each possible provider

  • I.e "OpenAI: Add new API key"

Keys need to be associated with Providers, not blocks

• For example an OpenAI key should ONLY be used with a OpenAI Model, not with Anthropic or Ollama.
• Keys should always automatically be selected when changing models etc. without any user action.

When User Has No Credentials (including system keys)

• Hide the credentials selection dropdown field
• Display a prominent "Add New API Key" button directly on the block (keep existing functionality when clicked).
  • Do not place the button inside a dropdown (as it is currently).
• Also display the same button next to to each possible provider on the Settings page.
  • I.e "OpenAI: Add new API key"

When User Has One User Level Key

• Automatically use the user level key for compatible providers
• Hide the credentials field entirely
• User level keys should take precedence over System Level Keys
• No dropdown menu needed

When User Has Multiple User Level Keys

• Only show the credentials dropdown when multiple User Level Keys exist for the same provider (e.g., OpenAI)
• Only show keys compatible with the selected provider
• Don't show System Keys in the dropdown

Key Deletion Behaviour

• When a user deletes their user level key, revert to the appropriate state based on remaining credentials (as detailed above):
  • If one User Level Key remains: Use it automatically without showing dropdown
  • If System Level Keys available: Use those silently
  • If no keys available: Show the "Add New API Key" button in credentials field