Changelog

Data source setup is smoother across the board

Connecting data feels a little friendlier this week. ClickHouse now uses the modern clickhouse:// URI scheme for connection strings, with older jdbc:clickhouse:// URIs still supported so existing connections keep working without changes.

The BigQuery connection form also includes inline guidance on where to create and download a service account JSON key in Google Cloud Console, so getting your credentials in the right place is less of a scavenger hunt.

A clearer experience when a trial ends

If your organization’s trial has ended, the product no longer locks you out of places where you actually need to take action. You can still reach Profile and Billing settings, which makes upgrading, updating payment info, or managing your account straightforward instead of frustrating.

The navigation also adapts to the trial-over state. A dedicated “Trial over” item in the sidebar links directly back to the upgrade page, so the next step is always one click away even when the main nav is hidden.

Fixes and improvements

• Added a Move to folder submenu in the dashboard header’s overflow menu, right below Duplicate, so you can reorganize dashboards without opening the sidebar.

Dashboards are much easier to create with AI

The Dashboards page now gives AI dashboard creation a much more prominent starting point. Instead of feeling like a secondary workflow, you can now begin from a dedicated input right on the page, describe the dashboard you want, and jump straight into editing the new dashboard once it is created.

We also made that flow feel more guided instead of more mysterious. Empty dashboards now show a clear generating state while Basedash AI is building them, and the page includes curated dashboard templates you can use as a faster starting point when you want ideas instead of writing a prompt from scratch.

Insights are more reliable and less confusing

Insights should now show up more consistently in the background. We fixed a scheduling issue that could silently prevent many organizations from receiving their scheduled insights, and we also fixed retry behavior that could occasionally send duplicate Slack or email notifications for the same insight.

We cleaned up the Insights UI too. Header actions that only make sense on the main Insights page no longer appear on individual insight detail pages, which makes the detail view feel more focused and less cluttered.

Fixes and improvements

• Improved automation editing by giving the instructions field much more room.
• Improved automation detail pages so the active toggle and label stay aligned and easier to scan.
• Fixed dashboard creation flows so duplicate submissions are less likely while AI is still working.
• Improved chart stability when working with charts that have long version histories.

Chats are easier to share and collaborate on

Chats now use the same kind of grant-based sharing model as the rest of Basedash. That makes it much easier to control who can see or manage a chat, and it makes chat sharing feel more consistent with the way dashboards and other resources already work.

Admins can also set default access for new chats, and new organizations now start with chats shared to everyone with full access by default. For teams that use chat as a shared workspace instead of a private scratchpad, this should make collaboration feel much more natural from the start.

Insights are easier to generate on demand

You can now manually generate an insight from the Insights page whenever you want one, instead of waiting for the next scheduled run. That makes it easier to pull a fresh insight right after your data changes or when you want to actively explore a question.

We also increased the reasoning effort behind Insights. In practice, that should make Insights feel more thoughtful on harder questions and more useful when you want something that goes beyond a quick summary.

Connector setup feels smoother end-to-end

The connector setup flow got a broad UX cleanup. Forms are easier to read, descriptions render more cleanly, keyboard submission feels better, and loading states feel more polished instead of looking like unfinished placeholder UI.

We also fixed some rough edges after setup. New connectors now take you to the connector page directly, brand-new warehouses no longer look broken before their first sync, and SQL autocomplete handles names with special characters more cleanly.

Fixes and improvements

• Improved dashboard auto-refresh so large dashboards do less unnecessary work and stay more stable under frequent refreshes.
• Fixed mobile dashboards so charts render reliably on smaller screens.
• Fixed the chat composer getting stuck in “Generating…” after an AI response had already finished.
• Preserved chart version history when reopening charts from dashboards and made reverted AI versions show up correctly in the timeline.
• Added character counters and sensible limits across AI context fields so it is easier to tune context without guessing.
• Improved MCP connector OAuth setup so supported servers request better scopes and launch authorization more reliably.
• Enabled automations in embedded sidebars, with an option to hide them when they do not belong in the embed.
• Improved number chart sizing so large metric cards render more consistently.
• Improved the billing AI usage breakdown so system-generated usage is visible alongside user-attributed usage.

Organization and member settings are easier to manage

Organization and member settings now live in dedicated settings pages instead of being tucked into the command menu. That makes admin tasks easier to find, easier to revisit, and more in line with the rest of the product instead of feeling like secondary actions.

