What's New

Weekly product updates and new features

​

Week of July 6, 2026

AI Studio

• JSON Mode tool — A new tool type that has an agent return a structured JSON payload for your own backend to process, instead of a text reply. You define the fields in AI Studio → Tools and attach the tool to an agent; when the agent calls it, AGO hands the JSON to whoever is driving the conversation over the API and ends the turn. It’s tied to the agent (not declarable from the browser), so only agents you configure can produce it. See the JSON Mode Tool reference.

Ticketing

• Run an agent on new tickets — A new ticket trigger action, Invoke AGO Agent, hands a new ticket to a background agent. The ticket gets an internal note linking to the agent’s run so you can watch it work, and the agent’s answer is posted back to the ticket as a staff-only internal note. Turn on Background agent for the agent you want, then add the action to a Ticket Created trigger and pick the agent (set an optional objective with placeholders like {{ticket.subject}}). If the agent needs approval for a sensitive step, the ticket gets a note linking straight to the approval.

Admin

• See what the Assistant is doing — The in-admin Assistant now shows each step inline as it works — “Navigating to Agents”, “Updating the page”, “Opening conversations” — in order, between the parts of its reply, so an answer reads as the sequence of what it did and what it wrote.

API & Integrations

• Proactive mode (SDK) — An embedded agent can now detect friction in your app — inactivity on a page, hesitation between pages, rage clicks — and offer help before the user opens the chat. Developers declare triggers in the app code; clear-cut cases show a fixed message, ambiguous ones ask the agent whether a nudge is worth it and what to say. Nudges are small dismissable bubbles (never pop-ups), rate-limited per session and per day, held back for 24 hours after a dismissal, and can offer a one-click action like pre-filling a form. Off by default; enable it per workspace and tune it per agent. See Proactive Mode.

​

Week of June 29, 2026

AI Studio

• Approve sensitive agent actions before they run — Tools can now be marked Require approval in background runs (tool builder → Access & Restrictions). When a background agent is about to use one — issuing a refund, say — the run pauses and an approval card appears in the conversation: staff users see the tool and the exact values it wants to send, approve or reject in one click, and get a bell notification; other viewers only see that the run is waiting. Rejecting tells the agent the action was not approved so it concludes honestly, and a pending approval expires after 72 hours. Every decision is recorded in the run’s progress log with who decided and when.
• Background runs survive interruptions — Background agents now save their progress as they work. If a run is cut off mid-task (a deployment, a crash), it no longer restarts from zero or silently disappears: a card in the conversation asks a staff member whether to resume from the last completed step or stop the run. The saved progress is encrypted, and it is deleted as soon as the run finishes.
• Background agents: clearer progress, in your language — While a background agent works through its task plan, the progress log now names each tool it uses (the tool name only — never the tool’s data), and the whole progress panel follows the conversation’s language: task names, the “Task Details” and “Progress Log” sections, the completion bar, and every log line (“Plan mis à jour : 2/5 tâches terminées” in a French conversation). When the agent finishes, the task list now closes out at 100% instead of leaving the last task hanging, answers keep their formatting (poems, lists, and paragraphs render with proper line breaks), a run that stops early says “Objective not fully completed”, and a run that hits an internal error shows as a failed message rather than a successful reply.

API & Integrations

• Pause and resume the agent on client functions — When your app registers client-side functions, you can now send messages with client_functions_mode: "pause": instead of continuing without the function’s result, the agent stops and waits (the stream ends with a WAITING_CLIENT status). Run the function, submit its result, then call the new POST /messages/{id}/continue endpoint — the agent picks the same turn back up with the real result and the current page’s functions and context. The paused state is stored server-side, so it survives a full page reload: reload the conversation, submit the pending calls, and continue. A turn that called several functions resumes once all results are in, and sending a new message abandons the paused turn. The default mode is unchanged.
• Send app events to the agent (hidden messages) — The SDK Send Message endpoint accepts a new hidden flag for messages sent by your application code instead of the user — for example “the user completed the payment”. The agent reads the event and replies right away, but the message comes back with role: "system" so your chat interface can skip the user bubble. In the AGO conversation history, these events appear as a small centered chip instead of a user message. A hidden message requires an existing conversation_id; it cannot start a conversation.

Admin

