CLI & Scripted Players
A Python CLI for managing lobbies and launching scripted players in API-mode games.
Installation
pip install -e cli/ # RECOMMENDED: dev install from repo root
# or
uv tool install anjeer # production install
Run anjeer setup from your bot's project directory. It prompts for your API key and preferred language, saves config to anjeer.json in the current directory, and copies a starter script template.
Commands
anjeer setup # first-time setup in cwd
anjeer find # list open API-mode lobbies
anjeer create # interactive lobby creation
anjeer create --game-mode advanced \
--spawn-bots \
--bot-difficulty hard # non-interactive
anjeer join <code> # join a lobby and launch your script on start
anjeer start <code> # (creator) start the game and launch your script
anjeer close <code> # leave and delete if empty
anjeer preset list/save/delete # manage saved lobby configurations
anjeer start and anjeer join set environment variables (ANJEER_API_KEY, ANJEER_SERVER_WS_URL, ANJEER_LOBBY_CODE, ANJEER_GAME_MODE) then exec your configured script. Your script connects to the same WebSocket the browser uses and receives the full wire protocol.
Scripted Players
Scripts receive everything: MBP-N depth snapshots, MBO order lifecycle events, eval module outputs, delta tables, and round lifecycle messages. This is enough data surface to build serious strategies.
The spectator view shows a live script log panel — your script can send script_log messages over the WebSocket and they appear in real time for anyone watching.
A few directions people might take this:
- Bayesian agent — replicate or extend the hard bot's hypergeometric posterior in Python with full access to your own hand
- Time-series model — buffer depth snapshots and trade events into a feature matrix; act on confidence crossings
- Reinforcement learning — treat each round as an episode; reward = end-of-round balance delta
The interface is stable enough for real strategies. Helper templates covering connection setup, book reconstruction, and hand tracking are planned.
Metadata
Release files for anjeer 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| anjeer-0.1.0.tar.gz | 20.0 kB | Without provenance | Details for anjeer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anjeer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for anjeer-0.1.0-py3-none-any.whl |
Total release size: 39.0 kB
Release files / anjeer-0.1.0.tar.gz
| Download URL | anjeer-0.1.0.tar.gz |
|---|---|
| Size | 20.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbade90360e24539b861f721cddbf3a36bd854a1de9efbb9c930b3a505dbe0d5
|
|
BLAKE2b-256 checksum How to use checksums |
2671c735eb9ec7364791289a13de8c6b61ecb704528430249729527844a412e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / anjeer-0.1.0-py3-none-any.whl
| Download URL | anjeer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f074bf76fe82ebb9a9382ebcf78511d81e25e32e7e77a99f277d8c531fc5a9aa
|
|
BLAKE2b-256 checksum How to use checksums |
a9096917472b36b0ae6ae57dc91cca9ceba9dfe0a4b1884c897050b7187cc9f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for anjeer 0.1.0
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.