How to ask your agent to install the Mojulo workshop.

Paste this into your agent

Don't install anything yourself — hand the job to the agent you already run. Open Claude Code or Codex and paste this prompt. It checks the machine first, reports what it found, and asks your permission before installing anything — nothing enters your machine without a yes.

Help me install mojulo — a free, local 3D factory you'll drive over MCP.
Orientation, if you can fetch it: https://mojulo.ai/llms.txt
(mirror if the site is down: https://github.com/zombico/mojulo)

1. First just check: run `node --version`. Mojulo needs Node 22.12+.
   Tell me what you found before changing anything.
2. If Node is missing or too old, ask my permission, then install it
   the way this machine expects (brew / winget / nvm / apt).
3. With my go-ahead, run `npx mojulo init`. It wires mojulo into the
   coding agents on this machine (one yes/no per host) and opens a
   dashboard at localhost:3001. Everything stays on my machine.
4. When it finishes, tell me to open a fresh session and ask you:
   "what is this?"

Never install anything without asking me first.

What comes down: the package and its native runtime — about 985 MB on disk, measured on one machine — and, on first launch, a ~130 MB search model. The 3D render libraries are in the default install. The one thing that isn't is the headless browser the factory bakes still pictures with: it is fetched the first time a bake needs it (about half a gigabyte), never at install, and a Chrome, Chromium, Edge or Brave already on the machine is used instead. The measured figures, and everything else the machine needs, are in technical requirements below.

Prefer to drive it yourself? Install Node.js 22.12+ from nodejs.org and run npx mojulo init. Either way, everything runs on your machine — the dashboard opens at localhost:3001 (or the next free port; the installer prints the URL) and state lands in ~/.mojulo/. No account, no credential to hand over; re-running init repairs older wiring instead of duplicating it. The same install doubles as a command line — npx mojulo tools lists what's inside, npx mojulo call <tool> runs any of it, no agent in the loop.

Ask your agent what it's looking at

Open a fresh agent session — the new wiring is picked up on start — and type one line. Mojulo reads its own routing index and orients itself out loud — no provider key, no cloud call, nothing built yet.

what is this?

forward_context — the factory explaining itself. This is the intended interface: you ask, your agent discovers the right tool and reaches for it.

Ask for one small thing

Then ask for something that's yours. Your agent authors it, mojulo keeps it as a small deterministic recipe, and hands you a URL to open.

model a coffee mug in real centimetres I can orbit   → mint_solid

the recipe is the stored artifact — a few readable lines that regrow the same mug on every open. the render is derived and disposable; the recipe stays on your disk to pick up again next week.

If a 3D tool ever refuses and names mojulo install creative, run that. The render libraries ship in the default install, but an npm install --omit=optional or a failed native build can leave them out — and the refusal says so rather than failing quietly.

Then change it

"Make it taller." "Change the tint." Your agent edits a few lines of the same recipe in place and it re-renders; nothing is regenerated from a black box, and the lines it changed are there to read.

make the handle thicker and the glaze matte black   → update_sketch

A mug is the floor, not the ceiling. What else the factory makes — and where a finished thing can go next — the workshop names when you have something in hand, or when you ask. This page stops promising here on purpose.