-
RIA Toolkit OSS v0.1.7 - Release Notes
StableSome checks failedBuild Sphinx Docs Set / Build Docs (push) Successful in 28sBuild Project / Build Project (3.10) (push) Successful in 3m46sTest with tox / Test with tox (3.10) (push) Failing after 5m22sTest with tox / Test with tox (3.12) (push) Successful in 18m39sBuild Project / Build Project (3.12) (push) Successful in 21m57sBuild Project / Build Project (3.11) (push) Successful in 22m6sTest with tox / Test with tox (3.11) (push) Successful in 20m10sreleased this
2026-05-26 16:02:38 -04:00 | 0 commits to main since this releaseRIA Toolkit OSS v0.1.7 - Release Notes
This release hardens the ria-agent register flow that connects on-prem RIA Agents to a RIA Hub instance. Newly registered agents now receive a friendly default name (e.g. swift-teal-falcon), and registration errors surface as actionable English instead of raw HTTP status codes. The release also fixes two real-world blockers seen in the field: Cloudflare-fronted hubs rejecting the CLI as a bot, and the CLI hanging forever when a hub is unreachable.
🌟 New Features
- Human-readable agent names — When --name is omitted, ria-agent register now auto-generates a memorable adjective-colour-animal name (e.g. swift-teal-falcon) via the new namegen module, instead of registering the agent with an empty string. Operators get a recognizable label for each agent without having to invent one up front.
- Structured registration error messages — ria-agent register now translates known hub responses into clear, actionable English. The CLI recognizes the documented failure reasons — invalid_key, expired, revoked, already_consumed — as well as rate-limit responses (HTTP 429), and explains what the user should do next, rather than dumping a raw HTTP 4xx body.
🚀 Enhancements
- --api-key help text now documents the per-user registration flow. The help string for ria-agent register --api-key describes the personal ria_reg_* registration key flow — minted from Settings → RIA Agents on the hub and shown once at mint time — which is now the preferred way to register agents.
- ria-agent register success output is more informative. On success, the CLI prints both the hub-assigned agent ID and the chosen name: Registered agent: (), so operators can correlate the local CLI run with the agent record on the hub.
🛠️ Performance Improvements
- None in this release.
🐛 Bug Fixes
- ria-agent register was being blocked by Cloudflare on hubs behind it. The CLI now sends an explicit User-Agent header — ria-agent/ (+https://riahub.ai/qoherent/ria-toolkit-oss) — instead of the default Python-urllib/, which Cloudflare's Browser Integrity Check rejects with an HTTP 403 (edge error code 1010). The version is read from package metadata so it tracks releases automatically.
- ria-agent register could hang indefinitely against an unreachable hub. Added an explicit 15-second timeout on the HTTP request to the hub. Previously, urllib's default behavior (no timeout) meant a stuck or unreachable hub would block the CLI forever; the command now fails fast with a clear error.
⚠️ Deprecations
- Shared [wac] API_KEY for agent registration is soft-deprecated in favor of per-user ria_reg_* registration keys minted from Settings → RIA Agents on the hub. The hub still accepts the legacy shared key for backwards compatibility, but the CLI documentation and tooling now point to the per-user flow as the recommended path.
🗑️ Removals
- No removals or interface changes in this release.
🚧 Known Issues
- None at time of release. Please report any issues via the project's issue tracker.
💡 Future Plans
- Continued improvements to the RIA Agent lifecycle (registration, key rotation, health reporting) as part of the broader RIA Hub ↔ on-prem agent integration.
ℹ️ Additional Information
SHA256 Checksums:
7a04816c54b40759f5692671ca8f400974bfdea5f55658fc42ed4d1a6526e44c ria_toolkit_oss-0.1.7-py3-none-any.whl 109929b93a99abd3d4a9b20dab5a0e029e5a1c3c7aa8e61c146437f75919505b ria_toolkit_oss-0.1.7.tar.gzChangelog: v0.1.6...v0.1.7
If you have any questions or concerns regarding this release, wish to provide feedback, or would like to suggest an improvement to the project, please feel free to contact the project maintainers.
Downloads