• The Assistant can create and fill in builder forms — On the agent, tool, and knowledge source builder pages, the in-admin Assistant can now update the form for you. Ask it to “set the temperature to 0.2 and switch the model to GPT-5” on the agent builder, “make it a background agent with the Order Lookup tool”, “let it search all the SharePoint sources”, “create an HTTP request tool with this input schema”, “mark this tool as requiring approval in background runs”, or “enable auto-sync” on a knowledge source. It can also start from scratch and navigate for you — “create an agent that searches all our SharePoint sources” opens a blank agent builder and pre-fills it in one step. It only touches the fields you mention, and nothing is saved until you click Save.
• More builder pages the Assistant can fill in — Form-filling now also covers the conversation starter, incident banner, prompt template, business hours, and permission builders. Try “create a starter titled Onboarding feedback and show it on the home screen”, “draft a maintenance banner in red and activate it”, “create a template named Support that tells the agent to keep answers short”, “name this schedule Support hours and set the timezone to Europe/Paris”, or “create a permission named VIP, make it public and set priority 10”. As before, start from scratch too — “create a conversation starter …” opens a blank builder and pre-fills it, and nothing is saved until you click Save.
• The Assistant can drive the dashboard and list pages — Beyond forms, the Assistant can now change what you’re looking at. On the dashboard, “open the tickets tab” or “show the last 30 days” switches the active tab and time range. On list pages it applies filters for you: “search for john” or “show only staff users” on User Management, “show me the failed syncs” on the knowledge sync history, and “open the JWT-based permissions tab” on Agent Permissions.

​

Week of June 22, 2026

API & Integrations

• Review knowledge gaps over MCP — The MCP server now exposes knowledge update requests (detected knowledge-base gaps). Connected MCP clients can list and read gaps, set their review status, mark them resolved, and trigger recommended knowledge-base actions, without opening the web app.

Admin

• Create users before they sign in — A new Create User button on Settings → User Management → Users lets you create a user ahead of time and assign their organization, permissions, metadata, and statuses. When the person logs in for the first time, they’re matched by email and reused (no duplicate), keeping the details you set. Re-using an existing email updates that user instead. The same capability is available through the Public API (POST /api/v1/users) and the upsert_user MCP tool (accounts:write scope); the API can never grant Admin status.
• Grant and revoke a user’s permissions via the API — Two new Public API endpoints add or remove permissions one at a time without touching the rest. POST /api/v1/users/{user_id}/permissions adds permissions on top of what the user already has, and DELETE /api/v1/users/{user_id}/permissions/{permission_id} removes a single one. GET /api/v1/users/{user_id} now returns the user’s current permissions too. The same actions are available as the add_user_permissions and remove_user_permission MCP tools. Both write endpoints need the accounts:write scope.
• Find admin pages by name — The left admin menu now shows each item’s name next to its icon, grouped into Activity (chat history, dashboard, feedbacks, tickets) and Configuration (knowledge, data, AI Studio, settings). Pin the menu open, or unpin it to collapse to icons and free up space (for example next to a section’s own sub-menu) — using the pin button in the top-right corner, or by pressing Cmd/Ctrl + .. When collapsed, hover over the icons to bring the names back.

Knowledge

• Knowledge Coverage — A new Knowledge → Knowledge Coverage page measures how well your documents answer a set of reference business questions, grouped by domain (legal, HR, and so on). Import a question referential as JSON, run an evaluation, and see a coverage percentage per domain plus the list of questions your knowledge base can’t answer yet. Coverage, the reference questions, and the gaps are also available through the API and MCP for external agents.
• Import a local folder with the File Directory source — A new File Directory knowledge source imports every supported file in a folder and its subfolders, parsing each one by its type: Markdown and text files are used as-is, HTML is converted to Markdown, OpenAPI/Swagger specs are expanded into one document per API operation, and PDF, Office documents, and other supported files have their text extracted. Markdoc content is cleaned up too — {% partial %} includes are inlined, role-gated {% if %} sections are resolved for a chosen audience, and images referenced in Markdown are imported and served by AGO. Include and exclude glob patterns let you choose which files to import, and an optional base URL turns each file path into an external link.
• Filter gap reports by page and knowledge source — Knowledge Gap Reports has two new filters. Document pulls up every request about one knowledge base page — matching both requests linked to the page and those whose suggested edits target it — so you can handle a page’s gaps in one pass instead of one by one. Knowledge source narrows to requests for pages from a given source (for example Notion or Confluence). Both dropdowns list only entries that have at least one request, with a count. The old Source filter is now named Origin to make clear it filters by where the gap came from (user feedback, nightly review, simulation lab).

Messaging & Channels

• Connect WhatsApp without copying tokens — A new Connect WhatsApp button on Settings → Integrations → WhatsApp lets you connect a number by signing in to Facebook in a popup and picking your WhatsApp Business Account. Enter the two-step verification PIN and AGO collects the credentials, registers the number, and subscribes to message webhooks automatically. Manual token entry is still available under Advanced: manual setup.
• Reply to WhatsApp voice messages — When a customer sends a voice message on WhatsApp, AGO now transcribes the recording and the assigned agent answers it as text, using its knowledge and tools just like a typed message. The spoken language is detected automatically.

