Separate applications. Explicit setup.

The retired DNA-Blockchain/Helloworld install.ps1 and install.sh endpoints return 404. Do not pipe downloaded code into PowerShell or Bash. The replacement setup.py is a new preparation tool, not a recovered original installer.

Hosted RabbitOS console

Open RabbitOS in your browser. No sign-in, CAPTCHA or local installer is needed. Public research, hosted Qwen and browser-local brain/body tools are separate from the Python prototypes below. Chats, notes and settings stay in this browser; approved hosted AI requests leave it. Local files and devices are not connected automatically, and existing private account data is inaccessible.

Prerequisites and download

Install Python 3.11 or 3.12 and Git, then reopen your terminal. Python 3.11 is the backend CI baseline. The pinned dependencies do not support Python 3.13/3.14; setup rejects those versions before downloading source. Network access is required for GitHub and package downloads. Use a new writable folder, not an existing application checkout.

Windows / PowerShell

Invoke-WebRequest -Uri https://rabbitsoftware.io/installers/setup.py -OutFile rabbitsoftware-setup.py
# Review the saved script before continuing.
py -3.11 rabbitsoftware-setup.py --check
py -3.11 rabbitsoftware-setup.py --component all

Linux / WSL

curl -fL https://rabbitsoftware.io/installers/setup.py -o rabbitsoftware-setup.py
# Review the saved script before continuing.
python3.11 rabbitsoftware-setup.py --check
python3.11 rabbitsoftware-setup.py --component all

If you have Python 3.12 instead, use py -3.12 on Windows or python3.12 on Linux. Ubuntu may require the matching python3.11-venv or python3.12-venv package. Under WSL, use the Linux filesystem for setup rather than a Windows-mounted folder to avoid slow environment creation. No Python interpreter or system packages are installed automatically. A failed command stops setup and reports its error; already prepared components are not rolled back. Existing destinations are never overwritten. To retry a failed component, select it with a new --directory.

Choose a component

Replace all with backend, monitor, or research. Each component gets a source checkout and its own .venv under rabbitsoftware-local. Use --directory "my-new-folder" to choose another location. Source revisions are pinned in the reviewed script; this is not automatic updating or full Git-history synchronization.

backend: the RabbitOS FastAPI backend. Only the rabbit-os subtree is checked out, avoiding legacy Windows-invalid filenames. Git's NTFS protection override applies only to that sparse checkout command, not your global settings. Installs the declared dependencies and checks /health in-process with a mock provider and an in-memory database. Setup prints an explicit loopback-only Uvicorn command for later use. This is not the hosted console or a replacement OS.
monitor: the dna-chain prototype. Setup checks the monitor's --help command only. Its original Windows Task Scheduler and Linux systemd installers would register and start persistent monitoring; this replacement does neither. Running monitoring separately can inspect files and probe peer addresses. Only use your own or explicitly authorized sources and devices.
research: the cancer-mutation-blockchain research prototype. Setup installs its declared requirements, checks core dependency imports and the orchestrator entry point, but does not start the multi-service stack. Optional dependencies are not included. The old install.sh can install into system Python, start services and open tunnels; its stop mode uses broad process-name termination. Do not use that script as the RabbitOS installer.

What was verified

All three preparation targets passed on Windows with Python 3.12. The Linux/WSL backend health check passed with an isolated Python 3.11 interpreter. The initial WSL Python 3.14 attempt was stopped because its dependencies are unsupported; the second attempt stalled fetching the monitor repository from GitHub. Full Linux preparation of monitor/research is not yet verified.

Backend health, monitor help, dependency consistency and research dependency imports are preparation checks, not full workflow validation. No real account, device, network-monitoring, biomedical analysis, blockchain consensus or public deployment is certified by setup. These are research prototypes, not medical advice or clinical software.

No administrator privileges, auto-start services, public tunnels or global Python packages are required by the replacement tool. Source repositories have their own licenses; installing source does not change their terms. Review website privacy and each component's source before running it.