Input
ExecutionExecution trigger
AI/Agents
Executes an Agent with streaming, emitting chunks in real-time
Scores range from 0 to 10. Higher values mean more impact, exposure, or operational weight.
Execution trigger
Configured Agent object with tools
The LLM model id backing this agent
Model display name
Maximum number of iterations/tool calls before stopping
System prompt for the agent
Registered tools (function calling schemas for non-function tools)
Function references (node_id -> node_name mapping) These are converted to tools at execution time to keep data slim
MCP servers with optional tool filtering
MCP server registration with optional tool filtering
URI of the MCP server
Optional tool filter - if None, all tools are used If Some, only tools in this set are used
Whether the thinking tool is enabled
Optional conversation history to initialize with
DataFusion sessions for SQL-based data analysis Multiple sessions can be added to give the agent access to different data sources
DataFusion session context for SQL-based data analysis
Cache key to look up the session in ExecutionContext.cache
User-provided description of what this data represents e.g., "Sales data from 2020-2024 including customer demographics"
Per-table descriptions for better LLM understanding Key is the table name, value is description
Example SQL queries that work well with this data
Auto-discovered table schemas (populated at runtime) Key is table name, value is schema description
Enable infinite context mode with automatic context window management. When enabled, applies the selected context management strategy.
Strategy for managing context when it exceeds the token budget. - Truncate: Sliding window, removes oldest messages (fast, no extra cost) - Summarize: LLM compresses old messages (preserves info, adds latency/cost)
Sliding window truncation - removes oldest messages to fit budget. Fast, deterministic, no extra API costs. May lose important early context.
LLM summarization - compresses old messages into a summary. Preserves key information but adds latency and API cost.
Maximum tokens to retain when truncating history in infinite context mode. Defaults to 32000 tokens if not specified. Only used when infinite_context is true.
Lazy function references backed by a vector DB index. At execution time the agent can search this index to dynamically discover and load only the tools it actually needs, keeping the context window lean.
Reference to a lazy function tool index stored in a vector DB. Allows agents to do hybrid search over a large pool of tools at execution time instead of loading all tool schemas into the context upfront.
Cache key used to look up the LanceDB connection
Embedding model shared across all lazy function tool indexes. The model's cache key is encoded into the vector DB table name, so swapping the model automatically uses a fresh table (old embeddings are abandoned).
Persistent memory configuration. When set, the agent gains built-in `_memory_search`, `_memory_store`, and `_memory_compress` tools to autonomously store, recall, and compress observations across conversations.
Conversation history to provide context
Triggers whenever the agent streams a chunk
Latest streamed chunk from agent response
Fires when agent completes execution
Final complete agent response
Updated conversation history with all agent turns
Token usage, cost, and model statistics