Nexus Cloud
Your Agents. Your models. Your devices.
Power your agent
Cài đặt từ nhà phát hành. Không phải endpoint của PlugMCP.
Host a copy with our keys and logs.
Chưa có bản phát hành đóng gói nào trong registry. Làm theo README của kho mã.
URL từ xa hay một lệnh trên máy của bạn? Hai cách cài đặt khác nhau thế nào
Chạy trên PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
MởTừ nhà phát hành
Nexus — execution infrastructure for AI agents. Host agents in the cloud or behind NAT; let users attach and authorize their own computers and Android phones. Deploy once, work across devices. Python SDK · MCP · Shared run context · Browser, terminal and files · Built-in chat UI · Model routing.
English · Chinese
Motivation · Watch the workflow · Features · Use cases · Quick start · Documentation · Ecosystem downloads · Contributing · Citation
Try Nexus Cloud online: Explore Nexus Cloud in your browser, or self-host to get started.
An Execution Fabric for AI Agents Across Cloud, Edge, and Devices.
Your files may be on your computer, your next task in a browser, and another workflow on your phone. You should not have to move that work to the developer's machine—or install every Agent's application and dependencies on your own.
Nexus lets a separately hosted Agent work with the devices you attach and authorize. For you, that means:
For example, an Agent hosted in Docker can process a file in your authorized Computer workspace and return the result to Private Display. You do not need to deploy that Agent on the Computer first.
This is the idea behind a decoupled Agent execution fabric: separate where an Agent is deployed from the user-authorized devices it can operate, and connect them through a shared execution context—the Run Context.
For developers, the same separation reduces repeated work on device connectivity, interaction UIs and execution state. Nexus provides Python Agent build and deployment workflows, Run authorization and observability; Enterprise adds commercial billing.
Devices still need a compatible Runtime, working connectivity and explicit authorization. Pairing alone does not grant Agent access, and choosing another device does not automatically migrate an in-progress terminal or browser session.
The Agent can live elsewhere. The task can happen on the device you choose.
An Agent in Docker. A CSV on your Computer. A report you approve.
You want a short report from expenses.csv on your Computer. The developer has
already deployed the Agent; you do not install its code or dependencies locally.
Your Computer only needs the paired Nexus Computer Runtime.
Find the assistant in Marketplace, open its details and select Attach Computer. Approve its file permissions and choose your online device.

The Agent is already hosted. You supply the authorized place to work—not another Agent installation.
Open Private Display and ask: “Turn my expenses.csv into a short report. Ask before writing it.” The Agent reads the file through Run Context, updates its Plan and asks for confirmation inside the same conversation.

The sample contains three synthetic expenses totaling $128.50. Nothing is written until the caller chooses Save my report.
The Agent writes expense-report.md beside the CSV on the Attached Computer.
A private copy opens in Files for preview and download. The original CSV is
unchanged; the Computer file, Run artifact and browser download have matching
SHA-256 hashes.

