10 posts. Tags are topics; for the editorial split see Feature releases and Developer updates.
The data-room collector shipped, ran after every sync, and filed nothing. One AND in a where-clause had pinned it to the sixty seconds around the run it followed — which made a documented constant unreachable and the dedupe code around it dead. vocion-core#463.
Eight fixes to the web connector and the candidate extractor, each found by running a real sync and reading the log. Listing-first crawl ordering, feed discovery scoped to the listing path, caps sized for one model call per document, a dry-run line that carries the dedup key, and a record that can no longer flag the card it is refreshing. Release notes 2026-09-16 — vocion-core#356, #362, #364, #365.
Release notes 2026-09-15 — vocion-core#319 (merged): a knowledge source may declare a processor that runs once per changed document inside the sync, with its own budget and failure scope; the web connector reads feeds and URL lists; sources and budgets get v1 routes.
Release notes 2026-09-15 — the Slack chat surface (vocion-core#251) is on main and deployed: app_mention and DM in, agent reply out, channels bound to agents, no Approve/Reject buttons in Slack yet. Updates our earlier post, which described it as in review.
v2.23.0 adds a Strapi connector that discovers your collections from a URL and a token, ingests many collections through one source, and survives a collection it cannot read.
The Jira connector lands — projects and issues as retrievable knowledge, hourly incremental — alongside per-source reconcile schedules: a second full-sync cadence, on every connector, that prunes what incremental syncs can never see deleted.
The credential vault is now wired into the ingestion pipeline — a connector's OAuth/API credentials are stored encrypted-at-rest per tenant and resolved at sync time, so the connector pack can actually authenticate.
Two more waves of platform work shipped: tenant API tokens that resolve into the permission model (the control plane), and a connector pack — Google Ads, GA4, HubSpot, Gmail, Slack — on the durable, incremental ingestion pipeline.
The Drive connector — Docs, Sheets, Slides, and text files exported into scoped, retrievable knowledge — completes the connector set the two reference deployments run on.
A source's schedule now actually fires — runSync runs inside a durable Temporal Workflow on a Schedule, so connectors keep their knowledge fresh on their own cadence, crash-safe and incremental.