Hades Remote
A Windows client for explicitly enrolled Hades animation playback.
Requires Python 3.9 or later, Windows PowerShell 5.1, an interactive Windows
desktop session, internet access, and an invitation from a relay controller.
Install once on each Windows PC:
python -m pip install hadesremote
Then:
import hadesremote as hades
hades.enroll()
On a new PC, enroll() asks for the one-time code from the controller's
"Create Hades Enrollment Code" desktop shortcut. It installs the visible
tray client and its sign-in startup shortcut. Already enrolled PCs are left
unchanged. Importing the module alone does not install or start anything.
On your configured controller PC:
hades.play()
No Tailscale connection is required. Internet access is required.
The tray menu allows pause/exit, and a desktop shortcut uninstalls the client.
Use "as hades" for the short name, or import hadesremote and call
hadesremote.enroll().
Enrollment options:
hades.enroll(code="ONE_TIME_CODE", name="My PC")
hades.enroll(relay_url="https://your-compatible-relay.example")
Prefer the interactive prompt to putting enrollment codes in saved scripts.
The default relay is operated by this project's controller; installing the
package does not grant access to it or give you controller credentials.
Installation behavior:
- Copies the bundled player and animation to %LOCALAPPDATA%\HadesRemote.
- Creates a visible tray client and a current-user sign-in startup shortcut.
- Stores the device credential encrypted for the current Windows account.
- Adds desktop start and uninstall shortcuts; requires no administrator rights.
- Accepts only the fixed playback action, not arbitrary scripts or downloads.
Importing is inert. enroll() explicitly installs; it leaves an already enrolled
PC unchanged. play() needs separately configured controller credentials on
the invoking PC. Those credentials are not included in this package.
Playback covers connected monitors once; Esc exits. Sleeping or offline PCs
cannot display the animation, and cross-PC playback is not frame-synchronized.
Metadata
Release files for hadesremote 1.0.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 | |
|---|---|---|---|---|
| hadesremote-1.0.1.tar.gz | 566.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hadesremote-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / hadesremote-1.0.1.tar.gz
| Download URL | hadesremote-1.0.1.tar.gz |
|---|---|
| Size | 566.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78a5747df93b6649942dcefc5839f76b10edf017c92c704e79a6e1d29168a7ce
|
|
BLAKE2b-256 checksum How to use checksums |
012358401d27b0e6baadf8c818f11a3919d54c5a125265824b3b318af9ae406e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / hadesremote-1.0.1-py3-none-any.whl
| Download URL | hadesremote-1.0.1-py3-none-any.whl |
|---|---|
| Size | 567.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc10df369453dab08b64d1f71c81940de780336fa3c7951fa9ac93b8820d848d
|
|
BLAKE2b-256 checksum How to use checksums |
8c514f4e66647bec4a74d16e784cc0485778db453f35be26cbce46ab36d47532
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for hadesremote 1.0.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.