Try mojulo headless in a web agent, or install it locally.

Paste the prompt for where your agent is

Don't install anything yourself — hand the job to the agent you already run. In a web agent the prompt is one sentence; the one for your machine checks first and asks before every step.

Headless, in a web agent. The sentence is nearly the same everywhere. What differs is the door the file comes back through, and the line under each host says which, and what was seen in a run. Then ask for one small thing, and ask for the recipe JSON in the reply — that is the one door every box has, and all a local install needs to regrow the thing.

open a linux box and install mojulo npm package in it

on work mode, open a linux box and install mojulo npm package in it

open a linux box and install mojulo npm package in it

open a linux box and install mojulo npm package in it

On your own machine. 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 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.
4. When it finishes, tell me to open a fresh session and ask you:
   "what is this?"

Never install anything on my machine without asking me first.

What comes down, in either place: a 6.7 MB package that lands at about 227 MB on disk with its dependencies, measured on one machine, and no model — search ranks by the words in your ask until you opt into mojulo install recall. The dashboard is a separate package, fetched only when you open it. The browser that bakes still pictures is not in the install: an explicit render fetches one the first time it needs it (about half a gigabyte) if none is on the machine, never at install, and a Chrome, Chromium, Edge or Brave already there 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. 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. That shell route is exactly how Grok chat's sandbox runs it. When init has no terminal to ask — a pipe, CI, an agent's box — it changes nothing without --yes: it prints its plan and exits 2. npx -y mojulo init --yes --no-ui is the explicit spelling.

In Claude Code, the plugin. /plugin marketplace add zombico/mojulo, then /plugin install mojulo@mojulo, starts the same server pinned to one version. Use the plugin or init for Claude Code, not both: two registrations run two servers.

Already on 2.x? An unpinned npx mojulo moves to 3.0 on its next start, and 3.0 re-encrypts your saved provider keys one way, so back up ~/.mojulo/secret.key with the database first. The chatbot factory is no longer part of mojulo as of 3.0 and is moving to its own project. Earlier 2.x versions that include it are unmaintained and have known security issues. The steps are in Upgrading from 2.x.

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. Headless, the agent asks the same question from inside its box and reports the answer back.

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 to pick up again next week — on your disk, or in the report the box handed back.

Headless, ask for the page, not a still: the box may have no browser to bake a picture with, but the exported world.html is self-contained and opens from disk. Every export the agent writes tells it which door this host has, so it knows how to hand the file back. And keep the recipe — the box will not.

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.