shaial

The title says you replaced RAG, but ChromaFs is still querying Chroma on every command — you replaced RAG's interface, not RAG itself. Which is actually the more interesting finding: the retrieval was never the bottleneck, the abstraction was. Agents don't need better search. They need `grep`.

Link to Open Source Booking.com AI search example: https://github.com/shaialon/ai-search

I explain in detail what worked (and didn't work) for us at Orca Security building the AI search.

The video description has a link to an Open Source node.js repo with all the foundation for a good AI search!

Awesome! We built the simple version in-house, and hoped someone would productize it.

Congrats, this looks neat, and surely great to have more TS products in the ecosystem.

One plugin or feature that I will like to see in an AI gateway: *Cache* per unique request. So if I send the same request (system, messages, temperature, etc.), I will have the option to pull if from a cache (if it was already populated) and skip the LLM generation. This is much faster and cheaper - especially during development and testing.

I pushed ChatGPT to it’s coding limits in a javascript (Node.js) interview flow, and learned how it reasons about the various challenges it’s presented with.

I was blown away by what this magnificent AI can do - it seems ChatGPT can make the cut for a junior Node.js developer role :)

How would you improve the content?

I get your point. There is certainly a spectrum here. I can tell you (as the author) that for mission-critical assets with less 3rd party dependencies - I do see that most prefer to use the hard-coded or policy, or pull it via api per build in the CI/CD.

However for more dynamic websites (like blogs) that tend to have many 3rd party dependencies - It's very useful and effective to be able to update the policy with one click (or even automatically).

Thanks for your input! Subscribe to get future stuff