LiveAgent

🌟 Special Thanks

❤️ Sponsor

🤝 Come Build With Us!

Why LiveAgent?

LiveAgent is a local-first AI agent desktop client. It deeply integrates large language model reasoning with local system tools, so the AI can genuinely operate your file system, run commands, and manage scheduled tasks — while the Gateway enables remote access and collaboration.

• An agent that actually gets things done — beyond chat: read and write files, make precise edits, run Bash, and supervise long-running processes
• A fully open ecosystem — bridge any external tool via the MCP protocol, and load Skills packages on demand
• Both local and remote — the desktop app works fully standalone; deploy the Gateway and control it from any browser

Core Features

🧠 Multi-Model & Chat

• Multi-model routing — Claude (Anthropic), Codex (OpenAI), and Gemini protocols, with custom Base URL support for third-party compatible services
• Rich rendering — streaming Markdown with built-in KaTeX math, Mermaid diagrams, and Monaco code preview
• History compaction — dual-layer Segment + Summary Checkpoint persistence keeps long conversations from losing context
• Internationalization — built-in i18n multi-language framework

🔧 Local Tool Execution

• Full file-system capabilities — precise Read / Write / Edit / Delete, plus Glob / Grep pattern and regex search
• Bash & long-running processes — non-interactive command execution (cwd / timeout), with ManagedProcess supervising dev servers and other resident tasks
• Sub-agent delegation — independent sub-agents execute in parallel with worktree isolation and automatic merging
• Tunnel exposure — TunnelManager exposes local services to the public internet in one click

🧩 MCP & Skills Ecosystem

• MCP protocol bridging — the Tauri side natively bridges any stdio / http MCP server for unlimited tool extension
• Skills packages — progressive disclosure and on-demand loading, with install / create / package support and the ClawHub ecosystem

💾 Memory & Automation

• Persistent memory — Markdown + SQLite FTS full-text search for cross-session knowledge management
• Scheduled tasks — bash / http / prompt cron job types, executed automatically in the background

🌐 Remote Gateway

• Access from any browser — Go gateway (WebSocket + Protobuf) with a WebUI for remotely controlling the local agent
• Disconnect recovery — a bounded seq window replays short outages, with desktop-side persistence as the safety net

Download & Deployment

Installers are automatically built, signed, and published by GitHub Actions — grab the latest version from GitHub Releases.

System Requirements

macOS

Download the DMG matching your chip from Releases, open it, and drag LiveAgent into Applications:

• Apple Silicon (M-series): LiveAgent-<version>-macOS-aarch64.dmg
• Intel: LiveAgent-<version>-macOS-x64.dmg

The installer is signed and notarized by Apple — no manual security override is needed on first launch.

Windows

Pick an installation method from Releases:

Linux

Choose by distribution from Releases:

Need Remote Access? Deploy the Gateway

The desktop app works out of the box and depends on no server. Deploy the Gateway only if you want to control your local agent from a browser.

Note: when deployed behind an Nginx reverse proxy, set the Gateway address on the Settings → Remote page to the HTTPS URL and use port 443.

# Pull the image (built by GitHub Actions, multi-arch: amd64 / arm64)
docker pull ghcr.io/stack-cairn/liveagent-gateway:latest

# Run in the background (HTTP/WebSocket → host 3000)
docker run -d \
  --name liveagent-gateway \
  --restart unless-stopped \
  -p 3000:8080 \
  -v liveagent-gateway-data:/var/lib/liveagent \
  -e LIVEAGENT_GATEWAY_TOKEN=your-token \
  ghcr.io/stack-cairn/liveagent-gateway:latest

The named volume persists the Gateway database and independently issued Agent tokens across container upgrades.

One-command upgrade to the latest version — pull the new image → remove the old container → recreate it with the same arguments (if you changed the port mappings or token, adjust the arguments below accordingly):

docker pull ghcr.io/stack-cairn/liveagent-gateway:latest \
  && docker rm -f liveagent-gateway \
  && docker run -d \
    --name liveagent-gateway \
    --restart unless-stopped \
    -p 3000:8080 \
    -v liveagent-gateway-data:/var/lib/liveagent \
    -e LIVEAGENT_GATEWAY_TOKEN=your-token \
    ghcr.io/stack-cairn/liveagent-gateway:latest \
  && docker image prune -f

Since protocol v2, all traffic — the WebUI, the HTTP API, and the WebSocket links of both the browser and the desktop app — goes through the single HTTP port (default 3000).

WebSocket upgrades happen on several paths (/ws/v2, /ws/v2/agent, /ws/v2/terminal, and tunnels under /t/), so the simplest correct setup enables the upgrade on the whole vhost:

# WebUI SPA/static/API + every WebSocket link (browser and desktop)
location / {
    proxy_pass http://127.0.0.1:3000;
    proxy_http_version 1.1;

    # WebSocket upgrade
    proxy_set_header Upgrade $http_upgrade;
    prox