Axi now writes your model changes into a draft

Axi could already explain your semantic model. It can now change it — by putting the change in your draft, where your own edits live, and leaving Save model to you.

Ask, then read what it did

Open a connection in Settings → Data, press Cmd/Ctrl + K, and ask in your own words: describe this table and its columns, hide the technical columns, add a measure summing amount, id is the primary key.

The changes appear as a card in the conversation — one row each, saying what changed and what it rests on. Checked on the data means Axi ran a query to be sure; From the names and types means it did not, and is reading the schema. Show jumps to the column the change touched.

Nothing is saved. The rows read Edited, the tree shows the blue dot, and the model changes when you press Save model — not before. Discard takes the whole batch back out.

What it refuses to do

Two refusals are deliberate, and the card shows them greyed rather than hiding them.

Anything imported from dbt is left alone: that definition belongs in your dbt project, and overwriting it here would only survive until the next import. And text you wrote yourself is never replaced — a description you typed stays yours unless you ask Axi again to change that one.

Your draft survives a wrong click

Unsaved edits used to vanish the moment you navigated out of the section. They now survive leaving it and reloading the tab, and Axiome tells you what it restored.

If someone saved that model in the meantime, the stale draft is dropped instead of being re-applied over their work, and the notice says which tables were affected.

📖 Modelling with Axi · Semantic layer overview · Keys and joins