Cline - 中文版 Docs
  • Cline Documentation
  • 入门指南
    • 快速开始
    • What is Cline?
  • Basics
    • Cline - 中文版胜算 说明文档
      • Cline 和模型上下文协议 (MCP) 服务器:提升 AI 能力
      • Interactive blocks
        • OpenAPI
      • Integrations
        • Cloud Provider Integration
        • Security Concerns
      • .clineignore 功能支持
  • Cline - 中文版胜算 说明文档
    • 什么是Cline - 胜算云增强版
    • 对于新程序员
    • 安装 Cline-胜算云增强版
    • 安装 Dev Essentials
    • 我们最喜欢的技术栈
    • 上下文管理
    • 型号选择指南
  • Getting Started
    • What is Cline?
    • For New Coders
    • Installing Cline
    • Installing Dev Essentials
    • Our Favorite Tech Stack
    • Context Management
    • Model Selection Guide
  • 提高提示技巧
    • 提示工程指南
    • Cline-胜算云增强版 内存库
  • Improving Your Prompting Skills
    • Prompt Engineering Guide
    • Cline Memory Bank
  • 探索 Cline 的工具
    • Cline-胜算云增强版 工具指南
  • 检查站
  • 计划与行动模式:有效人工智能发展指南
  • 新建任务工具
  • Remote Browser 支持
  • Exploring Cline's Tools
    • Cline Tools Guide
    • Checkpoints
    • Plan & Act Modes: A Guide to Effective AI Development
    • New Task Tool
  • Remote Browser Support
  • 企业解决方案
    • 安全问题
  • 云提供商集成
  • MCP 服务器
  • 自定义说明
  • Security Concerns
    • Security Concerns
  • Cloud Provider Integration
  • MCP Servers
  • Custom Instructions
  • MCP服务器
    • MCP概述
    • MCP市场
  • 从 GitHub 添加 MCP 服务器
  • 配置 MCP 服务器
  • 连接到远程服务器
  • MCP 传输机制
  • MCP 服务器开发协议
  • MCP Servers
    • MCP Overview
  • MCP Marketplace
  • Adding MCP Servers from GitHub
  • Configuring MCP Servers
  • Connecting to a Remote Server
  • MCP Transport Mechanisms
  • MCP Server Development Protocol
  • 自定义模型配置
    • 带有凭证身份验证的 AWS Bedrock
    • 带配置文件身份验证的 AWS Bedrock
    • GCP Vertex AI
  • LiteLLM 和 Cline-胜算云增强版(使用 Codestral)
  • Custom Model Configs
    • AWS Bedrock w/ Credentials Authentication
  • AWS Bedrock w/ Profile Authentication
  • GCP Vertex AI
  • LiteLLM & Cline (using Codestral)
  • 本地运行模型
    • 请先阅读
    • Ollama
    • LM 工作室
  • Ollama
  • LM Studio
  • Running Models Locally
  • More Info
    • Telemetry
    • 遥测
Powered by GitBook
On this page
  1. Exploring Cline's Tools

Plan & Act Modes: A Guide to Effective AI Development

PreviousCheckpointsNextNew Task Tool

Last updated 2 months ago

Overview

Plan & Act modes represent Cline's approach to structured AI development, emphasizing thoughtful planning before implementation. This dual-mode system helps developers create more maintainable, accurate code while reducing iteration time.

Use Plan to gather context before using Act to implement the plan

Understanding the Modes

Plan Mode

  • Optimized for context gathering and strategy

  • Cannot make changes to your codebase

  • Focused on understanding requirements and creating implementation plans

  • Enables full file reading for comprehensive project understanding

Act Mode

  • Streamlined for implementation based on established plans

  • Has access to all of Cline's building capabilities

  • Maintains context from the planning phase

  • Can execute changes to your codebase

Workflow Guide

1. Start with Plan Mode

Begin every significant development task in Plan mode:

In this mode:

  • Share your requirements

  • Let Cline analyze relevant files

  • Engage in dialogue to clarify objectives

  • Develop implementation strategy

2. Switch to Act Mode

Once you have a clear plan, switch to Act mode:

Act mode allows Cline to:

  • Execute against the agreed plan

  • Make changes to your codebase

  • Maintain context from planning phase

3. Iterate as Needed

Complex projects often require multiple plan-act cycles:

  • Return to Plan mode when encountering unexpected complexity

  • Use Act mode for implementing solutions

  • Maintain development momentum while ensuring quality

Best Practices

Planning Phase

  1. Be comprehensive with requirements

  2. Share relevant context upfront

  3. Point Cline to relevant files if he hasn't read them

  4. Validate approach before implementation

Implementation Phase

  1. Follow the established plan

  2. Monitor progress against objectives

  3. Track changes and their impact

  4. Document significant decisions

Power User Tips

Enhancing Planning

  • Use Plan mode to explore edge cases before implementation

  • Switch back to Plan when encountering unexpected complexity

  • Leverage file reading to validate assumptions early

  • Have Cline write markdown files of the plan for future reference

Common Patterns

When to Use Plan Mode

  • Starting new features

  • Debugging complex issues

  • Architectural decisions

  • Requirements analysis

When to Use Act Mode

  • Implementing agreed solutions

  • Making routine changes

  • Following established patterns

  • Executing test cases

Contributing

Share your experiences and improvements:

  • Participate in discussions

  • Submit feature requests

  • Report issues


Remember: The time invested in planning pays dividends in implementation quality and maintenance efficiency

Join our

Discord community