Ticketing

• Pick when a ticket trigger runs — Creating a ticket trigger now happens on its own page (under Tickets → Settings → Ticket Triggers) with a Trigger on choice: Ticket created or Ticket updated. “Updated” triggers fire when an AGO-managed ticket changes — its status changes, it’s assigned to a team member, or a staff member replies — so you can route or notify on changes, not just on new tickets. Conditions and actions (including AI category, permission, organization, and assign-to-team/user) work the same on both events.
• In-app notifications for ticket assignments and replies — A bell in the admin sidebar shows your notifications with a count of unread ones. You get one when a ticket is assigned to you (by a teammate or a routing rule) and when someone else replies on a ticket assigned to you. Click a notification to open the ticket; use Mark all read to clear the badge.

​

Week of June 15, 2026

AI Studio

• See which agents use a tool — The tool editor has a new Agents tab listing every agent that has the tool attached. Click an agent to open it, so you can check what depends on a tool before changing or removing it.

Analytics

• Filter conversations by tool used — The Admin conversation list has a new Tool Used filter to show only conversations where the agent called a specific tool. Each conversation row also shows a Tools Used column listing the tools called during that conversation.
• Team Pulse counts reviews by review date — In the Team Evaluation dashboard, the Total reviews, Active reviewers and KO rate cards now count human evaluations by the date the reviewer evaluated the conversation, not by when the conversation happened. So work done this week shows up in this week’s numbers even for older conversations. The Unevaluated backlog card still counts by conversation date, and the Total reviews and Unevaluated backlog cards now show an info tooltip explaining what they measure.

Knowledge

• Per-step timing and crash location in sync history — Each finished import now shows how long it spent in each phase (Import, Cleanup, Links, Embeddings, Translation). When an import fails, the history row shows which phase it stopped on (for example “Crashed at: Embeddings”), so you can see where a run broke without digging through logs.

Ticketing

• SLA tracking — New SLA policies set first-response and resolution targets measured in business hours. Manage them under Tickets → Settings → SLA Policies, matching on the ticket’s priority, typology, and tags, or on the requester’s organization, permission, or email domain. When a ticket is created, the matching policy sets its deadlines; a badge on the tickets list and ticket detail shows the time left and turns orange as a deadline nears, red once it’s missed. The first-response deadline is met when an agent posts the first public reply, the resolution deadline when the ticket is closed.
• Route new tickets with triggers — Triggers can now match on who the requester is — their permission, organization, or which AI agents they can use — and on an AI Category assigned by an AI classifier that reads each ticket. New Assign to User and Assign to Team actions send the matching ticket to the right place as soon as it is created. Configure the classifier’s prompt and category list per ticketing system.
• Assign tickets to a team member — Each ticket now has an Assignee you can set from the ticket detail view, with an Assignee column on the tickets list so you can see who owns what. Pick any internal team member or set it back to Unassigned; every change is recorded. Tickets synced from an external system keep that system’s assignee.
• Business hours schedules — A new Settings → Business Hours page lets you define a timezone, weekly opening hours (including breaks via multiple intervals per day), and holidays. Each schedule marks which hours are open and which are closed — for a Monday–Friday 9:00–17:00 calendar, Friday evening and the weekend are closed and the next open time is Monday at 9:00.

Admin

• In-app Assistant — Chat with AGO’s own agent without leaving the admin interface. Open it from the Assistant icon in the left sidebar; it docks as a companion panel on the right so the page stays usable while you chat. Ask about your account, knowledge base, or conversations, attach a file to a question, and ask it to take you to a page (“open the agents page”, “show ticket settings”) — it navigates you there, and can open the conversations list with filters already applied (“conversations needing review handled by the Support agent”). Your conversation is kept across page refreshes, and a New conversation button starts a fresh chat.

​

Week of June 8, 2026

AI Studio

