ysunyang4/Nexus

What It Does

Nexus is a desktop control plane that connects remote or web-based AI assistants (ChatGPT, DeepSeek, Cursor, Windsurf and other MCP clients) to a local workstation. The AI client talks to a Fastify MCP server over Streamable HTTP with a Bearer token; the server forwards JSON-RPC calls to a local runner daemon that performs the actual file, Git, shell, browser and Windows UI actions.

The runner exposes 332 canonical MCP tools across filesystem, Git, command execution, background jobs, LSP code intelligence, browser automation, Windows Computer Use, local memory and prompt storage. A SQLite-backed Action Ledger with write-ahead logging records side-effecting operations for crash recovery and idempotent replay, and an AST-based command risk engine classifies commands as SAFE, CAUTION or DANGEROUS, blocking destructive calls by default.

Access is scoped by authorized project roots with physical path canonicalization and symlink/junction escape checks. Sensitive files such as .env*, *.pem, *.key and id_rsa are masked.

Quick Start

Requirements for source builds: Node.js >= 24, pnpm >= 10 and stable Rust.

git clone https://github.com/ysunyang4/Nexus.git
cd Nexus
pnpm install
pnpm run build
pnpm --filter @localbridge/desktop dev

If a prebuilt installer is listed on the v1.3.1 release page, download the asset matching your platform and verify any published checksum or signature before running it. The README's Chinese section lists expected installer names for Windows, macOS, Linux and a Tampermonkey userscript, but the English section warns not to assume an asset exists unless it appears on the release page.

Then, inside the desktop app:

1. Under Workspace -> Projects, authorize a directory and choose read-only or read-write access plus disabled, safe-only or project-code execution mode.
2. Under Settings -> Tokens, generate an MCP client token (lb_...).
3. Point your AI client at http://127.0.0.1:18080/mcp with Authorization: Bearer lb_your_token_here. A standard MCP config looks like this:

{
  "mcpServers": {
    "nexus": {
      "url": "http://127.0.0.1:18080/mcp",
      "headers": {
        "Authorization": "Bearer lb_your_token_here",
        "MCP-Protocol-Version": "2024-11-05"
      }
    }
  }
}

Constraints

• Node.js >= 24, pnpm >= 10 and Rust stable are required to build from source; the desktop app is bundled with Tauri 2.
• Windows Computer Use features depend on WinRT OCR and UI Automation and are described as Windows-native, so they are not portable to macOS or Linux.
• Default settings are read-only access and safe-only execution. Enabling read-write, project-code, Computer Use or unrestricted mode places full responsibility for executed commands and modified files on the user; back up work or use Git.
• The repository is licensed AGPL-3.0-only, which carries source-availability and notice obligations for modified versions distributed or offered as a network service, as well as attribution and branding rules separate from the license.
• Security behavior and the scope of sandboxing are described in the project's SECURITY.md; the README is the author's description, not independent verification.

HotRepo's take

Nexus appeared on HotRepo's TypeScript new-project list on 2026-11-15, gaining 13 stars in roughly one hour within a 24-hour growth window, reaching 119 stars and 23 forks. That is a single snapshot, so it shows early attention on launch day rather than sustained momentum. The technical design is unusually detailed for a repository this young: a defined 332-tool protocol package, a WAL-backed action ledger, dual-token isolation and a documented threat model all point to a real multi-package codebase. The main open question for readers is release provenance, since the shipped binaries are the primary entry point and this snapshot does not establish their build origin.