Bring your own model. Work with Dot on your phone, desktop or browser.
Quick start · Documentation · 简体中文 · Feedback · Contribute
More languages
繁體中文 | Español | Français | Bahasa Indonesia | 日本語 | 한국어 | Русский | Tiếng Việt
Nanodot is an open-source personal AI agent with Dot as its default assistant. It brings together conversation, tools, memory and scheduled work, with Android and iOS app source, a desktop shell, a Web console and a Python runtime in one repository. It is derived from nanoMuse; the phone apps are based on OpenMinis 1.13.
Download the Android APK · Release and checksums · Release notes
The first Nanodot Android prerelease targets Android 8.0+ / ARM64, version 1.1.0 (versionCode 45). The asset is Nanodot-1.1.0-arm64.apk, signed with a dedicated Nanodot release key. Download its SHA-256 file alongside it to check the file. Read the installation notes before replacing a development build signed with a different key.
The ModelScope project presents the “科技无碍” concept through a labelled local interaction, an actual Android recording and the signed APK. Source and deployment instructions explain manual GitHub/ModelScope collaboration and keep browser simulation, development evidence and cloud architecture claims separate. Competition identity fields and final submission remain with the entrant.
- Crystal Dot. A floating crystal orb with breathing motion, drag trails and foreground chat in a blue glass panel.
- Ask about a selected region. Select part of the screen, review the local preview, then send your question. Models explicitly configured for images receive the masked image; other models use available selected text.
- Care guidance. Follow a highlighted target and a written instruction, confirm a completed step, or use Stop. The instruction stays in the conversation after the temporary cue disappears.
The theme follows the system. Custom names, SOUL.md, avatars, animations, models and preferences remain yours. Continuous voice and automatic updates default to off; check this repository’s releases manually.
| Nanodot home | Care conversation |
|---|---|
 |  |
