cooloo Python API and GUI launcher — 0.1.3
Thin wrapper around the bundled C GUI+CLI client and cooloo-text editor (0.3.0, JSONL schema 1).
No Python Native/Noise implementation, SSH backend, daemon, or CLI-only distribution.
Initial wheels target Windows x86_64 and macOS arm64. Python >=3.10.
Licensed under MIT; bundled third-party components retain their own licenses.
Installation / launch
pip install cooloo
pipx install cooloo
cooloo --gui
cooloo-text
# Or without a persistent pipx installation:
pipx run --spec cooloo cooloo --gui
pipx run --spec cooloo cooloo-text
cooloo with no arguments prints terminal help; use cooloo --gui for the GUI.
cooloo-text launches the standalone text editor. Other commands are forwarded unchanged.
On Windows, the installed cooloo console entry point waits for the bundled GUI
executable and preserves stdin/stdout/stderr. No separate native CLI artifact is
required. Desktop shortcuts may continue to target the native executable with --gui.
If a standalone GUI cooloo.exe earlier on PATH shadows this entry point,
PowerShell/CMD can return to their prompt while that process is still running.
Check Get-Command cooloo -All (PowerShell) or where cooloo (CMD). Use
python -m cooloo whoami with the Python environment where cooloo is installed
to bypass PATH ambiguity; remove the obsolete PATH entry when appropriate.
Do not copy the bundled _bin/cooloo.exe into a command directory as a replacement
for the installed console entry point.
With current client source, terminal trust confirmation requires this waiting
launcher. Redirected input never confirms trust: verify the displayed fingerprint
and explicitly use -y/--tofu for first-use automation. Changed pins still fail.
Version 0.1.3 includes these native protections in the bundled binaries pinned
in release-inputs.json, together with the waiting launcher and module entry point.
Upgrade to the Shanghai server
python -m pip install --upgrade cooloo
# pipx users: pipx upgrade cooloo
Version 0.1.3 bundles refreshed client 0.3.0 artifacts, whose default is 123.206.215.121:4222.
Persisted old official 43.133.202.144:4222 config is resolved to Shanghai; identity
and history caches are not deleted or rewritten. An existing old-server pin is reused
only when it equals the verified unchanged official fingerprint
e6da669a4763acc8e790c6c757f698eed8eeab2c56007a62d28fd48f421c06bf.
An explicit pin for Shanghai takes precedence; fresh installs still require first-use
trust. Restart running GUI/Python processes after upgrading.
Explicit overrides are preserved: if your environment sets COOLOO_HOST or your
code passes Client(host="43.133.202.144:4222"), remove/update that override. Custom
servers and nonstandard ports are not migrated. Client() uses the native default;
no separate Python protocol or endpoint fallback is introduced.
Unsigned/not notarized native artifacts retain their platform trust limitations.
No runtime downloads, PATH lookup, implicit identity creation or registration.
Unsupported platforms have no matching wheel; source users may explicitly supply a
compatible local C executable. No source distribution is published in this first release.
Python usage
from cooloo import Client
client = Client(host="your-server:4222", config_dir="./bot-identity")
# client.keygen() # once, explicitly
# Client(..., tofu=True).register("bot") # explicitly trust first server connection
end = client.send("<destination-id>", "hello\n世界")
with client.read("<destination-id>", offset=0) as messages:
for message in messages:
print(message.sender, message.content, message.end_offset)
with client.follow("<destination-id>", offset=saved_offset) as messages:
for message in messages:
process(message)
save_checkpoint(message.end_offset) # only AFTER business processing
Replace example IDs, server, and application functions. Obtain/trust the server pin through
an appropriate trusted channel; tofu=True is an explicit first-use trust decision, not
protection from a first-connection MITM. Changed stored pins always fail. Config defaults
match native CLI (~/.cooloo); use a separate directory per service/credential. Parent
of a new config directory must exist. Private identity files must not be shared/logged.
Methods: keygen, register, whoami, rooms, create_room, meta, rename, avatar, send,
read, follow, sent, join, approve_join, set_room_mode, delegate. Pass
effective_identity=child_id with the parent's credentials to select an ordinary
child's message identity. delegate(child_id, ...) controls the parent's access to
that child, not the child's access to its parent; failed AS never falls back to login identity. Administrative operations require actual owner
credentials. sent(peer, offset=...) returns SentResult(messages, scan_offset), including
an advanced cursor on empty filtered results. SENT never populates normal message caches.
Private rooms currently permit any registered user to make them public: not a
confidentiality guarantee. No aggregate history or complete multi-device recovery.
Each call starts a process and authenticates a connection. timeout=30 bounds finite
commands. FOLLOW has no overall timeout; optional idle_timeout bounds silence. It may
end when the server closes an idle connection; no automatic reconnect, keepalive or retry.
Context managers close streams and reap subprocesses; always close streams on early
exit, including breaks. GUI caches are untouched by machine READ/FOLLOW. No exactly-once
claim: replay can occur; deduplicate by destination/end_offset and persist business cursors.
CoolooError exposes code/message. SendOutcomeUnknown means delivery may have happened; never blindly retry. A valid server acknowledgement returns end_offset. No guarantees of thread-safe shared Client usage. No shell execution; SEND uses UTF-8 stdin, max 4096 bytes.
Automatic releases
SDK version tags trigger tests, platform wheel builds and PyPI Trusted Publishing (OIDC, no API token). Manual workflow runs build and validate only. See PUBLISHING.md for setup, pinned native artifacts and release steps.
Development and packaging
PYTHONPATH=src python -m unittest discover -s tests -v
Integration tests need sibling client/cooloo-cli and server/coolood, or explicit test
binary overrides; all connections use temporary identities and loopback servers.
This CLI-only build is a local test fixture, not the distributed product. The distributed
platform wheels bundle both the cooloo and cooloo-text native products.
Build each platform from a separate package source copy: stage its verified cooloo and
cooloo-text artifacts with tools/stage_binary.py, then python -m build --wheel. The builder refuses
missing artifacts, changed hashes, and source distributions. macOS wheel tag must match
the actual deployment target; do not infer it from the build host version. Keep the
manifest's source commit/version/hash with the binary. The bundle must include third-party
license notices and the C client's MIT license before public distribution.
See LICENSE for the Python SDK's MIT license.
Source repository: https://github.com/cooloo-app/python-sdk . The planner includes it as
python-sdk/ submodule; package name and Python import remain cooloo.
Metadata
Release files for cooloo 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cooloo-0.1.3-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| cooloo-0.1.3-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
Total release size: 5.8 MB
Release files / cooloo-0.1.3-py3-none-win_amd64.whl
| Download URL | cooloo-0.1.3-py3-none-win_amd64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
307af72a102e24793b87f72b4aac32952833200c1d332242141fe08ec0daff45
|
|
BLAKE2b-256 checksum How to use checksums |
34548355f78127e09a07b04a3e66f1e3e76c2d36e08cff0a609be2fbbf50caa3
|
| 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 19, 2026.
Transparency logRelease files / cooloo-0.1.3-py3-none-macosx_11_0_arm64.whl
| Download URL | cooloo-0.1.3-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f9bc1145ac2d4cd204650de46bae1fafed6aec4cc40451372c604f3f77ae05ad
|
|
BLAKE2b-256 checksum How to use checksums |
7d110cbd71c2e9dc786c9de946a6a6301477adf705f5d000530d54ce5e9a320a
|
| 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 19, 2026.
Transparency logSecurity for cooloo 0.1.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cooloo-0.1.3-py3-none-win_amd64.whl
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 19, 2026.
Transparency logA 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.