Changelog

Subscribe to any dashboard or chart

You can now subscribe to a dashboard or chart and have it delivered on a schedule—straight to your inbox or a Slack channel. Set the cadence with a plain-language schedule, choose who receives it (teammates, yourself, or Slack), and Basedash sends a fresh, up-to-date screenshot every time it runs.

Subscriptions live right in the dashboard and chart menus, so keeping stakeholders in the loop no longer means remembering to export and share things manually. You can set up multiple subscriptions with different schedules and audiences, and edits save inline as you make them.

One unified AI on every dashboard

Dashboards no longer have separate Ask and Edit modes. The dashboard assistant is always available, and you steer it by clicking a chart to attach it as context—then ask a question or request a change, and press Esc (or the badge ✕) to deselect. The input even tells you which chart is selected, so it’s always clear what you’re asking about.

View-only teammates can now select a chart and ask about it too, while any changes stay gated to people with edit access. We also polished direct manipulation: you can resize cards from all four corners, handles only appear where you can actually grab them, and the card you’re resizing stays cleanly on top with no distracting drop shadow.

SCIM provisioning for enterprise teams

Basedash now supports SCIM 2.0, so enterprise teams can connect an identity provider like Okta or Microsoft Entra ID and automatically provision, update, and deactivate members—and keep groups in sync—without managing access by hand. Admins generate a SCIM token from Settings → Security, drop the base URL into their IdP, and membership follows whatever their directory says.

Deactivating someone in your IdP removes their access in Basedash automatically, and users provisioned this way sign in through SSO. Token creation is available on paid plans, matching how SSO works today.

A more personal way to start a chat

The new-chat screen now greets you with starter prompts tailored to your organization and your connected data, so there’s always a useful next step in front of you instead of a blank box. When you haven’t connected Slack or a data source yet, you’ll see quick actions to do that right from the home screen.

We’ve extended the same idea to your dashboard and automation pages, which now show personalized, AI-generated suggestion cards to help you spin up something new. Anything you’re not interested in can be dismissed on hover.

Fixes and improvements

• Added an MCP server settings page so you can grab your Basedash MCP server URL and connect Basedash to AI tools like ChatGPT, Claude, and Cursor—and made the URL easy to select and copy manually.
• Added Claude Sonnet 5 and Claude Fable 5 to the model picker.
• Rotated crowded x-axis labels on vertical bar charts so they stay readable instead of overlapping, with extra room reserved so nothing gets clipped.
• Refreshed chat attachment previews with rounded image thumbnails, richer file cards, consistent sizing, and a hover-to-remove control on every attachment.
• Smoothed out the AI chat input and panel with rounded corners and a cleaner shadow.
• Fixed deleted chats briefly reappearing after you removed them, and moved delete confirmation to only show once the server accepts it.
• Stopped the AI from trying to query data sources that are offline, with clearer messages naming the unavailable source.
• Kept embedded dashboards working after a customer’s signing token expires, so charts and exports no longer break mid-session.

Edit charts directly in chat

You can now refine a chart without starting over. When you ask the assistant to tweak a chart it already made in the current conversation, it edits that chart in place instead of spinning up a brand-new replacement—so iterating on a visualization feels like a real back-and-forth rather than a growing pile of near-duplicates.

Chat also keeps each chart pinned to the exact version it referenced, so scrolling back through a conversation always shows the chart as it looked at that moment. Adding an older chart to a dashboard or copying it brings over that original version, not whatever the latest edit happened to be.

A cleaner, more capable AI chat

The chat experience got a visual refresh. Your own messages now sit in a rounded bubble aligned to the right with no avatar, while messages from teammates (and from Slack) show their name and avatar on the left—so multi-person conversations are much easier to follow at a glance.

The assistant’s thinking is tidier too. While it works, you see live tool activity; once it’s done, the steps collapse into a simple “Thought for…” summary you can expand on hover. We also unified the scroll-to-bottom button across every chat surface and fixed completed web searches so they show their sources instead of a stuck loading spinner.

Smarter analysis across your databases

