Changelog

The Billing page now shows your current billing period and credit refresh date, and the Usage page lets you filter usage stats to that same period.

New users can skip onboarding and finish it later, instead of being forced through it in one sitting to start using Brainbase.

Task and thread titles are now generated more consistently and no longer get overwritten or lost once a name has already been set.

Inviting someone who's already on your team no longer silently fails.

Fixed several issues that could cause an agent run to fail outright instead of completing.

Usage-based billing and plan entitlements for teams under an enterprise account are now attributed and applied consistently.

You can now start an agent task directly from the command line, without opening the dashboard.

Agents that respond in Slack now know exactly who sent each message, fixing cases where they could confuse a message with someone else's identity — including across different connected Slack workspaces.

We've unified how access to threads, stored files, and attachments is verified across the platform, so it consistently reflects your team's actual membership.

We've broadened automatic secret redaction to provide more thorough, consistent masking of credentials across logs and stored messages.

When a row write to an agent's memory table is rejected, the memory tab now explains why instead of showing a generic failure.

The memory table editor now shows which column references another table up front, instead of only after a write is rejected.

Canceling a running task now measures usage correctly, and task completion events are delivered in the right order so a run's final status is reported accurately.

Skills added from the skill registry now install correctly into an agent's sandbox and from the console, instead of silently failing to install.

We tightened how integration credentials and custom secrets are stored and transmitted, so their values are never sent to your browser once saved.

The task timeline no longer shows a browser session replay pane, or a misleading playback error, on tasks that never used the browser.

Tasks created through the MCP integration now run automatically by default, matching how tasks behave when created from the app, instead of sitting idle waiting on a start that never happens.

A task whose final step is cut off mid-call is no longer reported as having completed successfully.

Skills now install under the name declared in their own instructions, so agents can reliably find and use a skill by the name they were told to use.

Fetching an agent, or your full list of agents, no longer fails when one of an agent's skills comes from a GitHub source.

Agents now reliably boot with every skill they declare, fixing a case where a skill install could be removed and never replaced.

New agent onboarding no longer gets stuck bouncing between the creation form and the setup guide when you navigate back or reload mid-setup.

Session recording playback now recovers automatically from a bad video segment instead of freezing, so you don't have to refresh the page to keep watching.

Long task transcripts no longer get stuck on an infinite loading spinner after the task has actually finished successfully.

When a task run or model request fails outright, you now get a clear, specific error explaining what went wrong instead of an unexplained failure.

Agents that use Slack can now reliably open direct messages and read thread replies, fixing two failures that previously blocked those actions.

Creating a task or thread through the API is now safe to retry — resending the same request after a network hiccup reuses the original result instead of creating a duplicate.

You can now download a recording of what your browser agent did during a task, even after its sandbox is gone, so you can review exactly what happened.

Workflow steps that pause for your approval or additional input now reliably stay paused when an automatic retry occurs, instead of occasionally completing on their own.

Workflow runs that post to Slack no longer include an extra internal status line alongside the real completion message.

Closes a remaining timing gap where a finished task could still show as Running and block you from adding a follow-up.

Connecting Brainbase to ChatGPT no longer fails because of inconsistent client ID matching, and retrying a connection attempt is now handled safely.

Browser screenshots in an agent's task history render as images again instead of falling back to raw JSON or a broken-image icon.

Orchestrations can now give every member agent one shared memory database, edited from a new Memory tab, instead of keeping each agent's memory separate.

Deleting an agent no longer fails with a server error if it has ever received a connector message or had a dedicated data backend provisioned.

Replying to an agent's follow-up question now always resumes the conversation, instead of occasionally leaving the thread stuck showing it still needs info.

The evals panel in a transcript's turn detail view now scrolls properly instead of clipping results once several evals are open.

You can now @mention a playbook and attach files when creating a task or sending a follow-up, so the agent has the right instructions and materials from the very first message.

You can now remove individual files from an agent's shared folder right in the file directory, instead of asking the agent to delete them for you.

The usage page now clearly separates the credits you've spent in the selected time window from your cumulative plan total, so the two numbers no longer look inconsistent at a glance.

Enterprise plans once again apply across every organization owned by the same account, so affected workspaces regain their full plan and the ability to invite members.

Files you attach when kicking off a coding task from Slack are now brought into the task workspace, so the agent can work with them from the start.

While an agent's computer is starting up, the task view now shows a startup notice before the first activity appears, instead of a generic spinner, so it's clear that setup is in progress.

