Metadata-Version: 2.4
Name: bazaar-contrib-messages
Version: 0.3.0rc33
Summary: Message contracts, history, delivery and conversation services
License-Expression: Apache-2.0
License-File: LICENSE
Requires-Dist: bazaar-core~=0.3.0rc1
Requires-Dist: bazaar-contrib-channel~=0.3.0rc1
Requires-Dist: bazaar-contrib-storage~=0.3.0rc1
Requires-Dist: bazaar-contrib-sidecar~=0.3.0rc8
Requires-Dist: bazaar-contrib-schema~=0.3.0rc1
Requires-Dist: bazaar-contrib-audit~=0.3.0rc1
Requires-Dist: bazaar-contrib-timer~=0.3.0rc7
Requires-Dist: bazaar-contrib-legacy-node-migrations~=0.3.0rc1
Requires-Dist: jinja2>=3.1.6
Requires-Dist: pydantic>=2.12.0
Requires-Python: >=3.15
Project-URL: Repository, https://github.com/yuchanns/bazaar-compute-node
Description-Content-Type: text/markdown

# bazaar-contrib-messages

The message contracts are installed with the Node implementation.

```sh
bcn contrib add messages --enable messages-node
```

The corresponding entry in `config.toml`:

```toml
version = "5"

[[contribs]]
package = "bazaar-contrib-messages==0.3.*"
[[contribs.enabled]]
entry = "messages-node"
```

Use `bcc message check`, `bcc message read`, and `bcc message send` from an agent session.
