Lia 1.2 is a working release, not a demo: it adds the things that came up most often while running real accounts through the chat. Here is what changed and why.
Quick actions on a slash
Not every change deserves a conversation. Type / in the composer and the toolbox opens: new ad set, new ad, protective rule, duplicate, budget, activate. The tool mounts into the composer, you fill two or three fields, and you are done.
The guardrails do not change. A quick action is a shortcut to the same card the conversation would have produced: born paused, applied only on your Confirm, journalled in Relay with your name on it.
Protective pause rules
The rule everybody asks for first: stop spending when the cost per lead goes wrong. Point a rule at a campaign or an ad set, set the threshold and the window, and Lia watches it while you do something else.
Rules read cost per lead, not click-through rate. CTR tells you something about the creative; CPL tells you what the lead actually costs.
There is a full walkthrough in the protective rules playbook.
An honest context meter
Long threads used to end in a surprise. The composer now shows what the model is actually holding: the system prompt, the tools, the messages and the free space, in tokens, live. The same popup shows your session and weekly usage, so nothing arrives as a shock at the end of the month.
Relay folders
Relay, the feed where every change lands, now groups accounts into folders you define, with drag and drop ordering. On phones it reads like a messenger: the list first, the thread second, comments under every entry.
Smaller things worth knowing
- Media library picks cost zero bytes. Choosing a file Meta already holds references it instead of re-uploading it.
- Ads created by Lia carry a readable name. Meta auto-fills a creative name from the ad body if you do not set one, which is how accounts end up full of ads called by their first sentence.
- Language follows you. Ask in Italian, get Italian, for the whole thread.
What is next
A global map of your creatives on durable assets, and a public developer API for CRM integrators. Both are in progress; the write layer stays the part we touch most carefully.