Introducing the Less Assistant
A new way to interact with Less

You can now ask the assistant about your workspace and have it do the work for you. It explores your catalog, traces lineage, reads job logs, and answers questions about your data - and when you ask it to, it makes changes: running assets, editing configuration, creating sources and destinations, and managing access.
The assistant does the legwork; you stay in control. Anything that changes your workspace happens at your request, and credentials are handled separately from the model (more on that below).

Here's what it can do:
Understand your workspace and models. Ask it to find any source, destination, model, table, or orchestration, and it explains how they fit together. It reads metadata and configuration, traces lineage upstream and downstream ("where does this data come from?"), reads change history ("when did this break?"), walks a model step by step in plain English, diffs two model versions, and runs semantic search across pipelines ("which models filter on column X?").
Monitor jobs and debug failures. Get run counts by status over any date range, open individual runs with deep links to their logs, and read the logs themselves — error-level by default, or in full for "which step was slowest?"
Analyze your data. Ask questions of your verified tables and get a direct answer back, along with a plain-English explanation of how the assistant arrived at it.
Act on assets. Run an asset on demand, set or clear schedules (cron, with timezones handled), edit basics like name, description, table prefix, and compute size, patch connector configuration (including reordering orchestration pipelines), create and move folders, duplicate assets (folders included), and publish a model version.
Create sources and destinations. The assistant walks you through a new connection end to end — browsing connector types, checking requirements, collecting credentials or OAuth, testing database connections, and selecting Google Sheets or SharePoint files. Secrets are collected in a dedicated form and never pass through the model.
Manage access. Find users, list and create groups, add members, inspect roles and folder permissions, and set a group's role on a folder.
Why it's accurate. Everything is backed by a transaction log with real data, not just metadata. And because Less is no-code, every transformation is structured and explicit, so the assistant can reason about what each step does without guessing.
What's next. The assistant doesn't build or edit models on the Canvas yet. That's what we're working on now.





