Progress expands Agentic RAG without a migration—but live-app access widens the review surface

Progress has shipped three capabilities to existing Agentic RAG deployments: a Smart Agent, a native Microsoft Teams app and a WordPress plugin. The company says customers receive them as configuration on their current platform, with no installation or migration required. That makes this more than a feature bundle: it is a test of whether an enterprise retrieval foundation can absorb new reasoning, delivery and ingestion paths without a rebuild. Progress

The agent now chooses when it has enough evidence

The Smart Agent decomposes a question into sub-questions, selects sources, re-queries when needed and evaluates whether the assembled answer is sufficient before stopping. Progress says quality scoring runs at each step, rather than only on the final response. It also says citations and audit logs preserve a trace of the agent’s steps for review. Progress

The consequential change is that retrieval no longer ends at indexed content. Through MCP connections, the agent can combine records from live applications such as CRM, ERP and ticketing systems with documents already in the knowledge base. Progress gives the example of joining an account’s CRM history, an open support ticket and a contract in one answer. Progress

That convenience also broadens the review surface. The launch post says steps are cited and audited, but it does not describe how permissions are reconciled when one answer spans several live systems. Teams access is clearer: Progress says the app carries over the deployment’s existing access controls and cited answers, without requiring a custom bot framework or authentication flow. Progress

WordPress moves freshness closer to the source

The WordPress plugin replaces a crawl-only path with a native, source-side integration intended to preserve structure and metadata while keeping content current. Progress characterizes it as a precision upgrade rather than a new source category. Progress

For practitioners, the release separates three deployment questions that are often bundled together: where an answer is delivered, which systems the agent may consult and how current the underlying content is. Existing customers avoid a migration, but adding live MCP applications should still trigger an access and audit review. The platform can ship configuration instantly; an organization’s authorization model still deserves deliberate validation.