Changelog

The Brainbase naming rollout covers sign-in, browser metadata, MFA completion, and auth emails, keeping the auth path aligned with the rest of the product.

Execution-tool results carry compact failure context for edge cases like non-zero exits and Python tracebacks, helping agents recover from broken commands without confusing read-only logs or file contents for failures.

New accounts landing on the developer app now go through a short multi-step welcome wizard, and the Help → Tutorials experience matches it with the same full-page, decluttered Web and Code walkthroughs.

Each agent's persistent file system now has its own Filesystem tab in the developer sidebar — next to Memory and Browser — with a polished native file browser instead of an inline section on the overview page.

Permission-only pauses in chat are more direct: the approval card appears without an extra free-text step, while multi-question need-more-info flows still behave the same way.

Enterprise customers can now view their invoices, add a card on file, and see live payment status without leaving Brainbase.

API keys can now be given a human-readable name when created and renamed inline later, so it's easier to tell production, staging, and per-developer keys apart.

The Files tab on the agent chat now loads the same way it does in the developer task view, so chats with cloud-runtime tasks no longer sit on a loading state forever.

New accounts landing on the developer app now see a guided UI-or-CLI onboarding chooser, and every developer page has a persistent help button linking to docs, an in-app tutorial wizard, and contact.

The developer Tools page and per-run task detail now show live health for each MCP server, with separate states for connected, not yet checked, and "couldn't verify this run" so an unverified or unhealthy server is no longer painted as healthy.

Several long-asked polish items now ship on the agent chat: per-day date headers, a thinking indicator during sandbox spin-up, a bookmarks panel, owner attribution for teammates, and a queued send-while-busy flow so mid-turn sends no longer drop or show the wrong banner.

Orchestration connections can now expose multiple dispatch tools to the source agent and run in both directions, with the two directions drawn as parallel lanes on the canvas.

The bash script that prepares an agent's sandbox before the harness boots is now editable from a new Entrypoint tab in the developer sidebar, alongside Secrets and Instructions.

The tasks list and overview on an agent's developer page now show all of that agent's threads instead of a small slice, even when the agent's team is busy.

Prompt caching now survives multi-minute idle gaps in human-interactive threads, and team-connected agents stop paying a full prefix rewrite on every new turn.

Scraped tool or web content that contained an embedded null character no longer aborts the surrounding agent run with a database write error.

Installing a marketplace skill from the UI no longer surfaces twice in the CLI manifest, so `agent pull` and `agent push` work cleanly without an unusable placeholder entry.

`brainbase agent push` now writes playbook components alongside instructions, skills, and MCPs, so playbooks can live in source control and reconcile to your cloud agent in a single push.

Agents whose workspace has an active meeting integration now automatically get the built-in Meeting MCP installed, matching how Slack-connected agents already work.

Tools that need explicit user approval now consistently surface an approval prompt with the correct capability attached, instead of relying on the model to recover from the error mid-turn.

Organization-level settings tabs now appear in the settings dialog from any page that shows the agents sidebar, not just the team home, so admins can adjust team settings without backing out first.

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.