refactor: Remove validation for 'enabled' field in agent configuration

- Eliminated the check for the 'enabled' field in the ValidateConfig method of agentService.
- Updated comments in session service to reflect the removal of the 'enabled' field from AgentConfig.
- Streamlined agent configuration handling for improved clarity and maintainability.
This commit is contained in:
wizardchen
2025-11-21 14:32:28 +08:00
parent 6687e81b96
commit 301d400cce
2 changed files with 1 additions and 6 deletions
@@ -244,10 +244,6 @@ func (s *agentService) ValidateConfig(config *types.AgentConfig) error {
return fmt.Errorf("config cannot be nil")
}
if !config.Enabled {
return fmt.Errorf("agent is not enabled")
}
if config.MaxIterations <= 0 {
config.MaxIterations = 5 // Default
}
+1 -2
View File
@@ -880,9 +880,8 @@ func (s *sessionService) AgentQA(ctx context.Context, session *types.Session, qu
// Create runtime AgentConfig by merging session and tenant configs
// Tenant config provides the runtime parameters (MaxIterations, Temperature, Tools, Models)
// Session config provides Enabled and KnowledgeBases
// Session config provides KnowledgeBases
agentConfig := &types.AgentConfig{
Enabled: session.AgentConfig.AgentModeEnabled,
MaxIterations: tenantInfo.AgentConfig.MaxIterations,
ReflectionEnabled: tenantInfo.AgentConfig.ReflectionEnabled,
AllowedTools: tenantInfo.AgentConfig.AllowedTools,