Analytics Agent types and canvas¶
Status: Current | Last reviewed: 2026-10-02
Use this guide when extending Analytics authoring with another agent type or changing its canvas. See Analytics operations for data preparation, runtime services and deployment.
Type contract¶
Analytics agents have a versioned config.analytics.type, separate from the
Studio analytics_agents subtype. The first supported value is call_drivers,
labelled Call Drivers in the creation wizard and Agent settings Type
dropdowns. Missing types on older versions resolve to Call Drivers without a
database migration; their prompts, model bindings and data selections retain
their existing behavior. Explicit unsupported types fail configuration validation.
Type labels live in agent-types.ts. agent-type-editors.ts registers each type's ordered steps, draft initialization and settings component. The shared canvas derives positions and edges from that step list. Call Drivers owns its four panels in CallDriversNodeSettings.tsx; collaboration, versions and Preview remain in the shared shell. To add a type, provide its configuration schema and default factory, register its editor and runtime behavior, and define any conversion of existing settings before enabling type switching. Adding another label alone does not enable another runtime.
Canvas behavior¶
/agents/{id}/analytics is the authoring canvas; the old
/analytics/agents/{id} route redirects. Call Drivers has four preset nodes in a fixed layout that open
a left inspector when selected or when their pencil button is clicked. The
inspector header stays visible while its settings scroll; closing it returns
the space to the canvas. Cards use the voice editor's accent borders, icon
tiles, title layout and summary footer, with a persistent purpose description
above the dataset/model summary. Canvas background, dots and zoom controls
reuse the shared Studio tokens and component. On narrow screens, the inspector
overlays the left edge of the canvas. Preset nodes cannot be dragged or
rearranged, matching the copilot canvas. Panning, zooming and click-to-edit remain
available. Legacy saved node positions are accepted but ignored; canvas
interactions no longer write positions to the shared draft.