Long-running and multi-step agent runs now report a finished status only when the whole run is genuinely done, so a task no longer appears completed while it is still working.

Teammates and members of groups an agent is shared with can now view that agent's evaluations and results, instead of seeing an empty evals view.

Connecting GitHub now returns you to Brainbase to finish setup, and reconnecting a previously removed GitHub app restores the integration automatically instead of leaving it stuck.

Starting a run or calling the API with a model that isn't available on Brainbase now returns an explicit "model not available" error, instead of a misleading authentication failure or an opaque run crash.

Editing rows in an agent's memory tables now always updates the row you selected, even when several rows share the same key value.

Recurring schedules set from inside a Claude Code agent now fire reliably in Brainbase cloud sandboxes, so time-based automations actually run instead of being silently accepted and never triggered.

Screenshots and image results from browser and task runs now render as inline thumbnails you can open full-size, and previews that had expired now refresh on their own instead of breaking.

The agent memory viewer now loads table data in a single round trip and lands with aligned headers and row actions, so browsing an agent's memory is quicker and easier to scan.

You can now pick the sandbox provider for any cloud agent when you create it or change it later, with E2B available as an option for every coding runtime.

Any member of an agent's team can now change its model and other preferences — previously only the agent's original creator could, and everyone else hit a permissions error.

GPT-5 and o-series models now run correctly on the OpenCode and Qwen coding runtimes, fixing an error that caused every turn to fail on its first model call.

The hosted browser tool now detects and clears CAPTCHA and anti-bot challenges on its own, so browser agents keep moving through sites that used to stop them cold.

Agents connected to Slack now read a thread's history once and then follow only new replies, so long Slack conversations no longer balloon context or cause runs to fail — and duplicate replays are gone.

Agents you create through the API now land in a group in your workspace automatically, so they show up in your dashboard alongside the rest of your agents instead of being created out of sight.

Workflow agents now send their answer as a normal chat message before ending a turn, so replies show up in the conversation instead of turns looking empty.

The Brainbase CLI now keeps your login fresh across sessions, signs in through the correct Brainbase app domain, and shows the control-plane endpoint you're connected to in login and whoami.

You can now rename an agent inline from its overview page, with instant validation and no full-page reload.

Slack macro runs now map to a single task across every reply path, and the completion message links directly to that task so you can jump from Slack into the full run in one click.

When an agent stops to ask a question — or a run cuts short before it can finish — the thread and task views surface the question and the reason clearly, with an Answer action right where you're watching the run.

Time spent by managed sandbox tasks now shows up in your credit usage as its own line, with only active minutes counted and team attribution preserved from the run onward.

Tasks can be renamed inline from the task detail panel, and the new title updates in place across the task list without waiting for a refetch.

The free signup credit claim is now reachable from the onboarding wizard and a compact banner in the sidebar, in addition to the Billing page, and disappears everywhere the moment credits are activated.

Running a macro on a workflow that also has webhook or schedule triggers now consistently starts from the macro trigger you chose, and macro invocations fail closed with a clear error if no macro trigger is configured.

Editing and testing app triggers is more forgiving: toggle saves no longer wait on slow provider option refreshes, and the Test trigger button gives clear, durable feedback instead of false failures or duplicate submits.

The Meeting MCP now accepts Brainbase personal access tokens and live API keys with an explicit profile selection, alongside the existing OAuth flow.

Claude Sonnet 5 is now a featured model, with reasoning effort levels through xhigh, a 1M-token context window, and up to 128k output tokens.

Macros can now be invoked with a slash command from v2 Chat and the developer Task view, macro-triggered workflows publish cleanly, and Slack macro results are always posted back to the originating thread.

When you draw a new connection between two agents, sending a message and continuing an existing task now works out of the box: Send a message is the first tool listed, and messaging tools are enabled by default for new connections.

When an upstream model provider returns a rate-limit or transient error to Brainbase's streaming path, the fallback retry now backs off with jitter and honors Retry-After headers instead of failing the run on the first stumble.

Three new GPT-5.6 variants — Sol, Terra, and Luna — are now selectable across agents, flows, and chat surfaces. Sol becomes the default model for new agents and flows.

Workflows can be renamed directly from the editor breadcrumb or the /dev topbar with a visible pencil affordance. Renames now persist reliably — including for personal workflows without a team — instead of appearing to save and then reverting.

Cursor, Factory, and Qoder agents now have a purpose-built key-entry flow: enter your vendor API key when you pick one of these harnesses, and Brainbase will prompt you to add or fix the key before a run fails — instead of leaving a mismatched agent to wedge silently.

