Pychess External Engine
Analyse positions on Pychess with native engines running
on your own computer. Use your own UCI-compatible engine for its supported variants.
The required pyffish and pyffish-alice libraries validate rules and moves;
they do not choose your analysis engine.
Version 0.2.0 registers your local engine with a Pychess account token and requires
the matching Pychess frontend/server integration.
Install and run
Install uv and obtain your engine executable. Create an engine token at Pychess Account → External engines and save it to a local file. Run:
uvx --python 3.13 pychess-external-engine@0.2.0 \
--engine /path/to/your-uci-engine --token-file /path/to/your-token
Engines and NNUE networks are supplied locally. For Alice, configure a compatible engine and any network it needs as described in the usage guide.
Connect to Pychess
- Leave the app running after it reports that your engine is registered.
- Open Pychess analysis engine settings and select your engine by name.
- Allow local network access if your browser asks, then enable analysis.
The default address is http://127.0.0.1:9670. Stop the app with Ctrl+C; restarting
refreshes its registration automatically. Select the browser engine to switch back;
the remove button removes an external registration. Only one tab can use the native
engine at a time. Account tokens stay in the local app; search traffic stays local.
Linux x86_64 native transport and integrated UI are verified with Chromium 154, Edge 155 and Firefox 155. Firefox permission Allow was verified; explicit denial remains a manual check. Safari and other operating systems remain unverified. Connection controls require Pychess's external-engine frontend integration.
For configuration, resource limits and troubleshooting, see the usage guide. See compatibility for tested engines and variants.
Metadata
Release files for pychess-external-engine 0.2.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 | |
|---|---|---|---|
| pychess_external_engine-0.2.0.tar.gz | 180.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pychess_external_engine-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 225.4 kB
Release files / pychess_external_engine-0.2.0.tar.gz
| Download URL | pychess_external_engine-0.2.0.tar.gz |
|---|---|
| Size | 180.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
109128ebde3ad228e1e3e612ca6eca1d0d0c2e4f9b04307963b6613424590fee
|
|
BLAKE2b-256 checksum How to use checksums |
38d026d753ea6dd152cce5dd896e1770d4ddf86612ff16f9f44117de543b0e93
|
| 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 14, 2026.
Transparency logRelease files / pychess_external_engine-0.2.0-py3-none-any.whl
| Download URL | pychess_external_engine-0.2.0-py3-none-any.whl |
|---|---|
| Size | 44.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d155b10e852c5ddd06a5c8ad8558970937c45ef20f1fa059275ed7753a161b7c
|
|
BLAKE2b-256 checksum How to use checksums |
3ae99948483ddcf860efb83cea72191c9a794043da630a6b94cccccfa81f098d
|
| 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 14, 2026.
Transparency log