Agenvo
Agenvo is a local temporary conversation log for agents that share a room path. It exposes only two actions:
agenvo say <room-path> --as <speaker> "message text"
agenvo hear <room-path> --as <speaker> [--after <message-id>]
Installation
cargo install agenvo-cli
npm install -g agenvo
pipx install agenvo
brew install xuanwo/tap/agenvo
<room-path> is a string. Plain values such as /tmp/agenvo-room are treated
as local filesystem rooms. OpenDAL URIs such as file:///tmp/agenvo-room,
fs:///tmp/agenvo-room, and s3://bucket/path/to/room are passed to OpenDAL.
The workspace follows a core/CLI split:
agenvo-coreimplements the protocol, storage operations, JSONL rendering, and tests.agenvo-cliis a thin command-line wrapper aroundagenvo-core.
say accepts message bodies from multiple sources:
agenvo say ~/.agenvo/review-001 --as user "inline message"
agenvo say ~/.agenvo/review-001 --as user --body "inline message"
agenvo say ~/.agenvo/review-001 --as user --body @msg.md
agenvo say ~/.agenvo/review-001 --as user --file msg.md
printf 'message from stdin\n' | agenvo say ~/.agenvo/review-001 --as user -
printf 'message from stdin\n' | agenvo say ~/.agenvo/review-001 --as user --stdin
Multiple body chunks can be passed with repeated --body or --file; Agenvo
joins chunks with newlines before writing one message.
Protocol
- A room path is the whole conversation boundary.
saywrites one immutable JSON object per message.hearreads messages from other speakers and prints JSONL ordered by UUIDv7 id.hear --after <id>is a client-side cursor filter.- Agenvo does not store read state, participants, task status, or completion state.
Stored objects use this layout:
<uuidv7>.<safe-speaker>.json
The JSON payload is:
{
"version": 1,
"id": "0197d8b2-0a91-7a20-86b2-31ce95b5dd54",
"speaker": "author",
"created_at": "2026-07-03T12:02:15Z",
"body": "Updated /path/to/design.md."
}
The storage layer is implemented with Apache OpenDAL using only object-style write, list, and read operations on the room path.
Metadata
Release files for agenvo 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| agenvo-0.2.0-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details |
| agenvo-0.2.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| agenvo-0.2.0-py3-none-manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| agenvo-0.2.0-py3-none-manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| agenvo-0.2.0-py3-none-macosx_11_0_x86_64.whl | Python 3 | none | macOS 11.0+ x86-64 | Details |
| agenvo-0.2.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
Total release size: 26.1 MB
Release files / agenvo-0.2.0-py3-none-win_arm64.whl
| Download URL | agenvo-0.2.0-py3-none-win_arm64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
000b848af3bf290af0211a545015f7f27bf8442fa427d283abb6c1557c050d05
|
|
BLAKE2b-256 checksum How to use checksums |
010e31eaa3f8844f7e84228dc51bb2462211d03de62c66c8099fe632d0659bda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency logRelease files / agenvo-0.2.0-py3-none-win_amd64.whl
| Download URL | agenvo-0.2.0-py3-none-win_amd64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d86aa6e23d7ffb893c26a767fb36c245478aa3fb3aedce7ab0e2eff6796def8b
|
|
BLAKE2b-256 checksum How to use checksums |
6a3b2537fb4258103e1377725c6e234772784dd6f7796e87c69fa5462b9ff10d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency logRelease files / agenvo-0.2.0-py3-none-manylinux2014_x86_64.whl
| Download URL | agenvo-0.2.0-py3-none-manylinux2014_x86_64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
f07c177f8d4c294b788cae0728160ac4a9abbd060c24995d22a5d7f282f287c0
|
|
BLAKE2b-256 checksum How to use checksums |
49a7dac1457736724bb094d5c77df8e594f8ab941a25ce22fb33745d266dbc4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency logRelease files / agenvo-0.2.0-py3-none-manylinux2014_aarch64.whl
| Download URL | agenvo-0.2.0-py3-none-manylinux2014_aarch64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
6e32a50757e73609587609305b9dd6baa97fc81f236a80c16a741056f26587fc
|
|
BLAKE2b-256 checksum How to use checksums |
58bda0de51b3c4eb7d14ddae20f07f39724f45ebd8d0b0a8729dc7bf3eedfaa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency logRelease files / agenvo-0.2.0-py3-none-macosx_11_0_x86_64.whl
| Download URL | agenvo-0.2.0-py3-none-macosx_11_0_x86_64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | Python 3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
0354b99dcfa8a981223d22b5ac179c678106bfb2b16c5e81a31e3685cabe33cf
|
|
BLAKE2b-256 checksum How to use checksums |
f1fc93f9e7cf5db50fa0fbe4cf35f28ca35ed0b2169c481f824f465de9ffa3df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency logRelease files / agenvo-0.2.0-py3-none-macosx_11_0_arm64.whl
| Download URL | agenvo-0.2.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f81ff407add62038a257a4f40ef3bc3c3530d4e896bf33d725669523b57586d9
|
|
BLAKE2b-256 checksum How to use checksums |
b83a41a8509b181cf163bf77cf621d34d8c5d2aaf844a8348acf190c7b0b35c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 3, 2026.
Transparency log