Source: https://mokxi.com/docs/start/coming-from-wokwi
Updated: 2026-10-05

Getting started Getting started The screen, part by part Your first project in five minutes Save, share, and come back Import a project from another tool Help someone fix their code Coming from Wokwi The editor Boards Parts Accounts and plans Live collaboration Classrooms Lessons and the learning game Hobby builds Troubleshooting Reference

Docs / Getting started / Coming from Wokwi

# Coming from Wokwi

Your Wokwi projects open in Mokxi as they are. Here is what each Wokwi idea is called here, and what changes.

## Bring a project over

Paste the project's link (https://wokwi.com/projects/...) into the
import page, or drop Wokwi's project zip, or drop the files
themselves: diagram.json, the sketch and its tabs, libraries.txt, and
wokwi.toml if it has one. A Wokwi for VS Code project in the PlatformIO
layout (src/, include/, platformio.ini) works too. The import report
lists everything that came across and everything that did not, with the
reason, before anything replaces the project on your canvas.

## Side by side

In Wokwi
In Mokxi
What happens on import

diagram.json
The diagram: parts, wires and notes on the canvas
Each part becomes the matching Mokxi part with its pins and settings. Positions and rotations are kept.

A part's attrs
The part's properties, in the panel when you click it
Color, value, I2C address, pixel count, temperature and the other settings that change behavior are carried over.

connections
Wires
Each keeps its color. Routing hints become the wire's corners. Tidy wires routes them around the parts.

$bb (plugged into a breadboard)
A pin sitting in a breadboard hole
The part sits in the same holes.

wokwi-junction
Wires joined at a pin
Every wire that met at the junction is joined.

wokwi-text
A sticky note
The text is kept where it stood.

sketch.ino and tabs
The board's files, in the code panel
All of them, as they are.

libraries.txt
Built-in libraries
Every library Mokxi ships is already there and free: nothing to install. One Mokxi does not have is named in the report.

wokwi.toml
Nothing needed
Mokxi builds your code when you press Run, so no firmware path is needed. An SD card folder is put on the microSD card.

$serialMonitor wires
The serial monitor
Always connected to the board. No wires needed.

serialMonitor settings
The serial panel
The plotter is the Plot button. Typed lines end with a line feed, as in Wokwi.

Wokwi-GUEST Wi-Fi
The board's access point setting
Set to Wokwi-GUEST with no password, so your WiFi.begin connects unchanged.

wokwi-wifi-ap
The board's access point setting
Its name and password are copied to the board.

Logic analyzer
Logic analyzer
Mokxi's has four channels, so D4 to D7 go to a second one beside it. Channel names become net labels.

Custom chips (chip-*)
Mokxi chips, built from parts
A Wokwi custom chip is a compiled program, so it comes across as a note. Build the same logic from parts, or package it as a Mokxi chip.

Keyboard shortcuts on parts (key)
Click the part
Press buttons and turn knobs with the mouse or a finger.

## What to check after the import

- Starting positions. A potentiometer's knob, a slide switch, the
HC-SR04's distance and other parts you move by hand start at rest in
Mokxi. The report says when the Wokwi project started one somewhere else.
Move it on the canvas while the sketch runs.

- Boards Mokxi draws but does not run yet. Some boards (the ESP32-S2, the
ESP32-P4, the STM32 Nucleo boards, the Pi Pico 2) come across with their
wires and code, so you can export them for real hardware, but Run does
not start them yet.

- Libraries Mokxi does not ship. The report names them. Add one as a
custom library to build the sketch.

- MicroPython. Mokxi builds Arduino C++, so .py files are kept as text
but do not run.

For how importing works with every tool Mokxi reads, see
Import a project from another tool.

### On this page

Bring a project over Side by side What to check after the import