Repository navigation
Are you using Lucid or Qdrant memory backends in ZeroClaw? #10344
Audacity88
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Are you using Lucid or Qdrant memory backends in ZeroClaw?
RFC #9103 is deciding the boundary between authoritative memory storage and optional enrichment connectors before v0.9.0.
The current proposal does not remove Lucid or Qdrant by itself. It says we should first decide, with evidence, whether each integration should be removed, feature-gated, or retained behind a future enrichment seam.
Current code facts:
[storage.lucid.<alias>]config family. It shells out to a configured binary or the barelucidcommand onPATH.[storage.qdrant.<alias>]backend. It is omitted from one onboarding backend list, but gateway and ZeroCode picker surfaces still expose it as a storage kind.If you currently use Lucid or Qdrant in a real ZeroClaw deployment, please reply with:
Please put detailed evidence on RFC #9103 so the final decision is attached to the vote record: #9103
All reactions