• AI-generated test cases in the Agent Lab — A Generate with AI button in the dataset builder reads the agent’s knowledge base and prompt, then writes realistic test cases with expected answers (1–50 at a time). Test cases are multi-turn conversations by default: each one opens with a question and follows up the way a real user would, up to the per-conversation message limit you pick in the dialog (set it to 1 for single questions). Two modes: generate from the knowledge documents directly, or describe a user profile (type of user and how they behave) so questions are asked the way that user would. Generation runs in the background and the new test cases land in the dataset ready to run or edit.
• Knowledge gap detection from simulation runs — A Detect knowledge gaps option when starting a simulation run turns failed answer tests into Knowledge Gap Reports. Each report carries the question, what was missing, suggested knowledge base edits, and the new “Simulation lab” source so you can filter them in Knowledge → Knowledge Gap Reports.
• Keep HTTP tool API keys out of the headers config — In an HTTP Request tool, put your credential in the encrypted Secret Key field and reference it from a header with the {{secret_key}} placeholder. The placeholder is replaced at request time, so the key never sits in the headers JSON. Works with any auth scheme, including custom token formats like Token token="{{secret_key}}".

Knowledge

• Import duration in sync history — Each finished sync now shows a Duration column in the sync history, so you can see how long an import took from start to finish.

API & Integrations

• The JavaScript SDK is now open source — @useago/sdk is published under the Apache 2.0 license. You can read the source, use it in commercial projects, and build on it freely. Install it with npm install @useago/sdk and follow the framework guides for React, Vue, Angular, or plain JavaScript.
• Filter MCP results by agent — The list_conversations, search_conversations, list_feedback, and list_tickets MCP tools now accept an agent filter, so an integration can pull just the conversations, feedback, or tickets handled by a specific agent. Pass an agent name or ID, or a comma-separated list to match several. Conversations and feedback match the name exactly; tickets match by substring. Use list_agents to find valid names.
• MCP requests queue under heavy load — When too many MCP requests arrive at once, the server now holds excess requests briefly until a processing slot frees up, instead of letting the load degrade every request. If no slot frees up in time, the request gets a 429 response with the concurrency_limit_exceeded error code and a Retry-After header telling your client how long to wait before retrying. See API Errors for details.
• Define a conversational form in the backend — A form’s fields can now be stored in AGO and fetched by name instead of written into your page. Reference it with loadFormCollector(client, { name }), useFormCollector({ name }), or a { name } entry in the widget’s forms — change a field in the admin interface and every page picks it up on next load.
• Submit a conversational form to a webhook URL — In the form builder, a Webhook URL field sets where a completed form is sent: AGO POSTs the values to that URL as JSON, from the server. No HTTP tool to create first — the advanced submit config (custom headers, tool destinations) stays available when you need it.
• Form submission history — Every conversational form submitted through the server is now kept in a history. Open Form Collectors → Form Submissions to see when each form was sent, by whom, and whether it completed or failed; click a row to open its detail page with the full submitted data. Filter by form, status, or date range.
• Simpler SDK API authentication — The widget/SDK identification header is now called X-User-Anon-Id, matching what it really is: an anonymous identifier for the end user. The old X-Widget-Id name keeps working. On the SDK API, requests that carry a JWT can skip the header entirely — the user identity comes from the token’s sub claim. See Widget & SDK Authentication.

​

Week of June 1, 2026

AI Studio

• Smart Table search returns full row content — When an agent searches a Smart Table, the full content of each matching row is now included in the results by default, so the agent can read the whole document. A new Exclude full row content option in the tool configuration leaves the content text out (keeping the column values and a link to view it) when rows are large.
• Tunable follow-up replies — Follow-up reply suggestions are now configured per agent in the agent’s Follow-up Replies section, with an optional Instructions field to set your own rules for when to skip them. Suggestions are also skipped automatically when the agent is asking the user for information such as their name or email.

Knowledge

• Translation progress counter — When your knowledge base uses more than one language, a syncing source’s history row now shows how many documents are left to translate during the translation step (for example, 6/10 documents remaining to translate). Only documents that actually need translation are counted.
• Internal documents are never cited — Documents with public display disabled can still inform an agent’s answer, but the agent no longer cites, quotes, or links them. Internal and public sources are kept in separate lists when building the agent’s context.

Analytics

• Team Pulse dashboard tab — A new Team Pulse tab on the Dashboard tracks how your team reviews conversations over the selected period, compared to the period before: total reviews, active reviewers, KO rate, and the unevaluated backlog. A per-reviewer table shows each person’s review count, OK% and KO%, and a tag table ranks the tags most often found on KO-rated conversations. Clicking a reviewer, a tag, or the backlog opens the matching conversations in Chat History.

API & Integrations

