Why Cline doesn't index your codebase
101–110 of 131 posts
Re: Why Cline doesn't index your codebase
#102Earlier quoted context omitted.
GPT 4.1 / mini / nano
As the context grows, all LLMs appear to turn into idiots, even just at 32k! > We evaluate 12 popular LLMs that claim to support contexts of at least 128K tokens. While they perform well in short contexts ( https://news.ycombinator.com/item?id=44107536
Re: Why Cline doesn't index your codebase
#103Warning: I don't know what this post does in the background but it definitely slows down Firefox 138 to the point that it is barely usable
Re: Why Cline doesn't index your codebase
#104Earlier quoted context omitted.
As the context grows, all LLMs appear to turn into idiots, even just at 32k! > We evaluate 12 popular LLMs that claim to support contexts of at least 128K tokens. While they perform well in short contexts ( https://news.ycombinator.com/item?id=44107536
This paper is slightly outdated by LLM model standards -- GPT 4.1 or Gemini 2.5 haven't been released at that time.
Ideally, isn't this a metric that should be included on all model cards? It seems like a crucial metric.
Re: Why Cline doesn't index your codebase
#105Re: Why Cline doesn't index your codebase
#106Earlier quoted context omitted.
Fair point Jeff -- you're right that we're still doing retrieval. The key distinction is how we retrieve. Traditional RAG for code uses vector embeddings and similarity search. We use filesystem traversal and AST parsing - following imports, tracing dependencies, reading files in logical order. It's retrieval guided by code structure rather than semantic similarity. I highly recommend checking out what the Claude Cod…
Don’t take this the wrong way, but did you use an LLM to generate this reply? The reply is good, but the writing style just piqued my curiosity.
Re: Why Cline doesn't index your codebase
#107Earlier quoted context omitted.
Fair point Jeff -- you're right that we're still doing retrieval. The key distinction is how we retrieve. Traditional RAG for code uses vector embeddings and similarity search. We use filesystem traversal and AST parsing - following imports, tracing dependencies, reading files in logical order. It's retrieval guided by code structure rather than semantic similarity. I highly recommend checking out what the Claude Cod…
Don’t take this the wrong way, but did you use an LLM to generate this reply? The reply is good, but the writing style just piqued my curiosity.
Re: Why Cline doesn't index your codebase
#108Cline is the most impressive agentic coder tool I’ve used and it seems to be getting better. I’ve learned to work with it to the extent where I can plan with it for 10-15 minutes, set it loose on my codebase, go get lunch, and then its diff is almost always completely on the money. You should commit often for those rare cases where it goes off the rails (which seems to happen less frequently now). Using Gemini 2.5 pr…
I've always wondered... Making agents edits (like vibe coding), all the tools I've tried (Cursor, Zed, VSCode) are pretty equal since most of the brains are in the underlying models themselves. But the killer app that keeps me using Cursor is Cursor Tab, which helps you WHILE you code. Whatever model they have for that works beautifully for me, whereas Zed's autocomplete model is the last thing that keeps me away fro…
Re: Why Cline doesn't index your codebase
#109Re: Why Cline doesn't index your codebase
#110Earlier quoted context omitted.
I use Cline within Cursor — best of both worlds!
What's the benefit? If you're paying $20/month for cursor you already get all the agentic coding as part of it.
I also don't love that Cursor generally plays "context compression" games since they have an incentive to keep their costs minimal. I just don't love any of these tools that try to be a bit too smart as a middleman between you and the LLM (where smart is often defined as 'try to save us the most money or be maximally efficient without the user noticing').
Cline also tries to be smart, but it's all for the benefit of the user. I like the transparent pricing -- you bring your own API key so you're paying the underlying API costs without a middle man markup.
Am I being pennywise and should I just use Cursor directly? Maybe...but I've found my Cline results to be generally better for the more complex queries.