The AI teammate

An assistant that edits the open document with you: what it can reach, what it cannot, and how to take back what it did.

The AI teammate is a panel inside the app, working on the document you have open. It does not describe what you should click; it calls the same actions your clicks call.

Access is granted per member by an administrator. It does not come with a subscription, a backer tier or an access link. If the panel is not there, it has not been granted to your account.

How it works#

Ask for something in plain language. The teammate then loops: it reads your document, calls actions, reads the results, and repeats until the job is done or it runs out of steps: eight per request, a hard ceiling so a confused model cannot spin forever.

The loop runs in your browser, in your tab. The tools it calls are the app's own action registry, one function call away. There is no relay, no collaboration room, and no cloud project in the path, which is why it works on a local document that was never synced, and offline documents too.

No model key ever lives in the browser. The panel talks to a gateway on aukimi.com, authenticated with your own member token; the server holds the credentials and talks to the model.

What it is told to do#

The instructions it works under are worth knowing, because they explain its behaviour:

  • Only the actions of the module you have open. It is handed that catalogue and told never to invent an action or a parameter. Switching modules changes the catalogue, and it is told to read again after switching.
  • Read before writing. It inspects the document: the artboard, the shapes, the frames, so what it adds fits what is already there.
  • Small precise steps, not one sweeping one, because you are watching its cursor move as it works.
  • A failed action is fed back, not thrown. "No shape with id 999" is something it recovers from, and usually does.
  • Never report as done something that failed. If it could not do what you asked, it is told to say so in one sentence.
  • Think in pipelines. When the intent clearly spans one, Sculpt → Retopo → Matter/Pigment → Engine; it may prepare the next stage. Conservatively: it inspects the downstream work first, creates only reversible drafts it owns, and never overwrites your topology, UVs, paint, materials or scene setup.

The conversation#

The transcript is the record. Actions fold under a single N actions line, successes take no room, only failures earn one, so the conversation reads as prose with the machinery tucked underneath, expandable when you want it.

Retraction sits under the last AI turn: one click undoes what the teammate just did, in any studio that supports it. That is separate from Ctrl+Z, and it is the right tool when the teammate did five things and you want all five gone.

Per-module quick actions#

The panel offers starting points that match where you are: topology tips and optimize mesh in Sculpt, fix topology and edge flow in Retopo, PBR materials, baking tips and UV help in Pigment, animation principles, easing curves and keyframe help in Animator, plus get started and shortcuts everywhere.

What it will not do#

  • Reach a module you do not have open.
  • Reach another person's tab, in a shared session or otherwise.
  • Run more than eight steps on one request.
  • Overwrite work you own when it is anticipating a pipeline stage you did not ask for.