Adds skills for reviewing GitHub pull requests and local branches with parallel reviewers, plus tools for creating, installing, and validating LiveAgent skills.
Claude Code
$ npx -y skills add Stack-Cairn/LiveAgent --agent claude-code
Codex
$ npx skills add Stack-Cairn/LiveAgent -a codex
Cursor
$ npx skills add Stack-Cairn/LiveAgent -a cursor
Gemini CLI
$ npx skills add Stack-Cairn/LiveAgent -a gemini-cli
GitHub Copilot
$ npx skills add Stack-Cairn/LiveAgent -a github-copilot
OpenCode
$ npx skills add Stack-Cairn/LiveAgent -a opencode
Windsurf
$ npx skills add Stack-Cairn/LiveAgent -a windsurf
Your Local-First AI Agent Desktop Multi-model access · Local tool execution · MCP & Skills ecosystem · Remote Gateway
English | 简体中文
Core Features • Download & Deployment • FAQ • Docs
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~)
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.
Read / Write / Edit / Delete, plus Glob / Grep pattern and regex searchManagedProcess supervising dev servers and other resident tasksTunnelManager exposes local services to the public internet in one clickInstallers are automatically built, signed, and published by GitHub Actions — grab the latest version from GitHub Releases.
| Platform | Requirements |
|---|---|
| macOS | Both Intel (x64) and Apple Silicon (aarch64) architectures |
| Windows | x64; requires the WebView2 runtime (bundled with Windows 11) |
| Linux | x86_64; requires WebKitGTK 4.1 (Ubuntu 22.04+ / Debian 12+, etc.) |
Download the DMG matching your chip from Releases, open it, and drag LiveAgent into Applications:
LiveAgent-<version>-macOS-aarch64.dmgLiveAgent-<version>-macOS-x64.dmgThe installer is signed and notarized by Apple — no manual security override is needed on first launch.
Pick an installation method from Releases:
| Method | File | Best for |
|---|---|---|
| Setup wizard | LiveAgent-<version>-Windows-x64-Setup.exe | Most users |
| MSI package | LiveAgent-<version>-Windows-x64.msi | Enterprise distribution / silent install |
| Portable | LiveAgent-<version>-Windows-x64-portable.zip | No install — unzip and run |
Choose by distribution from Releases:
| Format | Distributions | Install |
|---|---|---|
| AppImage | Any distribution | chmod +x, then run directly |
| DEB | Debian / Ubuntu family | sudo dpkg -i LiveAgent-<version>-Linux-x86_64.deb |
| RPM | Fedora / openSUSE family | sudo rpm -i LiveAgent-<version>-Linux-x86_64.rpm |
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
Nginx reverse proxy configuration — reference for custom domains / TLS
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 runabove: HTTP/WebSocket 3000 (inside the container, HTTP actually listens onPORT=8080). The server block needslisten 443 ssl;and aclient_max_body_sizelarge enough for attachment uploads (e.g.100m).
Expand the Development Guide below for the full set of Make commands.
Architecture Overview — diagram & tech stack
Stars on GitHub
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraHelps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookInstall it with the command on its page. It includes liveagent-code-review, skills-creator, skills-installer. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it