New in Basedash: SQL definitions 📘

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.