What's new in Kafka.

Pressing Stop in a workflow-driven thread now cancels the workflow itself, so the run cannot resume later and finish in the background.

When an agent references a registry skill without pinning a version, each Brainbase CLI push now resolves to the latest published version.

The bot name and avatar saved in Meeting Setup now carry through to the meeting attendee, so participants see the identity you configured.

Slack threads no longer receive a redundant completion summary after a workflow finishes. The agent's own posted result remains the final message.

Starting the same workflow again from Slack or the dashboard now creates a fresh run, even when the inputs match a recent run.

Workflow agent steps now recover from transient timeouts and stay focused on the current step before handing control back to the workflow.

Unreadable or truncated images now produce a clear error after one retry, instead of failing the entire agent run.

Slack workflow commands can now collect inputs directly in the thread with a Run button, alongside the existing modal flow.

Gmail, Linear, and other app triggers now collapse duplicate deliveries into one workflow run, so one source event does not create multiple threads.

App triggers that rely on polling now check for new events about every 15 seconds instead of every 15 minutes.

Threads started from Slack now use the workflow's naming convention instead of staying named after the slash command.

Slack-triggered workflows now finish with the workflow's final output instead of re-posting an earlier acknowledgement.

Persistent memory can now be enabled or disabled per agent from the sidebar, with a confirmation step before memory is turned off.

Configure HTTP and HTTPS proxies for an agent's browser sessions, including regional egress, authenticated networks, and staging environments.

The orchestration view remembers your camera angle, and agent pages opened from an orchestration keep a breadcrumb back to that orchestration.

The Brainbase CLI can now show orchestration triggers, including app triggers such as Linear issue updates.

Slack and Teams messages can now start Claude Code and Codex agents as background coding tasks that post results back to the thread.

Integration setup forms now hide internal fields, so triggers and actions only ask for the information your workflow actually needs.

When you start a workflow from Slack, the confirmation message now includes the inputs you submitted so you can verify the run without leaving Slack.

Skills you publish with the Brainbase CLI can now be attached to agents and appear in the UI, so published custom skills are ready to use.

Orchestrations created in the UI now pull and push cleanly through the Brainbase CLI, including members that did not start from a local checkout.

Turn on recovery mode to block risky follow-up actions after a tool fails, while keeping read-only inspection available so the agent can understand what happened first.

SVG and other unusual image attachments now convert or fall back gracefully instead of breaking the message.

Workflows started from Slack or the web app now resume correctly after a reviewer approves a paused step.

Create custom modes with your own names and transitions, backed by stricter validation and clearer instructions for the model.

Team admins and owners can transfer an agent to another team member directly from the agent side panel.

Teams can launch Kafka workflows directly from Slack with custom slash commands and reliable one-response delivery.

Enterprise teams can connect their own SAML identity provider, auto-provision users on first sign-in, and merge matching existing accounts.

Kafka workflows now wait for missing input instead of failing, then resume when the needed details arrive.

Version history now shows who made each meaningful edit across agents, playbooks, and workflows.

Enterprise admins and owners can review contract terms directly in Billing without asking Brainbase staff.

Kafka now recovers from desynced external trigger deployments and gives clearer errors when publishing cannot proceed.

The model picker remembers the chat model you chose for each thread, so opening it later picks up where you left off instead of resetting to the agent default.

A Google-Docs-style preview for past Kafka workflow versions: click a version in history, view it on the canvas hermetically, then Restore or Exit.