Lovart 2.0 Ships Arti: A Design Agent That Remembers Your Taste
Summary
Lovart 2.0 adds a personal design agent that carries memory across projects, runs scheduled design delegations, audits the canvas for drift and turns element level comments into revisions. Built for solo creators, small shops and brand teams without a design department.
Recommend- Name
- Lovart
- Version
- 2
- Open source
- Proprietary
- Operating system
- Web
- Website
- https://www.lovart.ai
- Updated
- 2026-11-06 23:00
Making a single image stopped being hard a while ago. The hard part is pushing a design job all the way to handoff. Lovart 2.0 answers with an agent that remembers you.
Over the past year the barrier to entry for generated imagery fell close to zero. Anyone who has actually shipped design work knows the picture is only an intermediate artifact. Before it there is reference hunting and direction setting; around it there is brand consistency to hold; after it there is a stream of scattered revision notes to absorb. None of that gets solved by rolling the dice one more time.
Lovart 2.0 arrived on 19 October and put its weight on exactly that ring of work which sits outside generation. The role it introduces is called Arti, positioned as a personal design agent: not a model that draws better, but a collaborator that remembers you, goes looking for material on its own, and reads the draft once before you do.
It learns you first, then it designs
Most tools keep memory in a black box. Lovart turned it into a list you can page through. Memory splits into basics, communication preferences, business context, working style, delivery preferences and aesthetic taste. You can edit entries in conversation, or upload a portfolio, a resume or an existing memory file and let the agent read it and distil the rest. After a few weeks of use its read on you settles into concrete lines, such as offering several directions before taking a brief, or producing covers in multiple sizes.
Those lines are not decoration. When a new project opens, Arti pulls the relevant slice automatically, so you stop restating your taste every time.
Design delegation: hand over the whole job
The most substantial addition in 2.0 is design delegation. It replaces a request for one image with a standing instruction, for instance walking through competitor visuals every Monday morning, picking three directions worth borrowing and filing them into a given project. You set the goal, the delivery standard, the cadence and a credit ceiling per run. Before the first real pass you can do a trial run and judge from the output whether the thing deserves to keep running.

Run history shows what each pass produced and what it actually cost in credits. That matters if you watch spend: a subscription is not an unlimited tap, and work that runs for months needs the math done up front.
Research and audits: surfacing what you missed
Design research works in the background, hunting cases around the current task and returning a report with sources and analysis attached. Images inside that report can be dragged straight onto the canvas as reference. This used to cost an afternoon of tab hopping; now the agent does the hopping and you only judge which lead is the right one.
Canvas audit is the other kind of initiative. On a schedule it compares the project requirements against what is actually on the canvas and flags the mismatches: a page still carrying last quarter copy, a set of assets that drifted off style. It tells you first and waits for your go-ahead before touching anything. The stated cadence is once a day. What is restrained about the design is that it will not rewrite your draft on its own authority.
Revisions finally have a place to land
Open comments on a share link and a reviewer can pin a note to a specific element. Hand that thread to Arti and it turns the notes into a revision plan before executing it. The link stays identical and earlier versions remain viewable. Anyone who has worked on the agency side knows the real saving here: collapsing a dozen requests to make something a little bigger, scattered across chat, into one list.

Repeated workflows also get distilled into skills. You approve one the first time; afterwards, when a similar task appears, the agent asks whether to invoke it. The mechanism is not novel, but it fits design work, where the same brand ships the same handful of assets every month on a fixed pattern.
It is not the one signing off
Worth stating plainly: Arti waits on your judgement the whole way. You pick the direction, you confirm what the audit suggests, you accept what a delegation produced. The first proposal will most likely not be the final one. It behaves more like an intern with fast reflexes, a good memory and no complaints about a tenth round of edits.
So the fit is specific: people with a steady flow of design work that never quite justifies a design team, who are willing to spend time spelling out their briefs and preferences once in exchange for not repeating them fifty times. If you only need the occasional illustration, most of these proactive behaviours never come into play and plain image generation is enough.
Lovart 2.0 does not change image quality, it changes the workflow: memory holds your taste, delegation runs the cadence, audits catch the drift. Moving human attention off repeated briefing and back onto judgement is the job a design agent should be doing.