惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Microsoft Azure Blog
Microsoft Azure Blog
大猫的无限游戏
大猫的无限游戏
月光博客
月光博客
V
V2EX
PCI Perspectives
PCI Perspectives
Latest news
Latest news
博客园 - 三生石上(FineUI控件)
C
CERT Recently Published Vulnerability Notes
W
WeLiveSecurity
Last Week in AI
Last Week in AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
P
Palo Alto Networks Blog
T
The Exploit Database - CXSecurity.com
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
WordPress大学
WordPress大学
V
Vulnerabilities – Threatpost
H
Heimdal Security Blog
Attack and Defense Labs
Attack and Defense Labs
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Hacker News: Ask HN
Hacker News: Ask HN
博客园 - 叶小钗
V
Visual Studio Blog
Jina AI
Jina AI
P
Proofpoint News Feed
罗磊的独立博客
SecWiki News
SecWiki News
J
Java Code Geeks
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
L
LINUX DO - 热门话题
Security Archives - TechRepublic
Security Archives - TechRepublic
The Hacker News
The Hacker News
Hugging Face - Blog
Hugging Face - Blog
N
News and Events Feed by Topic
NISL@THU
NISL@THU
T
Tailwind CSS Blog
T
Tenable Blog
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Recent Announcements
Recent Announcements
H
Hacker News: Front Page
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
T
Tor Project blog
宝玉的分享
宝玉的分享
Help Net Security
Help Net Security
S
Security Affairs
Microsoft Security Blog
Microsoft Security Blog
Google DeepMind News
Google DeepMind News
F
Fortinet All Blogs
G
GRAHAM CLULEY

Inside Nutrient

