mirror of
https://gitee.com/wanwujie/deer-flow
synced 2026-04-02 22:02:13 +08:00
* Adds Kubernetes sandbox provisioner support * Improves Docker dev setup by standardizing host paths Replaces hardcoded host paths with a configurable root directory, making the development environment more portable and easier to use across different machines. Automatically sets the root path if not already defined, reducing manual setup steps.
255 lines
11 KiB
Python
255 lines
11 KiB
Python
from langchain.agents import create_agent
|
|
from langchain.agents.middleware import SummarizationMiddleware, TodoListMiddleware
|
|
from langchain_core.runnables import RunnableConfig
|
|
|
|
from src.agents.lead_agent.prompt import apply_prompt_template
|
|
from src.agents.middlewares.clarification_middleware import ClarificationMiddleware
|
|
from src.agents.middlewares.dangling_tool_call_middleware import DanglingToolCallMiddleware
|
|
from src.agents.middlewares.memory_middleware import MemoryMiddleware
|
|
from src.agents.middlewares.subagent_limit_middleware import SubagentLimitMiddleware
|
|
from src.agents.middlewares.thread_data_middleware import ThreadDataMiddleware
|
|
from src.agents.middlewares.title_middleware import TitleMiddleware
|
|
from src.agents.middlewares.uploads_middleware import UploadsMiddleware
|
|
from src.agents.middlewares.view_image_middleware import ViewImageMiddleware
|
|
from src.agents.thread_state import ThreadState
|
|
from src.config.summarization_config import get_summarization_config
|
|
from src.models import create_chat_model
|
|
from src.sandbox.middleware import SandboxMiddleware
|
|
|
|
|
|
def _create_summarization_middleware() -> SummarizationMiddleware | None:
|
|
"""Create and configure the summarization middleware from config."""
|
|
config = get_summarization_config()
|
|
|
|
if not config.enabled:
|
|
return None
|
|
|
|
# Prepare trigger parameter
|
|
trigger = None
|
|
if config.trigger is not None:
|
|
if isinstance(config.trigger, list):
|
|
trigger = [t.to_tuple() for t in config.trigger]
|
|
else:
|
|
trigger = config.trigger.to_tuple()
|
|
|
|
# Prepare keep parameter
|
|
keep = config.keep.to_tuple()
|
|
|
|
# Prepare model parameter
|
|
if config.model_name:
|
|
model = config.model_name
|
|
else:
|
|
# Use a lightweight model for summarization to save costs
|
|
# Falls back to default model if not explicitly specified
|
|
model = create_chat_model(thinking_enabled=False)
|
|
|
|
# Prepare kwargs
|
|
kwargs = {
|
|
"model": model,
|
|
"trigger": trigger,
|
|
"keep": keep,
|
|
}
|
|
|
|
if config.trim_tokens_to_summarize is not None:
|
|
kwargs["trim_tokens_to_summarize"] = config.trim_tokens_to_summarize
|
|
|
|
if config.summary_prompt is not None:
|
|
kwargs["summary_prompt"] = config.summary_prompt
|
|
|
|
return SummarizationMiddleware(**kwargs)
|
|
|
|
|
|
def _create_todo_list_middleware(is_plan_mode: bool) -> TodoListMiddleware | None:
|
|
"""Create and configure the TodoList middleware.
|
|
|
|
Args:
|
|
is_plan_mode: Whether to enable plan mode with TodoList middleware.
|
|
|
|
Returns:
|
|
TodoListMiddleware instance if plan mode is enabled, None otherwise.
|
|
"""
|
|
if not is_plan_mode:
|
|
return None
|
|
|
|
# Custom prompts matching DeerFlow's style
|
|
system_prompt = """
|
|
<todo_list_system>
|
|
You have access to the `write_todos` tool to help you manage and track complex multi-step objectives.
|
|
|
|
**CRITICAL RULES:**
|
|
- Mark todos as completed IMMEDIATELY after finishing each step - do NOT batch completions
|
|
- Keep EXACTLY ONE task as `in_progress` at any time (unless tasks can run in parallel)
|
|
- Update the todo list in REAL-TIME as you work - this gives users visibility into your progress
|
|
- DO NOT use this tool for simple tasks (< 3 steps) - just complete them directly
|
|
|
|
**When to Use:**
|
|
This tool is designed for complex objectives that require systematic tracking:
|
|
- Complex multi-step tasks requiring 3+ distinct steps
|
|
- Non-trivial tasks needing careful planning and execution
|
|
- User explicitly requests a todo list
|
|
- User provides multiple tasks (numbered or comma-separated list)
|
|
- The plan may need revisions based on intermediate results
|
|
|
|
**When NOT to Use:**
|
|
- Single, straightforward tasks
|
|
- Trivial tasks (< 3 steps)
|
|
- Purely conversational or informational requests
|
|
- Simple tool calls where the approach is obvious
|
|
|
|
**Best Practices:**
|
|
- Break down complex tasks into smaller, actionable steps
|
|
- Use clear, descriptive task names
|
|
- Remove tasks that become irrelevant
|
|
- Add new tasks discovered during implementation
|
|
- Don't be afraid to revise the todo list as you learn more
|
|
|
|
**Task Management:**
|
|
Writing todos takes time and tokens - use it when helpful for managing complex problems, not for simple requests.
|
|
</todo_list_system>
|
|
"""
|
|
|
|
tool_description = """Use this tool to create and manage a structured task list for complex work sessions.
|
|
|
|
**IMPORTANT: Only use this tool for complex tasks (3+ steps). For simple requests, just do the work directly.**
|
|
|
|
## When to Use
|
|
|
|
Use this tool in these scenarios:
|
|
1. **Complex multi-step tasks**: When a task requires 3 or more distinct steps or actions
|
|
2. **Non-trivial tasks**: Tasks requiring careful planning or multiple operations
|
|
3. **User explicitly requests todo list**: When the user directly asks you to track tasks
|
|
4. **Multiple tasks**: When users provide a list of things to be done
|
|
5. **Dynamic planning**: When the plan may need updates based on intermediate results
|
|
|
|
## When NOT to Use
|
|
|
|
Skip this tool when:
|
|
1. The task is straightforward and takes less than 3 steps
|
|
2. The task is trivial and tracking provides no benefit
|
|
3. The task is purely conversational or informational
|
|
4. It's clear what needs to be done and you can just do it
|
|
|
|
## How to Use
|
|
|
|
1. **Starting a task**: Mark it as `in_progress` BEFORE beginning work
|
|
2. **Completing a task**: Mark it as `completed` IMMEDIATELY after finishing
|
|
3. **Updating the list**: Add new tasks, remove irrelevant ones, or update descriptions as needed
|
|
4. **Multiple updates**: You can make several updates at once (e.g., complete one task and start the next)
|
|
|
|
## Task States
|
|
|
|
- `pending`: Task not yet started
|
|
- `in_progress`: Currently working on (can have multiple if tasks run in parallel)
|
|
- `completed`: Task finished successfully
|
|
|
|
## Task Completion Requirements
|
|
|
|
**CRITICAL: Only mark a task as completed when you have FULLY accomplished it.**
|
|
|
|
Never mark a task as completed if:
|
|
- There are unresolved issues or errors
|
|
- Work is partial or incomplete
|
|
- You encountered blockers preventing completion
|
|
- You couldn't find necessary resources or dependencies
|
|
- Quality standards haven't been met
|
|
|
|
If blocked, keep the task as `in_progress` and create a new task describing what needs to be resolved.
|
|
|
|
## Best Practices
|
|
|
|
- Create specific, actionable items
|
|
- Break complex tasks into smaller, manageable steps
|
|
- Use clear, descriptive task names
|
|
- Update task status in real-time as you work
|
|
- Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
|
|
- Remove tasks that are no longer relevant
|
|
- **IMPORTANT**: When you write the todo list, mark your first task(s) as `in_progress` immediately
|
|
- **IMPORTANT**: Unless all tasks are completed, always have at least one task `in_progress` to show progress
|
|
|
|
Being proactive with task management demonstrates thoroughness and ensures all requirements are completed successfully.
|
|
|
|
**Remember**: If you only need a few tool calls to complete a task and it's clear what to do, it's better to just do the task directly and NOT use this tool at all.
|
|
"""
|
|
|
|
return TodoListMiddleware(system_prompt=system_prompt, tool_description=tool_description)
|
|
|
|
|
|
# ThreadDataMiddleware must be before SandboxMiddleware to ensure thread_id is available
|
|
# UploadsMiddleware should be after ThreadDataMiddleware to access thread_id
|
|
# DanglingToolCallMiddleware patches missing ToolMessages before model sees the history
|
|
# SummarizationMiddleware should be early to reduce context before other processing
|
|
# TodoListMiddleware should be before ClarificationMiddleware to allow todo management
|
|
# TitleMiddleware generates title after first exchange
|
|
# MemoryMiddleware queues conversation for memory update (after TitleMiddleware)
|
|
# ViewImageMiddleware should be before ClarificationMiddleware to inject image details before LLM
|
|
# ClarificationMiddleware should be last to intercept clarification requests after model calls
|
|
def _build_middlewares(config: RunnableConfig):
|
|
"""Build middleware chain based on runtime configuration.
|
|
|
|
Args:
|
|
config: Runtime configuration containing configurable options like is_plan_mode.
|
|
|
|
Returns:
|
|
List of middleware instances.
|
|
"""
|
|
middlewares = [ThreadDataMiddleware(), UploadsMiddleware(), SandboxMiddleware(), DanglingToolCallMiddleware()]
|
|
|
|
# Add summarization middleware if enabled
|
|
summarization_middleware = _create_summarization_middleware()
|
|
if summarization_middleware is not None:
|
|
middlewares.append(summarization_middleware)
|
|
|
|
# Add TodoList middleware if plan mode is enabled
|
|
is_plan_mode = config.get("configurable", {}).get("is_plan_mode", False)
|
|
todo_list_middleware = _create_todo_list_middleware(is_plan_mode)
|
|
if todo_list_middleware is not None:
|
|
middlewares.append(todo_list_middleware)
|
|
|
|
# Add TitleMiddleware
|
|
middlewares.append(TitleMiddleware())
|
|
|
|
# Add MemoryMiddleware (after TitleMiddleware)
|
|
middlewares.append(MemoryMiddleware())
|
|
|
|
# Add ViewImageMiddleware only if the current model supports vision
|
|
model_name = config.get("configurable", {}).get("model_name") or config.get("configurable", {}).get("model")
|
|
from src.config import get_app_config
|
|
|
|
app_config = get_app_config()
|
|
# If no model_name specified, use the first model (default)
|
|
if model_name is None and app_config.models:
|
|
model_name = app_config.models[0].name
|
|
|
|
model_config = app_config.get_model_config(model_name) if model_name else None
|
|
if model_config is not None and model_config.supports_vision:
|
|
middlewares.append(ViewImageMiddleware())
|
|
|
|
# Add SubagentLimitMiddleware to truncate excess parallel task calls
|
|
subagent_enabled = config.get("configurable", {}).get("subagent_enabled", False)
|
|
if subagent_enabled:
|
|
max_concurrent_subagents = config.get("configurable", {}).get("max_concurrent_subagents", 3)
|
|
middlewares.append(SubagentLimitMiddleware(max_concurrent=max_concurrent_subagents))
|
|
|
|
# ClarificationMiddleware should always be last
|
|
middlewares.append(ClarificationMiddleware())
|
|
return middlewares
|
|
|
|
|
|
def make_lead_agent(config: RunnableConfig):
|
|
# Lazy import to avoid circular dependency
|
|
from src.tools import get_available_tools
|
|
|
|
thinking_enabled = config.get("configurable", {}).get("thinking_enabled", True)
|
|
model_name = config.get("configurable", {}).get("model_name") or config.get("configurable", {}).get("model")
|
|
is_plan_mode = config.get("configurable", {}).get("is_plan_mode", False)
|
|
subagent_enabled = config.get("configurable", {}).get("subagent_enabled", False)
|
|
max_concurrent_subagents = config.get("configurable", {}).get("max_concurrent_subagents", 3)
|
|
print(f"thinking_enabled: {thinking_enabled}, model_name: {model_name}, is_plan_mode: {is_plan_mode}, subagent_enabled: {subagent_enabled}, max_concurrent_subagents: {max_concurrent_subagents}")
|
|
return create_agent(
|
|
model=create_chat_model(name=model_name, thinking_enabled=thinking_enabled),
|
|
tools=get_available_tools(model_name=model_name, subagent_enabled=subagent_enabled),
|
|
middleware=_build_middlewares(config),
|
|
system_prompt=apply_prompt_template(subagent_enabled=subagent_enabled, max_concurrent_subagents=max_concurrent_subagents),
|
|
state_schema=ThreadState,
|
|
)
|