# ⚡️ Building Lightdash: Deep Research, nicer URLs, and safer slugs

Canonical: https://brew.new/browse/templates/email/pt1_k97rs8vz376a9xkngqmhjfsmf58e2br0

Brand: lightdash.com
Category: newsletter

![Preview of ⚡️ Building Lightdash: Deep Research, nicer URLs, and safer slugs](https://cdn.brew.new/email-preview-a088e454dff678e5-tracking_r57y7p4bpmm0m0ka44cwkkrsrs8dv1sv-1788996914754.png)

## Email content

Hey there 👋

How's the summer been treating you? At Lightdash, we've been down and busy. A tiny heatwave wasn't going to stop this team from building 👀

So, I'm back with an update of what we’ve shipped over the last couple of weeks.

🔭 Trust every answer you get with Deep Research

Now you can ask your AI agents complex business questions with even more confidence than before. With Deep Research turned on, you'll get clear, evidence-backed answers that come from running several queries, testing competing explanations, and building a report from evidence found.

Use it for root cause analysis, anomaly investigation, or open-ended questions you’ll want to save and revisit.

📚 Run your first Deep Research investigation →

✨ Get readable Lightdash links

Most project, chart, and dashboard URLs now use slugs. Instead of a path full of UUIDs, you’ll see something like /projects/jaffle-shop/saved/revenue-by-month, which is much easier to read, share, and recognise later.

Your existing UUID links will keep working, and Slack unfurls understand the new project URLs too.

📝 Rename a chart without leaving broken links behind

You can now rename a chart slug with lightdash slug-update. The command updates the chart in Lightdash and your local content-as-code files, so you can clean up an old copy-of-... slug without creating a small trail of broken links behind you.

Don't worry, old links will keep working.

🛸 Rename a chart slug safely →

🧑‍💻 Watch the governed AI stack come together, end to end

Last week, dltHub, MotherDuck, and Lightdash built a working data stack live: from the first API request to a complete Lightdash project, using agents at every layer and one terminal throughout.

It’s a useful look at everything that has to happen around the query before you can trust the answer: ingesting the data, understanding the schema, defining the metrics, and giving agents the right context.

Missed it live? The full recording and source code are available to view.

▶️ Watch it back here →

🧮 By the numbers

We've been busy. In the last few weeks, we've also had:

🚀 129 new releases

💅🏼 65 enhancements

🐞 184 bug fixes

See all our releases here →

⚡️ Thanks for reading!

You've made it to the end of the update! Thanks for being our biggest fan 💜

If you have feedback, hit reply or drop us a note in our Slack community. We'd love to hear from you 🤝

And if you want to get started with Lightdash, talk to a member of our team!

With love,

Shanzé

Marketing Lead @ Lightdash

You are receiving this email because you opted in to receive updates from Lightdash

Lightdash, 7 Bell Yard, London, WC2A 2JR, United Kingdom

Unsubscribe

[Open and remix this design](https://brew.new/browse/templates/email/pt1_k97rs8vz376a9xkngqmhjfsmf58e2br0)

[Browse email designs](https://brew.new/browse/templates)