This release is a pre-release and may not be stable for production use.
Bazaar Compute Node
Collaborate with your Agents in the bazaar across compute nodes, through any interface, with any harness runtime.
在集市里与你的 Agent 们合作，透过任意界面与任意 Harness。
Documentation is coming soon...
Quick Start / 快速开始
Python 3.14+ is required.
需要 Python 3.14 或更高版本：
# Install / 安装
uv tool install bazaar-compute-node
bcn --version
# Upgrade / 升级
uv tool upgrade bazaar-compute-node
# Add an Agent / 添加 Agent
bcn agent add \
--name Tifa \
--channel telegram \
--runtime codex \
--set channel.token_env=BCN_TELEGRAM_TIFA_TOKEN
# Configure the runtime environment / 配置运行时环境
# Example file content / 示例文件内容:
# BCN_TELEGRAM_TIFA_TOKEN=replace-with-your-token
# Register the user-level system service / 注册用户级宿主机服务
bcn system-service install --env-file ~/.config/bcn/runtime.env
# Start the registered service / 启动已注册的服务
bcn system-service start
# Inspect registration and bcn health / 查看注册状态和 bcn 运行状态
bcn system-service status
# Restart or stop the registered service / 重启或停止已注册的服务
bcn system-service restart
bcn system-service stop
Service logs / 服务日志
Linux: journalctl --user -u bcn.service -f
macOS: tail -f ~/.bcn/system-service.log
Windows: Get-Content "$env:USERPROFILE\.bcn\system-service.log" -Wait
Features / 功能
- ✅ Done / 已完成
- 🚧 Working in progress / 开发中
Facilities / 通用能力
| Status / 状态 | Ability / 能力 |
|---|---|
| ✅ | Reminders / 定时器 |
| ✅ | Attachments / 附件 |
| ✅ | Multi-Agents / 多 Agent |
| 🚧 | Teams / 团队协作 |
Channels / 渠道
| Status / 状态 | Channel / 渠道 |
|---|---|
| ✅ | WeCom / 企业微信 |
| ✅ | Telegram |
| ✅ | Lark / 飞书 |
| 🚧 | GitHub |
| 🚧 | GitLab |
Harnesses
| Status / 状态 | Runtime / 运行时 |
|---|---|
| ✅ | Codex |
| ✅ | Claude Code |
| 🚧 | Pi |
| 🚧 | Hermes Agent |
| 🚧 | DeepSeek Harness |
Platforms / 平台
| Status / 状态 | Platform / 平台 |
|---|---|
| ✅ | Windows |
| ✅ | macOS |
| ✅ | Linux |
License / 许可证
This project is licensed under the AGPLv3. 本项目采用 AGPLv3 许可证。
Credits / 致谢
This project is inspired by raft.build. 本项目的灵感来自 raft.build。
1 maintainer
Release files for bazaar-compute-node 0.1.39rc4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bazaar_compute_node-0.1.39rc4.tar.gz | 282.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bazaar_compute_node-0.1.39rc4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 653.6 kB
Release files / bazaar_compute_node-0.1.39rc4.tar.gz
| Download URL | bazaar_compute_node-0.1.39rc4.tar.gz |
|---|---|
| Size | 282.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
866e0f023239690818ec848212e1bafca49110c21cab7d405121fe360d8bd96a
|
|
BLAKE2b-256 checksum How to use checksums |
1951541a09d42c795445bd0a8ed9553d11f6e260ea685f29b68e194e9c3d4aa8
|
| 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 Sep 3, 2026.
Transparency logRelease files / bazaar_compute_node-0.1.39rc4-py3-none-any.whl
| Download URL | bazaar_compute_node-0.1.39rc4-py3-none-any.whl |
|---|---|
| Size | 371.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11d6289463ae2c87a7e55ad5a7acdf5663600429e03b8d06f3ecba7b581dda77
|
|
BLAKE2b-256 checksum How to use checksums |
df8f374c93661f0ec336503cc43951d2b0f1ec9cc5caee4492ab7b8be8226b47
|
| 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 Sep 3, 2026.
Transparency log
