Summary

On Administration → Models, the UI makes it difficult to tell whether the current configuration has been saved, which model is being tested, and whether the connection succeeded or failed.

Observed behavior

1. Success feedback is barely visible. In dark mode, Reachable and authenticated (OK) and the API key’s configured label have very low contrast.

2. Feedback after changing the API key is ambiguous. After a successful connection, entering an incorrect key and clicking Test connection produces feedback such as Saved, without a clear connection result. It is unclear whether the message refers to saving, testing, or a previous operation.

3. Embedding still shows Not configured. The fields contain https://api.siliconflow.cn/v1 and BAAI/bge-m3, with a masked API key and a configured label. However, the card still says Not configured, without explaining what is missing or whether the status is current.

4. Both test buttons appear to respond. Clicking either Test connection button makes both buttons appear to react. It is unclear whether Chat, Embedding, or both are being tested.

Screenshot

Low-contrast success feedback and embedding fields populated while the status remains Not configured. API keys are masked.

Expected behavior

• Clearly distinguish unsaved changes, saved configuration, testing, success, and failure.
• Identify which model and configuration each result applies to, and clear or mark outdated results after edits.
• Display readable success/error messages and explain missing configuration.
• Make button feedback match the actual test scope.

Environment

• UI version: v0.1.0
• Theme: dark
• Provider: SiliconFlow
• Chat model: deepseek-ai/DeepSeek-V3
• Embedding model: BAAI/bge-m3

These observations concern UI feedback. They do not establish that invalid credentials are accepted or that current inputs are ignored.