Skip to content

DocsGPT 0.16: From Smart Agents to Orchestrated Workflows

A visual Agent Workflow Builder with CEL condition nodes, Amazon S3 and SharePoint connectors, and a Docling-powered parser with OCR for messy documents.

Pavel Torbinupdated 7 min readreleaseworkflowsagents

Workflow graph in the DocsGPT builder language: Document upload, Score against policy, a Route by approval tier condition node in accent, three agent branches (Legal review memo, CFO business case, Commercial approval) and an End node, joined by dashed connectors.

Individual agents are useful. But the real unlock happens when agents work together, making decisions, branching based on conditions, and executing multi-step tasks without human babysitting. That’s what 0.16 is about.

DocsGPT 0.16 introduces a visual Agent Workflow Builder, expands enterprise data connectivity with Amazon S3 and SharePoint, and ships a Docling-powered parser that can OCR its way through documents most models would choke on. Whether you’re a developer building internal tools or an enterprise team evaluating document AI platforms, this release gives you the building blocks for production-grade automation.

Build Multi-Step Agent Pipelines Visually

The headline feature of 0.16 is the Agent Workflow Builder, a visual interface for chaining agents into conditional, multi-step pipelines.

Previous DocsGPT versions let you configure powerful individual agents. The problem? Complex tasks rarely fit inside a single agent’s scope. Summarizing a legal document, cross-referencing it against internal policy, then drafting an action plan requires coordination, not just capability.

The Workflow Builder solves this with a drag-and-drop canvas where you define agent sequences, set condition nodes using CEL (Common Expression Language) evaluation, and route outputs between steps. If step one returns a risk score above a threshold, route to the compliance agent. Otherwise, skip to the summary agent. That kind of logic is now configurable without writing code.

Why this matters: Workflows turn DocsGPT from a tool you query into a system you orchestrate. For enterprise teams, this means repeatable, auditable automation. For developers, it means less glue code.

app.docsgpt.cloud — Agents › Workflow builder
Workflow builder canvas: Score against policy (code node, import json, re) feeds Set approver + turnaround (4 variables), then Route by approval tier, a condition node with If Legal review, Else if CFO business case, Else if Commercial approval and Else. The branches lead to four agent nodes on docsgpt-local, Legal review memo, CFO business case, Commercial approval and Fast-track confirmation, each with Output: memo, which all join at End. Two yellow notes explain how the flow works and the approval tiers from the Delegation of Authority Matrix.
app.docsgpt.cloud — Agents › Workflow builder
Workflow builder canvas: Score against policy (code node, import json, re) feeds Set approver + turnaround (4 variables), then Route by approval tier, a condition node with If Legal review, Else if CFO business case, Else if Commercial approval and Else. The branches lead to four agent nodes on docsgpt-local, Legal review memo, CFO business case, Commercial approval and Fast-track confirmation, each with Output: memo, which all join at End. Two yellow notes explain how the flow works and the approval tiers from the Delegation of Authority Matrix.

Enterprise Data Where You Already Store It

Agents are only as good as the data they can access. 0.16 adds two major integrations that enterprise teams have been asking for.

Amazon S3 Support & Sync connects DocsGPT directly to your S3 buckets. Documents sync automatically, so when your team updates a file in S3, DocsGPT picks it up without manual re-ingestion. For organizations already built on AWS, this removes the friction of getting data into the system.

SharePoint Integration does the same for Microsoft-centric environments. If your company’s knowledge lives in SharePoint (and for many enterprises, it does), DocsGPT can now pull from it directly.

Beyond new sources, we’ve also improved crawlers and chunk filtering across the board. Crawled content is cleaner, chunks are more precise, and the overall ingestion pipeline produces better results downstream.

Why this matters: The biggest bottleneck in document AI adoption isn’t model quality. It’s getting your actual data connected. S3 and SharePoint support removes that barrier for the two most common enterprise storage patterns.

Sources sync from where they already live0.16 · connectors
Amazon S3, SharePoint and Google Drive sync into DocsGPT sourcesThree source boxes connect with dashed lines to a highlighted Sync node, which connects to a Knowledge box on the right.Amazon S3SharePointGoogle DriveSyncKnowledgeaccess key · bucket · auto-syncentra id · graph api · auto-syncoauth2 · on demandscheduled · changed files onlyone source per storecrawlers · chunk filteringretrieval
Text version

