whatisgithub

What is napaxi?

antgroup/napaxi — explained in plain English

Analysis updated 2026-05-18

26RustAudience · developerComplexity · 4/5LicenseSetup · hard

In one sentence

A mobile SDK that lets developers embed an on device AI agent directly inside their app, keeping data and tool execution on the phone instead of a cloud server.

Mindmap

mindmap
  root((Napaxi))
    What it does
      On device agent runtime
      Sandboxed tools
      Cross app connectivity
    Tech stack
      Rust
      Flutter
      Android and iOS
    Use cases
      Mobile dev agent
      File tool sandbox
      Smart home control
    Audience
      Mobile app developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Embed an on device AI agent inside a Flutter mobile app

USE CASE 2

Let an agent build, update, and install an Android app from the phone itself

USE CASE 3

Expose sandboxed file tools like image compression to an agent

USE CASE 4

Connect an agent to smart home or other external devices

What is it built with?

RustFlutterKotlinSwiftDart

How does it compare?

antgroup/napaxialexgladkov/quickaicriccomini/sleet
Stars262626
LanguageRustRustRust
Setup difficultyhardeasymoderate
Complexity4/52/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires Rust, Git LFS, and native Android or iOS build tools depending on target platform.

GPL 3.0 or later requires that any app or project using this code, if distributed, must also share its source code under the same license.

So what is it?

Napaxi is a software development kit that lets app developers add an AI agent directly inside their mobile app, running on the phone itself rather than through a cloud server. The core engine is written in Rust and shared across different mobile platforms, with a Flutter version being the most complete right now, alongside adapters for Android and iOS being developed alongside it. The main idea is that the agent's memory, session history, files, and tool use all stay on the device, so nothing needs to be sent to a Napaxi run server beyond whatever calls the host app itself chooses to make to an AI model. Any tool the agent wants to use, such as reading a file, opening a browser, or controlling a smart home device, runs inside a sandboxed environment where the surrounding app decides exactly what permissions to grant. Developers building on Napaxi keep full control of their app's look, accounts, and which AI model or provider it connects to. Napaxi supplies the reusable pieces underneath: session handling, stored workspace state, a set of built in tools, support for the Model Context Protocol, and connections to other apps, agents, and devices, described in the project as xApp, xAgent, and xChannel connectivity. Example uses shown in the project include building and installing an Android app entirely from the phone, compressing an image through a sandboxed file tool, and controlling a smart home light through a connected device provider. Getting started requires the Rust toolchain, the Flutter SDK if working with that adapter, Git LFS for downloading bundled binary assets, and Android or iOS native build tools depending on target platform. The project is released under the GPL 3.0 or later license, meaning any project built using this code and distributed to others must also share its own source code under compatible terms.

Copy-paste prompts

Prompt 1
Show me how to run the Flutter demo app for Napaxi and connect it to a model provider.
Prompt 2
Explain how Napaxi's sandbox controls which tools and permissions an agent can use.
Prompt 3
Help me build the native Android and iOS artifacts for the Napaxi SDK.
Prompt 4
Walk me through what xApp, xAgent, and xChannel mean in Napaxi's architecture.

Frequently asked questions

What is napaxi?

A mobile SDK that lets developers embed an on device AI agent directly inside their app, keeping data and tool execution on the phone instead of a cloud server.

What language is napaxi written in?

Mainly Rust. The stack also includes Rust, Flutter, Kotlin.

What license does napaxi use?

GPL 3.0 or later requires that any app or project using this code, if distributed, must also share its source code under the same license.

How hard is napaxi to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is napaxi for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.