For teams that manage access often, this should feel like a meaningful cleanup. Settings have a clearer home, member administration is less buried, and common account-management workflows are easier to understand at a glance.

Large data sources are much easier to browse

The Data page is now dramatically more usable on very large connections. Instead of trying to load everything at once, schema and table browsing is much more incremental, which makes big databases feel far less likely to freeze or bog down the page.

Search and navigation are more intentional too. Browsing through lots of schemas should feel smoother, expanding sections is lighter-weight, and the command menu follows the same direction so exploring a large connection feels faster instead of overwhelming.

New dashboards can start with the right default access

Admins can now choose the default access pattern for newly created dashboards at the organization level. New dashboards can default to being available to everyone, only the creator, or the creator’s groups, with control over whether that shared access starts at manage, edit, or view.

This is especially useful for larger teams and embedded setups where “everyone can manage” is too open as a default. It gives teams a better starting point for governance without adding extra sharing cleanup every time a dashboard is created.

Automations can now be turned on and off cleanly

Automations now have a real active switch, so you can pause an automation without deleting it or rebuilding it later. When an automation is inactive, it stops scheduling runs, stops reacting to data-change triggers, and stops sending notifications.

That makes it much easier to temporarily pause an automation while you are testing, investigating, or waiting on upstream data. It also prevents half-disabled workflows where something looks paused in the UI but still keeps doing work in the background.

Fixes and improvements

• Simplified the charts page filters and included charts created from chat in the charts list.
• Improved time-series x-axis labels when SQL does not explicitly provide interval metadata.
• Fixed pie chart legend values so percentages and currency use the right formatting.
• Improved the SQL editor actions bar so it no longer obscures the bottom of the editor.
• Improved CSV exports for Excel on Windows so UTF-8 downloads open more cleanly.

Dashboards and insights feel much faster and more live

We reworked how dashboard charts and Insights load so the app does less unnecessary client-side work and updates more intentionally. Large dashboards should feel noticeably snappier, especially while editing, dragging charts around, or switching between tabs.

Insights benefit from the same shift. Loading is smoother, updates arrive more cleanly, and new content feels more immediate. We also tightened chart actions so duplicating or deleting a chart reflects right away instead of feeling delayed.

Number charts can compare two values

Number charts can now display a primary value alongside a comparison value. That makes them much more useful for common KPI patterns like current versus previous period, actual versus target, or value versus benchmark.

You can choose both fields directly in chart settings instead of working around the limitation in SQL or another chart type. The result is a simple KPI card that carries a lot more context at a glance.

Groups are now available through the public API

You can now list, create, update, and delete groups through the public API, and add organization members to them as well. This makes it easier to manage access-related workflows programmatically if you are syncing users and permissions from your own systems.

For teams building on top of Basedash, this closes an important gap in API coverage. Group management can now be automated instead of handled manually in the UI.

Fixes and improvements

• Added export support for chart drill-down tables.
• Improved embedded dashboards by fixing copy actions in embedded views and hiding copy-link actions that do not make sense there.
• Fixed SSO login issues that could block some SAML and embedded JWT flows.
• Fixed the demo data source onboarding flow so new connections load reliably right after creation.
• Fixed pie charts that could render cut off.
• Improved time-based x-axis labels so month and year boundaries read more naturally.
• Fixed connector logos so more data sources show the right icon.
• Fixed a crash on the new organization flow during full page loads.
• Improved the sidebar and dashboard context menu experience on large workspaces.
• Kept MCP-created chats out of the standard chats list so chat history stays cleaner.
• Fixed table picker row sizing so table selection feels less cramped.
• Fixed number charts so they still choose a sensible default value when one is not explicitly set.

Automations are much more capable

Automations now feel more like a first-class part of Basedash. The product language is now unified around automations, setup is cleaner, automations show up in command menu search, and you can give each one its own icon and color so important workflows are easier to spot at a glance.

We also added data-change triggers, so automations can run when a query result changes instead of only on a schedule. Sharing and permissions are more intentional now too, with clearer view and edit access for teammates, and automation pages refresh more smoothly while you are watching new runs come in.

AI can now follow your personal context

You can now add personal AI context from your profile, which gives Basedash guidance that is specific to how you work. This is a useful place to tell AI what metrics you care about most, how you want answers framed, or what business context matters for your role.

This personal context works alongside your team’s shared AI context instead of replacing it. That means AI can stay grounded in company-wide context while still adapting responses to each teammate across chat, chart creation, and other AI-assisted workflows.

Basedash feels noticeably faster