Three enterprise stores on the left, Amazon S3 (access key and bucket, auto-sync), SharePoint (Entra ID and the Graph API, auto-sync) and Google Drive (OAuth2, on demand), feed one Sync step that runs on a schedule and picks up changed documents. Sync writes into the knowledge layer on the right: each store becomes its own source, passed through the improved crawlers and chunk filtering before retrieval.

Smarter Document Processing with Docling & OCR

Not every document is a clean UTF-8 text file. Scanned PDFs, image-heavy reports, and legacy documents with embedded charts have always been a pain point for document AI systems.

DocsGPT 0.16 ships the Docling parser, an advanced document processing engine with built-in OCR support for attachments. Docling extracts structured content from documents that would otherwise require manual pre-processing.

Paired with this, we’ve added synthetic PDF processing: when a model doesn’t natively support file uploads, DocsGPT processes the PDF synthetically and feeds the extracted content to the model. No more “unsupported file type” dead ends.

The new Research Agent rounds out this pillar. It’s a purpose-built agent type designed for multi-step information gathering and synthesis, the kind of task where you need to pull from multiple sources, cross-reference findings, and produce a structured output.

Why this matters: Document AI that only works on perfect inputs isn’t useful in the real world. Docling and synthetic processing mean DocsGPT handles the messy documents that actually exist in enterprise environments.

Docling parser with OCR, 0.16
  1. 01Scanned PDFimage-only pages · legacy report
  2. 02Docling parse + OCRlayout · tables · text from images
  3. 03Structured contentsections · tables · captions
  4. 04Chunksfiltered · per-source settings
  5. 05Agentcited answer · synthetic pdf fallback
Text version

A scanned or image-heavy PDF enters the Docling parser, which reads layout, tables and text inside images with OCR. The structured content is chunked and filtered per source, then retrieved by the agent. When a model cannot take file input, DocsGPT feeds it the extracted content instead of failing on the file type.

Organize, Stream, and Secure

Every major release carries a wave of improvements that don’t make the headline but make the daily experience better.

Agents Grouped Under Folders

As agent libraries grow, flat lists become unmanageable. You can now organize agents into folder structures, making it practical to maintain dozens of specialized agents without losing track of them.

Streaming Thinking Tokens

When an agent reasons through a complex task, you can now watch it think. Streaming thinking tokens surface the model’s intermediate reasoning in real time, giving you transparency into how the agent arrived at its answer.

Speech-to-Text

Voice input is now initialized in 0.16, allowing users to interact with agents through speech. Early-stage, but the foundation is in place.

Advanced Settings & Dynamic Config

New advanced settings give power users more control over agent behavior, and dynamic configuration rendering makes MCP tool setup more flexible.

Accessibility & Security

Frontend accessibility improvements make DocsGPT usable for a wider range of users. Token calculation and history counting have also been corrected for accuracy.

Novita AI Provider

Novita AI joins the list of supported model providers, expanding the range of models you can plug into your agents.

9 New Contributors Joined This Release

Open source grows through community. DocsGPT 0.16 includes contributions from 9 first-time contributors alongside the core team, spanning features, bug fixes, accessibility, and testing.

What 0.16 Means for DocsGPT

This release marks a shift in what DocsGPT is. Previous versions focused on making individual agents smarter: better prompts, better memory, better tools. 0.16 focuses on making agents work together. The Workflow Builder is the clearest expression of that direction, but it shows up everywhere, in how data flows in from S3 and SharePoint, in how Docling pre-processes documents before agents ever see them, in how folders organize growing agent libraries.

The trajectory is clear: DocsGPT is becoming an orchestration platform, not just a chat interface.

← All posts
  • · 6 min

    DocsGPT 0.19: Agents That Make Things (and Know When to Stop)

    Agents now produce versioned files, run code in a sandbox and operate behind configurable guardrails, while the chat shows every step as it happens.

    release · agents · guardrails · artifacts

  • · 5 min

    DocsGPT 0.18: What Your Agents Actually Know

    A rebuilt retrieval stack with per-source tuning and hybrid search, GraphRAG over a knowledge graph, a wiki your agents can edit, and teams.

    release · knowledge · agents

  • · 5 min

    What Your Agents Do at 3 A.M.

    Agent scheduling on a cron or one-off basis, enterprise SSO with OIDC and SCIM, and a rebuilt analytics and logs stack that shows exactly what ran.

    agents · workflows

See DocsGPT on your documents

A 30-minute demo on your use case, or a free on-premises review with an engineer.