AI helper agents

DataMind's AI, Kartlos, also works in smaller ways: single-purpose helpers that suggest one thing at a time, inside the page you are editing. This page collects what each helper reads, what it proposes, and what stays yours to approve.

Where the helpers appear

Every helper works the same way: it proposes, and nothing is saved until you save it. They are separate from the agent that builds whole Warehouse tables with you; that one is The Warehouse Builder.

Comment on your columns

In the Columns step of a table's setup, the toolbar holds the comment helper: Generate column comments with AI.

• It reads a small sample of the table's rows, then proposes one comment for each column that has no comment yet.
• The comments come back in the language selected in the popover. When the helper cannot tell what a column means, it may start the comment with Most Probably, marking its guess so you can check it.
• The proposals land in the grid as unsaved changes. Nothing is stored until you save the columns.
• When every column already has a comment, the button is greyed out with All columns already have comments.

Configure a Lake table shows the step itself.

Suggest a primary key

The same toolbar holds the key helper: Suggest primary key with AI.

• It studies a sample of the table and picks the column or columns that identify each row.
• When it is not fully sure, it includes extra columns rather than too few: a key that misses a column lets duplicate rows through, while an extra column does no harm.
• The keys appear in the grid as unsaved changes; review them and save the columns.
• When the table already has a key, the button is unavailable, with Primary key is already defined. A saved key is also what lets the table deploy.

Draft a transformation query

On a transformation's Query step, click Generate with AI. The Generate SQL with AI window opens:

1. Tick the tables the query should read in the panel.
2. Describe what you need under Describe your query. If the transformation already has a query, choose Create new or Modify first.
3. Click Generate.

The draft arrives in Query Difference Checker, with Current Query beside the AI Suggested Query.

• The helper returns the SQL text only: no explanations and no commentary, and only statements that read data.
• Generating saves the tables you ticked as the transformation's dependencies, replacing the list from the Dependencies step, so tick every table the query needs.
• Nothing is applied until you click Apply Changes. Close discards the draft.
• After you apply, the query waits as an unsaved change, and the footer reads Query not validated until you validate it.

Build, test and finalize a transformation covers the full flow.

Fill or extend a static table

On a Static table's Data Mapping step, click Fill or add rows with AI to open AI Data Assistant.

1. Select the rows the helper should fill, or select nothing to add new rows.
2. Describe what to fill or add, then click Generate.

• The answer comes back as rows: the selected rows are filled in place and new rows are added to the grid. A message reports how many rows were updated or added.
• Only the columns you can edit are changed. The key and system fields keep their values on existing rows, and a new row leaves them empty.
• The rows are unsaved changes until you save them with Apply. The helper does not run on a table with PII columns.

Static tables covers the step.

Names for chats and consoles

Two more helpers work in the background:

• A new chat is named from your first message. Files count too: a first message that carries only files is named from the files.
• A console that still carries its default name is named from its first successful query, so a console called New Console may rename itself after your first run.
• Names are short, in plain words, and never written as camelCase.
• Both helpers are best effort. If naming does not work, the chat keeps a fallback name taken from your message and the console stays New Console. A console you have renamed yourself is left alone.

Questions, answered

Do the helpers save anything for me?

No. Every helper proposes into the page you are editing, and the proposal stays an unsaved change until you save it. The query helper is no different: applying a draft only puts the SQL in the query editor, where you validate and save it.

What does the AI read to make a suggestion?

The comment and key helpers read a small sample of the table's rows. The static-table fill works from the table's structure and the rows you give it. The query helper works from the definitions of the target table and of the tables you tick.

Which language do the comments come in?

The language selected in the popover. The comment helper writes each comment in it, and the default instruction already asks for that language.

Why does a comment start with "Most Probably"?

The helper is unsure what that column means, so it marks its best guess for you to check before you keep it.

When is a helper unavailable?

The comment helper is unavailable when every column already has a comment. The key helper is unavailable when the table already has a key. And a table with PII columns is refused by both, with AI sample features are disabled for tables with PII columns.

Does the query helper run or save the query it drafts?

Neither. It returns the SQL, and nothing is applied until you click Apply Changes. From there it is an unsaved change in the query editor: validate it, then save and test it as usual.

Which tables does the query helper read?

The tables you tick in the window. Generating also records them as the transformation's dependencies, replacing the earlier list, so tick every table the query reads.

Which values can the fill helper change?

Only the columns you can edit. The key and system fields keep their values on existing rows, and a new row leaves them empty.

How do I cancel what a helper suggested?

Discard the unsaved changes before saving, or close the window without applying. Close in Query Difference Checker drops a query draft, and the fills and comments go away when you discard the unsaved changes on the page.

Who names my chats and consoles?

A new chat is named from its first message, and a console with its default name is named from its first successful query. Both are best effort and never use camelCase.