neruva-control
Status (v0.10.0+, 2026-05-18): Maintenance-only. Original role — running Neruva Computer and Neruva Code agents on your laptop — was retired in the 2026-05-18 substrate-first pivot. The Cockpit chat UI moved to neruva.io/cockpit as a hosted Memory Inspector. For new installs, see neruva-mcp + neruva-record.
This daemon used to drive two on-device agents (screen control + code editing)
from the Neruva Cockpit web UI. Both agents were archived to _attic/ in
this release; the daemon survives as a small loopback service for users who
still want to host a local control plane for custom agent harnesses they
build on the Neruva substrate.
If you don't have a specific need for neruva-control, you almost certainly
want one of these instead:
| You want | Install |
|---|---|
| Persistent memory in Claude Code / Cursor / any MCP agent | pip install neruva-mcp — or use @neruva/mcp on npm |
| Auto-record every Claude Code session to your Neruva memory | pip install neruva-record && neruva-record-install |
| Browse / query / replay records in a web UI | https://neruva.io/cockpit (hosted, no install) |
| Raw REST against the substrate | curl https://api.neruva.io/v1/records/ingest -H "Api-Key: ..." |
What's still here
- A FastAPI process bound to
127.0.0.1:7331with auth-token gating - A session model + WebSocket stream you can wire your own agent into
- Project / file-tree / wallet endpoints used by
neruva-record's hook flow
What was removed in v0.10.0
_agent.py(Neruva Computer agent loop) →_attic/_agent.py_code_agent.py(Neruva Code agent loop) →_attic/_code_agent.py_browser.py,_axtree.py,_ocr.py,_skills.py,_repo_map.py,_lsp.py,_indexer.py,_tool_catalog.py→ all_attic/- Optional-dep extras
[agent](pyautogui / pillow / playwright / pyright / pytesseract / pygetwindow / uiautomation) — no longer needed - All
agent_type=computer|codespawning paths in_sessions.py— stubbed to raiseRuntimeError
The full file history lives in _attic/ if you need to lift anything out.
Install
pip install neruva-control
neruva-control-install
Privacy
- Daemon listens on
127.0.0.1only — never on a network interface - Sessions stream over loopback WebSocket; never leave your machine in transit
- Memory writes (via
neruva-recordor your own client) go to your Neruva account over HTTPS, with client-side 14-pattern secrets redaction
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for neruva-control 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| neruva_control-0.10.1.tar.gz | 43.9 kB | Without provenance | Details for neruva_control-0.10.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neruva_control-0.10.1-py3-none-any.whl | Python 3 | none | any | Details for neruva_control-0.10.1-py3-none-any.whl |
Total release size: 91.5 kB
Release files / neruva_control-0.10.1.tar.gz
| Download URL | neruva_control-0.10.1.tar.gz |
|---|---|
| Size | 43.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb64e71e7f9ce5cb7325dff99e483589abdd8bd69495ddcd859b69ba3c9a2cf6
|
|
BLAKE2b-256 checksum How to use checksums |
1c8fdb9386787aabba7c1f5f9133cf1792f97d58fd23fdd8471befa19fffda3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / neruva_control-0.10.1-py3-none-any.whl
| Download URL | neruva_control-0.10.1-py3-none-any.whl |
|---|---|
| Size | 47.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bb4cce9e514661b120314f9ae17992271d3470fa8dc92399c03ab2618c9ca513
|
|
BLAKE2b-256 checksum How to use checksums |
117193018e9c8ee4a0e59f51943b8a4d2f210579e9c167d8b586df2a0364e90c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for neruva-control 0.10.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
