Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

bazaar-contrib-telegram

Telegram Channel provider for Bazaar Compute Node.

Setup

Create a Telegram bot with BotFather, then install BCN and this provider:

uv tool install bazaar-compute-node
bcn contrib add telegram --enable

Add an agent using an installed Harness provider:

bcn agent add --name Editor --channel telegram --harness HARNESS_KIND
bcn run

Configuration

Set either field in the agent's telegram Channel configuration:

  • token_env: Environment variable holding the Telegram bot token.
  • token: Bot token supplied directly by the configer; takes precedence.

Metadata

Release files for bazaar-contrib-telegram 0.3.0rc4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bazaar-contrib-telegram 0.3.0rc4
File Size Uploaded Provenance Actions
bazaar_contrib_telegram-0.3.0rc4.tar.gz 31.1 kB Without provenance Details for bazaar_contrib_telegram-0.3.0rc4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bazaar-contrib-telegram 0.3.0rc4
File Interpreter ABI Platform Actions
bazaar_contrib_telegram-0.3.0rc4-py3-none-any.whl Python 3 none any Details for bazaar_contrib_telegram-0.3.0rc4-py3-none-any.whl

Total release size: 67.0 kB

Release files / bazaar_contrib_telegram-0.3.0rc4.tar.gz

Download URL bazaar_contrib_telegram-0.3.0rc4.tar.gz
Size 31.1 kB
Tags Source
SHA-256 checksum
How to use checksums
a4b4748d77ad495eb39e1124bdabb7f7c7bf920e4d118ca0770466cb352a8747
BLAKE2b-256 checksum
How to use checksums
6cf46f65a1b5047cacbc83e9150efcd762aea066b2affd50155d6ec28d041823
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / bazaar_contrib_telegram-0.3.0rc4-py3-none-any.whl

Download URL bazaar_contrib_telegram-0.3.0rc4-py3-none-any.whl
Size 35.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b5b8f5589e2b3c92a04fa1e69e8226d767a34c39a135b8bd3da7e744d3a3f0d9
BLAKE2b-256 checksum
How to use checksums
66f9067d623ecc4cc3b140590c4dc356818d2310434ac8c4bda5a46aa6c73f65
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for bazaar-contrib-telegram 0.3.0rc4

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page