We cut a large amount of client-side weight out of the app and pushed more heavy code to load only when it is actually needed. That means less JavaScript up front, faster page readiness, and a lighter feel across common workflows.

The sidebar also renders much sooner now. Static navigation no longer waits on billing, sync, or live collaboration dependencies before appearing, so the app should feel more responsive instead of showing a blank sidebar while the page catches up.

Fixes and improvements

• Added a billing page that shows AI usage, included credits, and overages for the current billing period.
• Improved Slack AI conversations with clearer streamed progress updates.
• Improved chart drill-down reliability by validating drill-down SQL as charts are created and updated.
• Fixed automation trigger edits so saved data-change settings no longer get cleared unexpectedly.
• Fixed dashboard controls so values no longer carry across organizations.
• Fixed chart x-axes so small numeric values are less likely to be interpreted as dates.
• Simplified navigation by removing the standalone Charts sidebar item.

Members can now be deactivated and reactivated

Admins can now deactivate a member without permanently deleting their account history. This gives you a cleaner way to temporarily remove access when someone changes roles, goes on leave, or no longer needs the product day to day.

You can also reactivate that member later, which makes this much more practical than a delete-and-recreate flow. Existing ownership and linked data stay intact, so team administration is less disruptive when access changes over time.

Slack can now use approved tools

Slack conversations can now use MCP tools, which means Basedash can do more than just answer questions in Slack. When a tool needs approval, the approval flow happens right in Slack so you can keep moving without jumping back into the app.

We also extended tool access to background automations for tools that are explicitly allowed to run automatically. Taken together, this makes AI workflows feel more useful across both real-time Slack conversations and scheduled work.

Dashboards are easier to organize

Dashboards and folders are now easier to manage from the sidebar. You can quickly create folders from the dashboards page, reorder dashboards with a list-based drag-and-drop layout, and see cleaner folder nesting that makes larger workspaces easier to scan.

We also reduced some of the friction around navigation and sharing. Favorited dashboards still stay visible in the main dashboards list, and share buttons now show the current visibility state at a glance before you even open the menu.

Fixes and improvements

• Improved connection and table browsing with clearer breadcrumbs, easier settings access, and status dots for SQL databases and MCP servers.
• Improved chat and automation reliability so responses are less likely to stay stuck on “Generating…” when many automation runs are open.
• Fixed PDF exports for funnel charts and newer Tailwind color styles.
• Fixed DuckDB and S3 date handling so charts and AI see readable timestamps and dates.
• Fixed DuckDB PRAGMA table_info(...) and SHOW ALL TABLES queries when they include trailing semicolons.
• Fixed Data page record counts for DuckDB and S3 tables.
• Improved reliability for databases with strict connection limits by reducing default connection pool pressure.
• Fixed multi-select chart variable defaults so saved values behave more consistently.
• Added Redshift support for SSH connections.

Automations got a full refresh

Automations now have a cleaner, more structured home in Basedash. The redesigned experience adds a dedicated sidebar, a more useful header, and a command menu-driven setup flow that makes configuring automations feel more consistent with the rest of the product.

We also made automations easier to organize day to day. You can now favorite automations to keep the most important ones close at hand, and we fixed automation schedule editing so typing times feels natural instead of fiddly.

Chat is more reliable, more private, and better grounded

Ask mode is now better at understanding what you are looking at. When you open chat from a dashboard or a table, it can use that route context to stay grounded in the page you are already exploring instead of starting from a blank slate.

We also tightened up the rough edges that could make chat feel unreliable. This release reduces cases where chats stay stuck on “Generating…” after reconnects, prevents final answers from getting buried inside the steps accordion, and makes new chats private by default. Uploaded files and images are also handled more consistently, so exploratory workflows feel safer and smoother.

Browsing large data sources feels faster

Browsing schemas and tables is now much smoother on large data sources. The table picker is now virtualized, which keeps the UI responsive instead of rendering massive trees all at once as you explore bigger databases.

We also polished the browsing experience itself with cleaner hover states, easier copy actions, and improved dashboard and folder context menus. Altogether, moving around complex data sources should feel faster and less cluttered.

Fixes and improvements

• Fixed a line chart edge case that could make long category series loop backwards.
• Added a logout option during onboarding.
• Improved desktop app redirects.
• Prevented confusing dashboard filter edits from the chart editor when the filter belongs to a dashboard.
• Improved AI file uploads by normalizing file extension casing and fixing uploaded image rendering.