> This repo failed to process nice
Hey, our DB was temporarily down from the traffic, sorry about that. Could you try again if you get a chance?
Launch HN: Greptile (YC W24) - RAG on codebases that actually works
71–80 of 173 posts
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#72Earlier quoted context omitted.
We have a VS code extension in the store (also called "greptile"), feel free to check it out! Docs is a good idea but we haven't found a reliable enough scraper to add docs from a website. We were thinking it would be cool if you could drop in like "docs.stripe.com" and it automatically adds stripe docs to the context.
A JetBrains plugin might be worth looking at too. They are pretty popular in several language communities and still resisting the juggernaut that is VS Code.
Definitely, we currently have that on our roadmap for April, been cautious because IMO a bad IDE extension is way worse than no IDE extension.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#73Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#74[flagged]
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#75I've been looking for something like this, but local-only. Any plans to let people self-host and point at local repositories?
We’ve been grappling with making it local but two considerations 1. Haven’t figured out what should trigger updates. Every commit sounds crazy, every save would be perfect but too intensive also. 2. LLMs will not be self hosted. We haven’t been able to get the same results with any smaller LLMs To answer your questions we definitely want to make this available for local repos and ideally self hosted, on a technical l…
> Haven’t figured out what should trigger updates.
What triggers updates when it is not local?
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#76"We don't store any code on our servers after initial processing"
Are you storing the embedding vectors you've calculated from the code? If so, those are likely quite easily reversible - so I would still consider that source code stored on your servers from the point of view of a security audit.
As a result, I might actually prefer to have copies of my code stored on your servers if it resulted in faster performance.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#77I'd love to try it, but pretty much all my repos are >10mb. It's not because there is that much code, but because I am doing bioinformatics and the test files (for the unit tests) inflate the repo size. It would be great if there was a way to test it on just 1 large repo for perhaps a week or something, because I balk at the idea of spending $20 a month on something that I don't even know works well. This is importan…
pretty easy to fork your repo and remove all the test files.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#78"We don't store any code on our servers after initial processing" Are you storing the embedding vectors you've calculated from the code? If so, those are likely quite easily reversible - so I would still consider that source code stored on your servers from the point of view of a security audit. As a result, I might actually prefer to have copies of my code stored on your servers if it resulted in faster performance.
> embedding vectors you've calculated from the code? If so, those are likely quite easily reversible
I don't think embeddings are generally reversible... you're usually projecting onto a lower dimensional space, and therefore losing information.
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#79[deleted]
Re: Launch HN: Greptile (YC W24) - RAG on codebases that actually works
#80What does RAG stand for?
tried to explain it here: https://nux.ai/concepts/rag