PraisonAI Desktop

Native chat app that runs PraisonAI agents locally on macOS, Windows, and Linux

Next

PraisonAI Desktop is a native app that runs your PraisonAI agents locally with streaming chat, tool calls, approvals, MCP servers, per-conversation memory, and fine-tuning — no browser required. Sampling and reasoning effort are settable from Settings → Models, so you can tune how the model responds without touching code. It ships as macOS DMGs (Apple silicon + Intel), a Windows NSIS installer, and a Linux .deb.

from praisonaiagents import Agent

agent = Agent(
    name="Assistant",
    instructions="You are a helpful assistant.",
)
# Talk to this agent from the PraisonAI Desktop app —
# it picks up your local venv automatically.
agent.start("Summarize this file")

The app is a Tauri (Rust) shell that supervises a small Python engine on loopback. Chat text streams straight from that engine into the webview over 127.0.0.1 — nothing leaves your machine unless the model itself does.

Prefer a terminal? The Desktop engine ships with praisonai-desktop — see Headless CLI.

Quick Start

1. Install a venv with praisonaiagents

   The app looks for a local virtual environment inside the checkout. Create one and install the SDK:

   cd src/praisonai-agents
   python3 -m venv .venv
   .venv/bin/pip install praisonaiagents

2. Build the app from source

   The bundle targets are defined in src-tauri/tauri.conf.json (productName: "PraisonAI", identifier ai.praison.desktop): app, dmg, nsis, and deb. macOS builds require 10.15+.

   cd src/praisonai-desktop
   cargo tauri build

3. Launch and watch the startup pill

   On first launch a status pill reports the engine’s state:

   Pill	Meaning
   starting engine	The shell is spawning Python
   Engine: updating…	The venv drifted from the shipped requirement — the app is re-running the install step before starting the engine (see Troubleshooting → Library fixes never reached an existing install (pre-4670))
   engine :PORT	The engine is listening and healthy
   engine failed	Startup failed — the tail of the log is shown

How It Works

The Rust shell picks a Python interpreter, proves it owns its own site-packages, spawns the engine, then confirms the announced port with a /health probe before handing it to the webview.

Where the app looks for the venv, in order (src-tauri/src/main.rs):

The first interpreter whose venv owns its own site-packages wins. A system Python or a mismatched venv is refused rather than guessed at.

System Requirements

Each release ships one file per platform — there is no universal build.

On Debian/Ubuntu the .deb declares its own dependencies, so apt resolves them:

The package is built on Ubuntu 22.04, so it runs on Ubuntu 22.04+, Debian 12, and anything newer. On an older distribution, build from source.

When To Use It

Best Practices

Related