These are actual API 35 emulator captures from earlier development candidates. The Care example uses a controlled test page and a local planner. They document the interface; they are not a new runtime acceptance run of the signed 1.1.0 APK. See the dated verification record for APK identities and test boundaries.
Preview limits. A complete real-provider Care task ending in verified success, arbitrary third-party apps, ARM64 hardware, older Android versions, Chinese microphone recognition and audible speech still need broader acceptance. Controlled image questions produced 4/4 correct core results, but only 2/4 complete answers had no detected errors; the full record keeps those errors visible. This release does not establish current iOS or desktop runtime acceptance.
| Use case | What the project provides | Learn more |
|---|---|---|
| Research and everyday work | Chat with your chosen model; use search, files and shell tools to turn a request into an output. | Tools and configuration |
| Work that continues over time | Memory, goals, reminders and routines. Scheduled work requires a running agent. | CLI |
| Your own workflows | Extend the agent with skills and MCP servers. | Skills and MCP |
| Phone and computer tasks | Screen-operation implementations, with platform-specific permissions and limits. iOS cannot operate other apps. | Phone · Computer use |
| Access from more than one device | A local Web console, plus optional device and conversation integrations through a relay. | Web · Devices |
These capabilities come from the inherited implementations. Nanodot packaging and device acceptance are tracked separately below; model support and platform permissions determine which tools are available.
You need Python 3.11+ and a configured model provider. Install from this repository so you get Nanodot's source; the package and CLI retain the internal name nanomuse.
git clone https://github.com/Mola-maker/nanodot.git
cd nanodot
python3 -m venv .venv
. .venv/bin/activate
python -m pip install -e .
nanomuse config initOn Windows, use py -m venv .venv and activate with .venv\Scripts\Activate.ps1 in PowerShell. Edit the [llm] section of config/config.toml with your provider, model, endpoint and API-key environment variable. The example configuration and provider guide explain the choices. Model API usage may incur provider charges; the default setup does not supply a key or allowance.
nanomuse doctor # Check your configuration and available tools.
nanomuse chat # Start a conversation in the terminal.
# Or start the local Web console:
nanomuse serveOpen the local URL printed by serve, including its authentication details. It listens locally by default. See Web setup before enabling remote access.
Try a small first task: “Create a checklist for my next trip and save it as trip.md.” Review tool approval requests as they appear. Browser automation and desktop screen operation need additional setup.
The Android target is Android 8+ on ARM64. Follow the build guide to prepare JDK 21, the Android SDK/NDK, Go and native dependencies, then run:
bash scripts/build-nanodot-apk.sh debugThe wrapper writes the APK and verification records under dist/nanodot/. Debug packages use a debug signature; a release build requires a dedicated signing key. It does not publish a release. Configure your model under Settings → Models, then start with a text conversation.
1.1.0 Crystal is the first Nanodot Android prerelease, versionCode 45. Download the signed arm64 APK and its verification files from the release page.
| Area | Current boundary |
|---|---|
| Android | Crystal orb, foreground conversation, region questions and user-guided Care are included. Runtime evidence above retains the identity of earlier development APKs. |
| Release signing | A dedicated release certificate is used. Earlier debug builds cannot be overwritten by this package; data migration and physical-device acceptance remain open. |
| Desktop and iOS | Source and build configurations are present; this release does not distribute desktop or iOS packages or claim their runtime acceptance. |
| Models and updates | Configure your own provider. Automatic updates and continuous voice default to off. |
Accessibility and other permissions require an explicit device action. Upstream nanoMuse APKs, desktop installers and TestFlight builds are separate products.
- Use your own model provider. The inherited runtime and clients support provider configuration; available capabilities depend on the selected model. See own-key setup.
- Review actions. The Python runtime's Sentinel handles tool approvals. Phone and desktop operation also require the relevant platform permissions.
- Understand data flow. Local execution still sends prompts and selected content to the model provider when inference runs. Read privacy and data controls.
- Optional upstream services keep their identity. nanoMuse Cloud is the upstream service. Nanodot does not operate it or promise its availability or free allowance; its provider controls accounts and policies.
Android uses io.github.nanodot.app and the external nanodot:// scheme. Existing internal packages, minis:// routes and sandbox paths remain stable. Nanodot has separate private app storage: moving data from nanoMuse requires an explicit supported export/import.
Start here · Build · Configuration · Architecture · Troubleshooting · Changelog
Platform and runtime pages include inherited nanoMuse implementation guidance. Read them alongside Nanodot's build boundaries.
Both users and developers can help:
- Try a workflow and report the result, including your source revision, platform, model and reproducible steps. Keep credentials and private content out of reports.
- Improve onboarding with clearer docs, translations or platform build notes. Read CONTRIBUTING.md and AGENTS.md; commits require DCO sign-off.
- Share a concrete example with a link to this repository. If Nanodot is useful to you, a GitHub star helps other people discover it.
Use Nanodot issues for this project. The licence is GPL-3.0-or-later; upstream attribution is retained in NOTICE and THIRD_PARTY_NOTICES.md. Nanodot is independent of Meta and its Muse trademark.
The following news, paper citation, maintainer and contributor cards, and acknowledgements are inherited nanoMuse records. Their original dates, names and links identify the upstream project, not Nanodot releases or maintainers.
nanoMuse
2026-10-09🚀 Version 1.0.0 Keel is out, for the phone, the desktop and the browser; it installs over the version before and keeps your data, and its release notes list every change.2026-10-08🤗 Our paper is on Hugging Face Daily Papers, ranked third on the list for October 8; questions and comments are welcome on the paper page.2026-10-07📄 Our paper is available on arXiv: nanoMuse: An Open-Source Personal Agent for Every Device You Own, by Guangyi Liu, Yong Liu and Jiangning Zhang (Zhejiang University); the citation is at the end of this page.2026-09-25🎉 nanoMuse is released on GitHub under GPL-3.0-or-later: an Android app built on OpenMinis 1.13; the relay, the desktop app and the iPhone app came in the days after.
Every version: releases.
 Guangyi Liu  |
Everyone whose change has landed on main, from GitHub's contributors list.
If you find nanoMuse useful, please cite the paper.
@misc{liu2026nanomuseopensourcepersonalagent,
title={nanoMuse: An Open-Source Personal Agent for Every Device You Own},
author={Guangyi Liu and Yong Liu and Jiangning Zhang},
year={2026},
eprint={2610.08699},
archivePrefix={arXiv},
primaryClass={cs.AI},
url={https://arxiv.org/abs/2610.08699},
}nanoMuse stands on other people's work; THIRD_PARTY_NOTICES.md has the terms.
- OpenMinis: the on-device agent the phone app is built on, with proot and Alpine Linux for the sandbox.
- DeepSeek Harness: the agent harness the desktop app is a plugin of.
- UI-TARS-desktop (ByteDance): the desktop hands' operator is a port of theirs, and the stage's markers follow their ScreenMarker.
- MobileGym, MemGUI-Bench, PhoneHarness, CopilotKit/OpenMuse, Open-AutoGLM, ClawGUI: the phone operator, the traces and the product ideas.