• Team Pulse over MCP — The full Team Pulse dashboard (period-over-period KPIs, the per-reviewer table, and the conversation- and admin-tag breakdowns of KO conversations) is available through a single MCP tool, get_team_evaluation_analytics, protected by the Analytics Read (analytics:read) scope.
• Conversational forms survive a reload — A form an AGO agent was filling now comes back when a visitor reloads the page and reopens the conversation. The SDK replays the values the agent already recorded, so the form’s collected values, what’s still missing, whether it’s complete, and whether it was already submitted are all restored instead of starting over.
• Conversational forms in the SDK — A new createFormCollector helper (and useFormCollector React hook) lets an agent fill a form through conversation: define the fields once and the SDK keeps a live store, gives the agent a function to record values, tells it what’s still missing, and submits the completed form either from the browser or via a server-configured destination.
• Tool calls in the SDK conversation history — The SDK conversation endpoint now returns a tool_call_data array on each message, listing the tool calls the agent made (with their status and how to display them). You can use it to replay a past conversation — including its tool calls — in a custom chat interface, matching what the built-in widget shows.

​

Week of May 25, 2026

AI Studio

• Connect agents to external MCP servers — Register external Model Context Protocol servers (streamable-http transport) under AI Studio > MCP Servers with their endpoint URL and an optional auth header. Saving a server pulls its tool list and adds each one to your tool catalog. From an agent’s Capabilities tab you can then attach the whole server (the agent gets every current and future tool from it) or pick individual tools one-by-one if you only want a subset. Tools synced from an MCP server are tagged with the server name in the picker. A Forward end-user JWT option swaps the stored credential for the chat user’s bearer token at call time, for MCP servers that authenticate against your IdP.

Knowledge

• Step-by-step import progress — While a knowledge source is syncing, its history row now shows a live checklist of each stage of the import, ticking off one by one as it progresses. This now works across all connectors, not just SharePoint.

API & Integrations

• Richer markdown in the SDK chat widget — Assistant replies rendered by the SDK’s React ChatWidget and Message components now show GitHub-flavored markdown (tables, task lists, strikethrough), plus headings and images, on top of the existing bold, lists, code, and links. A new exported Markdown component lets you render the same formatting in a fully custom chat UI. A showAgentName prop on ChatWidget and Message hides the agent name above replies when set to false.

​

Week of May 18, 2026

AI Studio

• Sort smart-table results from the chat agent — When configuring a custom data source search tool, pick which columns the agent may sort by. The agent can then answer “top/largest” and “smallest/lowest” questions on its own, like “give me the 5 invoices with the largest amount”. Sort is ignored during semantic search, where results are already ranked by relevance.
• Smart-table row content + viewer page — Each smart-table row now has a content field that holds the full extracted markdown (auto-filled for PDF uploads and document smart sources, or set explicitly via the API). A dedicated viewer page renders the markdown at /smart-tables/<slug>/rows/<external_id>, accessible from the admin rows table. When the chat agent searches a smart table, rows with content also expose a view: URL so the agent can link to the full content in its replies.

Analytics

• Filter chat history by conversation starter — Admin Chat History has a new Conversation Starter filter so you can list every conversation triggered by a specific starter. The starter’s edit page also gets a View all in chat history link and clickable rows in its conversation list, making it easier to export or drill into the underlying conversations.

API & Integrations

• Full Access scope for API keys — When creating an API key under Settings > Integrations, you can now pick Full Access to grant access to every API v1 endpoint, present and future — handy for back-office integrations that would otherwise need every scope checked individually. The dedicated custom_data_sources:read and custom_data_sources:write scopes for smart tables also appear in the scope picker.
• Clear a smart table — A new Clear table action in the rows view deletes every row in a smart table in one go while keeping the schema. Also exposed as POST /api/v1/custom-data-sources/{slug}/rows/clear. The smart tables list now shows a Rows column with the current row count for each table, and the Data section’s left nav now opens directly on Smart tables.

​

Week of May 11, 2026

Messaging & Channels

• Conversation starter cards on the home page — Mark a conversation starter as Show on home to display it as a clickable card on the chat home page and widget welcome screen. The card shows the starter’s description; clicking it sends the initial message and opens the conversation.
• “Widget starter” renamed to “Widget auto-starter” — The toggle that auto-sends a starter when a widget user opens with no active conversation is now labelled Widget auto-starter to make its behavior clearer.

Knowledge

• Live import progress for SharePoint — Sync history now shows live stats for in-progress SharePoint imports: documents done out of total, the file currently being extracted, how long ago the last file finished, throughput, and ETA. The page refreshes automatically while a sync is running.
• Cancel a SharePoint import — Stop a running SharePoint sync from its row in sync history. The import halts once the files currently being extracted finish; already-imported documents are kept and the row is marked Cancelled.

​

Week of May 4, 2026

API & Integrations

• Connect Claude Web with OAuth — Paste your AGO MCP URL into Claude Web’s “Add custom connector” and sign in once — no API key copy-paste. AGO now supports OAuth 2.1 with PKCE for MCP clients. Existing X-API-Key integrations keep working unchanged.

