AI Agents & Automations

Collate 2.0 replaces the fixed agent-app model with a general AI Automations system, renames the Skills API, folds Knowledge Center into the platform’s Context Center, and closes two long-standing access-control gaps on AI Dashboards and AI charts.

The Documentation, Tier, and Quality agent apps are deleted

Breaking. Affects every deployment that installed the Documentation, Tier, or Quality agent.

Removed application	Replaced by
`CollateAIApplication` (Documentation Agent)	An AI Automation built from the Documentation template
`CollateAITierAgentApplication` (Tier Agent)	An AI Automation built from the Tier template
`CollateAIQualityAgentApplication` (Quality Agent)	An AI Automation built from the Quality template

Their agentType enum values (CollateAI, CollateAITierAgent, CollateAIQualityAgent) are removed from the schema — only Metadata remains — and each app’s bot is deleted along with it. CollateAIApplicationBot and the Tier and Quality agent bots no longer exist after the upgrade, so any token issued to one of them stops authorizing immediately. The migration converts each installed app into an AI Automation carrying the original Elasticsearch filter, named with a (migrated) suffix, but it arrives disabled and unscheduled — your Documentation, Tier, and Quality automation stops running at the upgrade and stays stopped until someone turns it back on. Fresh 2.0 installs never had the agent apps, so none of this applies to them; the templates are simply available in the catalog from day one.

Reissue any bot token built against CollateAIApplicationBot or the other removed bots before you upgrade, then open AI Automations, find the entries suffixed (migrated), review the carried-over filter, set a schedule and enable it. If the original agent notified a channel, reattach a destination — the migration never sets one.

Automation that filters GET /v1/services/ingestionPipelines by the old agentType values must move to the new values metadata and application.

AI Automations: a materially larger replacement surface

Additive, but the shape is different enough that anything built against the old agent-app APIs needs to change, not just repoint. AI Automations are a first-class entity at /v1/ai/automations with a considerably larger surface than the apps they replace:

Capability	Detail
Templates	Ship with Documentation, Tier, Quality, PII Discovery, Glossary Term Linking, and Domain Assignment templates
3-step wizard	Template → Configure → Schedule, with agent icons, scope asset count, and a flat query builder
Server-side listing	Search, filters, pagination, and a `runState` filter: `GET /v1/ai/automations/search/list`
Categories & providers	Filter the catalog by category and by provider
Run history with impact	Per-run impact statistics, and a persisted latest-run impact snapshot
Streamed logs	`GET /v1/ai/automations/{id}/logs/stream/{runId}` streams run logs over SSE; a centralised logs modal is also available in the UI
Lifecycle control	`deploy`, `trigger`, `toggle`, `kill`
Reporting	`runs/report` and `runs/publish`, plus chart-bearing email reports that can target Collate AI
Incremental	Entities already processed in previous runs are skipped
Summary	`GET /v1/ai/automations/summary` and `GET /v1/ai/automations/status`

Run records are mapped onto the same shape the app run history used, so dashboards built on agent run records keep working, but they must read from the automations endpoints, not GET /v1/collate/apps/name/{name}/agentRuns, which is removed.

Abilities renamed to Skills, Knowledge Center moves into Context Center

Breaking. Affects any client, script, or integration calling /v1/agents/abilities or /v1/knowledgeCenter. All fifteen /v1/agents/abilities endpoints move to /v1/agents/skills — a pure path rename, the request and response shapes are unchanged:

- GET|POST|PUT      /v1/agents/abilities
- GET|PATCH|DELETE  /v1/agents/abilities/{id}
- GET|DELETE        /v1/agents/abilities/name/{fqn}
- PUT               /v1/agents/abilities/restore
- PUT               /v1/agents/abilities/{id}/restoreDefault
- PUT|DELETE        /v1/agents/abilities/{id}/followers[/{userId}]
- GET               /v1/agents/abilities/{id}/versions[/{version}]
- DELETE            /v1/agents/abilities/async/{id}
+ ...the same fifteen operations under /v1/agents/skills

Because abilities became skills across the backend, AI Studio’s labels and navigation change to match — behavioural, but expect enablement material and screenshots that say “abilities” to go stale.

Additive. AI Studio itself also gains in-UI authoring for agents, personas, and skills in 2.0, including drafting a planner description for a dynamic agent. The UI-selected persona is forwarded to the AI platform, so agent behaviour follows the persona.

Agent invocation gains new surface alongside the rename:

Change	Detail
`POST /v1/agents/invoke`	New synchronous invocation endpoint alongside the streaming path
`GET /v1/agents/run/{conversationId}/events`	Server-sent events for an agent run
`GET /v1/agents/dynamic/run/{conversationId}/events`	The same for dynamic agents
`POST /v1/agents/dynamic/draftPlannerDescription`	Draft a planner description when authoring

