Bot Father: LangChain Updates
Overview
The Bot Father has been updated to support configuration of the new LangChain task features introduced in EDDI 5.6.0. Users can now configure built-in tools, tool whitelisting, and conversation history limits when creating connector bots.
Changes Made
New Configuration Options
All LLM provider connector bots now support three new configuration options:
Enable Built-in Tools (
enableBuiltInTools)Boolean flag to enable/disable built-in tools (calculator, websearch, datetime, weather, etc.)
Default:
false(must be explicitly enabled)
Built-in Tools Whitelist (
builtInToolsWhitelist)JSON array specifying which specific tools to enable
Only shown if built-in tools are enabled
Empty array
[]= enable all toolsExample:
["calculator", "websearch", "datetime"]
Conversation History Limit (
conversationHistoryLimit)Integer controlling how many conversation turns to include in context
Values:
-1(unlimited),0(none), or positive number (recommended: 10-20)Default:
10
Updated Providers
The following connector bot providers have been updated:
OpenAI (
6740832a2b0f614abcaee7a4)Supports GPT-4, GPT-4o, and other OpenAI models
Anthropic/Claude (
6740832a2b0f614abcaee7b0)Supports Claude 3 models (Opus, Sonnet, Haiku)
Hugging Face (
6740832a2b0f614abcaee7aa)Supports various Hugging Face models
Gemini (
6740832b2b0f614abcaee7b6)Supports Google Gemini models
Gemini Vertex (
6740832b2b0f614abcaee7bc)Supports Google Vertex AI Gemini models
Ollama (
6740832b2b0f614abcaee7c2)Supports local Ollama models
Jlama (
6740832b2b0f614abcaee7c8)Supports Jlama models
Files Modified Per Provider
For each provider, the following files were updated:
1. Behavior Rules (*.behavior.json)
*.behavior.json)Added behavior rules to ask for built-in tools configuration
Added conditional logic to show/skip tools whitelist based on enableBuiltInTools value
Added behavior rule to ask for conversation history limit
Updated confirmation flow to include new steps
2. Property Configuration (*.property.json)
*.property.json)Added property capture for
enableBuiltInToolsfrom user inputAdded property capture for
builtInToolsWhitelist(with default[]if tools disabled)Added property capture for
conversationHistoryLimitfrom user input
3. Output Messages (*.output.json)
*.output.json)Added output message asking about built-in tools with quick reply buttons
Added output message asking about tools whitelist with examples and quick replies
Added output message asking about conversation history limit with recommendations
4. HTTP Calls (*.httpcalls.json)
*.httpcalls.json)Updated langchain creation body to include three new parameters:
enableBuiltInTools:[(${properties.enableBuiltInTools})]builtInToolsWhitelist:[(${properties.builtInToolsWhitelist})]conversationHistoryLimit:[(${properties.conversationHistoryLimit})]
User Experience Flow
When creating a new connector bot, users will now see:
Existing prompts (API key, model name, temperature, timeout)
NEW: "Would you like to enable built-in tools?"
Quick replies: "Yes, enable tools" / "No, just simple chat"
NEW (if tools enabled): "Which specific tools would you like to enable?"
Quick replies: "Enable all tools" / "Calculator & Web Search" / "Calculator, Web, DateTime"
Users can also type a custom JSON array
NEW: "How many conversation turns would you like to include in the context?"
Quick replies: "10 turns (recommended)" / "20 turns" / "Unlimited"
Confirmation and bot creation
Available Tools
When built-in tools are enabled, the following tools are available:
Calculator
calculator
Perform mathematical calculations
Date/Time
datetime
Get current date, time, timezone info
Web Search
websearch
Search the web (includes Wikipedia & News)
Data Formatter
dataformatter
Format JSON, CSV, XML data
Web Scraper
webscraper
Extract content from web pages
Text Summarizer
textsummarizer
Summarize long text
PDF Reader
pdfreader
Extract text from PDF files
Weather
weather
Get weather information
Example Generated Configuration
When a user creates a bot with tools enabled, the HTTP call will generate a configuration like:
Backward Compatibility
All changes are additive - existing bot configurations continue to work
New fields have sensible defaults if not specified
Users who choose "No, just simple chat" will have
enableBuiltInTools: falseand empty whitelist
Testing Recommendations
Test creating a new OpenAI bot with tools enabled
Test creating a new Anthropic bot without tools
Verify tools whitelist only shows when tools are enabled
Verify all quick reply options work correctly
Test custom JSON array input for tools whitelist
Test different conversation history limit values
Related Documentation
Version
Updated for EDDI 5.6.0 Bot Father version: 3.0.1
Last updated
Was this helpful?