Admin

• OAuth Connections page — Review and revoke active OAuth tokens issued to MCP clients (Claude, etc.) under Settings > OAuth Connections. Revoking a token forces the client to reconnect.

Knowledge

• SharePoint folder browser — When configuring a SharePoint knowledge source or smart source, click into the folder tree of the selected site and library instead of typing the path manually. Breadcrumbs let you jump back to any parent folder.
• Granted SharePoint sites list (Selected sites mode) — Add the SharePoint site URLs your admin granted to AGO under Settings > Integrations > SharePoint. The site picker is now a real dropdown in Selected sites mode instead of asking you to paste a URL each time.
• Automatic knowledge gap detection — When a user marks an answer as “information not found”, AGO now reviews the conversation in the background and files an Update Request shortly after. A nightly review at 3:00 AM also catches gaps that users did not flag. Both new and old requests appear under Knowledge → Knowledge Gap Reports.

Ticketing

• Option messages on ticket fields — Show a contextual message under a select field as soon as a specific option is picked. Pick a style — Info (blue), Warning (amber), or Danger (red) — to flag expected delays, ask for an attachment, or warn about restricted scope before the user submits.

​

Week of April 27, 2026

Analytics

• Thread to Ticket Rate — The dashboard overview now shows the share of conversations converted into tickets, replacing the old “Escalation Rate” card. The new metric counts conversations linked to a ticket, giving a clearer picture of when the AI hands off work to your team.

Knowledge

• SharePoint Selected sites mode — Restrict AGO’s SharePoint access to specific sites only. Choose between “All sites” (Sites.Read.All, simple setup) and “Selected sites” (Sites.Selected, limited scope) under Settings > Integrations > SharePoint. In Selected sites mode, paste a site URL when creating a knowledge source and click “Test access”; if access is denied, AGO surfaces the Microsoft Graph curl command to send to your admin.

AI Studio

• Agent Lab results view — Run results now lead with a success-rate ring and a verdict card showing the LLM evaluation reasoning and per-criterion scores. Expected and actual answers display side-by-side with full markdown rendering (tables, code blocks, lists). Datasets and personas show as cards with relative “last run” times. Fixed: dataset test-case count was multiplied by the number of runs.

Admin

• Agent permissions diagram — A visual flow on the Agent Permissions page now shows how a user is granted a permission and how that permission unlocks an agent.

API & Integrations

• Conversation thread payload enriched — GET /api/v1/conversations/{thread_id} now returns the full thread with all of its messages, including knowledge sources, feedback, tool calls, attachments, agent details, ticket info, and evaluation fields. Breaking: the separate GET /api/v1/conversations/{thread_id}/messages endpoint has been removed — request the thread instead and read its messages array.
• Top shared documents MCP tool — List the top N knowledge documents shared (cited) in conversations over a given period. Available as the get_top_shared_documents MCP tool under the analytics:read scope, with usage and clicks ranking metrics. Defaults to the last 7 days and 50 documents.
• Conversations write API — Set thread evaluation, admin comment, admin tags, and admin status programmatically via Public API v1. New conversations:write scope unlocks POST /api/v1/conversations/{id}/evaluation, /admin-comment, /admin-tags, and /status.

​

Week of April 20, 2026

Knowledge

• SharePoint connector — Import documents from SharePoint document libraries (Word, PowerPoint, Excel, PDF, OpenDocument, plain text). Supports Microsoft Entra ID app credentials for background sync and OAuth for user-based access. Configure under Settings > Integrations > SharePoint, then create a knowledge source of type SharePoint with site, library, and folder pickers.
• Smart Tables PDF upload — Add a row to a smart table by uploading a PDF. An LLM reads the document and fills in the table’s columns based on the schema and extraction prompt. Available from the rows view via “Add file”, and over the API at POST /api/v1/custom-data-sources/{slug}/upload.

​

Week of April 13, 2026

API & Integrations

• SDK page context — Attach structured context to every message so the agent knows what the user is viewing. Use client.setContext() or the React useAgoContext hook with static objects or dynamic provider functions.
• Simulation API — Full programmatic access to agent quality simulations via Public API v1 and MCP. Create datasets and test cases, start simulation runs, poll for results, and run quick single-question tests. 24 MCP tools available for AI agent workflows.
• AGO CLI — Manage knowledge documents, agents, conversations, tickets, and analytics from your terminal. Install with npm install -g @useago/cli, then run commands like ago agents list or ago documents create. Every command supports --json for piping into jq.

AI Studio

