mojox

CLI and execution layer for Mojo build tooling.

mojox reads your pyproject.toml manifest (via mojox-core), discovers targets, builds an execution plan, and runs mojo commands with structured output. It handles profile resolution, local settings (.mojox/config.toml), diagnostic formatting, and -- in dev mode -- transparent ore acceleration (LLVM bitcode splitting for faster rebuilds) when LLVM tools are available.

Install

uv add mojox "mojo-compiler==1.0.0"    # in a project
uv tool install mojox                      # globally

Subcommands

test

Run test targets (dev profile by default).

mojox test                                    # all test targets
mojox test -k "parse" tests/unit/             # filter by name + path
mojox test --output-format json               # NDJSON to stdout (CI)
mojox test --no-fail-fast                     # run all tests even after failures
mojox test --failure-output final             # show failing output after all tests

Test-specific flags:

run

Run a single .mojo file (dev profile by default).

mojox run src/main.mojo

build

Compile binary targets (release profile by default).

mojox build

check

Validate the manifest and run lints. No compiler needed.

mojox check

metadata

Output the build plan as JSON.

mojox metadata

Common flags

These flags are available on every subcommand:

How it works

1. Parses pyproject.toml via mojox-core (manifest model layer)
2. Reads .mojox/config.toml local settings, if present (TOCTOU-safe via openat)
3. Resolves policy: profile, defines, flags, CLI overrides
4. Discovers targets and builds a plan (pure -- returns commands as data)
5. Executes the plan: runs mojo commands, collects outcomes, formats output
6. In dev mode, transparently uses ore acceleration when LLVM tools are available; degrades gracefully to standard mojo run

Exit codes

See also

• mojox-core -- manifest parsing, target discovery, and build planning (pure model layer)
• mojox-build -- PEP 517 build backend for packaging Mojo libraries as wheels

License

MIT