Drive a MetaClaw runtime from your browser.
The configurator is a web page. Your runtime, your solvers, and your design files stay on your machine. Open this page and it looks for a runtime listening on the loopback address, then connects.
Each candidate answers a handshake request. The runtime is accepted only when it reports the expected web-UI runtime contract; a stale or foreign listener is refused, not adopted.
Set up your runtime
Use your existing MetaClaw source checkout to connect this dashboard to your computer.
The launcher finds your current MetaClaw checkout and starts it with the MetaHz connection enabled.
Requires an existing MetaClaw source checkout with its dependencies installed. This small launcher does not include the runtime or native solvers.
- Extract the ZIP, then double-click
Start-MetaHz.cmd. - If asked, enter your MetaClaw source folder. Keep the runtime window open.
- Return here and click Connect. Allow local-network access if the browser asks.
- Your MetaHz page connects automatically. No pairing code is needed with the current launcher.
From your current MetaClaw source folder, run:
powershell -NoProfile -File .\sites\metahz\start-runtime.ps1A compatible standalone Windows installer is not yet published. The launcher above needs an existing checkout; older installers do not include this hosted connection.
You can still design, save and export antennas in the studio while runtime setup is pending.
Continue designingSetup
What the runtime reports about itself, and the design it currently holds.
LLM backend
The runtime plans and interprets commands with one provider at a time. Local providers keep prompts on this machine.
Choose a model already installed in Ollama on the runtime computer. Use model applies it to this runtime and 3D chat editing until the runtime restarts. No model is downloaded and no restart is required.
Connect to the runtime to load its Ollama models.
Use the Ollama picker to change the local model for this runtime session. Startup defaults and other providers come from the runtime environment. API keys are entered on the runtime machine and never reach this page.
Engines
Every engine the runtime knows about, with the readiness it reports for execution and for scientific claims.
| Engine | Status | Execution | Scientific | Notes |
|---|
Skills
Runtime skill profiles from the catalog. Each declares its engine route and whether it is implemented.
| Profile | Domain | f0 (GHz) | Status |
|---|
Simulation
Dispatch a profile through an engine. Arming is deliberate, like a motor test: it disarms after each job.
Design loop
Iterate a profile toward an objective through the runtime's design-iteration job. Results carry the evidence level of the route that produced them.
Evidence
What the runtime holds as its latest solver artifacts and reports. A file's presence is not proof; the labels say what was verified.
Fabrication
Export the current model for a fab or printer. Exports carry the evidence level of the result they came from.
Runs the runtime's export for the active skill profile.
Bridges
Other ways to reach this runtime: a hosted configurator, the phone app, and chat channels.
A hosted copy of this page pairs with the runtime using this code.
Console
The same command layer the CLI and chat bridges use. Try help or status.
Options
Configurator preferences. They live in this browser, not on the runtime.