Thank you! Glad to hear you're a fan of the syntax; the idea is that it be equally accessible to an experienced dev looking to save time and to a novice tackling their first-ever AI task.
If you have any further feedback later, I'll be more than grateful for it!
This is cool. Can I bring my own vector database? I'm currently prototyping and want to experiment with different solutions. Would be ideal if I could avoid needing to implement a few different SDKs.
Not quite yet—that's something we have on the roadmap, but at present vector databases can only really be searched through by combining a text-embedder module and a vector-db module (detail for both below). Any file processed through such a pipeline will be semantically searchable.
Very cool! Syntax looks very streamlined with no fluff. Looking forward to checking this out. Thanks for sharing.
Thank you! Glad to hear you're a fan of the syntax; the idea is that it be equally accessible to an experienced dev looking to save time and to a novice tackling their first-ever AI task.
If you have any further feedback later, I'll be more than grateful for it!
This is cool. Can I bring my own vector database? I'm currently prototyping and want to experiment with different solutions. Would be ideal if I could avoid needing to implement a few different SDKs.
Not quite yet—that's something we have on the roadmap, but at present vector databases can only really be searched through by combining a text-embedder module and a vector-db module (detail for both below). Any file processed through such a pipeline will be semantically searchable.
Text embedder: https://krixik-docs.readthedocs.io/latest/modules/ai_modules...
Vector DB: https://krixik-docs.readthedocs.io/latest/modules/database_m...
Please continue submitting suggestions and requests; we'll take them very much into account as evolving our roadmap.