• Selectable by users toggle — A new switch on each agent’s General tab lets you keep an agent active for tools and routing while hiding it from the user-facing agent picker. The Agents list shows a “Selectable” column so you can see at a glance which agents end users can choose.

Messaging & Channels

• Default agent by name in widget — defaultAgent in the widget snippet now accepts an agent name (as shown in the admin interface) in addition to a UUID, making routing config easier to maintain. If the name doesn’t match an agent the user has access to, the user’s permission default is used instead.

​

Week of April 6, 2026

Admin

• Legacy API keys deprecated — Legacy API keys are now deprecated in favor of API v1 scoped keys. New key generation is disabled. Existing keys continue to work, but you should migrate to API v1 keys for scoped access and better security.

API & Integrations

• Organization and User API — Read-only access to organizations and users via Public API v1 and MCP, with a new accounts:read scope
• Conversation organization filtering — Filter conversations by organization name or ID, or exclude a specific organization
• Simplified SDK setup — Removed API key requirement and added automatic widget ID generation for easier integration
• SDK framework integrations — Added Vue.js and Angular integration guides, SSE helpers, zero-config mode, and pre-built functions

AI Studio

• Full system message in debug — View the complete system message sent to the AI in the conversation debug page
• API source data in debug — See which API data sources were queried and their responses in the conversation debug page

Ticketing

• Smarter ticketing instructions — Ticket permission instructions are now hidden when no ticketing system is active, reducing noise for non-ticketing agents

​

Week of March 30, 2026

AI Studio

• Suggested actions — AI generates clickable reply options to guide conversations, with keyboard shortcuts and multi-question support
• Simulation improvements — Tool call overrides, persona-specific simulation users, and agent routing validation for more realistic testing

Analytics

• Satisfaction feedback dashboard — Filter and analyze user satisfaction ratings with new dashboard visualizations
• MCP analytics — Track MCP tool server usage with call logging and a dedicated analytics dashboard tab

Admin

• Redesigned admin portal — Separated admin interface from the customer-facing portal with a dedicated design system

​

Week of March 23, 2026

AI Studio

• Multi-turn simulation tests — Create test cases with multiple conversation steps to validate back-and-forth agent workflows within a single thread
• Simulation personas — Define reusable personas with custom roles, behavior notes, and agent overrides to simulate different user profiles during testing
• Invisible router — Route conversations transparently between specialized agents without visible handoff to the user
• API data source mocking — Mock API data sources when testing agents with personas in Agent Lab

Knowledge

• XML-to-JSON knowledge sources — Import XML data as a knowledge source with configurable field exclusions
• YouTube private videos — Include private videos when importing YouTube playlists

Messaging & Channels

• Home page management — Customize the chat homepage layout with global and per-permission-group settings
• Widget selection per permission — Control which widgets are available for each permission group

Analytics

• Feedback status filters — Filter satisfaction feedback by status and admin tag

Admin

• Read-only viewer role — New viewer user type with limited read-only access to the admin interface
• Not-in-organization filter — Filter chat history and dashboard by users not linked to any organization

API & Integrations

• SDK developer tools — AgoProvider component, defineFunction helper, and testing utilities for the JavaScript SDK
• SDK navigation and logo — Navigate programmatically and display a custom logo via the JavaScript SDK

​

Week of March 16, 2026

Messaging & Channels

• Conversation starters — Configure pre-defined conversation openers that users can click to start chatting instantly

Analytics

• Smiley satisfaction feedback — New 3-smiley response type for quicker user satisfaction ratings
• Message timestamps — Timestamps now visible in the admin conversation view

Knowledge

• Image auto-compression — Large images are automatically compressed before AI extraction for better processing

​

Week of March 9, 2026

Knowledge

• Diataxis documentation templates — Quickly create document types aligned with the Diataxis framework (Tutorial, How-to Guide, Reference, Explanation) using pre-configured quality rules
• Auto-classify documents by doc type — Automatically classify all documents in a knowledge source into doc types using AI, with a coverage report showing distribution and gaps
• YouTube playlist connector — Import content from YouTube playlists as a knowledge source
• .docm file support — Upload and extract content from macro-enabled Word documents
• Regenerate translations — Regenerate individual document translations on demand from the translations page

Analytics

• CX score export — CX score details are now included in conversation exports
• CX score filter — Filter conversations by overall CX score in the dashboard
• Topic tree view — Topics now display in a hierarchical tree with parent-child tooltips

Admin

• Incident info banner — Display configurable alerts to all users directly in the chat interface
• Translations page redesign — Redesigned translations admin page with table layout and builder page
• Multiple JWT JWKS URLs — Configure multiple JWT JWKS endpoints in the widget SDK settings