A guide to the invisible work behind documents Introducing Nutrient Documents for Salesforce: Native document generation and signing Document AI vs. traditional OCR: Choosing between OCR, AI, and hybrid pipelines PDF SDK compliance and security evaluation checklist for enterprise teams (2026) Invariant Corp replaces paper processes with Nutrient Workflow and scales without limits What is process mapping? A complete guide Nutrient vs. Conga Composer for Salesforce document generation (2026) Document routing: How to automate document distribution The CTO’s AI playbook: Why accountability architecture beats orchestration Compliance workflow automation: Why built-in compliance is table stakes Workflow diagrams: Examples, symbols, and how to build one that actually runs Digital forms: Replace paper forms with automated workflows Approval workflow software: How to automate approvals Why document-centric automation is different The CEO’s AI playbook: Why decision architecture beats model selection Nutrient SDK product updates for Q1 2026 PDF redaction verification: How to prove sensitive data is permanently removed What is a VPAT? The complete guide to accessibility conformance reports What is PDF/UA? The accessible PDF standard explained Salesforce eSignatures: Generate, sign, and track documents in one flow Online document viewer: Options, tradeoffs, and how to embed one Document viewer for web apps: React, Vue, Angular (2026) Best document viewers in 2026: A buyer’s guide How to edit a PDF in Python: Add text, images, and annotations Nutrient advances Workflow platform with agentic AI for enterprise-grade speed and consistency in document-heavy operations How to create a Salesforce quote template from opportunity data The business case for accessibility: Five ways it drives enterprise value Python PDF library comparison (2026): 7 libraries for developers Why your AI agent hallucinates PDF table data PDF.js limitations: When to upgrade to a commercial PDF SDK How Subject scaled 5× with Nutrient’s PDF SDK without rebuilding its document layer I replaced our sales training with an AI coach that runs in Slack — here’s what broke Redirecting to: https://securitybuzz.com/cybersecurity-news/why-enterprise-permissions-are-ais-most-dangerous-inheritance/ Nutrient .NET SDK vs. iText Core: Complete comparison for .NET developers DocuVieware: Support’s most frequently asked setup questions Introducing Nutrient Workflow How to convert PDF to Word in C# (.NET) When email and spreadsheets stop working: Work order approval workflows for field teams on the move Compliance with confidence: Why document-centric automation is the foundation of your mission Nutrient expands AI Assistant, automating multistep document workflows inside any application What is document generation? A developer’s guide to PDF generation Document Converter data flow and how real-time watermarks skip the queue PDF/UA compliance guide: Requirements, standards, and best practices Computers still can’t understand you How Athena Intelligence built AI agents for regulated enterprises with Nutrient’s document infrastructure How to convert HTML to PDF (2026): 4 methods from browser print to SDK How to build a document extraction pipeline with Nutrient Vision API OCR vs. intelligent document processing: Choosing the right document extraction engine Beyond OCR: How document intelligence eliminates manual processing in regulated industries Nutrient vs. IronPDF: Complete comparison for .NET developers Nutrient vs. Aspose.PDF: Complete comparison for .NET developers Redirecting to: https://fortune.com/2026/02/19/openclaw-who-is-peter-steinberger-openai-sam-altman-anthropic-moltbook/ Lufthansa Systems uses Nutrient to deliver reliable, scalable PDF rendering for pilots worldwide Nutrient vs. Syncfusion: Complete comparison for .NET developers React’s useTransition: The hook you’re probably using wrong First City Monument Bank streamlines banking processes with Nutrient Workflow Redirecting to: https://www.sdcexec.com/warehousing/automation/article/22957364/nutrient-workflow-automation-the-missing-link-in-supply-chain-efficiency The complete guide to digital signatures: PAdES, CAdES, and XAdES explained Nutrient Python SDK: Production-grade document processing for Python Introducing agentic document editing for web applications with AI Assistant Nutrient vs. QuestPDF: Complete comparison for .NET developers How we fixed the GdPicture license expiration (and what to do if you’re affected) Red team security testing with agentic AI The future of healthcare document automation Best healthcare workflow software compared Nutrient SDK product updates for Q4 2025 How Harvey scaled legal document workflows 50 percent MoM without rebuilding infrastructure HIPAA-compliant document management in hospitals How we optimized rendering performance while handling thousands of annotations in React — Part 2 Automated PII removal with Nutrient API Redirecting to: https://www.devopsdigest.com/2026-low-code-no-code-predictions Redirecting to: https://www.kmworld.com/Articles/Editorial/ViewPoints/Leaders-predict-AI-to-continue-permeating-all-aspects-of-KM-in-2026-172594.aspx Whipping up document magic: Your easy-bake recipe for Vue and Nutrient Web SDK 🧁 What I’ve learned about product iteration planning while building SDKs Passwordless document signing: Three-layer security guide New zip folder functionality streamlines file management in Document Automation Server The keyboard shortcuts playbook: Taking control of keyboard events in Nutrient Web SDK From experienced engineer to AI beginner: My unexpected journey AI-assisted manual testing: Handling Safari’s PDF rendering and UI quirks How to keep a 20-year-old SDK up to date How we optimized rendering performance while handling thousands of annotations in React — Part 1 Nutrient announces new executive hires to accelerate next phase of growth High performance UI using web workers Automate document conversion at scale with Python and Nutrient DCS From curiosity to PLG (and AI): My journey to understanding product-led growth Prost to progress: One year as Nutrient Pigeon usage at Nutrient: Bridging native SDKs to Flutter Modernizing CI build servers: How to migrate from Chef to Ansible Unix man pages: AI-friendly documentation since 1971 Consistent hashing for even load distribution Best AI redaction APIs: Complete comparison guide for 2025 Why AI document redaction matters for modern security From coding to coordinating: How AI transformed my workflow What is intelligent document processing (IDP)? A complete guide Enterprise PDF SDKs: Best PSPDFKit (now Nutrient) alternatives Nutrient SDK product updates for Q3 2025 GdPicture support best practices Redacting sensitive data with Nutrient AI redaction API How AI is transforming the customer experience at Nutrient: From instant answers to intelligent support How manual QA uses PR testing between releases
What are deep agents and how do they solve complex problems?
Nick Winder · 2025-12-29 · via Inside Nutrient

