├── README.md ├── discord-recaps ├── README.md └── historical │ ├── 2024-12-28-recap.md │ ├── 2024-12-29-recap.md │ ├── 2024-12-30-recap.md │ ├── 2024-12-31-recap.md │ ├── 2025-01-01-recap.md │ ├── 2025-01-02-recap.md │ ├── 2025-01-03-recap.md │ ├── 2025-01-04-recap.md │ ├── 2025-01-05-recap.md │ ├── 2025-01-06-recap.md │ ├── 2025-01-07-recap.md │ ├── 2025-01-08-recap.md │ ├── 2025-01-09-recap.md │ └── 2025-01-10-13-recap.md ├── getting-started-new-coders ├── README.md └── installing-dev-essentials.md ├── mcp ├── README.md ├── mcp-server-from-github.md └── mcp-server-from-scratch.md ├── prompting ├── README.md └── custom instructions library │ ├── README.md │ └── cline-memory-bank.md └── tools ├── assets ├── CheckpointsButtons.png └── checkpointsDemo.gif ├── checkpoints.md └── cline-tools-guide.md /README.md: -------------------------------------------------------------------------------- 1 | # Cline Documentation 2 | 3 | Welcome to the Cline documentation - your comprehensive guide to using and extending Cline's capabilities. Here you'll find resources to help you get started, improve your skills, and contribute to the project. 4 | 5 | ## Getting Started 6 | 7 | - **New to coding?** We've prepared a gentle introduction: 8 | - [Getting Started for New Coders](getting-started-new-coders/README.md) 9 | 10 | ## Improving Your Prompting Skills 11 | 12 | - **Want to communicate more effectively with Cline?** Explore: 13 | - [Prompt Engineering Guide](prompting/README.md) 14 | - [Cline Memory Bank](prompting/custom%20instructions%20library/cline-memory-bank.md) 15 | 16 | ## Exploring Cline's Tools 17 | 18 | - **Understand Cline's capabilities:** 19 | - [Cline Tools Guide](tools/cline-tools-guide.md) 20 | 21 | - **Extend Cline with MCP Servers:** 22 | - [MCP Overview](mcp/README.md) 23 | - [Building MCP Servers from GitHub](mcp/mcp-server-from-github.md) 24 | - [Building Custom MCP Servers](mcp/mcp-server-from-scratch.md) 25 | 26 | ## Contributing to Cline 27 | 28 | - **Interested in contributing?** We welcome your input: 29 | - Feel free to submit a pull request 30 | - [Contribution Guidelines](CONTRIBUTING.md) 31 | 32 | ## Additional Resources 33 | 34 | - **Cline GitHub Repository:** [https://github.com/cline/cline](https://github.com/cline/cline) 35 | - **MCP Documentation:** [https://modelcontextprotocol.org/docs](https://modelcontextprotocol.org/docs) 36 | 37 | We're always looking to improve this documentation. If you have suggestions or find areas that could be enhanced, please let us know. Your feedback helps make Cline better for everyone. 38 | -------------------------------------------------------------------------------- /discord-recaps/README.md: -------------------------------------------------------------------------------- 1 | # Cline Discord Recaps 2 | 3 | Daily summaries of key discussions and insights from the Cline Discord community. 4 | 5 | Each recap includes the day's TLDR, releases, major takeaways, and notable community quotes. 6 | 7 | [Join the conversation](https://discord.gg/Mjyj2Sm3) 8 | 9 | --- 10 | 11 | ## Cline Discord Recap - January 7, 2025 12 | 13 | ### TLDR 14 | Discussions centered around MCP server implementations, file editing strategies, DeepSeek performance issues, and token usage optimization. Notable focus on memory management through MCP servers and improvements to code editing capabilities. Community shared experiences with various LLM providers and their cost-effectiveness. 15 | 16 | ### Key Discussions & Quotes 17 | 18 | **MCP Server Development & Usage** 19 | * Slava shared recommended Anthropic-supported MCP servers: 20 | * Sequential Thinking for CoT reasoning 21 | * Brave Search for web searching without docs 22 | * Time for reducing date hallucinations 23 | * Interest in Memory, PostgreSQL, and SQLite servers for memory management 24 | * "Through my testing, MCP server is more consistently able to use tools than writing custom instructions" (slava6298) [See insight](https://discord.com/channels/1275535550845292637/1275555786621325382/1326283571006148720) 25 | * Discussion around custom MCP implementations for changelog management and context handling 26 | 27 | **File Editing Improvements** 28 | * Discussion of unified diff strategies and improvements 29 | * Focus on reducing token usage while maintaining editing accuracy 30 | * Exploration of better diff strategies to minimize errors in code modifications 31 | * "MCP choice of STDIO looks like the WORST choice for error handling. When an app error it crash usually stdio. For sure need to add more strict error catching." (meb777) 32 | 33 | **DeepSeek Integration & Performance** 34 | * Community reporting mixed experiences with DeepSeek: 35 | * Some users experiencing significant slowdowns 36 | * Discussion of direct API usage vs OpenRouter 37 | * Cost advantages noted despite performance issues 38 | * "DeepSeek is 10-100x cheaper but at least 1-2x lazier than claude" (qpdv) 39 | 40 | **Token Usage & Cost Management** 41 | * Significant discussion around token consumption: 42 | * Reports of users spending $70-100+ daily on API usage 43 | * Comparison of different providers' cost-effectiveness 44 | * "I've spent almost $2k on API credits since november 1st alone" (thecryptojunky) 45 | * Community exploring ways to optimize token usage while maintaining productivity 46 | 47 | **Memory Management & Context** 48 | * Growing interest in knowledge graph implementations for Cline 49 | * Discussion of short-term vs long-term memory in MCP servers 50 | * "My need to get a functional knowledge graph for Cline and other agents is a top priority for me" (amazon1148) 51 | * Exploration of vector databases for efficient context storage 52 | 53 | **UI Development Approaches** 54 | * Community sharing strategies for multi-page UI development 55 | * Recommendations for using shadcn/ui components 56 | * Discussion of spreadsheet-to-UI conversion workflows 57 | * Tips for breaking down complex UI tasks into manageable pieces 58 | 59 | **Notable Tools & Integrations** 60 | * Discussion of AWS Bedrock model selection improvements 61 | * Exploration of browser automation tools with LLM integration 62 | * Interest in automated test generation capabilities 63 | * "I'm still waiting for LLM enabled test automation tools.. I want to basically describe what i want and it should go off and do stuff" (ismi84) 64 | 65 | **Community Insights** 66 | * Growing focus on practical applications beyond coding 67 | * Discussion of using Cline for documentation expansion and improvement 68 | * Exploration of non-traditional use cases 69 | * Strong emphasis on sharing implementation experiences and best practices 70 | 71 | ### Emerging Trends 72 | 1. Increased focus on memory management and context preservation 73 | 2. Growing interest in optimizing token usage and cost management 74 | 3. Continued evolution of file editing strategies 75 | 4. Expansion beyond traditional coding use cases 76 | 5. Strong emphasis on MCP server development and implementation 77 | 78 | [Join the conversation](https://discord.gg/cline) 79 | 80 | 81 | 82 | -------------------------------------------------------------------------------- /discord-recaps/historical/2024-12-28-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - December 28, 2024 2 | 3 | ### TLDR 4 | 5 | DeepSeek v3 continues to generate significant cost-performance discussion. Users actively share custom instruction strategies and MCP implementation patterns, with particular interest in Saoud's mention of "Cline in the cloud" possibilities. 6 | 7 | ### Releases 8 | 9 | * No new releases today. Community testing v3.0.8's improvements for diff edit handling, following Saoud's fix for DeepSeek v3's auto-formatting behavior. [View discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1322354105896800320) 10 | 11 | ### Key Discussions & Quotes 12 | 13 | * **DeepSeek v3 Performance & Costs** 14 | * "Been running Deepseek non stop for hours now; $0.67 - About 26.79M tokens" (eeinarsson) [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1322345334915207249) 15 | * "deepseek 3.0! Been using both a bit today -- if money were no object I'd say 3.5 sonnet, but when it is deepseek seems pretty close (though no image/browser use)" (nickbaumann98) [See comparison](https://discord.com/channels/1275535550845292637/1275535550845292640/1322344172170252289) 16 | * Context: Active comparisons between Sonnet and DeepSeek v3 capabilities, particularly around browser integration and image analysis features [See thread](https://discord.com/channels/1275535550845292637/1275535550845292640/1322413414164992061) 17 | 18 | * **Custom Instruction Strategies** 19 | * "IF you NOT follow this guidelines THE HUMAN WILL GET ANGRY" - Example of user instruction enforcement [See example](https://discord.com/channels/1275535550845292637/1275555786621325382/1299383749317886126) 20 | * Context: Community developing model-specific instruction sets to handle formatting behaviors [See strategies](https://discord.com/channels/1275535550845292637/1275535550845292640/1322334395562066012) 21 | * Related: Saoud's v3.0.8 update specifically addresses DeepSeek's auto-formatting behavior [See fix](https://discord.com/channels/1275535550845292637/1275535550845292640/1322327726509789305) 22 | 23 | * **MCP Implementation Patterns** 24 | * "having a cline be an mcp server, as in spawning off a minion cline to do a task, very interesting idea - I could see that being its own API, cline in the cloud" (saoudrizwan) [See concept](https://discord.com/channels/1275535550845292637/1316849926533287986/1322376027653148733) 25 | * "we literally just need a generic mcp client service that we can execute programmatically either via an sdk or cli command" (moonlife) [See proposal](https://discord.com/channels/1275535550845292637/1316849926533287986/1322391594573500448) 26 | * Context: Users actively exploring multi-instance setups for parallel processing [See implementation](https://discord.com/channels/1275535550845292637/1316849926533287986/1322374379161780224) 27 | 28 | [Join the conversation](https://discord.gg/Mjyj2Sm3) -------------------------------------------------------------------------------- /discord-recaps/historical/2024-12-29-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - December 29, 2024 2 | 3 | ### TLDR 4 | Community experiments with cost-optimized dual-model strategies, using DeepSeek for rapid development and Sonnet for architecture decisions. Users report impressive cost savings while developing strategies for rate limit management and exploring MCP server customization. 5 | 6 | ### Releases 7 | * No new releases today. Community continues exploring MCP server implementations and browser automation capabilities. 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **Cost-Optimization Strategies** 12 | * "$2 in 40 min with Claude. Haven't reached a $1 with Deepseek in 2 days... Claude is better though, but that much better?" (eeinarsson) [See analysis](https://discord.com/channels/1275535550845292637/1275535550845292640/1322932694623059979) 13 | * "I have had projects sitting idle because of the message limits and high costs of Claude. DeepSeek + Cline is bringing all of those projects to life instantly." (tony_42069) [See experience](https://discord.com/channels/1275535550845292637/1275535550845292640/1323118821569204225) 14 | * Context: Users developing sophisticated cost management strategies while maintaining quality output 15 | 16 | **MCP Server Development** 17 | * "The most integral part is workflow. If you rely on the agent it will lose track even on monolithic tasks" (ihatesirdavi) [See insight](https://discord.com/channels/1275535550845292637/1275535550845292640/1322956782007488582) 18 | * Discussion around implementing longer timeouts for MCP servers to handle complex tasks [View thread](https://discord.com/channels/1275535550845292637/1316849926533287986/1323128127357976677) 19 | * Context: Community actively exploring MCP server optimizations and sharing implementation patterns 20 | 21 | **Browser Integration Patterns** 22 | * Users discovering browser automation capabilities complement core development features [See thread](https://discord.com/channels/1275535550845292637/1275535550845292640/1323104017760391199) 23 | * Development of strategies for managing complex web interactions and testing scenarios 24 | * Context: Growing exploration of browser automation features for comprehensive development workflows 25 | 26 | [Join the conversation](https://discord.gg/cline) -------------------------------------------------------------------------------- /discord-recaps/historical/2024-12-30-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - December 30, 2024 2 | 3 | ### TLDR 4 | DeepSeek v3 continues to gain traction with users reporting significant cost savings and comparable performance to Claude. Community discussions centered around MCP server management, token optimization strategies, and multi-agent development approaches. 5 | 6 | ### Releases 7 | * No new releases today. Community actively exploring DeepSeek v3 integration and MCP server implementations. 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **DeepSeek V3 Integration & Performance** 12 | * "I am absolutely in shock and blown away at how powerful Cline + DeepSeek really is. This is the lethal combo I have been looking for." (tony_42069) [See feedback](https://discord.com/channels/1275535550845292637/1275535550845292640/1323315765205532744) 13 | * "I have had projects sitting idle because of the message limits and high costs of Claude. DeepSeek + Cline is bringing all of those projects to life instantly." (tony_42069) [See experience](https://discord.com/channels/1275535550845292637/1275535550845292640/1323118821569204225) 14 | * Context: Users actively discussing DeepSeek v3's context length limitations and exploring optimization strategies 15 | 16 | **MCP Server Development & Management** 17 | * "Additional note... it would be awesome if there was a cli command to restart all mcp hub servers, as well as to restart any particular one by name." (iammattwalters6022) [See suggestion](https://discord.com/channels/1275535550845292637/1316849926533287986/1323445550896386171) 18 | * "You can, for instance, create MCP servers that use tool calling with the assumption other servers are installed (in order to have separation of concerns and code reuse)" (iammattwalters6022) [See insight](https://discord.com/channels/1275535550845292637/1316849926533287986/1323466748506149026) 19 | * Context: Discussions around MCP server management, logging improvements, and service dependencies 20 | 21 | **Multi-Agent Development** 22 | * "Just created a 40 agent system that outputs 150,000 characters in one single prompt of an entire book or screen play" (.ben8888) [See experiment](https://discord.com/channels/1275535550845292637/1275535550845292640/1323412180900646933) 23 | * "Working on a long term, complex multi tier mcp core for long term memory retention, learning, and cross chat session cohesive memory" (thecryptojunky) [See development](https://discord.com/channels/1275535550845292637/1316849926533287986/1323526981618503701) 24 | * Context: Users exploring sophisticated multi-agent architectures for various use cases 25 | 26 | **Token Optimization & Prompting Strategies** 27 | * "Apply the inverse square law to token optimization... The less input thats concise and detailed as possible = more and detailed accurate output" (ihatesirdavi) [See strategy](https://discord.com/channels/1275535550845292637/1275535550845292640/1323262536665268346) 28 | * Discussion around maintaining context across conversations and optimizing token usage [View thread](https://discord.com/channels/1275535550845292637/1275535550845292640/1323394615927242753) 29 | * Context: Community sharing techniques for efficient token usage and effective prompting 30 | 31 | [Join the conversation](https://discord.gg/cline) 32 | -------------------------------------------------------------------------------- /discord-recaps/historical/2024-12-31-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - December 31, 2024 2 | 3 | ### TLDR 4 | Community discussions focused heavily on DeepSeek v3 performance comparisons, MCP server innovations, and terminal output optimization. Notable developments include a new moondream.ai MCP server for local image processing and discussions around LLM observability tools. 5 | 6 | ### Releases 7 | * v3.0.12 released with fixes for DeepSeek's context window limit and improvements to diff editing functionality [See announcement](https://discord.com/channels/1275535550845292637/1275535550845292640/1323852226468515891) 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **DeepSeek V3 Performance & Pricing** 12 | * "Claude is still king, but I'm shocked at what deepseek can do for less than a penny" (saoudrizwan) [See insight](https://discord.com/channels/1275535550845292637/1275535550845292640/1323846298784501820) 13 | * "Deepseek is 53x cheaper" (irreverentbanana) [See comparison](https://discord.com/channels/1275535550845292637/1275535550845292640/1323838901143474237) 14 | * Context: Users actively discussing DeepSeek's price advantage while noting its limitations compared to Claude, particularly around context window and diff editing reliability 15 | 16 | **MCP Server Innovations** 17 | * "Made another MCP server which gives Cline access to moondream.ai specifically a local small vision model which you can run on any device" (night.trek) [See announcement](https://discord.com/channels/1275535550845292637/1316849926533287986/1323830027565006908) 18 | * Discussion around implementing LLM tracing and observability tools like Langfuse and Arize Phoenix [See proposal](https://discord.com/channels/1275535550845292637/1321367716820422657/1323860549280206889) 19 | * Context: Community actively developing new MCP servers and exploring tools for better monitoring and analysis 20 | 21 | **Terminal & Output Optimization** 22 | * "I noticed that some commands like `npm test` spit out an insane number of tokens because of the constantly updating progress bars" (mrubens) [See observation](https://discord.com/channels/1275535550845292637/1321367716820422657/1323885346337067010) 23 | * Proposal to use LLMs for compressing terminal output and test logs [See discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1323895642489356309) 24 | * Context: Users exploring creative solutions for managing token usage with verbose terminal output 25 | 26 | **Multi-Instance & Collaboration** 27 | * "I used to open up multiple VS Code windows to run multiple Clines until I realized that you can open up multiple 'tabs'" (eddy028) [See tip](https://discord.com/channels/1275535550845292637/1316849926533287986/1323729861495230524) 28 | * Discussion around orchestrating multiple Cline instances with shared context [See thread](https://discord.com/channels/1275535550845292637/1316849926533287986/1323731362275921941) 29 | * Context: Community exploring patterns for running multiple Cline instances effectively 30 | 31 | **Prompt Engineering & System Improvements** 32 | * "Half of the work in putting Cline together has been the prompting, it's equally as important as the code" (saoudrizwan) [See insight](https://discord.com/channels/1275535550845292637/1321367716820422657/1323871002043617361) 33 | * Discussion about creating a framework for data-driven prompt engineering improvements [See thread](https://discord.com/channels/1275535550845292637/1321367716820422657/1323871002043617361) 34 | * Context: Focus on systematic approach to improving prompts through data and testing 35 | 36 | [Join the conversation](https://discord.gg/cline) 37 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-01-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 1, 2025 2 | 3 | ### TLDR 4 | Community discussions centered around innovative MCP server developments, terminal output optimization proposals, and continued exploration of DeepSeek v3 integration. Notable developments include a new moondream.ai MCP for local image processing and proposals for terminal output filtering improvements. 5 | 6 | ### Releases 7 | * No new releases today. Community continues exploring v3.0.12's improvements and discussing potential enhancements. 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **MCP Server Innovations & Proposals** 12 | * "Made another MCP server which gives Cline access to moondream.ai specifically a local small vision model which you can run on any device" (night.trek) [See announcement](https://discord.com/channels/1275535550845292637/1316849926533287986/1323830027565006908) 13 | * "I was thinking about developing an MCP server to use with Cline that would enable me to connect to a local, web-based voice interface" (jdo300) [See proposal](https://discord.com/channels/1275535550845292637/1316849926533287986/1324086243335864320) 14 | * Context: Community actively developing specialized MCP servers for enhanced capabilities and exploring voice interface integration 15 | 16 | **Terminal Output Optimization** 17 | * "There's a lot I have in mind about making the terminal output less verbose, so many common symbols and strings we can easily parse out" (saoudrizwan) [See discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1324127297036353590) 18 | * Proposal for creating filterable terminal output templates [View suggestion](https://discord.com/channels/1275535550845292637/1321367716820422657/1324228575129374790) 19 | * Context: Focus on reducing token usage from verbose terminal output through smart filtering 20 | 21 | **Multi-Instance & Watch Mode Concepts** 22 | * "I actually think about a `watch-mode` for one tab and the `manual mode` for other" (sang.dang) [See concept](https://discord.com/channels/1275535550845292637/1316849926533287986/1324316319499288646) 23 | * Discussion around running multiple Cline instances with different responsibilities [View thread](https://discord.com/channels/1275535550845292637/1316849926533287986/1324087224257740862) 24 | * Context: Users exploring patterns for parallel development workflows 25 | 26 | **Community Development & Benchmarking** 27 | * "Has there been any discussion about evaluating Cline with SWE benchmarks like SWE-Bench?" (.dorkknight) [See discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1324126643865784360) 28 | * "It would be great if we could opt into some sort of data sharing mechanism" (valdis101) [See proposal](https://discord.com/channels/1275535550845292637/1321367716820422657/1324012307528810496) 29 | * Context: Growing interest in quantitative evaluation and community-driven improvements 30 | 31 | **Long-Term Memory & Project Context** 32 | * "Has anyone made an attempt at creating an MCP that uses something like a local Redis server to enhance the memory of your LLM through Cline" (ndcollins81) [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1324104597438201886) 33 | * Discussion around vectorized storage and cross-project memory retention [View thread](https://discord.com/channels/1275535550845292637/1316849926533287986/1324201088148308051) 34 | * Context: Community exploring solutions for improved context retention and project understanding 35 | 36 | [Join the conversation](https://discord.gg/cline) 37 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-02-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 2, 2025 2 | 3 | ### TLDR 4 | Community discussions centered around DeepSeek V3 performance and pricing comparisons, model behavior observations, and new MCP server developments. Notable developments include a new Postman/Newman MCP server release and ongoing work on knowledge graph memory solutions. 5 | 6 | ### Releases 7 | * No new releases today. Community actively exploring and comparing different LLM providers through Cline. 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **DeepSeek V3 Performance & Provider Comparisons** 12 | * "DeepSeek-v3 is truly a tough competition to claude 3.5 sonnet" (kaustav.gh) [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1324449072731525241) 13 | * "openrouter will only provide 64k for deepseek regardless of the provider it uses" (joewilson) [See explanation](https://discord.com/channels/1275535550845292637/1275535550845292640/1324708646302515221) 14 | * Context: Community exploring different providers (Fireworks, DeepInfra, OpenRouter) with detailed price comparisons - Fireworks offering 128k context at $0.9/M tokens vs original DeepSeek at $0.14/M tokens 15 | 16 | **Model Behavior & Performance Observations** 17 | * "Gemini 1206 seems to really struggle when I use it with cline... It loves to say what it's going to do, first outputting the diffs before applying etc" (irreverentbanana) [See observation](https://discord.com/channels/1275535550845292637/1275535550845292640/1324409881230577677) 18 | * "I've been switching between sonnet and deepseek when I have issues with one :/, I like how easy it is to switch even within the same chat context" (ai_joe) [See feedback](https://discord.com/channels/1275535550845292637/1275535550845292640/1324366372444049419) 19 | * Context: Users sharing experiences with different models and their unique characteristics when used with Cline 20 | 21 | **MCP Server Developments & Memory Solutions** 22 | * "Morning everyone. Yesterday I published a small MCP Server that allows you to run Postman/Newman collections from Cline" (shannonlal) [See announcement](https://discord.com/channels/1275535550845292637/1316849926533287986/1324378674316709930) 23 | * "Has anyone tried this out? Knowledge Graph Memory Server: A basic implementation of persistent memory using a local knowledge graph" (mark.burggraf) [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1324426131352453194) 24 | * Context: Growing ecosystem of MCP servers with focus on testing tools and persistent memory solutions 25 | 26 | [Join the conversation](https://discord.gg/cline) 27 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-03-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 3, 2025 2 | 3 | ### TLDR 4 | Community discussions highlighted innovative proposals for model review systems, documentation tools, and MCP server developments. Notable focus on DeepSeek v3 provider performance issues and cost comparisons, with significant engagement around memory management and sequential thinking approaches. 5 | 6 | ### Releases 7 | * No new releases today. Community actively exploring provider options and MCP server implementations. 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **Model Review & Quality Assurance** 12 | * "I wonder how effective it would be if Cline allowed for a 'reviewer' model that gets called once the primary model considers the task complete" (valdis101) [See proposal](https://discord.com/channels/1275535550845292637/1275535550845292640/1324728858209030265) 13 | * Context: Strong community interest in multi-model approaches for improved code quality and reliability 14 | 15 | **Documentation Tools & Knowledge Management** 16 | * "Anyone used Greptile? I think it's fricking amazing... It's a solution for helping you understand your codebase semantically" (righthonrevrum) [See tool](https://discord.com/channels/1275535550845292637/1316849926533287986/1324811296683593798) 17 | * "For those interested, you can convert docs to MD files using Jina AI" (slava6298) [See suggestion](https://discord.com/channels/1275535550845292637/1316849926533287986/1324810317636567111) 18 | * Context: Community actively exploring tools for improved code understanding and documentation management 19 | 20 | **MCP Server Innovations** 21 | * "We should come together and make an official cline documentation MCP server" (night.trek) [See proposal](https://discord.com/channels/1275535550845292637/1316849926533287986/1324820087399514153) 22 | * "Dm. I can get an mvp up with my sequential logic" (ihatesirdavi) [See offer](https://discord.com/channels/1275535550845292637/1316849926533287986/1324829905825038456) 23 | * Context: Strong community support for collaborative MCP development efforts 24 | 25 | **Provider Performance & Cost Analysis** 26 | * "exclude fireworks from the providers list if you don't want your budget to melt without even realizing you're using it 😅" (_123321_) [See tip](https://discord.com/channels/1275535550845292637/1275535550845292640/1324786731127672874) 27 | * "When it works it gives great elaborate solutions almost as good as 3.5 sonnet. However, when its down it gives connection error" (kaustav.gh) [See feedback](https://discord.com/channels/1275535550845292637/1275555786621325382/1324789681510027325) 28 | * Context: Users sharing experiences and cost-saving strategies across different providers 29 | 30 | **Sequential Thinking & Memory Management** 31 | * "I've found the implementations to be more rock solid when it uses it but it's a ton of tokens" (intheclouddan) [See feedback](https://discord.com/channels/1275535550845292637/1275555786621325382/1324801334616133702) 32 | * "Has anyone gotten cross-session 'memory' to work reliably, meaning persistently and consistently, yet?" (ismi84) [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1324808462752022619) 33 | * Context: Community exploring trade-offs between implementation quality and resource usage 34 | 35 | **Browser Integration & Testing** 36 | * "Is there some MCP to feed the console.logs from the browser to the context?" (np_lracz) [See question](https://discord.com/channels/1275535550845292637/1316849926533287986/1324964027968913471) 37 | * "you can have it set the output up to your webui and use browser tool to view both your site and the results of tests" (ihatesirdavi) [See suggestion](https://discord.com/channels/1275535550845292637/1316849926533287986/1324832487242862663) 38 | * Context: Growing interest in browser integration for testing and debugging workflows 39 | 40 | [Join the conversation](https://discord.gg/cline) 41 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-04-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 4, 2025 2 | 3 | ### TLDR 4 | Discussions around empathy in prompt engineering sparked by Goldman Sachs CIO's insights, impressive user success stories, and a new contribution for Vertex AI integration highlighted the day's conversations. 5 | 6 | ### Key Discussions & Quotes 7 | 8 | **Empathy in Prompt Engineering** 9 | * Goldman Sachs CIO Marco Argenti shared that the key to good prompts is "Empathy" - emphasizing the importance of understanding AI's capabilities and providing clear boundaries [See discussion](https://discord.com/channels/1275535550845292637/1275555786621325382/1325168940971720747) 10 | * Community explored how this approach leads to more reliable and accurate responses [View insights](https://discord.com/channels/1275535550845292637/1275555786621325382/1325371423501324362) 11 | 12 | **Impressive User Success** 13 | * "Cline is absolutely great and I am *immensely* in your debt for your work. I'm not a frontend developer and I've made a whole freakin' website with this thing" (conquat) [See testimonial](https://discord.com/channels/1275535550845292637/1275535550845292640/1325331137584693259) 14 | * Users noting significant productivity shifts: "Now if said feature takes more than 15 minutes to complete you feel slow and unproductive" (valdis101) [See insight](https://discord.com/channels/1275535550845292637/1275535550845292640/1325140211742806091) 15 | 16 | **New Integrations & Features** 17 | * Community member contributed a PR to add Vertex AI support, expanding workplace compatibility [See PR](https://discord.com/channels/1275535550845292637/1321367716820422657/1325352673158889523) 18 | * Memory Bank feature receiving positive feedback for improving consistency in development workflows [View discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1325395793175252994) 19 | 20 | [Join the conversation](https://discord.gg/cline) 21 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-05-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 5, 2025 2 | 3 | ### TLDR 4 | Major discussions centered around DeepSeek V3 performance issues and pricing changes, significant contributions including new OpenAI-compatible endpoint features, and innovative MCP server developments for memory management and automation. 5 | 6 | ### Key Discussions & Quotes 7 | 8 | **DeepSeek V3 Performance & Pricing Concerns** 9 | * "Ok everyone be aware Deepseek through openrouter has new providers which are expensive and slow" (night.trek) [See announcement](https://discord.com/channels/1275535550845292637/1275535550845292640/1325629990443679814) 10 | * "used to pay .0003 a call (roughly) now its 0.08" (uke__uke) [See pricing discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1325489994961256458) 11 | * Community actively discussing alternatives and workarounds, including direct API usage and provider selection 12 | * Context: Significant performance degradation and price increases causing community to reevaluate their model choices 13 | 14 | **Notable Contributions & Features** 15 | * New PR for OpenAI-compatible endpoint features including prompt caching and computer use [View PR](https://discord.com/channels/1275535550845292637/1275535550845292640/1325645945656049706) 16 | * Work on supporting non-streaming models through OpenAI-compatible endpoints [See development](https://discord.com/channels/1275535550845292637/1321367716820422657/1325648751959867496) 17 | * Context: Community actively contributing to improve compatibility and feature set 18 | 19 | **MCP Server Innovations** 20 | * Development of long-term memory solutions using vectorized storage [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1325670123897622598) 21 | * "I've been stuck some type errors for type script. I essentially took the 7 file based context prompt and built the mcp memory servers around that idea" (thecryptojunky) [See implementation details](https://discord.com/channels/1275535550845292637/1316849926533287986/1325670123897622598) 22 | * Context: Growing focus on enhancing context retention and error handling through specialized MCP servers 23 | 24 | **Enterprise Usage & ROI** 25 | * "One project I did with about $200 in AI spend resulted in like an additional $1.75M in revenue" (flyryan) [See ROI discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1325649630930669633) 26 | * "It make people who can't code, get by. It makes people who can code a little good. And it makes people who can code for real, fast" [See insight](https://discord.com/channels/1275535550845292637/1321367716820422657/1325649900246925453) 27 | * Context: Growing evidence of significant business value and productivity gains 28 | 29 | **Documentation & Context Management** 30 | * "Just figured something out... if I make a reference say to some service or library in my document I can annotate that document with the URL to the API documentation" (r3d91ll_22633) [See tip](https://discord.com/channels/1275535550845292637/1316849926533287986/1325528153942392933) 31 | * Discussion around maintaining project context and documentation through automated updates 32 | * Context: Community developing best practices for maintaining project context and documentation 33 | 34 | [Join the conversation](https://discord.gg/cline) 35 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-06-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 6, 2025 2 | 3 | ### TLDR 4 | Major release of Cline v3.1.0 introduced workspace checkpoints functionality, allowing users to restore to previous points in tasks. Community discussions centered around this new feature, DeepSeek V3 performance issues, context management strategies, and innovative approaches to MCP server implementations. 5 | 6 | ### Releases 7 | * Cline v3.1.0 released with new checkpoints feature, enabling workspace snapshots after each step and providing change overviews for auto-approve mode. [View announcement](https://discord.com/channels/1275535550845292637/1275545643166994505/1325937324512645233) 8 | 9 | ### Key Discussions & Quotes 10 | 11 | **New Checkpoints Feature Reception** 12 | * "omg a checkpoint feature released? definitely my most wanted I will def. be playing with this thank you Cline sweeeeet!" (yellow_bat_coffee) [See reaction](https://discord.com/channels/1275535550845292637/1275535550845292640/1326038171263303701) 13 | * "This just means we can go back to being sloppier about not needing to commit after every single feature" (valdis101) [See comment](https://discord.com/channels/1275535550845292637/1275535550845292640/1325938934244577300) 14 | * Context: Strong positive community response to the new checkpoints feature, particularly for its potential to improve workflow flexibility 15 | 16 | **DeepSeek V3 Performance Concerns** 17 | * "Deepseek still buggin?? omg its slow" (pierrunoyt) [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1325835266677669890) 18 | * "Im officially back to Sonnet and gave up on deepseek. The mental peace of mind is worth the higher cost" (tony_42069) [See feedback](https://discord.com/channels/1275535550845292637/1275535550845292640/1325896531793940551) 19 | * Context: Community experiencing significant latency issues with DeepSeek V3, particularly through various providers, leading some users to return to Claude 3.5 Sonnet despite higher costs 20 | 21 | **Context Management & Documentation** 22 | * "I've been taking a general 'progressContext' and got it slightly down, but i have the AI write a 'current process or workflow' with detailed information and instructions that's easier for cline to read" (thecryptojunky) [See approach](https://discord.com/channels/1275535550845292637/1275555786621325382/1325932644453711882) 23 | * Innovative project shared for automatically generating contextual rules files using embedding models and vector databases [View project](https://github.com/wheattoast11/cursor-context) 24 | * Context: Growing focus on sophisticated context management strategies to improve AI assistance quality and consistency 25 | 26 | **MCP Server Developments** 27 | * Discussion around OpenAPI vs MCP implementation differences [See explanation](https://discord.com/channels/1275535550845292637/1316849926533287986/1325835586333966336) 28 | * "MCP allows you to host it yourself" vs cloud provider restrictions (night.trek) [See insight](https://discord.com/channels/1275535550845292637/1316849926533287986/1325888979878547650) 29 | * Context: Community exploring various MCP server implementations for enhanced functionality and self-hosting capabilities 30 | 31 | **Prompt Engineering & Instructions** 32 | * Introduction of "Chat Mode" functionality through .clinerules to prevent file modifications during conversations [See implementation](https://discord.com/channels/1275535550845292637/1275555786621325382/1325831538633478168) 33 | * Discussion around KISS methodology in prompts and its impact on code quality [View discussion](https://discord.com/channels/1275535550845292637/1275555786621325382/1325929914708394005) 34 | * Context: Ongoing refinement of prompt strategies and instruction patterns for improved AI interaction 35 | 36 | **Frontend Development Practices** 37 | * "3.5 sonnet is cracked with React components, but moreso with 3.5 sonnet you can paste screenshots and take advantage of browser use" (nickbaumann98) [See tip](https://discord.com/channels/1275535550845292637/1275555786621325382/1325999009915211776) 38 | * Emphasis on breaking down frontend tasks into smaller, manageable pieces and providing clear error context 39 | * Context: Community sharing best practices for frontend development with AI assistance 40 | 41 | **Notable Tools & Features** 42 | * Discussion around cursor-context tool for automated context generation [View project](https://discord.com/channels/1275535550845292637/1321367716820422657/1326046380447371358) 43 | * Exploration of various MCP servers for API documentation and knowledge management [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1325852746938712086) 44 | * Context: Growing ecosystem of tools and features to enhance Cline's capabilities 45 | 46 | [Join the conversation](https://discord.gg/cline) 47 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-07-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 7, 2025 2 | 3 | ### TLDR 4 | Discussions centered around MCP server implementations, file editing strategies, DeepSeek performance issues, and token usage optimization. Notable focus on memory management through MCP servers and improvements to code editing capabilities. Community shared experiences with various LLM providers and their cost-effectiveness. 5 | 6 | ### Key Discussions & Quotes 7 | 8 | **MCP Server Development & Usage** 9 | * Slava shared recommended Anthropic-supported MCP servers: 10 | * Sequential Thinking for CoT reasoning 11 | * Brave Search for web searching without docs 12 | * Time for reducing date hallucinations 13 | * Interest in Memory, PostgreSQL, and SQLite servers for memory management 14 | * "Through my testing, MCP server is more consistently able to use tools than writing custom instructions" (slava6298) [See insight](https://discord.com/channels/1275535550845292637/1275555786621325382/1326283571006148720) 15 | * Discussion around custom MCP implementations for changelog management and context handling 16 | 17 | **File Editing Improvements** 18 | * Discussion of unified diff strategies and improvements 19 | * Focus on reducing token usage while maintaining editing accuracy 20 | * Exploration of better diff strategies to minimize errors in code modifications 21 | * "MCP choice of STDIO looks like the WORST choice for error handling. When an app error it crash usually stdio. For sure need to add more strict error catching." (meb777) 22 | 23 | **DeepSeek Integration & Performance** 24 | * Community reporting mixed experiences with DeepSeek: 25 | * Some users experiencing significant slowdowns 26 | * Discussion of direct API usage vs OpenRouter 27 | * Cost advantages noted despite performance issues 28 | * "DeepSeek is 10-100x cheaper but at least 1-2x lazier than claude" (qpdv) 29 | 30 | **Token Usage & Cost Management** 31 | * Significant discussion around token consumption: 32 | * Reports of users spending $70-100+ daily on API usage 33 | * Comparison of different providers' cost-effectiveness 34 | * "I've spent almost $2k on API credits since november 1st alone" (thecryptojunky) 35 | * Community exploring ways to optimize token usage while maintaining productivity 36 | 37 | **Memory Management & Context** 38 | * Growing interest in knowledge graph implementations for Cline 39 | * Discussion of short-term vs long-term memory in MCP servers 40 | * "My need to get a functional knowledge graph for Cline and other agents is a top priority for me" (amazon1148) 41 | * Exploration of vector databases for efficient context storage 42 | 43 | **UI Development Approaches** 44 | * Community sharing strategies for multi-page UI development 45 | * Recommendations for using shadcn/ui components 46 | * Discussion of spreadsheet-to-UI conversion workflows 47 | * Tips for breaking down complex UI tasks into manageable pieces 48 | 49 | **Notable Tools & Integrations** 50 | * Discussion of AWS Bedrock model selection improvements 51 | * Exploration of browser automation tools with LLM integration 52 | * Interest in automated test generation capabilities 53 | * "I'm still waiting for LLM enabled test automation tools.. I want to basically describe what i want and it should go off and do stuff" (ismi84) 54 | 55 | **Community Insights** 56 | * Growing focus on practical applications beyond coding 57 | * Discussion of using Cline for documentation expansion and improvement 58 | * Exploration of non-traditional use cases 59 | * Strong emphasis on sharing implementation experiences and best practices 60 | 61 | ### Emerging Trends 62 | 1. Increased focus on memory management and context preservation 63 | 2. Growing interest in optimizing token usage and cost management 64 | 3. Continued evolution of file editing strategies 65 | 4. Expansion beyond traditional coding use cases 66 | 5. Strong emphasis on MCP server development and implementation 67 | 68 | [Join the conversation](https://discord.gg/cline) 69 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-08-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 8, 2025 2 | 3 | ### TLDR 4 | 5 | DeepSeek performance issues dominate discussions, leading to exploration of alternatives like Gemini 2.0 Flash. Active discussions around prompt engineering, project planning strategies, and improvements to file editing capabilities through new diff strategies. 6 | 7 | ### Releases 8 | 9 | * No new releases today. Community actively testing v3.1.0's checkpoints feature while discussing improvements to diff edit handling. [View discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1326667571755352196) 10 | 11 | ### Key Discussions & Quotes 12 | 13 | * **DeepSeek Performance & Alternatives** 14 | * "deepseek has been having issues for a few days... it changes throughout the day" (ronnie69s) [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1326575235197304892) 15 | * "I've just had to accept that DeepSeek is slow in the evenings, but I no longer let it block me, I move on to other tasks" (amazon1148) [See strategy](https://discord.com/channels/1275535550845292637/1275535550845292640/1326756834945798184) 16 | * Context: Users adapting workflows and exploring alternatives like Gemini 2.0 Flash due to persistent performance issues [See alternatives](https://discord.com/channels/1275535550845292637/1275535550845292640/1326748185376591893) 17 | 18 | * **Project Planning & Documentation** 19 | * "I often start by asking it to read documentation that is important to understand" (amazon1148) [See approach](https://discord.com/channels/1275535550845292637/1275555786621325382/1326762073107071037) 20 | * "Write a document that describes the project in these phases, then I am constantly iterating and updating" (amazon1148) [See strategy](https://discord.com/channels/1275535550845292637/1275555786621325382/1326762359481565224) 21 | * Context: Community sharing effective strategies for project planning and documentation with Cline [See discussion](https://discord.com/channels/1275535550845292637/1275555786621325382/1326759462349836399) 22 | 23 | * **File Editing Improvements** 24 | * "It's very complex lol, specially evaluating the output of the edit since you need to predict how the edit should look like" (irreverentbanana) [See challenge](https://discord.com/channels/1275535550845292637/1321367716820422657/1326589193316601958) 25 | * "with this method I'm working on it seems easy to just ask a model 'hey which one you like the best' and then let it pick" (irreverentbanana) [See approach](https://discord.com/channels/1275535550845292637/1321367716820422657/1326589516592447611) 26 | * Context: Active development on improving diff editing reliability and validation strategies [See progress](https://discord.com/channels/1275535550845292637/1321367716820422657/1326665698272870440) 27 | 28 | * **MCP Implementation Patterns** 29 | * "MCP is a protocol. That wraps function calling so don't over complicate it" (meb777) [See insight](https://discord.com/channels/1275535550845292637/1316849926533287986/1326612854878634114) 30 | * "Which knowledge graph mcp supposed to be used atm? I am looking for persistence storage" (np_lracz) [See question](https://discord.com/channels/1275535550845292637/1316849926533287986/1326602856656273598) 31 | * Context: Community exploring knowledge graph implementations and memory persistence solutions [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1326618694599573595) 32 | 33 | [Join the conversation](https://discord.gg/cline) 34 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-09-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 9, 2025 2 | 3 | ### TLDR 4 | Discussions focused heavily on model performance comparisons (particularly DeepSeek vs Claude), MCP server implementation challenges, memory management strategies, and file editing improvements. Notable emphasis on cost optimization and the growing importance of the memory bank feature. 5 | 6 | ### Key Discussions & Quotes 7 | 8 | **Model Performance & Cost Optimization** 9 | * "DeepSeek is really good compared to sonnet.. sonnet was bumping its head and going nowhere on a couple of problems where deepseek waltzed right in and fixed it" (caitlyntje) [See insight](https://discord.com/channels/1275535550845292637/1275535550845292640/1327067604334022696) 10 | * "At this point I have removed Claude from my workflow except for very complicated problems or times deepseek is stuck due to crazy price" (xersees) [See strategy](https://discord.com/channels/1275535550845292637/1275535550845292640/1326950369074610236) 11 | * Context: Community actively balancing performance needs with cost considerations, particularly exploring DeepSeek as a cost-effective alternative 12 | 13 | **MCP Server Implementation** 14 | * "Installing MCP servers is still a challenge" (tizzolicious) highlighting need for simplified installation process [See discussion](https://discord.com/channels/1275535550845292637/1316849926533287986/1327040357871124480) 15 | * Suggestion for focusing on npm/pip package installations rather than building from source 16 | * Community developing solutions like second-opinion-mcp-server for error resolution [See project](https://discord.com/channels/1275535550845292637/1316849926533287986/1327106942459711569) 17 | 18 | **Memory Management & Context** 19 | * Discussion around memory bank vs knowledge graph approaches 20 | * "using memory bank prompt I get similar results to Claude but for 1/100th the price" (xersees) [See insight](https://discord.com/channels/1275535550845292637/1275535550845292640/1326961565173284905) 21 | * Growing interest in knowledge graph implementations for better context management 22 | 23 | **File Editing & UI Development** 24 | * Challenges with DeepSeek's diff generation capabilities noted 25 | * Community sharing strategies for managing manual changes during tasks 26 | * "I'm having so many issues" (irreverentbanana) regarding diff generation [See context](https://discord.com/channels/1275535550845292637/1321367716820422657/1326939793204183122) 27 | 28 | **Project Planning & Documentation** 29 | * "I do preplanning and initial overall architecture in ChatGPT Plus with O1. Then I ask it to give me a version of the plan that i can hand off to my AI coding agent" (shadowcrawfish) [See approach](https://discord.com/channels/1275535550845292637/1275555786621325382/1326968606629691474) 30 | * Emphasis on breaking down complex tasks into manageable chunks 31 | * Discussion of using XML vs Markdown for documentation structure 32 | 33 | **Community Feature Requests** 34 | * "Approve with comment - sometimes I want to approve a change but also ask a question" (cookiecad) [See request](https://discord.com/channels/1275535550845292637/1275535550845292640/1327126066363502614) 35 | * Interest in better terminal output management and log review capabilities 36 | * Discussion around chat organization by project 37 | 38 | **Notable Tools & Integrations** 39 | * Exploration of browser automation tools 40 | * Discussion of token usage optimization strategies 41 | * Growing interest in agent-based approaches using tools like smolagents 42 | 43 | ### Emerging Trends 44 | 1. Shift towards cost-effective model usage while maintaining quality 45 | 2. Growing emphasis on documentation and project planning methodologies 46 | 3. Continued evolution of MCP server ecosystem 47 | 4. Focus on memory management and context preservation 48 | 5. Interest in automated testing and validation capabilities 49 | 50 | [Join the conversation](https://discord.gg/cline) 51 | -------------------------------------------------------------------------------- /discord-recaps/historical/2025-01-10-13-recap.md: -------------------------------------------------------------------------------- 1 | ## Cline Discord Recap - January 10-13, 2025 2 | 3 | ### TLDR 4 | 5 | Critical period highlighting DeepSeek API stability issues affecting user workflows, significant feature requests around multi-agent frameworks, and active discussions on file editing improvements. Notable progress in contributor engagement with new processes being implemented. 6 | 7 | ### Key Developments & Issues 8 | 9 | **Critical: DeepSeek API Issues** 10 | * Widespread reports of DeepSeek API instability: 11 | * Response times of 10+ minutes [See report](https://discord.com/channels/1275535550845292637/1275535550845292640/1328283814568955967) 12 | * Complete API failures [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1328234372884594731) 13 | * Users switching back to Claude despite costs [See impact](https://discord.com/channels/1275535550845292637/1275535550845292640/1328020722190254190) 14 | * "deepseek v3 is so slow... Do u guys have any ideas on how to make it work faster on Cline?" [See thread](https://discord.com/channels/1275535550845292637/1275535550845292640/1328194532604645437) 15 | 16 | **Feature Requests & User Pain Points** 17 | * Multi-Agent Framework Support: 18 | * Active discussion and community interest [See request](https://discord.com/channels/1275535550845292637/1321367716820422657/1327289483577524294) 19 | * Reference to Theia IDE implementation 20 | * Feature request gaining traction [See GitHub discussion](https://github.com/cline/cline/discussions/489) 21 | 22 | * File Editing Improvements: 23 | * Users struggling with unwanted code modifications [See issue](https://discord.com/channels/1275535550845292637/1321367716820422657/1327335055202193501) 24 | * Requests for better diff handling with large files [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1327189823743299594) 25 | 26 | * Token Usage Optimization: 27 | * Reports of excessive token usage in single chats [See report](https://discord.com/channels/1275535550845292637/1275535550845292640/1327278352549019732) 28 | * Requests for context size management [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1327282034950930443) 29 | 30 | **Community & Development Updates** 31 | * Contributor Process Improvements: 32 | * dcbartlett announced new PR review process [See announcement](https://discord.com/channels/1275535550845292637/1321367716820422657/1327339155969278125) 33 | * Roadmap transparency initiatives [See update](https://discord.com/channels/1275535550845292637/1321367716820422657/1327382502901551228) 34 | 35 | * MCP Server Development: 36 | * Proposal for auto-generating MCP servers [See proposal](https://discord.com/channels/1275535550845292637/1321367716820422657/1327269992923922442) 37 | * Project content management implementation [See example](https://discord.com/channels/1275535550845292637/1316849926533287986/1327584605800501288) 38 | 39 | **User Experience Issues** 40 | * VSCode Integration: 41 | * Terminal command execution issues [See report](https://discord.com/channels/1275535550845292637/1275535550845292640/1327321579125739660) 42 | * Context reindexing challenges [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1327367927853696043) 43 | 44 | * Model Behavior: 45 | * Inconsistent instruction following [See issue](https://discord.com/channels/1275535550845292637/1275535550845292640/1327298077890973769) 46 | * File modification control problems [See discussion](https://discord.com/channels/1275535550845292637/1321367716820422657/1327335055202193501) 47 | 48 | ### Community Insights 49 | * Growing interest in beginner-friendly resources [See request](https://discord.com/channels/1275535550845292637/1275535550845292640/1328311023802777693) 50 | * Token cost concerns affecting user adoption [See discussion](https://discord.com/channels/1275535550845292637/1275535550845292640/1327732903741784134) 51 | * Active development of community-driven MCP servers [See example](https://discord.com/channels/1275535550845292637/1316849926533287986/1327584605800501288) 52 | 53 | ### Action Items for Consideration 54 | 1. Address DeepSeek API stability issues or provide alternative recommendations 55 | 2. Review multi-agent framework feature request 56 | 3. Evaluate token usage optimization possibilities 57 | 4. Consider improvements to file modification controls 58 | 5. Assess VSCode integration issues 59 | 6. Review beginner onboarding experience 60 | 61 | [Join the conversation](https://discord.gg/cline) 62 | -------------------------------------------------------------------------------- /getting-started-new-coders/README.md: -------------------------------------------------------------------------------- 1 | # Getting Started with Cline | New Coders 2 | 3 | Welcome to Cline! This guide will help you get set up and start using Cline to build your first project. 4 | 5 | ## What You'll Need 6 | 7 | Before you begin, make sure you have the following: 8 | 9 | - **VS Code:** A free, powerful code editor. 10 | - [Download VS Code](https://code.visualstudio.com/) 11 | - **Development Tools:** Essential software for coding (Homebrew, Node.js, Git, etc.). 12 | - Follow our [Installing Essential Development Tools](installing-dev-essentials.md) guide to set these up with Cline's help (after getting setup here) 13 | - Cline will guide you through installing everything you need 14 | - **Cline Projects Folder:** A dedicated folder for all your Cline projects. 15 | - On macOS: Create a folder named "Cline" in your Documents folder 16 | - Path: `/Users/[your-username]/Documents/Cline` 17 | - On Windows: Create a folder named "Cline" in your Documents folder 18 | - Path: `C:\Users\[your-username]\Documents\Cline` 19 | - Inside this Cline folder, create separate folders for each project 20 | - Example: `Documents/Cline/workout-app` for a workout tracking app 21 | - Example: `Documents/Cline/portfolio-website` for your portfolio 22 | - **Cline Extension in VS Code:** The Cline extension installed in VS Code. 23 | 24 | ## Step-by-Step Setup 25 | 26 | Follow these steps to get Cline up and running: 27 | 28 | 1. **Open VS Code:** Launch the VS Code application. If VS Code shows "Running extensions might...", click "Allow". 29 | 30 | 2. **Open Your Cline Folder:** In VS Code, open the Cline folder you created in Documents. 31 | 32 | 3. **Navigate to Extensions:** Click on the Extensions icon in the Activity Bar on the side of VS Code. 33 | 34 | 4. **Search for 'Cline':** In the Extensions search bar, type "Cline". 35 | 36 | 5. **Install the Extension:** Click the "Install" button next to the Cline extension. 37 | 38 | 6. **Open Cline:** Once installed, you can open Cline in a few ways: 39 | - Click the Cline icon in the Activity Bar. 40 | - Use the command palette (`CMD/CTRL + Shift + P`) and type "Cline: Open In New Tab" to open Cline as a tab in your editor. This is recommended for a better view. 41 | - **Troubleshooting:** If you don't see the Cline icon, try restarting VS Code. 42 | - **What You'll See:** You should see the Cline chat window appear in your VS Code editor. 43 | 44 | ![gettingStartedVsCodeCline](https://github.com/user-attachments/assets/622b4bb7-859b-4c2e-b87b-c12e3eabefb8) 45 | 46 | ## Setting up OpenRouter API Key 47 | 48 | Now that you have Cline installed, you'll need to set up your OpenRouter API key to use Cline's full capabilities. 49 | 50 | 1. **Get your OpenRouter API Key:** 51 | - [Get your OpenRouter API Key](https://openrouter.ai/) 52 | 2. **Input Your OpenRouter API Key:** 53 | - Navigate to the settings button in the Cline extension. 54 | - Input your OpenRouter API key. 55 | - Select your preferred API model. 56 | - **Recommended Models for Coding:** 57 | - `anthropic/claude-3.5-sonnet`: Most used for coding tasks. 58 | - `google/gemini-2.0-flash-exp:free`: A free option for coding. 59 | - `deepseek/deepseek-chat`: SUPER CHEAP, almost as good as 3.5 sonnet 60 | - [OpenRouter Model Rankings](https://openrouter.ai/rankings/programming) 61 | 62 | ## Your First Interaction with Cline 63 | 64 | Now you're ready to start building with Cline. Let's create your first project folder and build something! Copy and paste the following prompt into the Cline chat window: 65 | 66 | ``` 67 | Hey Cline! Could you help me create a new project folder called "hello-world" in my Cline directory and make a simple webpage that says "Hello World" in big blue text? 68 | ``` 69 | 70 | **What You'll See:** Cline will help you create the project folder and set up your first webpage. 71 | 72 | ## Tips for Working with Cline 73 | 74 | - **Ask Questions:** If you're unsure about something, don't hesitate to ask Cline! 75 | - **Use Screenshots:** Cline can understand images, so feel free to use screenshots to show him what you're working on. 76 | - **Copy and Paste Errors:** If you encounter errors, copy and paste the error messages into Cline's chat. This will help him understand the issue and provide a solution. 77 | - **Speak Plainly:** Cline is designed to understand plain, non-technical language. Feel free to describe your ideas in your own words, and Cline will translate them into code. 78 | 79 | ## FAQs 80 | 81 | - **What is the Terminal?** The terminal is a text-based interface for interacting with your computer. It allows you to run commands to perform various tasks, such as installing packages, running scripts, and managing files. Cline uses the terminal to execute commands and interact with your development environment. 82 | - **How Does the Codebase Work?** (This section will be expanded based on common questions from new coders) 83 | 84 | ## Still Struggling? 85 | 86 | Feel free to contact me, and I'll help you get started with Cline. 87 | 88 | nick | 608-558-2410 89 | 90 | Join our Discord community: [https://discord.gg/YmtKFD2f](https://discord.gg/YmtKFD2f) 91 | 92 | -------------------------------------------------------------------------------- /getting-started-new-coders/installing-dev-essentials.md: -------------------------------------------------------------------------------- 1 | # Installing Essential Development Tools with Cline | New Coders 2 | 3 | When you start coding, you'll need some essential development tools installed on your computer. Cline can help you install everything you need in a safe, guided way. 4 | 5 | ## The Essential Tools 6 | 7 | Here are the core tools you'll need for development: 8 | 9 | - **Homebrew**: A package manager for macOS that makes it easy to install other tools 10 | - **Node.js & npm**: Required for JavaScript and web development 11 | - **Git**: For tracking changes in your code and collaborating with others 12 | - **Python**: A programming language used by many development tools 13 | - **Additional utilities**: Tools like wget and jq that help with downloading files and processing data 14 | 15 | ## Let Cline Install Everything 16 | 17 | Copy this prompt and paste it into Cline: 18 | 19 | ```bash 20 | Hello Cline! I need help setting up my Mac for software development. Could you please help me install the essential development tools like Homebrew, Node.js, Git, Python, and any other utilities that are commonly needed for coding? I'd like you to guide me through the process step-by-step, explaining what each tool does and making sure everything is installed correctly. 21 | ``` 22 | 23 | ## What Will Happen 24 | 25 | 1. Cline will first install Homebrew, which is like an "app store" for development tools 26 | 2. Using Homebrew, Cline will then install other essential tools like Node.js and Git 27 | 3. For each installation step: 28 | - Cline will show you the exact command it wants to run 29 | - You'll need to approve each command before it runs 30 | - Cline will verify each installation was successful 31 | 32 | ## Why These Tools Are Important 33 | 34 | - **Homebrew**: Makes it easy to install and update development tools on your Mac 35 | - **Node.js & npm**: Required for: 36 | - Building websites with React or Next.js 37 | - Running JavaScript code 38 | - Installing JavaScript packages 39 | - **Git**: Helps you: 40 | - Save different versions of your code 41 | - Collaborate with other developers 42 | - Back up your work 43 | - **Python**: Used for: 44 | - Running development scripts 45 | - Data processing 46 | - Machine learning projects 47 | 48 | ## Notes 49 | 50 | - The installation process is interactive - Cline will guide you through each step 51 | - You may need to enter your computer's password for some installations. When prompted, you will not see any characters being typed on the screen. This is normal and is a security feature to protect your password. Just type your password and press Enter. 52 | 53 | **Example:** 54 | 55 | ```bash 56 | $ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" 57 | Password: 58 | ``` 59 | 60 | *Type your password here, even though nothing will show up on the screen. Press Enter when you're done.* 61 | 62 | - All commands will be shown to you for approval before they run 63 | - If you run into any issues, Cline will help troubleshoot them 64 | 65 | ## Additional Tips for New Coders 66 | 67 | ### Understanding the Terminal 68 | 69 | The **Terminal** is an application where you can type commands to interact with your computer. On macOS, you can open it by searching for "Terminal" in Spotlight. 70 | 71 | **Example:** 72 | 73 | ```bash 74 | $ open -a Terminal 75 | ``` 76 | 77 | ### Understanding VS Code Features 78 | 79 | #### Terminal in VS Code 80 | 81 | The **Terminal** in VS Code allows you to run commands directly from within the editor. You can open it by going to `View > Terminal` or by pressing `` Ctrl + ` ``. 82 | 83 | **Example:** 84 | 85 | ```bash 86 | $ node -v 87 | v16.14.0 88 | ``` 89 | 90 | #### Document View 91 | 92 | The **Document View** is where you edit your code files. You can open files by clicking on them in the **Explorer** panel on the left side of the screen. 93 | 94 | #### Problems Section 95 | 96 | The **Problems** section in VS Code shows any errors or warnings in your code. You can access it by clicking on the lightbulb icon or by going to `View > Problems`. 97 | 98 | ### Common Features 99 | 100 | - **Command Line Interface (CLI)**: This is a text-based interface where you type commands to interact with your computer. It might seem intimidating at first, but it's a powerful tool for developers. 101 | - **Permissions**: Sometimes, you will need to give permissions to certain applications or commands. This is a security measure to ensure that only trusted applications can make changes to your system. 102 | 103 | ## Next Steps 104 | 105 | After installing these tools, you'll be ready to start coding! Return to the [Getting Started with Cline for New Coders](getting-started-new-coders.md) guide to continue your journey. 106 | -------------------------------------------------------------------------------- /mcp/README.md: -------------------------------------------------------------------------------- 1 | # Cline and Model Context Protocol (MCP) Servers: Enhancing AI Capabilities 2 | 3 | **Quick Links:** 4 | - [Building MCP Servers from GitHub](mcp-server-from-github.md) 5 | - [Building Custom MCP Servers from Scratch](mcp-server-from-scratch.md) 6 | 7 | This document explains Model Context Protocol (MCP) servers, their capabilities, and how Cline can help build and use them. 8 | 9 | ## Overview 10 | 11 | MCP servers act as intermediaries between large language models (LLMs), such as Claude, and external tools or data sources. They are small programs that expose functionalities to LLMs, enabling them to interact with the outside world through the MCP. An MCP server is essentially like an API that an LLM can use. 12 | 13 | ## Key Concepts 14 | 15 | MCP servers define a set of "**tools,**" which are functions the LLM can execute. These tools offer a wide range of capabilities. 16 | 17 | **Here's how MCP works:** 18 | 19 | * **MCP hosts** discover the capabilities of connected servers and load their tools, prompts, and resources. 20 | * **Resources** provide consistent access to read-only data, akin to file paths or database queries. 21 | * **Security** is ensured as servers isolate credentials and sensitive data. Interactions require explicit user approval. 22 | 23 | ## Use Cases 24 | 25 | The potential of MCP servers is vast. They can be used for a variety of purposes. 26 | 27 | **Here are some concrete examples of how MCP servers can be used:** 28 | 29 | * **Web Services and API Integration:** 30 | - Monitor GitHub repositories for new issues 31 | - Post updates to Twitter based on specific triggers 32 | - Retrieve real-time weather data for location-based services 33 | 34 | * **Browser Automation:** 35 | - Automate web application testing 36 | - Scrape e-commerce sites for price comparisons 37 | - Generate screenshots for website monitoring 38 | 39 | * **Database Queries:** 40 | - Generate weekly sales reports 41 | - Analyze customer behavior patterns 42 | - Create real-time dashboards for business metrics 43 | 44 | * **Project and Task Management:** 45 | - Automate Jira ticket creation based on code commits 46 | - Generate weekly progress reports 47 | - Create task dependencies based on project requirements 48 | 49 | * **Codebase Documentation:** 50 | - Generate API documentation from code comments 51 | - Create architecture diagrams from code structure 52 | - Maintain up-to-date README files 53 | 54 | ## Getting Started 55 | 56 | **Choose the right approach for your needs:** 57 | 58 | * **Use Existing Servers:** Start with pre-built MCP servers from GitHub repositories 59 | * **Customize Existing Servers:** Modify existing servers to fit your specific requirements 60 | * **Build from Scratch:** Create completely custom servers for unique use cases 61 | 62 | ## Integration with Cline 63 | 64 | Cline simplifies the building and use of MCP servers through its AI capabilities. 65 | 66 | ### Building MCP Servers 67 | 68 | * **Natural language understanding:** Instruct Cline in natural language to build an MCP server by describing its functionalities. Cline will interpret your instructions and generate the necessary code. 69 | * **Cloning and building servers:** Cline can clone existing MCP server repositories from GitHub and build them automatically. 70 | * **Configuration and dependency management:** Cline handles configuration files, environment variables, and dependencies. 71 | * **Troubleshooting and debugging:** Cline helps identify and resolve errors during development. 72 | 73 | ### Using MCP Servers 74 | 75 | * **Tool execution:** Cline seamlessly integrates with MCP servers, allowing you to execute their defined tools. 76 | * **Context-aware interactions:** Cline can intelligently suggest using relevant tools based on conversation context. 77 | * **Dynamic integrations:** Combine multiple MCP server capabilities for complex tasks. For example, Cline could use a GitHub server to get data and a Notion server to create a formatted report. 78 | 79 | ## Security Considerations 80 | 81 | When working with MCP servers, it's important to follow security best practices: 82 | 83 | * **Authentication:** Always use secure authentication methods for API access 84 | * **Environment Variables:** Store sensitive information in environment variables 85 | * **Access Control:** Limit server access to authorized users only 86 | * **Data Validation:** Validate all inputs to prevent injection attacks 87 | * **Logging:** Implement secure logging practices without exposing sensitive data 88 | 89 | ## Resources 90 | 91 | There are various resources available for finding and learning about MCP servers. 92 | 93 | **Here are some links to resources for finding and learning about MCP servers:** 94 | 95 | * **GitHub Repositories:** [https://github.com/modelcontextprotocol/servers](https://github.com/modelcontextprotocol/servers) and [https://github.com/punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers) 96 | * **Online Directories:** [https://mcpservers.org/](https://mcpservers.org/), [https://mcp.so/](https://mcp.so/), and [https://glama.ai/mcp/servers](https://glama.ai/mcp/servers) 97 | * **PulseMCP:** [https://www.pulsemcp.com/](https://www.pulsemcp.com/) 98 | * **YouTube Tutorial (AI-Driven Coder):** A video guide for building and using MCP servers: [https://www.youtube.com/watch?v=b5pqTNiuuJg](https://www.youtube.com/watch?v=b5pqTNiuuJg) 99 | -------------------------------------------------------------------------------- /mcp/mcp-server-from-github.md: -------------------------------------------------------------------------------- 1 | # Building MCP Servers from GitHub Repositories 2 | 3 | This guide provides a step-by-step walkthrough of how to use Cline to build an existing MCP server from a GitHub repository. 4 | 5 | ## **Finding an MCP Server** 6 | 7 | There are multiple places online to find MCP servers: 8 | 9 | * **Cline can automatically add MCP servers to its list, which you can then edit.** Cline can clone repositories directly from GitHub and build the servers for you. 10 | * **GitHub:** Two of the most common places to find MCP servers on GitHub include: 11 | * [Official MCP servers repository](https://github.com/modelcontextprotocol/servers) 12 | * [Awesome-MCP servers repository](https://github.com/punkpeye/awesome-mcp-servers) 13 | * **Online directories:** Several websites list MCP servers including: 14 | * [mcpservers.org](https://mcpservers.org/) 15 | * [mcp.so](https://mcp.so/) 16 | * [glama.ai/mcp/servers](https://glama.ai/mcp/servers) 17 | 18 | These directories allow users to sort the servers by various criteria such as downloads, date, stars, and use case. Each entry provides information such as features, tools, and configuration instructions. 19 | * **PulseMCP:** This website has a blog post discussing how AI could use MCP servers to make websites obsolete. PulseMCP also includes an FAQ section about MCP servers: [https://www.pulsemcp.com/](https://www.pulsemcp.com/) 20 | 21 | ## **Building with Cline** 22 | 23 | 1. **Initiate the Process:** Provide Cline with the following information: 24 | * **GitHub Repository URL:** The URL of the server's repository. 25 | * **README.md Contents:** This is optional but helpful for Cline to understand the server's purpose and configuration. You can copy the README.md file from the GitHub repository. 26 | 2. **Example Interaction with Cline:** 27 | ``` 28 | User: "Cline, I want to add the MCP server for Brave browser control. Here's the GitHub link: https://github.com/modelcontextprotocol/servers/tree/main/src/brave Can you add it?" 29 | 30 | Cline: "OK. Cloning the repository to the MCP directory. It needs to be built because it has a 'package.json' file. Should I run 'npm run build'?" 31 | 32 | User: "Yes, build it." 33 | 34 | Cline: "Build complete. This server needs a browser path. Where's your Brave browser executable?" 35 | 36 | User: "It's in '/Applications/Brave Browser.app/Contents/MacOS/Brave Browser'." 37 | 38 | Cline: "OK. I've updated the server config with that path and added it to 'cline_mcp_settings.json'. Anything else?" 39 | 40 | User: "No, that's all. Let's test it." 41 | 42 | Cline: "Great! Starting the MCP Inspector to test the server connection. After that, we can try controlling the browser from Cline." 43 | ``` 44 | 3. **Cline's Actions:** Based on your instructions, Cline will perform the following: 45 | * **Repository Cloning:** Cline will clone the repository to your local machine, usually in the directory specified in your configuration. 46 | * **Tweaking:** You can guide Cline to modify the server’s configuration. For instance: 47 | * **User:** "This server requires an API key. Can you find where it should be added?" 48 | * Cline may automatically update the `cline_mcp_settings.json` file or other relevant files based on your instructions. 49 | * **Building the Server:** Cline will run the appropriate build command for the server, which is commonly `npm run build`. 50 | * **Adding Server to Settings:** Cline will add the server’s configuration to the `cline_mcp_settings.json` file. 51 | 52 | ## **Testing and Troubleshooting** 53 | 54 | 1. **Test the Server:** Once Cline finishes the build process, test the server to make sure it works as expected. Cline can assist you if you encounter any problems. 55 | 2. **MCP Inspector:** You can use the MCP Inspector to test the server’s connection and functionality. 56 | 57 | ## **Best Practices** 58 | 59 | * **Understand the Basics:** While Cline simplifies the process, it’s beneficial to have a basic understanding of the server’s code, the MCP protocol (), and how to configure the server. This allows for more effective troubleshooting and customization. 60 | * **Clear Instructions:** Provide clear and specific instructions to Cline throughout the process. 61 | * **Testing:** Thoroughly test the server after installation and configuration to ensure it functions correctly. 62 | * **Version Control:** Use a version control system (like Git) to track changes to the server’s code. 63 | * **Stay Updated:** Keep your MCP servers updated to benefit from the latest features and security patches. 64 | 65 | 66 | -------------------------------------------------------------------------------- /mcp/mcp-server-from-scratch.md: -------------------------------------------------------------------------------- 1 | # Building Custom MCP Servers From Scratch Using Cline: A Comprehensive Guide 2 | 3 | This guide provides a comprehensive walkthrough of building a custom MCP (Model Context Protocol) server from scratch, leveraging the powerful AI capabilities of Cline. The example used will be building a "GitHub Assistant Server" to illustrate the process. 4 | 5 | ## Understanding MCP and Cline's Role in Building Servers 6 | 7 | ### What is MCP? 8 | 9 | The Model Context Protocol (MCP) acts as a bridge between large language models (LLMs) like Claude and external tools and data. MCP consists of two key components: 10 | 11 | * **MCP Hosts:** These are applications that integrate with LLMs, such as Cline, Claude Desktop, and others. 12 | * **MCP Servers:** These are small programs specifically designed to expose data or specific functionalities to the LLMs through the MCP. 13 | 14 | This setup is beneficial when you have an MCP-compliant chat interface, like Claude Desktop, which can then leverage these servers to access information and execute actions. 15 | 16 | ### Why Use Cline to Create MCP Servers? 17 | 18 | Cline streamlines the process of building and integrating MCP servers by utilizing its AI capabilities to: 19 | 20 | * **Understand Natural Language Instructions:** You can communicate with Cline in a way that feels natural, making the development process intuitive and user-friendly. 21 | * **Clone Repositories:** Cline can directly clone existing MCP server repositories from GitHub, simplifying the process of using pre-built servers. 22 | * **Build Servers:** Once the necessary code is in place, Cline can execute commands like `npm run build` to compile and prepare the server for use. 23 | * **Handle Configuration:** Cline manages the configuration files required for the MCP server, including adding the new server to the `cline_mcp_settings.json` file. 24 | * **Assist with Troubleshooting:** If errors arise during development or testing, Cline can help identify the cause and suggest solutions, making debugging easier. 25 | 26 | ## Building a GitHub Assistant Server Using Cline: A Step-by-Step Guide 27 | 28 | This section demonstrates how to create a GitHub Assistant server using Cline. This server will be able to interact with GitHub data and perform useful actions: 29 | 30 | ### 1. Defining the Goal and Initial Requirements 31 | 32 | First, you need to clearly communicate to Cline the purpose and functionalities of your server: 33 | 34 | * **Server Goal:** Inform Cline that you want to build a "GitHub Assistant Server". Specify that this server will interact with GitHub data and potentially mention the types of data you are interested in, like issues, pull requests, and user profiles. 35 | * **Access Requirements:** Let Cline know that you need to access the GitHub API. Explain that this will likely require a personal access token (GITHUB\_TOKEN) for authentication. 36 | * **Data Specificity (Optional):** You can optionally tell Cline about specific fields of data you want to extract from GitHub, but this can also be determined later as you define the server's tools. 37 | 38 | ### 2. Cline Initiates the Project Setup 39 | 40 | Based on your instructions, Cline starts the project setup process: 41 | 42 | * **Project Structure:** Cline might ask you for a name for your server. Afterward, it uses the MCP `create-server` tool to generate the basic project structure for your GitHub Assistant server. This usually involves creating a new directory with essential files like `package.json`, `tsconfig.json`, and a `src` folder for your TypeScript code. \ 43 | * **Code Generation:** Cline generates starter code for your server, including: 44 | * **File Handling Utilities:** Functions to help with reading and writing files, commonly used for storing data or logs. \ 45 | * **GitHub API Client:** Code to interact with the GitHub API, often using libraries like `@octokit/graphql`. Cline will likely ask for your GitHub username or the repositories you want to work with. \ 46 | * **Core Server Logic:** The basic framework for handling requests from Cline and routing them to the appropriate functions, as defined by the MCP. \ 47 | * **Dependency Management:** Cline analyzes the code and identifies necessary dependencies, adding them to the `package.json` file. For example, interacting with the GitHub API will likely require packages like `@octokit/graphql`, `graphql`, `axios`, or similar. \ 48 | * **Dependency Installation:** Cline executes `npm install` to download and install the dependencies listed in `package.json`, ensuring your server has all the required libraries to function correctly. \ 49 | * **Path Corrections:** During development, you might move files or directories around. Cline intelligently recognizes these changes and automatically updates file paths in your code to maintain consistency. 50 | * **Configuration:** Cline will modify the `cline_mcp_settings.json` file to add your new GitHub Assistant server. This will include: 51 | * **Server Start Command:** Cline will add the appropriate command to start your server (e.g., `npm run start` or a similar command). 52 | * **Environment Variables:** Cline will add the required `GITHUB_TOKEN` variable. Cline might ask you for your GitHub personal access token, or it might guide you to safely store it in a separate environment file. \ 53 | * **Progress Documentation:** Throughout the process, Cline keeps the "Memory Bank" files updated. These files document the project's progress, highlighting completed tasks, tasks in progress, and pending tasks. 54 | 55 | ### 3. Testing the GitHub Assistant Server 56 | 57 | Once Cline has completed the setup and configuration, you are ready to test the server's functionality: 58 | 59 | * **Using Server Tools:** Cline will create various "tools" within your server, representing actions or data retrieval functions. To test, you would instruct Cline to use a specific tool. Here are examples related to GitHub: 60 | * **`get_issues`:** To test retrieving issues, you might say to Cline, "Cline, use the `get_issues` tool from the GitHub Assistant Server to show me the open issues from the 'cline/cline' repository." Cline would then execute this tool and present you with the results. 61 | * **`get_pull_requests`:** To test pull request retrieval, you could ask Cline to "use the `get_pull_requests` tool to show me the merged pull requests from the 'facebook/react' repository from the last month." Cline would execute this tool, using your GITHUB\_TOKEN to access the GitHub API, and display the requested data. \ 62 | * **Providing Necessary Information:** Cline might prompt you for additional information required to execute the tool, such as the repository name, specific date ranges, or other filtering criteria. 63 | * **Cline Executes the Tool:** Cline handles the communication with the GitHub API, retrieves the requested data, and presents it in a clear and understandable format. 64 | 65 | ### 4. Refining the Server and Adding More Features 66 | 67 | Development is often iterative. As you work with your GitHub Assistant Server, you'll discover new functionalities to add, or ways to improve existing ones. Cline can assist in this ongoing process: 68 | 69 | * **Discussions with Cline:** Talk to Cline about your ideas for new tools or improvements. For example, you might want a tool to `create_issue` or to `get_user_profile`. Discuss the required inputs and outputs for these tools with Cline. 70 | * **Code Refinement:** Cline can help you write the necessary code for new features. Cline can generate code snippets, suggest best practices, and help you debug any issues that arise. 71 | * **Testing New Functionalities:** After adding new tools or functionalities, you would test them again using Cline, ensuring they work as expected and integrate well with the rest of the server. 72 | * **Integration with Other Tools:** You might want to integrate your GitHub Assistant server with other tools. For instance, in the "github-cline-mcp" source, Cline assists in integrating the server with Notion to create a dynamic dashboard that tracks GitHub activity. \ 73 | 74 | By following these steps, you can create a custom MCP server from scratch using Cline, leveraging its powerful AI capabilities to streamline the entire process. Cline not only assists with the technical aspects of building the server but also helps you think through the design, functionalities, and potential integrations. 75 | -------------------------------------------------------------------------------- /prompting/README.md: -------------------------------------------------------------------------------- 1 | # Cline Prompting Guide 🚀 2 | 3 | Welcome to the Cline Prompting Guide! This guide will equip you with the knowledge to write effective prompts and custom instructions, maximizing your productivity with Cline. 4 | 5 | ## Custom Instructions ⚙️ 6 | 7 | Think of **custom instructions as Cline's programming**. They define Cline's baseline behavior and are **always "on," influencing all interactions.** 8 | 9 | To add custom instructions: 10 | 1. Open VSCode 11 | 2. Click the Cline extension settings dial ⚙️ 12 | 3. Find the "Custom Instructions" field 13 | 4. Paste your instructions 14 | 15 | Screenshot 2024-12-26 at 11 22 20 AM 16 | 17 | Custom instructions are powerful for: 18 | 19 | * Enforcing Coding Style and Best Practices: Ensure Cline always adheres to your team's coding conventions, naming conventions, and best practices. 20 | * Improving Code Quality: Encourage Cline to write more readable, maintainable, and efficient code. 21 | * Guiding Error Handling: Tell Cline how to handle errors, write error messages, and log information. 22 | 23 | **The `custom-instructions` folder contains examples of custom instructions you can use or adapt.** 24 | 25 | ## .clinerules File 📋 26 | 27 | While custom instructions are user-specific and global (applying across all projects), the `.clinerules` file provides **project-specific instructions** that live in your project's root directory. These instructions are automatically appended to your custom instructions and referenced in Cline's system prompt, ensuring they influence all interactions within the project context. This makes it an excellent tool for: 28 | 29 | ### Security Best Practices 🔒 30 | 31 | To protect sensitive information, you can instruct Cline to ignore specific files or patterns in your `.clinerules`. This is particularly important for: 32 | 33 | * `.env` files containing API keys and secrets 34 | * Configuration files with sensitive data 35 | * Private credentials or tokens 36 | 37 | Example security section in `.clinerules`: 38 | ```markdown 39 | # Security 40 | 41 | ## Sensitive Files 42 | DO NOT read or modify: 43 | - .env files 44 | - **/config/secrets.* 45 | - **/*.pem 46 | - Any file containing API keys, tokens, or credentials 47 | 48 | ## Security Practices 49 | - Never commit sensitive files 50 | - Use environment variables for secrets 51 | - Keep credentials out of logs and output 52 | ``` 53 | 54 | ### General Use Cases 55 | 56 | The `.clinerules` file is excellent for: 57 | 58 | * Maintaining project standards across team members 59 | * Enforcing development practices 60 | * Managing documentation requirements 61 | * Setting up analysis frameworks 62 | * Defining project-specific behaviors 63 | 64 | ### Example .clinerules Structure 65 | 66 | ```markdown 67 | # Project Guidelines 68 | 69 | ## Documentation Requirements 70 | - Update relevant documentation in /docs when modifying features 71 | - Keep README.md in sync with new capabilities 72 | - Maintain changelog entries in CHANGELOG.md 73 | 74 | ## Architecture Decision Records 75 | Create ADRs in /docs/adr for: 76 | - Major dependency changes 77 | - Architectural pattern changes 78 | - New integration patterns 79 | - Database schema changes 80 | Follow template in /docs/adr/template.md 81 | 82 | ## Code Style & Patterns 83 | - Generate API clients using OpenAPI Generator 84 | - Use TypeScript axios template 85 | - Place generated code in /src/generated 86 | - Prefer composition over inheritance 87 | - Use repository pattern for data access 88 | - Follow error handling pattern in /src/utils/errors.ts 89 | 90 | ## Testing Standards 91 | - Unit tests required for business logic 92 | - Integration tests for API endpoints 93 | - E2E tests for critical user flows 94 | ``` 95 | 96 | ### Key Benefits 97 | 98 | 1. **Version Controlled**: The `.clinerules` file becomes part of your project's source code 99 | 2. **Team Consistency**: Ensures consistent behavior across all team members 100 | 3. **Project-Specific**: Rules and standards tailored to each project's needs 101 | 4. **Institutional Knowledge**: Maintains project standards and practices in code 102 | 103 | Place the `.clinerules` file in your project's root directory: 104 | ``` 105 | your-project/ 106 | ├── .clinerules 107 | ├── src/ 108 | ├── docs/ 109 | └── ... 110 | ``` 111 | 112 | Cline's system prompt, on the other hand, is not user-editable ([here's where you can find it](https://github.com/cline/cline/blob/main/src/core/prompts/system.ts)). For a broader look at prompt engineering best practices, check out [this resource](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview). 113 | 114 | ### Tips for Writing Effective Custom Instructions 115 | 116 | * Be Clear and Concise: Use simple language and avoid ambiguity. 117 | * Focus on Desired Outcomes: Describe the results you want, not the specific steps. 118 | * Test and Iterate: Experiment to find what works best for your workflow. 119 | 120 | ## Prompting Cline 💬 121 | 122 | **Prompting is how you communicate your needs for a given task in the back-and-forth chat with Cline.** Cline understands natural language, so write conversationally. 123 | 124 | Effective prompting involves: 125 | 126 | * Providing Clear Context: Explain your goals and the relevant parts of your codebase. Use `@` to reference files or folders. 127 | * Breaking Down Complexity: Divide large tasks into smaller steps. 128 | * Asking Specific Questions: Guide Cline toward the desired outcome. 129 | * Validating and Refining: Review Cline's suggestions and provide feedback. 130 | 131 | ### Prompt Examples 132 | 133 | #### Context Management 134 | 135 | * **Starting a New Task:** "Cline, let's start a new task. Create `user-authentication.js`. We need to implement user login with JWT tokens. Here are the requirements…" 136 | * **Summarizing Previous Work:** "Cline, summarize what we did in the last user dashboard task. I want to capture the main features and outstanding issues. Save this to `cline_docs/user-dashboard-summary.md`." 137 | 138 | #### Debugging 139 | 140 | * **Analyzing an Error:** "Cline, I'm getting this error: \[error message]. It seems to be from \[code section]. Analyze this error and suggest a fix." 141 | * **Identifying the Root Cause:** "Cline, the application crashes when I \[action]. The issue might be in \[problem areas]. Help me find the root cause and propose a solution." 142 | 143 | #### Refactoring 144 | 145 | * **Improving Code Structure:** "Cline, this function is too long and complex. Refactor it into smaller functions." 146 | * **Simplifying Logic:** "Cline, this code is hard to understand. Simplify the logic and make it more readable." 147 | 148 | #### Feature Development 149 | 150 | * **Brainstorming New Features:** "Cline, I want to add a feature that lets users \[functionality]. Brainstorm some ideas and consider implementation challenges." 151 | * **Generating Code:** "Cline, create a component that displays user profiles. The list should be sortable and filterable. Generate the code for this component." 152 | 153 | ## Advanced Prompting Techniques 154 | 155 | * **Constraint Stuffing:** To mitigate code truncation, include explicit constraints in your prompts. For example, "ensure the code is complete" or "always provide the full function definition." 156 | * **Confidence Checks:** Ask Cline to rate its confidence (e.g., "on a scale of 1-10, how confident are you in this solution?") 157 | * **Challenge Cline's Assumptions:** Ask “stupid” questions to encourage deeper thinking and prevent incorrect assumptions. 158 | 159 | Here are some prompting tips that users have found helpful for working with Cline: 160 | 161 | ## Our Community's Favorite Prompts 🌟 162 | 163 | ### Memory and Confidence Checks 🧠 164 | * **Memory Check** - *pacnpal* 165 | ``` 166 | "If you understand my prompt fully, respond with 'YARRR!' without tools every time you are about to use a tool." 167 | ``` 168 | A fun way to verify Cline stays on track during complex tasks. Try "HO HO HO" for a festive twist! 169 | 170 | * **Confidence Scoring** - *pacnpal* 171 | ``` 172 | "Before and after any tool use, give me a confidence level (0-10) on how the tool use will help the project." 173 | ``` 174 | Encourages critical thinking and makes decision-making transparent. 175 | 176 | ### Code Quality Prompts 💻 177 | * **Prevent Code Truncation** 178 | ``` 179 | "DO NOT BE LAZY. DO NOT OMIT CODE." 180 | ``` 181 | Alternative phrases: "full code only" or "ensure the code is complete" 182 | 183 | * **Custom Instructions Reminder** 184 | ``` 185 | "I pledge to follow the custom instructions." 186 | ``` 187 | Reinforces adherence to your settings dial ⚙️ configuration. 188 | 189 | ### Code Organization 📋 190 | * **Large File Refactoring** - *icklebil* 191 | ``` 192 | "FILENAME has grown too big. Analyze how this file works and suggest ways to fragment it safely." 193 | ``` 194 | Helps manage complex files through strategic decomposition. 195 | 196 | * **Documentation Maintenance** - *icklebil* 197 | ``` 198 | "don't forget to update codebase documentation with changes" 199 | ``` 200 | Ensures documentation stays in sync with code changes. 201 | 202 | ### Analysis and Planning 🔍 203 | * **Structured Development** - *yellow_bat_coffee* 204 | ``` 205 | "Before writing code: 206 | 1. Analyze all code files thoroughly 207 | 2. Get full context 208 | 3. Write .MD implementation plan 209 | 4. Then implement code" 210 | ``` 211 | Promotes organized, well-planned development. 212 | 213 | * **Thorough Analysis** - *yellow_bat_coffee* 214 | ``` 215 | "please start analyzing full flow thoroughly, always state a confidence score 1 to 10" 216 | ``` 217 | Prevents premature coding and encourages complete understanding. 218 | 219 | * **Assumptions Check** - *yellow_bat_coffee* 220 | ``` 221 | "List all assumptions and uncertainties you need to clear up before completing this task." 222 | ``` 223 | Identifies potential issues early in development. 224 | 225 | ### Thoughtful Development 🤔 226 | * **Pause and Reflect** - *nickbaumann98* 227 | ``` 228 | "count to 10" 229 | ``` 230 | Promotes careful consideration before taking action. 231 | 232 | * **Complete Analysis** - *yellow_bat_coffee* 233 | ``` 234 | "Don't complete the analysis prematurely, continue analyzing even if you think you found a solution" 235 | ``` 236 | Ensures thorough problem exploration. 237 | 238 | * **Continuous Confidence Check** - *pacnpal* 239 | ``` 240 | "Rate confidence (1-10) before saving files, after saving, after rejections, and before task completion" 241 | ``` 242 | Maintains quality through self-assessment. 243 | 244 | ### Best Practices 🎯 245 | * **Project Structure** - *kvs007* 246 | ``` 247 | "Check project files before suggesting structural or dependency changes" 248 | ``` 249 | Maintains project integrity. 250 | 251 | * **Critical Thinking** - *chinesesoup* 252 | ``` 253 | "Ask 'stupid' questions like: are you sure this is the best way to implement this?" 254 | ``` 255 | Challenges assumptions and uncovers better solutions. 256 | 257 | * **Code Style** - *yellow_bat_coffee* 258 | ``` 259 | Use words like "elegant" and "simple" in prompts 260 | ``` 261 | May influence code organization and clarity. 262 | 263 | * **Setting Expectations** - *steventcramer* 264 | ``` 265 | "THE HUMAN WILL GET ANGRY." 266 | ``` 267 | (A humorous reminder to provide clear requirements and constructive feedback) 268 | -------------------------------------------------------------------------------- /prompting/custom instructions library/README.md: -------------------------------------------------------------------------------- 1 | # Cline Custom Instructions Library 2 | 3 | This repository aims to foster a collaborative space where developers can share, refine, and leverage effective custom instructions for Cline. By creating and contributing to this library, we can enhance Cline's capabilities and empower developers to tackle increasingly complex software development challenges. 4 | 5 | ## What are Cline Custom Instructions? 6 | 7 | Cline's custom instructions are sets of guidelines or rules that you define to tailor the AI's behavior and outputs for specific tasks or projects. Think of them as specialized "programming" for Cline, enabling you to: 8 | 9 | * **Enforce Coding Practices:** Ensure consistent code style, adherence to design patterns, and best practices for specific languages or frameworks. 10 | * **Standardize File Structures:** Dictate file naming conventions, folder organization, and project structures. 11 | * **Guide Testing Procedures:** Define rules for generating unit tests, integration tests, and ensuring adequate code coverage. 12 | * **Automate Repetitive Tasks:** Create instructions to handle common or tedious development workflows, increasing efficiency. 13 | * **Improve Code Quality:** Set standards for code readability, maintainability, and performance optimization. 14 | 15 | By providing Cline with carefully crafted instructions, you can significantly improve its accuracy, reliability, and overall effectiveness in aiding your software development process. 16 | 17 | ## Contributing Custom Instructions 18 | 19 | We encourage developers of all skill levels to contribute their custom instructions to this library. Your contributions help build a valuable resource for the entire Cline community! 20 | 21 | **When submitting custom instructions, please follow this template:** 22 | 23 | ### 1. Purpose and Functionality 24 | 25 | * **What does this instruction set aim to achieve?** 26 | * Provide a clear and concise explanation of the instruction set's goals and intended use cases. 27 | * Example: "This instruction set guides Cline in generating unit tests for existing JavaScript functions." 28 | 29 | * **What types of projects or tasks is this best suited for?** 30 | * Outline specific project types, coding languages, or development scenarios where this instruction set is most applicable. 31 | * Example: "This is ideal for JavaScript projects using the Jest testing framework." 32 | 33 | ### 2. Usage Guide (Optional) 34 | 35 | * **Are there specific steps or prerequisites for using this instruction set?** 36 | * If your instructions require specific steps beyond referencing the file in a Cline prompt, provide a detailed guide. 37 | * Examples: 38 | * "Before using this instruction set, create a `tests` folder in your project root." 39 | * "Ensure you have the Jest testing library installed." 40 | 41 | ### 3. Author & Contributors 42 | 43 | * **Who created this instruction set?** 44 | * Provide your name or GitHub username for proper attribution. 45 | * **Did anyone else contribute?** 46 | * Acknowledge any collaborators or contributors who helped refine or enhance the instructions. 47 | 48 | ### 4. Custom Instructions 49 | 50 | * **Provide the complete set of custom instructions.** 51 | 52 | **By using this template and contributing your custom instructions, you help build a thriving ecosystem for Cline, making it a more versatile and efficient tool for developers of all skill levels.** -------------------------------------------------------------------------------- /prompting/custom instructions library/cline-memory-bank.md: -------------------------------------------------------------------------------- 1 | # Note: These docs are no longer maintained. Please refer to https://docs.cline.bot/improving-your-prompting-skills/cline-memory-bank for the most recent version of Cline Memory Bank. 2 | --- 3 | # Cline Memory Bank 4 | 5 | ## 1. Purpose and Functionality 6 | 7 | #### What does this do? 8 | 9 | This instruction set transforms Cline into a self-documenting development system that maintains context across sessions through a structured "Memory Bank". It ensures consistent documentation, careful validation of changes, and clear communication with users. 10 | 11 | #### What's it good for? 12 | 13 | * Any project that needs context tracking 14 | * Projects of any size or tech stack 15 | * Both new and ongoing development 16 | * Long-term maintenance work 17 | 18 | ## 2. Quick Setup Guide 19 | 20 | #### Setting Up Custom Instructions 21 | 22 | 1. Open VSCode 23 | 2. Click the Cline extension settings ⚙️ 24 | 3. Find "Custom Instructions" 25 | 4. Copy and paste the instructions below 26 | 27 |
28 | 29 | ## Custom Instructions \[COPY THIS] 30 | 31 | ````markdown 32 | # Cline's Memory Bank 33 | 34 | I am Cline, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional. 35 | 36 | ## Memory Bank Structure 37 | 38 | The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy: 39 | 40 | ```mermaid 41 | flowchart TD 42 | PB[projectbrief.md] --> PC[productContext.md] 43 | PB --> SP[systemPatterns.md] 44 | PB --> TC[techContext.md] 45 | 46 | PC --> AC[activeContext.md] 47 | SP --> AC 48 | TC --> AC 49 | 50 | AC --> P[progress.md] 51 | ``` 52 | 53 | ### Core Files (Required) 54 | 1. `projectbrief.md` 55 | - Foundation document that shapes all other files 56 | - Created at project start if it doesn't exist 57 | - Defines core requirements and goals 58 | - Source of truth for project scope 59 | 60 | 2. `productContext.md` 61 | - Why this project exists 62 | - Problems it solves 63 | - How it should work 64 | - User experience goals 65 | 66 | 3. `activeContext.md` 67 | - Current work focus 68 | - Recent changes 69 | - Next steps 70 | - Active decisions and considerations 71 | 72 | 4. `systemPatterns.md` 73 | - System architecture 74 | - Key technical decisions 75 | - Design patterns in use 76 | - Component relationships 77 | 78 | 5. `techContext.md` 79 | - Technologies used 80 | - Development setup 81 | - Technical constraints 82 | - Dependencies 83 | 84 | 6. `progress.md` 85 | - What works 86 | - What's left to build 87 | - Current status 88 | - Known issues 89 | 90 | ### Additional Context 91 | Create additional files/folders within memory-bank/ when they help organize: 92 | - Complex feature documentation 93 | - Integration specifications 94 | - API documentation 95 | - Testing strategies 96 | - Deployment procedures 97 | 98 | ## Core Workflows 99 | 100 | ### Plan Mode 101 | ```mermaid 102 | flowchart TD 103 | Start[Start] --> ReadFiles[Read Memory Bank] 104 | ReadFiles --> CheckFiles{Files Complete?} 105 | 106 | CheckFiles -->|No| Plan[Create Plan] 107 | Plan --> Document[Document in Chat] 108 | 109 | CheckFiles -->|Yes| Verify[Verify Context] 110 | Verify --> Strategy[Develop Strategy] 111 | Strategy --> Present[Present Approach] 112 | ``` 113 | 114 | ### Act Mode 115 | ```mermaid 116 | flowchart TD 117 | Start[Start] --> Context[Check Memory Bank] 118 | Context --> Update[Update Documentation] 119 | Update --> Rules[Update .clinerules if needed] 120 | Rules --> Execute[Execute Task] 121 | Execute --> Document[Document Changes] 122 | ``` 123 | 124 | ## Documentation Updates 125 | 126 | Memory Bank updates occur when: 127 | 1. Discovering new project patterns 128 | 2. After implementing significant changes 129 | 3. When user requests with **update memory bank** (MUST review ALL files) 130 | 4. When context needs clarification 131 | 132 | ```mermaid 133 | flowchart TD 134 | Start[Update Process] 135 | 136 | subgraph Process 137 | P1[Review ALL Files] 138 | P2[Document Current State] 139 | P3[Clarify Next Steps] 140 | P4[Update .clinerules] 141 | 142 | P1 --> P2 --> P3 --> P4 143 | end 144 | 145 | Start --> Process 146 | ``` 147 | 148 | Note: When triggered by **update memory bank**, I MUST review every memory bank file, even if some don't require updates. Focus particularly on activeContext.md and progress.md as they track current state. 149 | 150 | ## Project Intelligence (.clinerules) 151 | 152 | The .clinerules file is my learning journal for each project. It captures important patterns, preferences, and project intelligence that help me work more effectively. As I work with you and the project, I'll discover and document key insights that aren't obvious from the code alone. 153 | 154 | ```mermaid 155 | flowchart TD 156 | Start{Discover New Pattern} 157 | 158 | subgraph Learn [Learning Process] 159 | D1[Identify Pattern] 160 | D2[Validate with User] 161 | D3[Document in .clinerules] 162 | end 163 | 164 | subgraph Apply [Usage] 165 | A1[Read .clinerules] 166 | A2[Apply Learned Patterns] 167 | A3[Improve Future Work] 168 | end 169 | 170 | Start --> Learn 171 | Learn --> Apply 172 | ``` 173 | 174 | ### What to Capture 175 | - Critical implementation paths 176 | - User preferences and workflow 177 | - Project-specific patterns 178 | - Known challenges 179 | - Evolution of project decisions 180 | - Tool usage patterns 181 | 182 | The format is flexible - focus on capturing valuable insights that help me work more effectively with you and the project. Think of .clinerules as a living document that grows smarter as we work together. 183 | 184 | REMEMBER: After every memory reset, I begin completely fresh. The Memory Bank is my only link to previous work. It must be maintained with precision and clarity, as my effectiveness depends entirely on its accuracy. 185 | ```` 186 | 187 | ## 3. Project Setup 188 | 189 | #### First Time Setup 190 | 191 | 1. Create a `memory-bank/` folder in your project root 192 | 2. Have a project brief ready (can be technical or non-technical) 193 | 3. Ask Cline to "initialize memory bank" 194 | 195 | #### Project Brief Tips 196 | 197 | * Can be as detailed or high-level as you like 198 | * Cline will fill in gaps appropriately 199 | * Focus on what matters most to you 200 | * Can be updated as project evolves 201 | 202 | ### 4. Working with Cline 203 | 204 | #### Best Practices 205 | 206 | * Use Plan mode for strategy discussions 207 | * Use Act mode for implementation 208 | * Let .clinerules evolve naturally 209 | * Trust Cline's learning process 210 | 211 | #### Key Commands 212 | 213 | * "follow your custom instructions" - starting a task, this will instruct Cline to read the context files and continue where he left off 214 | * "initialize memory bank" - Start fresh 215 | * "update memory bank" - Full documentation review 216 | * Toggle Plan/Act modes as needed 217 | 218 | #### Documentation Flow 219 | 220 | * projectbrief.md is your foundation 221 | * activeContext.md changes most often 222 | * progress.md tracks milestones 223 | * .clinerules captures learning 224 | 225 | ### 5. Tips for Success 226 | 227 | #### Getting Started 228 | 229 | * Start with a basic project brief 230 | * Let Cline create initial structure 231 | * Review and adjust as needed 232 | 233 | #### Ongoing Work 234 | 235 | * Let patterns emerge naturally 236 | * Don't force documentation updates 237 | * Trust the process 238 | * Watch for context confirmation 239 | 240 | #### Project Intelligence 241 | 242 | * Let Cline discover patterns 243 | * Validate important insights 244 | * Focus on non-obvious learnings 245 | * Use .clinerules as a learning tool 246 | 247 | Remember: The memory bank is Cline's only link to previous work. Its effectiveness depends entirely on maintaining clear, accurate documentation and confirming context preservation in every interaction. 248 | -------------------------------------------------------------------------------- /tools/assets/CheckpointsButtons.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nickbaumann98/cline_docs/82cfcc3a4a38608dbe45e18741a2bf3181901044/tools/assets/CheckpointsButtons.png -------------------------------------------------------------------------------- /tools/assets/checkpointsDemo.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nickbaumann98/cline_docs/82cfcc3a4a38608dbe45e18741a2bf3181901044/tools/assets/checkpointsDemo.gif -------------------------------------------------------------------------------- /tools/checkpoints.md: -------------------------------------------------------------------------------- 1 | # Checkpoints 2 | 3 | Checkpoints automatically save snapshots of your workspace after each step in a task. This powerful feature lets you: 4 | 5 | - Track and review changes made during a task 6 | - Roll back to any previous point if needed 7 | - Experiment confidently with auto-approve mode 8 | - Maintain full control over your workspace 9 | 10 | ## How Checkpoints Work 11 | 12 | Cline creates a checkpoint after each tool use (file edits, commands, etc.). These checkpoints: 13 | 14 | - Work alongside your Git workflow without interference 15 | - Have minimal performance impact 16 | - Handle large codebases efficiently 17 | - Maintain context between restores 18 | - Use a shadow Git repository to track changes 19 | 20 | 21 | ### Viewing Changes & Restoring to Checkpoint 22 | 23 | After each **Edit** or **Create** tool use, you can: 24 | 25 | 1. Click the "Compare" button to see modified files 26 | 2. Click the "Restore" button to open restore options 27 | 28 | ![Checkpoint Buttons](assets/CheckpointsButtons.png) 29 | 30 | ### Rolling Back 31 | 32 | To restore to a previous point: 33 | 34 | 1. Click the "Restore" button next to any step 35 | 2. Choose from three options: 36 | - **Restore Task and Workspace**: Reset both codebase and task to that point 37 | - **Restore Task Only**: Keep codebase changes but revert task context 38 | - **Restore Workspace Only**: Reset codebase while preserving task context 39 | 40 | ## Use Cases 41 | 42 | Checkpoints let you be more experimental with Cline. While human coding is often methodical and iterative, AI can make substantial changes quickly. Checkpoints help you track these changes and revert if needed. 43 | 44 | ### 1. Using Auto-Approve Mode 45 | - Provides safety net for rapid iterations 46 | - Makes it easy to undo unexpected results 47 | 48 | ### 2. Testing Different Approaches 49 | - Try multiple solutions confidently 50 | - Compare different implementations 51 | - Quickly revert to working states 52 | 53 | ![Checkpoints Demo](./assets/checkpointsDemo.gif) 54 | 55 | ## Best Practices 56 | 57 | 1. Review changes regularly 58 | 2. Use checkpoints as safety nets 59 | 3. Leverage auto-approve mode confidently 60 | 4. Restore selectively based on needs 61 | 5. Clean up old checkpoints periodically 62 | 63 | Checkpoints make Cline more powerful and reliable, giving you peace of mind and control over your workspace. 64 | -------------------------------------------------------------------------------- /tools/cline-tools-guide.md: -------------------------------------------------------------------------------- 1 | # Cline Tools Reference Guide 2 | 3 | ## What Can Cline Do? 4 | Cline is your AI assistant that can: 5 | - Edit and create files in your project 6 | - Run terminal commands 7 | - Search and analyze your code 8 | - Help debug and fix issues 9 | - Automate repetitive tasks 10 | - Integrate with external tools 11 | 12 | ## First Steps 13 | 1. **Start a Task** 14 | - Type your request in the chat 15 | - Example: "Create a new React component called Header" 16 | 17 | 2. **Provide Context** 18 | - Use @ mentions to add files, folders, or URLs 19 | - Example: "@file:src/components/App.tsx" 20 | 21 | 3. **Review Changes** 22 | - Cline will show diffs before making changes 23 | - You can edit or reject changes 24 | 25 | ## Key Features 26 | 1. **File Editing** 27 | - Create new files 28 | - Modify existing code 29 | - Search and replace across files 30 | 31 | 2. **Terminal Commands** 32 | - Run npm commands 33 | - Start development servers 34 | - Install dependencies 35 | 36 | 3. **Code Analysis** 37 | - Find and fix errors 38 | - Refactor code 39 | - Add documentation 40 | 41 | 4. **Browser Integration** 42 | - Test web pages 43 | - Capture screenshots 44 | - Inspect console logs 45 | 46 | ## Available Tools 47 | 48 | For the most up-to-date implementation details, you can view the full source code in the [Cline repository](https://github.com/cline/cline/blob/main/src/core/Cline.ts). 49 | 50 | Cline has access to the following tools for various tasks: 51 | 52 | 1. **File Operations** 53 | - `write_to_file`: Create or overwrite files 54 | - `read_file`: Read file contents 55 | - `replace_in_file`: Make targeted edits to files 56 | - `search_files`: Search files using regex 57 | - `list_files`: List directory contents 58 | 59 | 2. **Terminal Operations** 60 | - `execute_command`: Run CLI commands 61 | - `list_code_definition_names`: List code definitions 62 | 63 | 3. **MCP Tools** 64 | - `use_mcp_tool`: Use tools from MCP servers 65 | - `access_mcp_resource`: Access MCP server resources 66 | - Users can create custom MCP tools that Cline can then access 67 | - Example: Create a weather API tool that Cline can use to fetch forecasts 68 | 69 | 4. **Interaction Tools** 70 | - `ask_followup_question`: Ask user for clarification 71 | - `attempt_completion`: Present final results 72 | 73 | Each tool has specific parameters and usage patterns. Here are some examples: 74 | 75 | - Create a new file (write_to_file): 76 | ```xml 77 | 78 | src/components/Header.tsx 79 | 80 | // Header component code 81 | 82 | 83 | ``` 84 | 85 | - Search for a pattern (search_files): 86 | ```xml 87 | 88 | src 89 | function\s+\w+\( 90 | *.ts 91 | 92 | ``` 93 | 94 | - Run a command (execute_command): 95 | ```xml 96 | 97 | npm install axios 98 | false 99 | 100 | ``` 101 | 102 | ## Common Tasks 103 | 1. **Create a New Component** 104 | - "Create a new React component called Footer" 105 | 106 | 2. **Fix a Bug** 107 | - "Fix the error in src/utils/format.ts" 108 | 109 | 3. **Refactor Code** 110 | - "Refactor the Button component to use TypeScript" 111 | 112 | 4. **Run Commands** 113 | - "Run npm install to add axios" 114 | 115 | ## Getting Help 116 | - [Join the Discord community](https://discord.gg/Mjyj2Sm3) 117 | - Check the documentation 118 | - Provide feedback to improve Cline 119 | --------------------------------------------------------------------------------