​

Week of March 2, 2026

API & Integrations

• JWT Query Parameters for API Data Sources — Map JWT claim values to URL query parameters for user-specific API calls

Analytics

• Topic Analyzer — Renamed from Thread Tagger with a redesigned settings page featuring custom instructions and configurable settings
• Topic hierarchy — Topics now support parent-child relationships for hierarchical organization
• Conversations list update — Tags are now Topics, Admin Tags are now Tags, with updated filters and table columns

​

Week of February 24, 2026

API & Integrations

• File upload for knowledge sources — Upload files (PDF, Word, PowerPoint, Excel, images, and more) to knowledge sources via the REST API or MCP, with automatic extraction to markdown

Knowledge

• Back navigation on source detail — Navigate back to the sources list or quality overview from the source detail page
• Persistent quality overview filters — Filter selections on the quality overview page are now preserved across navigation
• Knowledge sidebar on document types — The knowledge sidebar is now visible on document type pages for consistent navigation
• Redesigned document type form — Tabbed layout with General, Built-in Rules, and Custom Rules sections for a cleaner editing experience

Messaging & Channels

• Welcome video modal — Configure a welcome video that auto-plays for new users on their first visit, with a rewatch link on the homepage
• Pre-chat qualification form — Configure a question with answer options in the widget to qualify users before they start chatting, each option assigning a permission that controls which agents the user can access

​

Week of February 17, 2026

Ticketing

• AI pre-fill for custom fields — Enable per-field AI pre-fill on ticket forms so the AI extracts custom field values from conversations automatically

​

Week of February 10, 2026

Ticketing

• Embedded external forms — Embed HubSpot, Typeform, or any web form directly in the chat instead of using the built-in ticket form
• Embed form auto-fill — AI-extracted conversation data now automatically fills fields in embedded external forms
• Embed form data capture — Submitted form data is captured and stored in tickets, including subject, body, and all field values

​

Week of February 3, 2026

API & Integrations

• MCP endpoint — Added to Public API for tool server integration
• SDK API v1 — Launched for programmatic widget and messaging control
• Zendesk ticket sync — Sync tickets with periodic polling and manual trigger

AI Studio

• Ticket context injection — Agents now receive ticket context for more relevant responses
• Review flagging — Flag conversations for review based on custom instructions
• Minimum validation score thresholds — Set minimum scores for the thread evaluator

Analytics

• User profile analytics — View date-based message charts and agent distribution per user
• Tag filter — Filter tickets by tag on the admin tickets page
• Mermaid diagram rendering — Conversation exports now render Mermaid diagrams

​

Week of January 27, 2026

AI Studio

• User memory — Agents remember context from previous customer interactions for personalized support

Knowledge

• HubSpot Knowledge Base connector — Import content from HubSpot Knowledge Base
• ReadMe connector — Import content from ReadMe documentation
• Source-type-specific forms — Easier knowledge source management with forms tailored to each source type

Ticketing

• HubSpot ticket integration — Sync and manage tickets with HubSpot

​

Week of January 20, 2026

Ticketing

• Configurable ticket success message — Customize the confirmation shown to users after ticket submission
• Ticket field configuration — Improved field management with custom select field support

AI Studio

• Version history for prompt templates — Track and compare changes to your prompts over time

Analytics

• Satisfaction feedback — Collect user satisfaction ratings via an in-chat widget
• User list improvements — Now shows last login and account creation date

​

Week of January 13, 2026

AI Studio

• Pinned documents — Pin key documents to agents for priority reference

Knowledge

• Qualios improvements — External link support and group filtering for Qualios connector

​

Week of January 6, 2026

Knowledge

• LLM-powered document extraction — Improved file processing using AI for better accuracy
• Qualios connector — Import content from Qualios knowledge bases

AI Studio

• Prompt template admin interface — Manage and organize prompt templates from the admin panel

Messaging & Channels

• Facebook Messenger integration — Connect with Facebook Messenger using OAuth authentication

Ticketing

• Custom enum field filters — Filter and chart tickets by custom enum fields

​

Week of December 22, 2025

Knowledge

• Dedicated document extraction service — Faster and more reliable file processing

Messaging & Channels

• Multi-widget permissions — Configure different access rules per widget

​

Week of December 15, 2025

Admin

• Agent display name — Customize how your agents appear to users

Messaging & Channels

• Shared discussion links — Share conversation links with team members

​

Week of December 8, 2025

AI Studio

• AI Studio UI refresh — Improved layout and navigation

Knowledge

• Document quality portal — Version diff comparison and change proposals for knowledge documents