Memory or LLM settings sometimes default to OpenAI LLM provider

[flopach]

Sometimes the memory or LLM settings default to OpenAI LLM provider which gives an error of the openAI missing API keys after starting the crew.

[nehmetohmedb]

Updated Root Cause Analysis: Agent Embeddings Inconsistency

After further investigation based on your feedback about the inconsistent behavior, I have identified multiple points where the embedding configuration can default to OpenAI:

The Multiple Default Points

1. Dispatcher-Generated Agents (src/frontend/src/components/Chat/utils/nodeGenerationHandlers.ts):

   • When agents are generated via the dispatcher (chat interface), line 44 defaults to "openai" if embedder_config exists but has no provider
   • The backend prompt template (GENERATE_AGENT_TEMPLATE) does not include embedder_config in its structure at all
   • This means dispatcher-generated agents start with no embedder_config

2. AgentService Defaults (src/frontend/src/api/AgentService.ts):

   • When saving an agent with memory enabled but no embedder_config, it adds OpenAI defaults (lines 80-87 and 199-206)
   • This happens for both createAgent() and updateAgentFull() methods

3. AgentForm UI Display (src/frontend/src/components/Agents/AgentForm.tsx):

   • The form shows "databricks" as the default in the dropdown (line 680)
   • But if embedder_config is undefined, it stays undefined until the user explicitly selects a provider

Why the Inconsistency Occurs

The inconsistent behavior happens because there are three different paths for agent creation:

1. Manual Creation via AgentForm:

   • If user does not touch the embedding dropdown → embedder_config remains undefined → AgentService adds OpenAI default
   • If user changes the dropdown (even to select the already displayed "databricks") → embedder_config gets set properly

2. Dispatcher Generation (Chat Interface):

   • Backend does not generate embedder_config → Frontend nodeGenerationHandler defaults to OpenAI if provider is missing
   • Then AgentService also checks and might add its own OpenAI default

3. When Editing Existing Agents:

   • If the agent already has embedder_config → it is preserved
   • If not → same issue as manual creation

The Issue Summary

There are three separate places setting OpenAI as default:

1. nodeGenerationHandlers.ts line 44 (for dispatcher-generated agents)
2. AgentService.ts lines 82-86 (for createAgent)
3. AgentService.ts lines 200-205 (for updateAgentFull)

But the UI shows Databricks as default, creating a mismatch between what users see and what gets saved.

Recommended Fix

1. Update the dispatcher prompt template to include embedder_config with Databricks as default
2. Update nodeGenerationHandlers.ts to use Databricks as the fallback instead of OpenAI
3. Update AgentService.ts to use Databricks as the default instead of OpenAI
4. OR Remove all the default-setting logic and let the backend handle it consistently

This explains why you see inconsistent behavior - it depends on which code path creates the agent and whether the user interacts with the embedding dropdown.