-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
knowledge2character
produces output file with wrong format.
#14
Comments
--EDIT: I just kept the Running into the same issue. Not sure whether I should keep either one of the two (documents or chunks) or whether it should be formatted differently |
-- I don't think so, When I used some doc like bitcoin doc converted to Markdown. Any help?? |
I removed the |
+1. @mintcloud 's solution worked, but is this the proper way to do it ? |
the same issue. |
same issue |
Apparently, the way the file is parsed is either incorrect or deprecated. It creates "documents" and "chunks," generating an object with two arrays. According to the current official documentation, "knowledge" is an array. I am unsure if it is correct to delete "documents," as I do not know its purpose, although it seems to maintain the knowledge map. Placing "chunks" in "knowledge" will probably work, as the knowledge is presumably there. https://elizaos.github.io/eliza/docs/core/characterfile/ Oficial example template Oficial documentation
Workaround
|
Due to the workaround mentioned here, I had to convert a PDF file to
knowledge
usingnode
.That created a file which holds an object (from folder2knowledge.js):
When running knowledge2character.js, it creates a new
character.json
file holding that object asknowledge
, but when running the agent withpnpm start --character="characters/<character>.character.json"
, it fails with a parsing error since it's expecting an array forknowledge
instead of an object.The text was updated successfully, but these errors were encountered: