Generated dashboards now arrive as real, custom-designed interfaces — and the assistant around them asks better questions, makes fewer false promises, and speaks up only when it has something to say.
Ask for a dashboard now and you get one that was actually designed. Behind the scenes, dashboard building moved from stitching together a fixed set of prebuilt blocks to generating real interface code: a design pass first decides the lead metric, the KPI row, the hero chart and the one list that matters for your workspace, then a builder writes the components and a compile-and-review loop checks the result before anything reaches you. The practical difference is variety and fit — dashboards that look purpose-built for the question you asked instead of poured into the same mold. The data layer underneath got stronger at the same time: KPI aggregates like sum, count, average and latest value, currency and date formatting that comes out right, per-day rollups with empty days filled in rather than skipped, and a longer build window so ambitious dashboards finish instead of timing out. Dashboards created under the old format won't render; they'll show a short prompt to rebuild, which takes one request.
The conversation around that kind of work changed too. When a request genuinely has two or three reasonable readings — "do a deep dive on our competitor research" could mean what's changed since last week, a full re-teardown, or the same set plus a scan for new names — Dagny now offers 2–4 tappable options instead of guessing or asking an open question. Tap one and it goes out as your reply; keep typing if none of them fit. Options cards are available in web chat for now, and shortly after launch we shipped a fix for a rare case where several cards fired at once and left a couple of conversations unable to continue. Affected chats repair themselves on their next message, only one card can appear per turn, and the options themselves picked up cleaner radio-style rows.
We also tightened what Dagny is allowed to claim. Previously she could tell you a deck or research report was "underway" when no job had been proposed or confirmed — the answer sounded right and nothing was running. All the propose-and-confirm rules now live in a single place, "it's running" language is only permitted after a job genuinely starts, and an automatic check flags any reply that claims progress without work behind it so we catch regressions rather than hear about them. In the same spirit, she now investigates a problem you report with the tools available before filing it as feedback. The proposal card you confirm work from was reworked to be plan-forward: credits no longer clutter it (pricing lives on the Automations page), the typography is calmer, and Adjust now visibly seeds your composer with "Adjust the plan: " instead of appearing to do nothing.
Autonomous messages got quieter. Watch and competitor-intel automations no longer post just to say nothing happened — a quiet run records as a success with a short note on its run history, so silence stays visible to you without landing in your Slack. And Dagny remembers her last several nudges rather than only the most recent one, so an item you've already seen and chosen to leave alone won't come back three passes in a row. For teams using the CRM connector, write access is here: creating companies, contacts, deals, tasks and notes is on by default, editing existing records is an owner opt-in that always asks you to confirm first, and deleting or archiving is simply not something Dagny can do — those actions were left out of her toolset entirely rather than merely discouraged.
A handful of smaller touches round things out. Slack status lines finally read correctly on both surfaces Slack renders — the typing indicator speaks in her own voice ("I'm searching my Brain…") while the line beside her name reads naturally in third person ("Dagny is searching her Brain…"). Workspace Home lost its intrusive native scrollbars, so cards keep their padding and the layout stays clean while scrolling behaves exactly as before. And the underused per-reply "Send to Slack" button is gone from web chat, leaving a simpler transcript; Slack itself remains fully connected everywhere else.
Legacy dashboards will prompt you to rebuild them once — worth the click, because what comes back looks nothing like what came before. As always, tell us what still feels rough.