Launched this week
Not another AI image tool. Miora is an Agentic Creative Studio with Memory. Bring one idea, generate multimodal assets on one editable canvas, turn auto-built memory into a reusable Skill, then create more, always true to your taste. One person, a whole creative studio.
The project-vs-personal memory split is what sells this for me — as an indie dev I'm always making promo art and covers for my own app, and the visual language has to stay consistent, which black-box "AI remembers your taste" tools always drift on. Saving that as an editable Skill I reuse per project is the part I'd actually use. When you share a Skill, does it carry its memory rules with it, or just the workflow steps?
Miora
@lennoxbeflying You are exactly the kind of creator we had in mind when we split project memory from personal memory.
The idea is that a shared Skill carries the workflow and the intent behind it, while each creator still brings their own context and references into the project.
So if your Skill says "keep the playful illustration style, the soft gradients, and the visual language from Project X", those rules travel with the Skill. The personal history behind why you like those choices stays yours.
We like to think of it as sharing the recipe and the taste profile, not your entire kitchen.
Ada.im
Memory is the most interesting part to me. Can users see why a particular memory was recalled for a generation and remove it from that run without deleting it permanently?
Miora
@s_cen In Miora, memory isn't hidden away in a black box. We separate personal memory from project memory, and both are visible and editable by the user.
You can also turn memory off entirely when you want to work from a clean slate.
The "why was this memory recalled for this generation?" part is a fascinating direction though. The moment AI starts having memory, it probably also needs receipts.
Agent memory is a real game changer. Is it the case that your brand memories are saved as vector embeddings attached to user profiles? Can your group share their style memories?
Miora
@saksham_salvi We actually think of it less as "a vector attached to a profile" and more as a memory graph that evolves over time.
That's also why we separate personal memory from project memory. Some things belong to the creator, while others belong to the work itself.
As for shared style memories across a team, we don't support that today, but it's a direction we're actively thinking about.
@liziyang appreciate the detail on the weighting. one thing I'm curious about beyond the single-session case - if I use Miora from a couple different clients or agents on the same account, could two of them read the same ambiguous weak signal differently and end up nudging a memory in opposite directions before either update crosses the "explicit correction" threshold? or is there a single arbitration step that all signals funnel through regardless of which client produced them
Congrats on the launch!
The editable memory approach is what stands out most to me. Treating brand rules, style, and taboos as something you can inspect and adjust is far more trustworthy than the usual “the AI just gets you” black box — especially for team and client work.
The personal vs project memory split feels like a smart guardrail too. I’ve been exploring AI-assisted workflows and building my own agent skills, so I’m curious how the “Skills you own” part handles boundaries: when you reuse or share a Skill, how do you make sure it carries the workflow without leaking a specific project’s brand rules or context?
Congrats! Turning learned creative preferences into reusable Skills is a smart idea.
Miora
@sandy_liusy Thanks! yeah that's the part I'm personally most excited about. The thing you used to re-explain every single time just... becomes a Skill you reuse. Feels obvious in hindsight but it took a while to get there
Miora
@sandy_liusy Thanks! Really glad that resonated with you~
Miora
@sandy_liusy Thanks Sandy! Exactly. We hope Skills and memory can go beyond reusable instructions and become a way for the Agent to truly learn how you create. The more you work together, the less you need to explain yourself again.
How does Miora decide which memories are worth keeping, and can users approve them before they affect future work?