It works the tools. You do the work.
aukimi's AI does not hand you a finished image. It reaches for the same controls you do — creating a layer, adding a node, writing notes onto a track — inside your document, where you can watch it and undo it.
It calls the same actions you do
Nothing is special-cased for the model. Each module publishes an action registry — create a primitive in Sculpt, add a node in Matter, write notes onto a DAW track — and the AI is simply another caller of that registry. If an action does not exist for you, it does not exist for the AI either.
- Vectra — 33 actions, Engine — 32, Sculpt — 29
- Inkwell — 22, Pigment — 20, Matter — 19
- Composer — 18, Pulse — 17, Retopo — 15
It works in your tab, on your document
The reasoning loop runs in your browser, not on a server, and it stops after eight steps. The tools execute in the tab you have open — which means the server never touches your document, and cannot: it has no route to it.
Every change is reversible
The AI owns what it makes. Each module exposes a way to revert the AI's changes specifically, so accepting a suggestion is never a commitment. This is the difference between a collaborator and a slot machine: you can always take the last move back.
The model runs on our own hardware
Prompts go to a model we host ourselves, not to a third-party API. What you type in the editor does not become someone else's training data on the way to an answer.
Try it on your own project
The teammate lives in a panel inside the editor. Ask it for something small first — it works best as a second pair of hands.
Back the Project