Praxia

Skipped by default (requires API keys + costs tokens)

pytest tests/llm_eval -m llm_eval -v

⬇ **Try Praxia in 30 seconds — no Python, no setup**

👉 [**📦 Download Praxia Desktop for Windows (.exe, 165 MB)**](https://github.com/praxia-dev/praxia/releases/latest/download/Praxia.Desktop_0.1.0-14_x64-setup.exe)

Windows 10 / 11 x64 alpha · Tauri + embedded Python sidecar · zero pip install, zero praxia serve. Paste an LLM API key (Anthropic / OpenAI / Azure / Google / Qwen / HF / Ollama) and you're chatting. Unsigned alpha — SmartScreen will warn on first launch, click "More info" → "Run anyway".

Other downloads · .msi for managed deployment · all releases & notes · macOS / Linux coming in Phase 1b.

---

1. Install (pick the extras you actually need)

pip install praxia # Core pip install "praxia[ui,connectors,office,audio]" # Common stack pip install "praxia[all]" # Everything

🚢 Deployment modes

Praxia ships in two halves you can mix:

Both modes share the same auth, memory, and skills — only the frontend differs. Step-by-step setup, production checklist, and migration path: docs/deployment-modes.md (JA).

```bash

🚀 Quickstart

### 🖥 Native desktop app (no Python required) The easiest way to try Praxia is the native desktop installer. | Platform | Installer | Status | |---|---|---| | Windows 10 / 11 | .exe (NSIS, 140 MB) / .msi (WiX, 203 MB) | ✅ v0.1.0-alpha1 shipped | | macOS 12+ | .dmg | 🚧 next alpha drop | | Linux (Debian / Ubuntu) | .deb / .AppImage | 🚧 next alpha drop | 📦 Direct download (Windows, ~147 MB): Praxia.Desktop_0.1.0-14_x64-setup.exe · alternatives: .msi for managed deployment · all releases & notes. The installer is unsigned during alpha, so Windows SmartScreen will warn on first launch — click "More info" → "Run anyway" (signed builds land with beta). The desktop app embeds the Praxia server inside the installer — install, launch, paste an LLM provider key, and you're running. No separate praxia serve process to start, no pip install, no Python on the user's machine. Settings exposes only the three things a user actually controls: LLM provider keys (Anthropic / OpenAI / Google / Azure OpenAI / Qwen DashScope / Hugging Face — Gemma covered via all three cloud paths), local LLM (Ollama URL + model), and optional SSO tenant URL for org connection. Everything else (port, API key, storage layout, CORS) is managed by the app. Multi-user organizational deployment still works the same way: install Praxia on a shared host as praxia serve, point a custom frontend or SDK consumer at it, and several users share L3 organizational memory + the L4 frozen layer with SSO / RBAC / audit / KMS-encrypted OAuth tokens — all in the OSS core. Desktop-only features (in addition to everything the server offers): - 🗂 Local folder ingestion with auto-discovery — point Praxia at a folder on your machine (e.g. ~/Documents/Contracts/); the desktop app walks it recursively, parses every supported file (PDF / DOCX / PPTX / XLSX / TXT / MD / code), and makes the contents searchable by the agent alongside L1 / L3 / L4 memory. Skips files above a size cap, watches for new / changed files, re-indexes incrementally by mtime + content hash. Useful for confidential documents you don't want uploaded to cloud storage. (🚧 Phase 1b) - 🔔 Native notifications when a long-running agent task finishes (🚧 Phase 1b) - 🪟 Native file dialogs for drag-and-drop attachments Cross-device continuity (PC ↔ phone handoff) and a mobile companion land in Phase 1b / Phase 2. --- For library / SDK / CLI use, the Python install below is the developer path.

```bash

Or: cp .env.example .env and edit

a fresh key. See docs/quickstart.md § 3a for the full first-login flow.

📊 Use Cases by Industry

Detailed Before/After tables for each domain are in docs/use-cases.md. Highlights:

3-year compounding effects: New-hire ramp 6–12mo → 2–3mo / Veteran-departure knowledge loss → zero / Cross-team best-practice diffusion 30+ items/month.

---

2. Configure once — all keys live in one place

praxia config init # interactive walkthrough praxia config show # display resolved config (secrets masked) praxia config path # show key resolution order

<provider>" via OIDC SSO when PRAXIA_SSO_PROVIDER is configured.

Each user authorizes individually (CLI loopback)

praxia oauth start box --user-id alice

↑ also bootstraps an `admin` user and writes its API key (one-time only)

to `.praxia/auth/BOOTSTRAP_API_KEY.txt`. Save it somewhere safe and

Dashboard / Preferences (+ Admin for admin role). Login: User ID +

Password (= API key from `praxia user create`), or "Sign in with

Backend-only HTTP API (8 endpoints under /api/v1)

pip install "praxia[server]" praxia serve --host 0.0.0.0 --port 8000 --cors-origin https://your-frontend.example ```

---

(b) Entry-point (third-party packages — no fork needed)

[project.entry-points."praxia.connectors"] notion = "praxia_connector_notion:NotionConnector" ```

After pip install praxia-connector-notion, the new connector shows up automatically in praxia connector list, the Streamlit UI, and the SDK — with no edit to Praxia itself.

Full guide with examples for all 4 plugin types: docs/PLUGINS.md.

---

Compare providers on the same cases

pytest tests/llm_eval --llm-eval-model gpt-4o ```

Built-in rubrics: keyword match, structure (heading) match, length band, must-not-contain, LLM-as-judge. One canonical case per business skill ships out of the box.