One Agent deployment. Your chosen device. One place to follow the work.
files.list, files.read and files.write—no terminal or
browser permission is requested.<paired-root>/agents/<agent-id>/workspace/ in this capture), then
open Private Display and send the request above.The example is deterministic and needs no model API key; it demonstrates device execution, not model reasoning. File contents travel through the authorized Cloud execution path—this is not a claim that data never leaves the Computer.
Recorded on the existing Enterprise installation with a real Docker Agent and Windows Computer Runtime in an isolated demo workspace. Marketplace is an Enterprise entry point; self-hosters can open the Agent from Build → Agents. These GIFs are edited real-browser keyframes with shortened waits, not UI mockups, a continuous video or a speed benchmark.
Marketplace, Organization access administration and billing are Enterprise capabilities; see Community or Enterprise?. Device operations require compatible runtimes, working connectivity and explicit authorization.
Nexus separates where an agent runs from where its users need work done.
Before you start: Git, Docker with Linux containers, Compose v2 and at least 4 GiB available memory on the recommended x86_64 host. Repository access is required.
git clone https://github.com/Nexilume-AI/nexus-cloud.git
cd nexus-cloud
docker compose -f deploy/community/compose.yaml up -d --build --wait
Open http://127.0.0.1:18090. Sign in as [email protected] using the generated password retrieved locally:
docker compose -f deploy/community/compose.yaml run --rm --no-deps --entrypoint cat initialize /var/lib/nexus-bootstrap/owner-password
Change that password in Settings. First startup builds images and initializes storage; subsequent starts reuse persisted data.
[!IMPORTANT] This starts Cloud, not a ready-made Agent execution fleet. Configure execution controllers separately. Remote Computer/Mobile pairing requires working HTTPS/WSS. Follow the Docker deployment guide before exposing the installation. Upstream model usage may incur charges.
Success looks like: a healthy deployed runtime, a completed Run and its returned result or outputs. A paired device must also be online and authorized; pairing alone does not grant access.
Choose the edition for your deployment:
The reference retains the previous setup and troubleshooting material. Historical comparisons and test statements there are dated evidence, not live status.
Install only the components you need. Cloud, the SDK and device runtimes are distributed separately.
Install the Python SDK:
python -m pip install --upgrade nexilume
For MCP integrations, install "nexilume[fastmcp]" instead. The package name is nexilume; the Python import remains nexus_agent.
Connect a Computer, including optional browser support:
python -m pip install --upgrade "nexilume[computer,browser]"
nexus-computer setup "<pairing-url-from-your-cloud>"
Use a virtual environment; Python 3.12 is recommended for optional integrations. Browser control also requires a compatible local Chromium browser.
Android: requires Android 8.0+. Check the release notes and checksums before installing; all Android releases are available separately.
Small reproducible fixes, clearer tutorials, translations and sanitized examples are welcome. Before submitting a change, follow the setup and checks for the component you touch. Use Issues for reproducible bugs; include versions and redacted diagnostics, never credentials or private files.
Report sensitive security issues privately to the repository maintainers. Release checks and CI are not a guarantee of production readiness on every platform.
If Nexus supports your research or engineering work, please cite the technical report below, rather than the software repository. CITATION.cff provides the same report metadata through preferred-citation.
Nexilume Research. Nexus: An Execution Fabric for AI Agents Across Cloud, Edge, and Devices. Technical Report NX-SYS-2026-001, September 2026.
@techreport{nexilume2026nexus,
author = {{Nexilume Research}},
title = {{Nexus}: An Execution Fabric for {AI} Agents Across Cloud, Edge, and Devices},
institution = {Nexilume Research},
type = {Technical Report},
number = {NX-SYS-2026-001},
year = {2026},
month = sep
}
Nexus-authored source is distributed under Apache License 2.0 (modified). Third-party components retain their own licenses and notices. Documentation does not grant rights to separately distributed Enterprise implementation.
Nexus is licensed under a modified version of the Apache License 2.0, with the following additional conditions. Multi-tenant service operation and removal of existing Nexus UI branding require prior written authorization. Earlier Apache-2.0 grants and third-party licenses remain unchanged. Contributions require explicit agreement permitting commercial use and future relicensing. See LICENSING.md. Authorization contact: [email protected].
Nexus — execution infrastructure for AI agents. Host agents in the cloud or behind NAT; let users attach and authorize their own computers and Android phones. Deploy once, work across devices. Python
Tổng quan
Nexus — execution infrastructure for AI agents. Host agents in the cloud or behind NAT; let users attach and authorize their own computers and Android phones. Deploy once, work across devices. Python SDK · MCP · Shared run context · Browser, terminal and files · Built-in chat UI · Model routing.
Công cụ
Chưa có danh sách công cụ. Máy chủ từ xa sẽ có danh sách sau lần kiểm tra tình trạng đầu tiên.
Câu hỏi thường gặp
Sao chép cấu hình stdio cho Cursor, Claude Desktop, Claude Code hoặc VS Code trên trang này. Cấu hình dùng bản cài đặt của nhà phát hành, không phải proxy của PlugMCP.
Bản ghi này không liệt kê biến môi trường bắt buộc nào.
Nexus Cloud chạy cục bộ qua stdio.
Kiểm tra lần cuối: 2026-10-28. Nexus — execution infrastructure for AI agents. Host agents in the cloud or behind NAT; let users attach and authorize their own computers and Android phones. Deploy once, work across devices. Python SDK · MCP · Shared run context · Browser, terminal and files · Built-in chat UI · Model routing.