FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npm i -g @swal/preflight. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository iberi22/xavier;first catalogued 2026-10-12;last seen 2026-10-12。There is no official certification or quality rating here — we record sources and dates only.
Xavier — Fast Vector Memory & Communal Context Runtime for AI Agents
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
> Some features are experimental or beta — see Experimental and beta features.
Xavier is a **high-performance, Rust-based vector memory runtime for AI agents** with native HTTP REST, CLI, and Model Context Protocol (MCP) entry points. It manages vector embeddings, hierarchical context graphs, and semantic relationships using a robust SQLite-backed store (sqlite-vec), granting agents sub-millisecond contextual recall without external service dependencies.
---
🚀 Quick Start
1. Build & Installation
Ensure you have Rust (1.94+) installed.
For platform-specific installation options (such as Windows Scheduled Tasks or Linux systemd setup), see Installer Guides.
2. Environment Setup
Configure master credentials and target workspace path:
3. Launching Services
Xavier provides unified daemons for HTTP REST and MCP interfaces:
4. Basic CLI Usage
---
🧠 Canonical Agent Skills
Xavier provides native, standardized agent skills located in skills/ for continuous development, code-graph navigation, and maintenance:
- **xavier-cognitive-memory**: Memory persistence, hybrid search (BM25 + vector), and MCP protocol integration.
- **xavier-rtk-execution**: High-speed command execution and 60–90% token reduction via the rtk-kernel proxy plugin.
- **xavier-code-graph-analysis**: AST symbol navigation, call hierarchy mapping, and blast-radius analysis.
- **xavier-wave-verification**: Automated GitCore feature verification and CI test execution.
- **xavier-maintenance-hygiene**: Anti-sprawl guidelines, database cache quarantine, and deprecated script handling.
5. Preflight Verification
Before committing changes or triggering releases, verify manifest version sync and readiness using the SWAL preflight runner:
---
📦 Downloads
Latest release: **v0.2.17** — built via .github/workflows/release.yml (3 targets + SHA256, plus the XavierSetup.exe Windows installer).
| OS | Arch | Artifact |
|---|---|---|
| Linux | x86_64 | xavier-v0.2.17-x86_64-unknown-linux-gnu.tar.gz |
| macOS | aarch64 (Apple Silicon) | xavier-v0.2.17-aarch64-apple-darwin.tar.gz |
| Windows | x86_64 | xavier-v0.2.17-x86_64-pc-windows-msvc.zip |
Each artifact has a .sha256 sidecar.
**Linux desktop app:** download Xavier_ _amd64.AppImage from the release, chmod +x, double-click (or a .deb). See docs/desktop.md.
Docker image: ghcr.io/iberi22/xavier:0.2.17 (also :latest) — also see Downloads page (Starlight).
---
🐳 Docker
Production (with local Ollama)
Healthcheck: curl -fsS http://localhost:8006/ready (503 until the memory store and code graph are ready). GET /health always answers HTTP 200 and reports status / degraded_reasons in the body, so it is not a liveness signal; xavier health exits non-zero when the node is unhealthy.
Development mode (no token, browser panel)
docker-compose.yml sets up local development. Ensure you use XAVIER_TOKEN for authentication.
---
🖥️ UI Modes
| Mode | How to run | URL | Notes |
|---|---|---|---|
| **Browser (prod)** | xavier http (serves panel-ui/build) | http://localhost:8006/ and /panel | No Tauri, uses VITE_XAVIER_API_TOKEN + polling fallback |
| **Browser (dev)** | pnpm --filter xavier-panel-ui dev + cargo run -- http | http://localhost:5173 (Vite) proxied to :8006 | Hot-reload, use XAVIER_TOKEN |
| **Tauri Desktop** | pnpm --filter xavier-panel-ui tauri dev | Native window | Requires __TAURI_INTERNALS__ guard + dynamic invoke/listen |
| **Custom panel path** | XAVIER_PANEL_UI_DIR=/path/to/dist xavier http | Same as browser | Priority: XAVIER_PANEL_UI_DIR → /panel-ui/build → /panel-ui/build → CARGO_MANIFEST_DIR/panel-ui/build (see src/server/panel/assets.rs) |
---
🐛 Known Issues
See **docs/KNOWN_ISSUES.md** for the full 15-item table (browser-compat, config inline-comment pitfall, panel build vs dist drift, etc.).
Short summary:
- Browser panel required __TAURI_INTERNALS__ guards + useApiToken hook (fixed in WAVE-5, 4af11709).
- XAVIER_TOKEN=foo # comment inline — the # comment becomes part of the literal token; put comments on their own lines.
- XAVIER_PANEL_UI_DIR priority list only in assets.rs — now documented in docs/reference/ENV_VARS.md.
- /v1/auth/login, /v1/auth/register, /v1/auth/refresh, /v1/auth/logout and /v1/auth/totp/* were dead endpoints (backed by a user store nothing ever wrote to) and are now deprecated (308/410 pointing to /auth/*) — see GH #2545 and docs/api/README.md for the real, working auth API and a tested install walkthrough in docs/manual/GETTING_STARTED.md.