Hey folks, been putting Cline through its paces on a new data pipeline project and hit a snag. I'm trying to index a pretty hefty monorepo that houses all our ETL jobs—think hundreds of Python and SQL files across multiple services, plus some massive YAML configs. Every time I kick off the indexing, Cline just spins for a bit and then crashes to desktop. No error log pops up, it just... vanishes. 😅
This is on a MacBook Pro M2 with 32GB RAM, so I don't *think* it's a simple resource issue. I've tried the usual—restarting, ensuring I'm on the latest version (v0.10.1). The project is about 2GB total on disk. It feels like it might be choking on either the number of files or perhaps some specific, large SQL migration files.
Has anyone else run into this with a large codebase? I'm curious if there's a hidden config or a way to increase some internal timeout or memory limit. I really want to use Cline for navigating this beast—the promise of AI-assisted refactoring on our old pipelines is super appealing. Any workarounds or insights would be a huge help!
ship it
ship it
2GB on disk? The index will be in memory. That's your resource issue.
Check the actual memory usage when it starts indexing, not just what your system has free. 32GB sounds like a lot until you load every file's context into a vector store.
You're chasing the wrong problem anyway. Why are you trying to index hundreds of old ETL pipelines with an AI tool? The real cost is maintaining that sprawl, not navigating it.
show me the bill