Dynamic agents that pointed at the deleted agent-app bots are repointed by the migration. Separately, Knowledge Center is removed because the capability moved into the platform’s own Context Center:

Removed	Replacement
`/v1/knowledgeCenter/**` (18 endpoints)	`/v1/contextCenter/pages/**`

The memory endpoints (/v1/contextCenter/memories/**, 10 endpoints) keep their paths but are now served by the platform implementation, and three operations are gone entirely: check-duplicates, promote-chat and remember. Any client calling those three must be reworked, not just repointed. Context memories are also now visibility-scoped in both AI answers and semantic search (behavioural) — you see org-wide memories, memories you own, and memories shared with you or your team, not everything. No action is required; if a memory seems to have disappeared, check who it’s shared with. /v1/ai/contextPlugins is new and additive: it lets the assistant read from external sources (Notion, Slack, GitHub, Google Drive ship seeded).

AI Dashboard visibility is enforced, and a chart now belongs to one dashboard

Breaking, and a security fix. Affects every existing AI Dashboard and any client creating AI charts. Dashboard visibility (Private, Shared, Public) was stored in 1.13 but never applied — any user with view rights could open any dashboard. 2.0 enforces it, and new dashboards default to Private. To preserve existing access on upgrade, every existing dashboard is set to Public; owners should review and restrict theirs afterward. Separately, a chart carried a list of parent dashboards in 1.13, and its read access was the union of them — so any user could read someone else’s chart by pinning it to a dashboard of their own. In 2.0 a chart belongs to exactly one dashboard:

- "dashboards": ["<fqn>", "<fqn>"]     // array of parents
+ "dashboard":  "<fqn>"                // exactly one parent

- "required": ["name", "queryConfig"]
+ "required": ["name", "queryType", "dashboard"]

On upgrade, charts pinned to several dashboards are split into one copy per dashboard, keeping title, owners and query but starting a fresh version history. Any client posting dashboards: [...] or the old queryConfig shape must be rewritten — dashboard (singular) and queryType are now required. Two related endpoint removals: GET /v1/ai/charts (list) is gone — chart listing now hangs off the owning dashboard at GET /v1/ai/dashboards/{id}/charts — and POST /v1/ai/charts/preview is replaced by a single consolidated preview endpoint. Scheduled chart refresh is also re-platformed onto in-JVM Quartz (behavioural): the ingestion pipeline, Argo workflow and Python path that used to run it are retired, so any monitoring built on those pipelines (alerting on a failed refresh pipeline, for example) will see the pipelines disappear — monitor the automation and dashboard endpoints instead. AI Analytics also gains further additive changes in 2.0:

Change	Class	Detail
Provenance	Additive	`GET /v1/ai/dashboards/{id}/provenance` and chart-level provenance record how a chart was produced, with dashboard-scoped visibility per chart
Chart types	Additive	Composed and Donut chart types, plus horizontal scroll and adaptive axis ticks for dense charts
Manual refresh	Additive	Data Insight and SQL charts can be refreshed on demand
Favourites & sharing	Additive	Favourite toggle in the dashboard header, plus dashboard schedule sharing

Legacy Slack webhook receivers on AI Automations are not migrated

Breaking. Affects any AI Automation that notified a Slack channel via a webhook URL. Legacy webhook-URL Slack notification configs on AI Automations are not migrated during the upgrade. Any channel receivers configured this way are lost.

After upgrading, re-enter your Slack channel receivers directly in the AI Automations UI to restore notifications.

Full detail

For the full narrative walkthrough of AI Agents & Automations in Collate 2.0 — including screenshots and step-by-step context — see Release 2.0: AI Agents & Automations.

Collate 2.0

Breaking Changes by Component

Breaking Changes - AI Agents & Automations | Official Documentation

AI Agents & Automations

The Documentation, Tier, and Quality agent apps are deleted

AI Automations: a materially larger replacement surface

Abilities renamed to Skills, Knowledge Center moves into Context Center

AI Dashboard visibility is enforced, and a chart now belongs to one dashboard

Legacy Slack webhook receivers on AI Automations are not migrated

Full detail

​AI Agents & Automations

​The Documentation, Tier, and Quality agent apps are deleted

​AI Automations: a materially larger replacement surface

​Abilities renamed to Skills, Knowledge Center moves into Context Center

​AI Dashboard visibility is enforced, and a chart now belongs to one dashboard

​Legacy Slack webhook receivers on AI Automations are not migrated

​Full detail

AI Agents & Automations

The Documentation, Tier, and Quality agent apps are deleted

AI Automations: a materially larger replacement surface

Abilities renamed to Skills, Knowledge Center moves into Context Center

AI Dashboard visibility is enforced, and a chart now belongs to one dashboard

Legacy Slack webhook receivers on AI Automations are not migrated

Full detail