Autonomous agents that ship results, not slides.
Agents that take a job, run it on your stack, and hand results to the next surface — hub, systems, instrumentation, and database — without a slide deck in between.
Illustrative agent activity. Not a live operations feed.
Agent surfaces
Three live tracksCore tracks
Systems · Instrumentation · DatabaseBuild complete AI systems
Control and instrumentation
AI database management
Agent catalogue
4 live surfacesBuild complete AI systems
Control and instrumentation
AI database management
Run your own autonomous agent in one line
The AINNA CLI runs entirely on your infrastructure with the models you configure. Choose Install for your platform, then use Quick Start to connect a provider and begin.
What it is
AINNA CLI runs on your infrastructure with the models you configure. It is built for controlled, private, operational use.
Live status
387 installs
Current release: 2.0.29 · 2026-10-17
curl -fsSL https://ainna.bond/ainna-agent/install | sh
curl -fsSL https://ainna.bond/ainna-agent/install | sh
iwr https://ainna.bond/ainna-agent/install.ps1 -useb | iex
pkg update && pkg install -y curl unzip
Linux · macOS · Windows · Android legacy package v1.18.33 · current release 2.0.29 · downloads from ainna.bond
Android guidance
AINNA CLI v2.0.29 does not currently include an Android or Termux build. The older ARM64 Debian package remains available as a legacy download.
Android ARM64
The available Android ARM64 .deb is the previous v1.18.33 release; it is not a Termux installer.
Linux Core
Keep the main agent engine on Linux for easier background work, file access, service control, and deployment reliability.
Hybrid Setup
Best model: Linux core + Android companion. Android can act as a thin controller, local client, or on-device runtime when needed.
Android legacy package
There is no one-line installer for Android/Termux in v2.0.29. The previous ARM64 Debian package is available for compatible Debian-based environments.
Quick Start
Install AINNA, connect your own provider, select a model, and send your first request.
ainna. On first launch it opens the AINNA panel.ainna providers login --provider opencode. AINNA keeps your credential in your own isolated AINNA data directory; it does not use a shared account.ainna model use big-pickle, or list available models with ainna models.Recommended choice
Linux-first core with Android companion is the best setup for the AINNA CLI.
- Linux runs the main agent engine.
- Android is for mobile control or ARM64 testing.
- Hybrid setup is the safest default.
Use Android when
You want mobile control, on-device testing, or a thin runtime wrapper for ARM64 Android environments.
Use Linux when
You want the main agent engine, background services, file operations, and predictable deployment behavior.
Bottom line
Do not make Android the only base unless the product is specifically a mobile-first agent. For the core CLI, keep Linux as the source of truth.
Does it run on my own server?
Yes. The CLI is designed to run on your infrastructure with your chosen models and provider setup.
Can I change models later?
Yes. You can connect providers and switch models without rebuilding the whole setup.
Where do updates appear?
Release notes are published in the changelog, and this block can link back to it anytime.
Which platform should I install?
Linux is the recommended core for background work and deployment. macOS is supported for local development, Windows via PowerShell, and the previous Android ARM64 .deb remains available as a legacy package.
