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.0rc3

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.0rc3
File Size Uploaded Provenance Actions
bazaar_contrib_telegram-0.3.0rc3.tar.gz 30.3 kB Without provenance Details for bazaar_contrib_telegram-0.3.0rc3.tar.gz

Built distribution (wheel)

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

Total release size: 64.8 kB

Release files / bazaar_contrib_telegram-0.3.0rc3.tar.gz

Download URL bazaar_contrib_telegram-0.3.0rc3.tar.gz
Size 30.3 kB
Tags Source
SHA-256 checksum
How to use checksums
283ef2051d58e708642bf28a00814e3607b1e6248706ee91df73bd217f5439a7
BLAKE2b-256 checksum
How to use checksums
1fc2eccfe057f4c29c766dd7310dff69703c727cd1bede25ec7ac41795d9ce5e
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.0rc3-py3-none-any.whl

Download URL bazaar_contrib_telegram-0.3.0rc3-py3-none-any.whl
Size 34.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
120b2b42b24f0ee273de5865d49123908d62fb3cb9bf29cc3b6111f512178020
BLAKE2b-256 checksum
How to use checksums
a41a406370bfc9ff6c6899085e53504737d1e4082f8e25ec26e68ad5b48cc1e7
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.0rc3

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