nexilume — Nexus Python Agent SDK
Build callable Agents and connect an authorized Computer to Nexus Cloud with the same Python SDK. Supports hosted MCP runtimes, OpenWrt registration and routed invocation, plus optional Computer, Browser and A2A integrations.
Install
Use a virtual environment. The dependency-free core supports Python 3.9+; Python 3.12 is recommended for optional integrations.
python -m pip install nexilume==0.48.0
python -m pip install "nexilume[fastmcp]==0.48.0"
Use python -m pip install --upgrade nexilume to upgrade the core SDK.
The distribution name is nexilume, while the import name remains
nexus_agent and the Computer CLI remains nexus-computer.
The PyPI project named nexus-agent-sdk is unrelated.
If migrating from our older GitHub wheel, uninstall nexus-openwrt-agent-sdk
first, then install nexilume in the same environment. Do not install both:
they contain the same import namespace. Existing Computer pairing configuration
is separate from the package and is not removed by pip uninstall.
A hosted MCP Agent
from nexus_agent import NexusAgent
agent = NexusAgent(runtime="hosted", cloud_name="Echo Agent")
@agent.capability("demo.echo")
def echo(payload):
return {"echo": payload}
if __name__ == "__main__":
agent.run()
Install the fastmcp extra to run this example. Starting the process alone does
not register it in Cloud; configure or deploy its hosted runtime through your
Nexus installation. OpenWrt LAN registration is a separate supported mode.
Computer Runtime
python -m pip install "nexilume[computer,browser]==0.48.0"
nexus-computer setup "<pairing-url-from-your-cloud>"
nexus-computer status
Run as your ordinary OS user. Wait until connected, then attach and authorize
the Computer in Cloud. No inbound SSH port is needed. Browser control requires
a compatible local Chromium browser and the browser extra. Never share
pairing links, device keys or tokens.
Attached Computer binary files
Version 0.48.0 adds synchronous and asynchronous binary Workspace transfers:
data = ctx.workspace.read_bytes("images/input.png")
ctx.workspace.write_bytes("images/result.png", data)
ctx.workspace.upload("/agent-local/result.zip", "exports/result.zip")
ctx.workspace.download("exports/result.zip", "/agent-local/download.zip")
These operations require a caller-attached Computer and files.read /
files.write authorization. Upgrade Cloud and Computer Runtime together to
support workspace.binary.v1; upgrading this package alone cannot add the
server-side protocol. The SDK never falls back to the Agent host's files.
In-memory operations are limited to 16 MiB; streamed files to 1 GiB. HTTPS
chunks and SHA-256 checks precede atomic replacement, so interrupted transfers
preserve existing files. Use ctx.aio.workspace for asynchronous counterparts.
After upgrading Runtime, run nexus-computer restart; pairings are retained.
Optional integrations
Dependency fixes in 0.47.1: Computer
Tool Setup uses tomli on Python 3.9/3.10; MCP/A2A extras declare their direct
imports; fastmcp-tasks uses official fastmcp[tasks]. See the
compatibility guide.
Browser/FastMCP/A2A require Python 3.10+; core and Computer support 3.9+.
The windows extra is for Windows address/service helpers, not ordinary pairing.
Browser binaries, Linux libraries, Docker and Provider images are not pip dependencies.
| Extra | Purpose |
|---|---|
fastmcp |
Hosted MCP tools |
fastmcp-tasks |
MCP task integration |
computer |
Outbound Computer Runtime |
browser |
Browser automation integration |
a2a |
Agent-to-Agent integration |
windows |
Windows service helpers |
Documentation and support
License
The current source uses a modified version of the Apache License 2.0, with additional conditions (LicenseRef-Nexus-Additional-Terms-1.0), a source-available license, not unmodified
Apache-2.0 or an OSI-approved open-source license. The complete LICENSE is
bundled in the wheel and source distribution.
Already published packages retain their bundled license and identifier. Version 0.48.0 includes this license clarification without replacing any earlier release files.
Personal and single-tenant self-hosted use, including commercial single-tenant use, is allowed under the license. Operating a multi-tenant service or removing supplied Nexus UI branding requires prior written authorization. Headless SDK integration does not require adding a new logo. Earlier Apache-2.0 grants and third-party licenses remain unchanged. New contributions require the explicit contributor agreement included in the source distribution.
Commercial licensing: cary.nexilume@outlook.com.
Metadata
Release files for nexilume 0.48.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nexilume-0.48.0.tar.gz | 365.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nexilume-0.48.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 594.0 kB
Release files / nexilume-0.48.0.tar.gz
| Download URL | nexilume-0.48.0.tar.gz |
|---|---|
| Size | 365.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5bca562cf68f489d4e01f0c7a1066571b57ef806a0610c2b20000e38faac668
|
|
BLAKE2b-256 checksum How to use checksums |
b114d877e880a1a3fffc17125fc8b8e58130ee83bb2ced0cea29656edc830e43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / nexilume-0.48.0-py3-none-any.whl
| Download URL | nexilume-0.48.0-py3-none-any.whl |
|---|---|
| Size | 229.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cebec067509c174276207d3e78cbab7e6e09b79ae313bf94cb9384120020713f
|
|
BLAKE2b-256 checksum How to use checksums |
98c9c0c802094018a444e3b8f64b113180242b07e0aed11a1b243111315f4f25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log