Table of contents

    What are deep agents and how do they solve complex problems?

    TL;DR

    Deep agents move beyond reactive AI responses to build systems that reason over time. They use detailed system prompts, planning tools, subagent coordination, and persistent memory to solve complex problems that traditional agents can’t handle.

    Imagine building an automated document processing system that handles everything from legal contracts to medical records. At first, it seems straightforward — extract data, validate compliance, generate reports. But the complexity reveals itself quickly. Legal contracts need different handling than financial statements. Validation rules learned from one document type don’t carry over to the next. And coordinating all these interdependent steps across diverse document formats proves harder than expected.

    Traditional AI agents handle individual tasks well — extract a specific field, answer a question about PDF structure — but they struggle with the bigger picture. They can’t maintain context about different document formats, remember validation patterns from previous sessions, or coordinate the complex workflow steps that real business processes require.

    This is the problem LangChain set out to solve with deep agents(opens in a new tab). Unlike traditional agents that react to individual requests, deep agents maintain complex mental models over extended periods and coordinate multiple specialized reasoning processes simultaneously.

    The problem with traditional agents

    Traditional AI agents work well for immediate responses: Ask a question, get an answer. Request a tool operation, they execute it. This handles straightforward interactions fine.

    But this approach fails when dealing with complex document workflows that businesses need daily. Processing legal contracts involves document parsing, data extraction, compliance validation, risk assessment, approval routing, and audit trail generation. Each area needs specialized expertise, and their interdependencies create coordination challenges beyond what traditional agents can handle.

    Understanding deep agents: Four core components

    Deep agents use four core components that work together to enable sustained reasoning and complex problem solving. Each component addresses a specific limitation of traditional agents, and their combination creates systems capable of handling sophisticated workflows.

    1. Detailed system prompts: Building domain expertise

    Deep agents use comprehensive system prompts as scaffolding. These go beyond basic instructions to transform a general language model into a domain-specific expert.

    Traditional agent prompts provide basic guidelines like “You are a helpful assistant that can use tools to answer questions.” Deep agent prompts include methodologies, patterns, and decision-making processes specific to their domain.

    For document processing applications, a deep agent’s system prompt might include:

    • Comprehensive guidance on document classification methods
    • Data extraction patterns for various document types
    • Compliance validation frameworks
    • Quality assurance workflows
    • Examples of how extraction, validation, and routing processes interact

    # Example: Deep agent system prompt structure

    system_prompt = """

    You are a senior document processing specialist with expertise in:

    ## Domain knowledge

    - Document classification and structure analysis

    - Data extraction from legal and financial documents

    - Compliance requirements for different industries

    - Quality assurance and validation workflows

    ## Decision framework

    When processing documents:

    1. Document type classification and confidence scoring

    2. Field extraction accuracy and validation

    3. Compliance rule application and exceptions

    4. Quality control and human review triggers

    5. Audit trail and documentation requirements

    ## Examples of expert reasoning

    [Detailed examples of document processing decision-making...]

    """

    2. Planning tools: Structured problem-solving

    Planning tools function as context engineering strategies(opens in a new tab) that keep agents focused on long-term objectives. The most common example is a todo list tool that’s essentially a no-op(opens in a new tab) — it doesn’t actually do anything substantive, but it serves as a psychological tool to help the agent maintain focus and structure its thinking.

    The planning tool serves as external memory, enabling the agent to:

    • Break down complex objectives into manageable steps
    • Track progress across multiple reasoning cycles
    • Maintain focus on the overall goal rather than getting distracted

    # Example: Todo list tool - essentially a "no-op" for context engineering

    from langchain.tools import BaseTool

    class TodoListTool(BaseTool):

    name = "todo_list"

    description = "A simple todo list for organizing thoughts and maintaining focus"

    def _run(self, action: str, item: str = None) -> str:

    """

    This tool doesn't actually do anything substantive - it's pure context engineering.

    The agent uses it to structure its thinking, but the real value is psychological.

    """

    if action == "add" and item:

    return f"✓ Added to todo list: {item}"

    elif action == "complete" and item:

    return f"✓ Marked as completed: {item}"

    elif action == "list":

    return "✓ Todo list reviewed - staying focused on current objectives"

    else:

    return "✓ Todo list accessed - use this to organize your thinking"

    # Usage example showing the psychological benefit

    agent_prompt = """

    You have access to a todo_list tool. Use it to break down complex tasks

    and maintain focus, even though it doesn't perform any real operations.

    Task: Process a complex legal document workflow

    Agent: I'll start by organizing my approach with the todo list.

    Action: todo_list(action="add", item="1. Classify document type")

    Action: todo_list(action="add", item="2. Extract key legal terms")

    Action: todo_list(action="add", item="3. Validate compliance requirements")

    Now I'll work through each item systematically...

    """

    3. Subagents: Distributed processing

    Subagents enable context management and prompt shortcuts(opens in a new tab) by allowing the main agent to spawn specialized agents for specific subtasks. This provides deeper exploration of individual problems while maintaining focus on the overall objective.

    Key benefits of subagents:

    • Specialized expertise — Each subagent can have domain-specific prompts and tools.
    • Context isolation — Subagents work with focused context rather than the full conversation.
    • Parallel processing — Multiple subagents can work simultaneously on different aspects.

    # Example: Subagent structure (based on LangChain's deepagents package)

    from typing import TypedDict, Optional, List

    from typing_extensions import Annotated

    from langgraph.prebuilt import InjectedState

    # Subagent definition as used in the actual deepagents package

    class SubAgent(TypedDict):

    name: str

    description: str

    prompt: str

    tools: Optional[List[str]]

    model_settings: Optional[dict]

    # Task tool implementation for coordinating with subagents

    def create_task_tool(sub_agents: List[SubAgent]):

    """

    Creates a task tool that can delegate work to specialized subagents

    """

    def task_tool(

    instructions: str,

    agent_name: Optional[str] = None,

    state: Annotated[dict, InjectedState] = None

    ) -> str:

    """

    Delegate a task to a specialized subagent or the general-purpose agent

    """

    # Default to general-purpose agent if no specific agent requested

    if agent_name is None:

    agent_name = "general-purpose"

    # Find the specified subagent

    selected_agent = None

    for agent in sub_agents:

    if agent["name"] == agent_name:

    selected_agent = agent

    break

    if selected_agent is None:

    return f"Agent '{agent_name}' not found. Available agents: {[a['name'] for a in sub_agents]}"

    # In the actual implementation, this would invoke the subagent

    # with its specialized prompt and tools

    return f"Task delegated to {agent_name}: {instructions}"

    return task_tool

    # Example usage with document processing subagents

    document_sub_agents = [

    {

    "name": "document-classifier",

    "description": "Classifies document types and structures",

    "prompt": "You are an expert at identifying document types and analyzing their structure...",

    "tools": ["document_parser", "structure_analyzer"],

    "model_settings": {"temperature": 0.1}

    },

    {

    "name": "compliance-checker",

    "description": "Validates documents against compliance requirements",

    "prompt": "You are a compliance expert who validates documents against regulatory requirements...",

    "tools": ["regulation_lookup", "compliance_validator"],

    "model_settings": {"temperature": 0.0}

    },

    {

    "name": "data-extractor",

    "description": "Extracts specific data fields from documents",

    "prompt": "You are specialized in extracting structured data from unstructured documents...",

    "tools": ["field_extractor", "data_validator"],

    "model_settings": {"temperature": 0.2}

    }

    ]

    # Create the coordinating task tool

    task_coordinator = create_task_tool(document_sub_agents)

    4. File system access: Persistent memory

    File system access provides a persistent workspace where agents can store context, modify files, and collaborate across agent instances. This concept is very similar to how Claude Code(opens in a new tab) operates, providing agents with a persistent workspace. The Manus team(opens in a new tab) has written extensively about this approach and its benefits for AI agent workflows.

    The virtual file system in deep agents enables:

    • Context storage — Save important information between sessions.
    • File modification — Edit and update documents as part of workflows.
    • Agent collaboration — Multiple agents can work on shared files.

    # Example: File system tools (based on LangChain's virtual file system)

    from langchain.tools import BaseTool

    import json

    import os

    from typing import Dict, Any

    class FileSystemTool(BaseTool):

    name = "file_system"

    description = "Read, write, and manage files in the agent workspace"

    def __init__(self, workspace_path: str = "./agent_workspace"):

    super().__init__()

    self.workspace_path = workspace_path

    os.makedirs(workspace_path, exist_ok=True)

    def _run(self, action: str, filename: str = None, content: str = None) -> str:

    """

    File system operations for persistent storage

    Actions: read, write, list, delete

    """

    if action == "write" and filename and content:

    file_path = os.path.join(self.workspace_path, filename)

    with open(file_path, 'w') as f:

    f.write(content)

    return f"Written to {filename}"

    elif action == "read" and filename:

    file_path = os.path.join(self.workspace_path, filename)

    try:

    with open(file_path, 'r') as f:

    content = f.read()

    return f"Content of {filename}:\n{content}"

    except FileNotFoundError:

    return f"File {filename} not found"

    elif action == "list":

    files = os.listdir(self.workspace_path)

    if not files:

    return "Workspace is empty"

    return f"Files in workspace:\n" + "\n".join(files)

    elif action == "delete" and filename:

    file_path = os.path.join(self.workspace_path, filename)

    try:

    os.remove(file_path)

    return f"Deleted {filename}"

    except FileNotFoundError:

    return f"File {filename} not found"

    return "Available actions: read, write, list, delete"

    # Example usage for collaborative workflows

    class CollaborativeWorkspace:

    def __init__(self):

    self.fs_tool = FileSystemTool()

    def save_agent_state(self, agent_id: str, state: Dict[Any, Any]):

    """Save agent state for persistence across sessions"""

    state_file = f"agent_{agent_id}_state.json"

    self.fs_tool._run("write", state_file, json.dumps(state, indent=2))

    def load_agent_state(self, agent_id: str) -> Dict[Any, Any]:

    """Load previous agent state"""

    state_file = f"agent_{agent_id}_state.json"

    result = self.fs_tool._run("read", state_file)

    if "not found" in result:

    return {}

    # Extract JSON from the formatted response

    json_start = result.find('{\n')

    if json_start != -1:

    json_content = result[json_start:]

    return json.loads(json_content)

    return {}

    Deep agents vs. traditional approaches

    While concepts like ReWOO planning and context engineering tools have existed before, deep agents represent a generalized approach that combines these ideas into a cohesive framework.

    The key differentiators of deep agents are:

    • Generalized subagent architecture — A standardized way to spawn and coordinate specialized agents
    • Comprehensive tooling ecosystem — Built-in planning tools, file system access, and coordination mechanisms
    • Detailed prompts as expertise — Using extensive system prompts to encode domain knowledge rather than relying solely on tool capabilities

    Traditional agents react — they respond to inputs with outputs, using tools when needed. Deep agents are proactive — they maintain long-term objectives and work systematically toward complex goals through coordinated subsystems.

    Consider the difference in approach when tasked with improving the performance of a web application.

    Traditional ReAct agent approach:

    Think: Need to find performance bottlenecks

    Act: `analyze_metrics()`

    Observe: Database queries taking 2.3s average

    Think: That's slow, let me optimize queries

    Act: `suggest_query_optimization()`

    Observe: Suggested adding indexes

    Think: Task complete

    Deep agent approach:

    Plan:

    1. Analyze overall system architecture

    2. Identify multiple optimization strategies

    3. Evaluate tradeoffs between approaches

    4. Implement coordinated optimization plan

    5. Measure results against performance objectives

    Execute:

    - Architecture analysis subagent — Reviews system design patterns

    - Database subagent — Analyzes query performance and indexing

    - Frontend subagent — Evaluates client-side optimization opportunities

    - Caching subagent — Identifies caching strategy improvements

    Synthesize:

    - Coordinate all findings into comprehensive optimization strategy

    When to choose deep agents

    Choosing between deep agents and traditional architectures depends on your problem characteristics.

    Deep agents work best for:

    • Deep document understanding and processing. Complex legal contracts, for example, require simultaneous analysis across multiple domains — document structure, legal terminology, compliance requirements, risk assessment, and data extraction — with interdependencies that require coordination beyond traditional agent capabilities.
    • Research and analysis that needs systematic information gathering, synthesis from multiple sources, and tradeoff evaluation.
    • Long-running projects spanning days or weeks that need persistent memory and state management.

    Traditional agents work better for:

    • Simple, well-defined tasks with clear success criteria. Answering technical questions, routine code transformations, or API operations don’t need deep agent overhead.
    • Real-time applications with strict latency requirements where planning overhead is unacceptable.
    • Cost-sensitive applications, since deep agents typically consume 10–15 times more computational resources.

    Conclusion

    Deep agents enable AI systems to tackle complex, real-world problems with expert-level reasoning. Current implementations have limitations and require significant investment, but their potential to handle complex technical challenges makes them worth exploring.

    Deep agents are a step toward AI systems that can work as partners with human experts on complex problems.

    Explore related topics

    Try for free Ready to get started?

    Related Development articles

    Explore more