fix(memory): support arbitrary Qdrant document ids - #1350
Merged
Conversation
EmersonBraun
marked this pull request as ready for review
July 27, 2026 12:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
Qdrant accepts point IDs only as unsigned integers or UUIDs. AgentsKit RAG creates
chunk IDs such as
doc-1_chunk_0, which the Qdrant adapter previously forwardedunchanged and Qdrant rejected with HTTP 400.
Validation
pnpm --filter @agentskit/core buildpnpm --filter @agentskit/memory test— 209 passedpnpm --filter @agentskit/memory lintpnpm --filter @agentskit/memory builddoc-1_chunk_0git diff --checkThis draft does not authorize merge, release, tag, npm publication, or the external
Qdrant example pull request.