Basedash’s AI analyst is now more rigorous about the kinds of questions that trip up most tools. It’s more careful with ambiguous metrics, distinguishes named rates from their supporting deltas, notices when a data source is stale versus fresh, and double-checks compound, multi-part answers before responding—so you get answers you can trust, with the caveats that matter.

We also taught it production-tested SQL gotchas for the databases you actually use—Postgres, Supabase, Redshift, Snowflake, SQL Server, MySQL, PlanetScale, BigQuery, and more—so the queries it writes run cleanly the first time, with fewer dialect-specific errors.

Set a spending limit on AI usage

Organization admins can now set an optional cap on AI overage spend right from billing settings. Once you reach your included credits plus the limit you’ve set, AI usage pauses instead of running up an unbounded bill—and admins get a heads-up email so there are no surprises.

Leave it unset for no limit, or adjust it anytime. Either way, you stay in control of exactly how much you’re willing to spend on AI in a given period.

Fixes and improvements

• Made AI-run write queries generally available—admins can enable them per data source, and every change still requires explicit approval before it runs.
• Gave organization admins full access to every dashboard, dashboard folder, chat, and automation, regardless of individual sharing settings.
• Preserved your exact SQL output column names in table charts—use SELECT aliases like AS "Customer Name" for readable headers.
• Fixed dashboard charts that could get stuck showing stale data after a missed refresh, and moved the “Updating data from…” note into the chart header spinner.
• Moved the dashboard tab auto-advance control into the tab bar and renamed it “Auto-advance through tabs.”
• Returned chart screenshots and resource links for charts referenced through the Basedash MCP server.
• Kept MCP connections signed in longer with smoother token refresh, so you re-authenticate less often.
• Stopped scheduled reports and automations from quietly modifying your saved AI context.
• Made chart images in Slack and email reports more reliable with automatic retries on transient rendering failures.

More control over how your charts look

You can now set a custom color for single-series charts. Line, bar, funnel, and scatter charts that don’t have a breakdown get a dedicated Series color setting, so you’re no longer stuck with the default and can match a chart to your brand, your dashboard, or whatever convention your team already uses.

Numeric charts also get a new Show full numbers toggle. By default Basedash keeps big values compact (like 1.2M), but when you need the exact figure you can flip a chart to show the full number in the primary value and data labels while keeping the axis labels compact and readable. It’s an easy way to make number and KPI charts precise without cluttering the rest of the chart.

Dashboards stay visible while their data refreshes

Charts on dashboards now render their cached data immediately, even when that data is due for a refresh. Instead of blocking on a fresh query and leaving you looking at a loading state, Basedash shows the most recent results right away and kicks off the refresh in the background, swapping in new rows the moment they’re ready.

The refresh itself moved off the web request and onto a dedicated background job, with duplicate refreshes for the same query collapsed into one. The chart header keeps a subtle spinner (with an “Updating data from…” tooltip) while a refresh is in flight, so you always know whether you’re looking at the latest numbers—without the dashboard ever going blank on you.

A cleaner, smarter AI chat

The AI chat’s thinking steps got a visual refresh. Reasoning summaries now render inline as plain text—like preambles—instead of hiding behind an expandable “Reasoning summary” row, so the assistant’s train of thought reads naturally as it works. Tool steps that still have details to expand got tidied up too, with a lighter row style and a caret that only appears on hover.

The assistant can also maintain durable memory more precisely. When it learns something worth keeping, it can make targeted edits to your organization’s global AI context—not just append to it—and each change comes with a short, human-readable description of what it updated, so it’s clear what the assistant chose to remember.

Fixes and improvements

• Added a Copy → SQL action to charts in chat, so you can grab the underlying query and drop it into the chat input in one step.
• Let the chart assistant set and update a chart’s description when editing it.
• Added hover tooltips, a crosshair, and clearer legend and segment interactions to the AI usage charts in billing settings.
• Fixed vertical bars overlapping on time-series charts with sparse, clustered dates.
• Fixed setup for Fivetran file connectors like Google Drive so Magic Folder connectors create correctly.
• Made chat handle files that can no longer be retrieved more gracefully instead of surfacing a generic error.

Export to Excel

You can now export to Excel (.xlsx) anywhere you could already export data. Charts, tables, markdown tables, and in-browser record views all get a native Excel option right alongside CSV, so the data you pull out of Basedash lands in a real spreadsheet—formatted columns and all—instead of a raw text file you have to clean up first.

