For all things AI, head to LINUX DO! Wishing the community ever greater success~
❤️ Sponsor
PackyCode is a reliable, efficient, and professional API relay service provider, offering relay services for Claude Code, Codex, Gemini, Chinese domestic models, and more — a long-established, top-tier relay. The vast majority of the model resources used to develop this software were provided by PackyCode — thank you, Laonong! Register to get started!
Right Code provides stable relay services for Claude Code, Codex, Gemini, Chinese domestic models, and more. Invoices are available upon top-up, and enterprise and team users receive dedicated one-on-one support. The remaining model resources used to develop this software were provided by RightCode — thanks to the RC site owner and the support team! Register here to get started!
Cubence is a reliable and efficient API relay service provider, offering relay services for Claude Code, Codex, Gemini, and more, with pay-as-you-go billing. Thanks to Cubence for supporting this project! Register here to get started!
🤝 Come Build With Us!
Scan the QR code to join our QQ group and help drive LiveAgent development!
(Why a QQ group? It just packs a few more features than a WeChat group~)
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
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
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):
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;
proxy_set_header Connection "upgrade";
# Required: the Gateway's same-origin check compares the browser's
# Origin header against X-Forwarded-Proto + Host
proxy_set_header Host $host;
proxy_set_header Authorization $http_authorization;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# The Gateway pings every WebSocket connection every 15s,
# so a generous-but-finite timeout is enough
proxy_read_timeout 300s;
proxy_send_timeout 300s;
proxy_buffering off;
}
The upstream port maps to the host port from the docker run above: HTTP/WebSocket 3000 (inside the container, HTTP actually listens on PORT=8080). The server block needs listen 443 ssl; and a client_max_body_size large enough for attachment uploads (e.g. 100m).
Build from Source
Expand the Development Guide below for the full set of Make commands.
No. Keys are stored locally on the desktop side only. The Gateway is a pure protocol relay — it never accesses the file system and never stores any credentials.
Do I have to deploy the Gateway?
No. The desktop client works standalone with all local capabilities; deploy the Gateway only when you need browser-based remote access to your local agent.
Which models are supported?
Claude (Anthropic), Codex (OpenAI), and Gemini protocols are built in, plus custom Base URL support for any compatible third-party service.
Will long conversations / disconnects lose context?
No. The desktop app persists the full history with Segment + Summary Checkpoints; the Gateway replays short disconnects through a bounded seq window and converges automatically after reconnecting.
Contributing
Issues and pull requests are welcome! See the Development Guide for setting up a dev environment.
Before submitting a PR, make sure all of the following checks pass (they match the CI gates):
Install frontend dependencies once from the repository root with pnpm install --frozen-lockfile.
Desktop client
Type check & build pass: pnpm build:gui
Lint passes: pnpm lint:ui && pnpm lint:gui
Frontend unit tests pass: pnpm test:gui (also run pnpm --filter liveagent test:release when touching release scripts)
Rust backend check passes: cargo check --manifest-path crates/agent-gui/src-tauri/Cargo.toml --tests (run from the repo root)
