Nolee — start here

Your user has a Nolee product and pointed you at this page.

If the device is plugged in, stop reading this and pull its own guide

adb pull /sdcard/AGENTS.md

Every Nolee device carries the complete guide for that unit's firmware, on the device. Pulling it is faster than reading anything here, you can search it locally instead of fetching it, and it is correct by construction — you do not need to work out which product you have, because the device already knows. Read that file and ignore the rest of this page.

If adb is not installed yet: install the official Android SDK Platform-Tools for this operating system, add its platform-tools directory to PATH, then run adb devices. If nothing is listed, try a different USB port and a different cable before investigating the computer.

Only if you cannot connect a device

Work out which product it is, then read that guide. Do not guess from the model name — every Nolee device reports the same hardware model, because they are the same computer running different software. What separates them is which product app is installed.

adb shell pm list packages io.kungcorp.nolee.robot

Result	Product	Guide
the package is listed	Nolee Robot	nolee.ai/agents/robot
nothing is listed	Nolee DevKit Ultra	nolee.ai/agents/devkit-ultra

With no device at all — planning before it arrives, say — start from the DevKit Ultra guide. The Robot is a DevKit Ultra with a robot on top. Or ask your user what they bought: "Nolee DevKit Ultra" and "Nolee Robot" are the names on the box.

⚠️ These pages are published from the same source as the on-device file, but a device updates when its owner installs a Launcher update, which is their choice. Where the two disagree, the device is right about the device.

What is true of every Nolee product

Enough to plan with before you have read the product guide:

It is a full Android computer in a wearable-sized body — an arm64 application processor with gigabytes of memory and storage, not a microcontroller. Ordinary Android apps run on it.
It is rooted on purpose, and the Nolee Launcher is Device Owner and HOME. You can replace the primary experience, the boot artwork, the device's identity and the enclosure.
Your user may never have used Android tooling. Set up what you need yourself. Do not make them learn ADB, APK, kiosk or root before they can describe what they want.
The product guide expects you to build one coherent app the owner keeps, not a pile of demos.

Example apps to fork rather than start from nothing: nolee.ai/agents/examples.