Skip to main content

​
July 2026

1

Jul — API: structured card data (json_data)

API breakingAgent reply cards now carry the entity in two self-contained representations: rendered_jsx (unchanged — a ready-to-render JSX string for React UIs) and the new json_data — the same card as structured JSON, so you can build your own card UI in any framework (Vue, Angular, mobile).json_data.entity is a flat key–value map of the card’s fields, and json_data.sub_entities holds nested groups such as product variants.The card’s previous name, category, and parameters fields were removed — everything you need to render is in json_data.See Cards.
2

Jul — API: agent version on thread lists

APIGET /management/v1/threads items now include version_tag — the agent version the conversation ran on. Use it to tell which release of your agent handled each thread when filtering or auditing conversations.See Management → Threads.
3

Jul — API: new base URL

API breakingThe API base URL changed from https://api-v3.aui.io/apollo-api-v2 to https://api-v3.aui.io/apollo-api. All paths under it are unchanged (e.g. POST /messaging/v1/messages, POST /management/v1/auth/token).The old base URL keeps working for a few more days to give you time to migrate, and will then be removed — switch to the new one now.
4

Jul — API: agent_id removed from messaging request bodies

API breakingYour agent is now identified by your access token: when you exchange a publishable key at POST /management/v1/auth/token, the resulting token already carries the agent. Sending agent_id in the body of POST /messaging/v1/messages, POST /messaging/v1/messages/stream, or POST /messaging/v1/threads/{threadId}/rerun is no longer accepted and returns a validation error (422).Migration: remove agent_id from your messaging request bodies — responses keep the same shape. See Send messages.
5

Jul — API: channel thread initiation (WhatsApp / SMS)

API breakingThe POST /messaging/v1/channels/{channel}/threads request body changed:
  • agent_id was removed — the agent now comes from your access token.
  • user_ref_id was renamed to user_id.
  • template_id and content_variables (WhatsApp template overrides) were removed — the agent’s configured template is always used; agent_display_name remains available.
See Channels.
6

Jul — SDK v3: new clients for the Apollo API

SDK breaking · v3.2@aui.io/aui-client v3 is a full rewrite against the Apollo API. The single ApolloClient is replaced by two clients, one per credential:
  • ApolloMessagingClient — publishable key, browser-safe. Token exchange and refresh are handled internally; the agent comes from the key, not request bodies. Messaging, channels, and WebSocket sessions.
  • ApolloManagementClient — organization API key, server-side only. Projects, agents, versions, threads, and usage.
Tasks are now threads: createTask is gone (threads auto-create on the first sendMessage), task_id became thread_id, and the client defaults to the production API with no environment configuration. See the migration guide.
7

Jul — API: threads, agent variables, welcome message & follow-up suggestions

API new
  • Update a thread — PATCH /management/v1/threads/{threadId} renames a thread (title); the full updated thread is returned.
  • Agent variables — POST /messaging/v1/messages and POST /messaging/v1/messages/stream accept an optional agent_variables object (static and dynamic) with per-message values for the agent’s configured context variables.
  • Welcome message — GET /messaging/v1/welcome-message returns your agent’s configured greeting, for opening a conversation UI before the first message.
  • Follow-up suggestions — POST /messaging/v1/followup-suggestions generates suggested next prompts from a context you provide.
8

CLI v0.4 — Runtime testing, versions, integrations & more

CLI beta · v0.4.45
  • Runtime messaging — talk to your agent against the live Apollo-1 runtime with aui apollo (create-thread, send-message, rerun, trace). Local .aui.json edits are forwarded automatically, and every reply includes the symbolic trace.
  • Version management — full lifecycle with aui version (draft → publish → activate → archive) plus point-in-time comparison via aui version snapshot diff.
  • Integrations — create and test manual MCP and native Composio integrations with aui integration (discover, tools, toolkits, mcp-url, create, test, mcp-test).
  • Mock DB — spin up a per-agent test database with aui mockdb (collections, seed data, endpoints, sessions, key rotation).
  • Evaluation scenarios — generate, push, and score scenarios with aui scenarios to turn a faithful agent into a reliable one.
  • Secrets — store and rotate integration credentials with aui vault.
  • Coding-agent first — nearly every command is non-interactive with a --json mode; imports scaffold skills for Cursor, Claude Code, and opencode; aui report surfaces issues and learnings.
  • Quality-of-life — aui agent --create provisions an agent end-to-end and imports it locally; aui sync-session keeps your session scoped to the project; aui serve launches a local web playground; aui curl, aui upgrade, and aui revert round out the toolset. New eu-production environment.

​
March 2026

1

Mar 9 — CLI Beta Release

CLI beta
  • Public beta of aui-agent-builder CLI (v0.1.77)
  • Local-first development workflow: import, edit, validate, and push agent configurations
  • Interactive chat and web playground via aui chat and aui serve
  • Smart push with git-based diffing
2

Mar 9 — Agent Builder API Alpha

Agent Builder API alpha · Closed to the public
  • Alpha release of the Agent Builder API — available to select partners only
  • Identity, organizations, accounts, and networks (agents) endpoints
  • Agent settings read/write: tools, parameters, entities, integrations, rules
  • Knowledge base management with file upload and website scraping
  • API Workflow integration generator