The developer Task view now has a Browser tab that shows the same per-task browser session already available on live threads, with a view-only default and an explicit Take control mode when you need to interact.

Successful auto-reload top-ups now record the Stripe receipt link so the Billing activity row shows a View receipt button — the same way manual top-ups already do.

Enabling an auto-reload rule immediately checks your prepaid balance and tops up if you're already low, and a background scan catches wallets that dip below their threshold between charges — so top-ups no longer wait for a manual nudge.

New Brainbase accounts activate their free signup credits by verifying a mobile number on the Billing page. Paid top-ups, saved payment methods, and existing balances are unchanged — only the free grant is gated.

Meeting Assistant calls are free through August 15. After the promo, meeting time will bill at 1 credit per started minute — an update from the 10 credits per minute rate announced earlier this week. The promo callout is now visible on the Meetings connector before you enable it.

Save a payment method, set a low-balance threshold and a reload amount, and Brainbase will top your prepaid credit wallet up in the background — so agents, workflows, and playbooks keep running without a manual refill.

The old referral promo, invite dialog, and email-based invite flow have been removed. Existing accounts are unaffected — only the legacy invite entry points and their credit granting have been turned off.

Thread links across search, task lists, kanban, and sidebars now pick the right chat surface based on the thread's runtime — managed cloud and ACP threads open in the agent chat view, while legacy threads keep their existing chat view.

Setting up the Slack integration is now a step-by-step walkthrough: name the app, create it, install it into your workspace, then save credentials — with an inline video demo and a note for workspaces that require admin approval.

When you click a run of a managed workflow, it now opens in the agent's task chat surface — where every node's messages, files, and follow-ups live in one thread — instead of a separate legacy view. Older workflow runs still open in their original view.

Time spent in a Meeting Assistant call is now metered against your credit balance at 10 credits per started minute, so meeting usage shows up alongside your other agent activity in Billing.

The three-dot actions menu on sidebar threads — including the Delete thread option — is now reachable for every thread, including those near the bottom of a long sidebar list where the menu used to be clipped.

Recurring auto-joined meetings now book exactly one Meeting Assistant bot, so calendars that were edited with "this and following events" no longer end up with two bots joining the same standup.

Organization administrators can pull orchestration manifests through the Brainbase CLI even for groups they are not a direct member of, matching the access rules the rest of the platform already applies.

When you run out of prepaid credits, the Upgrade plan action in the credits, workflows, and playbooks limit dialogs now opens the in-app Billing page — where you can buy credits, top up, or upgrade — instead of the external payment portal.

Switching browser tabs and coming back no longer discards unsaved edits in the agent Instructions editor. Your typed-but-not-yet-saved changes stay exactly as you left them.

Trigger configuration dropdowns that return plain-text option lists — such as the Repository selector when setting up a GitHub trigger — now populate correctly across every trigger and action configuration surface.

Qwen, OpenCode, Cursor, Factory, and Qoder agents now display their official brand icons throughout Brainbase, making it easier to tell your agents apart at a glance in agent lists, thread panels, and side panels.

Wallet credit top-ups unblock new runs immediately, Team plan upgrades stay active under duplicate payment confirmations, and team credit tracking picks a consistent billing owner across debits and enforcement.

Choose how each connected integration behaves when an agent wants to use it — allow silently, ask for approval, or deny outright — per integration and per action, so agents only pause on the tools that matter.

The model picker in the new Brainbase chat now saves your choice on the conversation and applies it on the next turn, so mid-conversation model switches actually take effect instead of being cosmetic.

Three additional frontier models — GLM 5.2, DeepSeek V4 Pro, and Kimi K2.7 Code — are now selectable in every Brainbase model picker.

Enterprise teams can now designate a dedicated billing contact so invoices, receipts, and card-expiry notices go straight to the right accounts-payable inbox instead of the earliest team owner.

When an agent joins a meeting and the meeting provider returns a transient rate-limit or capacity response, Brainbase now retries automatically with backoff, so bursts of meeting traffic no longer cause join failures.

Credit usage now captures Codex Cloud and Claude Code Cloud agent activity at the same fidelity as Brainbase cloud agents, and LLM consumption inside sub-threads rolls up into the parent thread reliably.

Streamed agent responses recover from upstream failures more gracefully, with automatic retries on early or mid-tool-call failures, clearer error events when something does go wrong, and partial output preserved so future turns stay coherent.

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.