Skip to main content

AI Agent

The node that actually performs the AI-based analysis: it reads the document (or a segment) and produces comments according to the configuration of the chosen agent. It can work alone (solo mode) or as a subagent driven by a Supervisor (supervised mode).

Ports

  • "Index" input (top, document index type) — always present regardless of mode; connect it from a Document Index node if needed.
  • In solo mode, outside a Parallel container: a content input (left) and an annotation output (right), like a regular analysis node.
  • In supervised mode, outside a Parallel container: neither a content input nor an annotation output — instead, a dedicated "supervisor" output to connect to the "agents" input of a Supervisor node.
  • Dragged inside a Parallel container: the content/annotation/supervisor ports are hidden (the container carries the group's port) — only the "index" input stays visible.

Node-level configuration (specific to this pipeline)

  • ModeSolo (the agent analyzes directly within the pipeline's flow) or Supervised (becomes a subagent, its document/annotation ports are hidden).
  • Agent — selection of the reusable agent to use (required); a button lets you create a new one directly from the panel.
  • AI model — optional override, for this node only, of the agent's default model.
  • Use support documents — unchecked by default; injects the text of support documents into this agent's context.
  • Role / objective / constraints overrides — locally replace (for this node/pipeline only) the chosen agent's defaults, without changing them globally.
  • Full prompt (advanced, hidden by default) — a raw override of the entire prompt.

Shared agent configuration

The "Configure agent" button opens the configuration of the Agent entity itself — these changes apply to every pipeline that uses this agent, not just the current node. See AI Agents for details on the fields (role/objective/constraints, default model, knowledge base, MCP connectors, extraction passes…).

The MCP connector checkboxes shown directly in the node's panel also act immediately on the shared agent, not on data specific to the node.