Exports stream from the server and page through large result sets, so even big tables download reliably without choking the browser. If your team lives in spreadsheets, this is one fewer copy-paste step between a Basedash query and the workbook you actually share.

More control over embedded Basedash

If you embed the full Basedash app inside your own product, you can now tailor what your users see with two new URL params: hide_chat and hide_dashboards. Hide the chat experience, hide the dashboards section, or hide both to scope the embed down to exactly the surface you want to expose.

Basedash automatically lands embedded users on the first feature that’s still visible, and your choices carry through as users navigate inside the embed—so there are no dead ends or empty sidebar sections. It’s a simple way to ship a more focused, on-brand embedded experience without custom work.

Filter dropdowns now populate on shared dashboards

Filter dropdowns on publicly shared and embedded dashboards now load their options the way they do inside the app. Both SQL-backed and record-backed filter dropdowns return their choices, so viewers of a shared dashboard can actually pick a value and filter instead of staring at an empty menu.

We did this without loosening anything: Basedash only ever resolves dropdowns for the in-scope, visible variables on the dashboard or chart you’re viewing, and hidden, cross-dashboard, and cross-organization queries stay locked down.

Fixes and improvements

• Restored file-based Fivetran connectors (like S3 and SFTP) so they create and sync correctly again.
• Fixed chart images in insight emails and Slack so they render with the correct row-level-security context instead of showing the wrong data.
• Made Connection issues sidebar rows link straight to the data source page instead of opening the command menu.
• Restricted creating, updating, and force-syncing data source connections to organization admins.
• Fixed padding on the Basedash warehouse access settings section so it matches other data source access sections.

SQL definitions: reusable snippets across your queries

You can now create SQL definitions scoped to a database connection—versioned, named SQL snippets that you can reference inline in any query with {{ definition("name") }}. Definitions get their own home in the Data page sidebar where you can create, edit, describe, and preview them, and the expansion is applied both for human-run queries and for queries the chat agent runs on your behalf.

The chat agent understands definitions too, so when it writes SQL it can reach for your team’s definitions automatically. Admins can also let the agent propose and save new definitions when it spots a pattern worth keeping around—so the SQL your team relies on becomes a real, reusable building block instead of something everyone re-types.

AI context now flows from groups

You can give a group its own AI context, and it now flows into chat, chart-editing, and automation agents whenever a member of that group is interacting. If different teams think about your data differently—engineering versus sales versus finance—you can finally encode that nuance per team without trying to cram it all into one global context block.

Chart agents spawned from inside a dashboard also now inherit the dashboard’s AI context, so editing a chart in place picks up the same guidance the dashboard agent has.

Billing got more transparent

The billing settings page got two new sections aimed at admins who actually need to reason about cost:

• Invoices lists recent Stripe invoices for the org with date, amount, status, and a hosted link straight to the invoice—no more bouncing into Stripe just to grab a PDF.
• The AI usage sections now have a billing period selector, so you can review totals and per-member breakdowns from any past period (capped to when your org was created). The current-period overage warning stays scoped to today’s period, so historical browsing doesn’t surface old warnings.

Skills and definitions join the public API

Following recent additions for Insights, automations, members, AI usage, data source access, and MCP servers, the public API now covers two more building blocks:

• Skills: list, create, fetch, update, and archive AI skills via /api/public/organizations/{orgId}/skills.
• Definitions: full CRUD for SQL definitions via /api/public/organizations/{orgId}/definitions.

If you’re provisioning Basedash from your own tools—or syncing skills and definitions from a runbook or repo—you can now keep both fully in sync from outside the app.

Fixes and improvements

• Returned typed structured payloads from the Basedash MCP server’s ask_question and get_data_sources tools, so MCP clients can consume them without parsing text.
• Fixed an MCP OAuth issue where rotating a refresh token could prematurely invalidate a still-valid access token.
• Tightened up the OAuth metadata the MCP server advertises, including bearer header support, resource name, and protected resource linkage.
• Capped the pie chart center metric at the standard number-chart size so it no longer balloons in larger charts.