REVIEWS / AI CODING / OWNER INSIGHTS
🦉 WE READ 899 OWNER COMMENTS
Cline: what owners actually say
Owners appreciate Cline's balance of autonomy and control, but hit recurring configuration headaches around MCP server setup
What owners complain about
- MCP server connection errors COMMON
Multiple users report 'spawn npx enoent' errors when connecting MCP servers, meaning Cline can't locate npx on their system. This affects both WSL2 and macOS users and requires manual workarounds like specifying full paths to node.exe or using Node Version Manager.
- Free tier access problems FEW
At least one user found the 'get started for free' option simply not working and had to switch to providing their own API key to get Cline running.
- RAG approach limitations for large codebases SOME
A company building a similar tool concluded that chunking and vector similarity search are 'fundamentally not great approaches' for code retrieval, and users note Cline lacks the robust codebase indexing that Cursor offers.
- Context window constraints on big files SOME
Users note the effective context window is small for large files and requires manual workarounds like feeding 10-20k tokens of sample code, schema, and shared libraries to get useful output.
What owners love
- Good autonomy-control balance
Owners like that Cline sits between fully autonomous 'vibes coding' and manual control — one user said it found 'a good mix' that keeps them engaged in the process.
- Works with local models
Users were surprised and pleased that Cline performs well with local models like Devstral, not just cloud APIs.
- Flexible MCP server configuration
Once configured correctly, users successfully connect multiple MCP servers (e.g., OpenRouter, sequential-thinking) enabling access to a range of models through a single interface.
Surprising patterns
- Owners manually stash tens of thousands of reference files — schemas, sample SQL, Swagger docs, hand-written notes — in project directories to compensate for Cline's limited context, with one user estimating 80% of their indexed material is database-related rather than code.
- Configuration fixes are shared informally through GitHub issues and Stack Exchange with working JSON snippets but minimal explanation, suggesting the setup documentation has significant gaps.
- Some owners use Cline alongside Cursor rather than choosing one, indicating the tools serve different workflow needs even within the same project.
WHO SHOULD SKIP IT
Developers working on large, complex codebases with heavy inter-dependencies who expect robust codebase indexing out of the box — you'll likely need extensive manual context management and may find Cursor's indexing more mature.
Synthesised from 899 real owner comments across 5 platforms. Every point is grounded in the comments — no marketing, no AI guessing. How we do it →