run prettier correctly on generated protos

.changeset/brown-sloths-search.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Add the o4-mini model in the isOminiModel

.changeset/calm-snakes-learn.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Allow option to collect events to send them in a bundle to avoid sending too many events

.changeset/chatty-planets-love.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+add open ai cache to ui

.changeset/chilled-paws-remain.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Fix ENAMETOOLONG when calling Claude Code

.changeset/chilly-oranges-play.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+disable autocapture

.changeset/clever-balloons-wave.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Update deployer team name

.changeset/clever-glasses-tickle.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Moved rule file conversions

.changeset/cool-bikes-learn.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+suggested model exists again

.changeset/curly-fireants-work.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+getRelativePaths protobus migration

.changeset/dull-beds-wash.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+getOllamaModels protobus migration

.changeset/fair-rats-explode.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add FeatureFlagProvider service for the Node.js extension side

.changeset/fifty-parents-clean.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+added copy buttons to task header and assistant messages

.changeset/five-eyes-rescue.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Increasing file size that can be read by cline

.changeset/flat-papayas-doubt.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Add org to team affiliation check

.changeset/fluffy-pears-cough.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+fix-bedrock-api

.changeset/gentle-paws-shout.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Add confirmation dialog to Delete All History button

.changeset/happy-radios-enjoy.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+breakpoint just in system prompt for gemini for OR and cline provider

.changeset/heavy-spoons-ring.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Fix for markdown copy excessive escape characters

.changeset/hungry-rules-relax.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+fetch cache details from generation endpoint

.changeset/lazy-dolls-smell.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Bump ollama from 0.5.13 to 0.5.15

.changeset/little-needles-play.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add npm script for issue creation

.changeset/long-worms-search.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate more info section to new docs

.changeset/modern-weeks-knock.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Only initialize posthog in the webview if the user has opted into telemetry

.changeset/nasty-cameras-do.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Extend ReasoningEffort to non-o3-mini reasoning models for all providers

.changeset/nasty-taxis-trade.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Re-enable tests in workflow

.changeset/old-jeans-applaud.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+requestVsCodeLmModels protobus migration

.changeset/purple-planes-speak.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Allow the user to form their next message while Cline is taking action

.changeset/quick-needles-smell.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Adding mistral medium-3 model

.changeset/quiet-cups-tie.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+updated gemini caching for OR and cline provider

.changeset/red-carrots-shout.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+searchFiles protobus migration

.changeset/rude-jeans-impress.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add ability to generate commit message via cline

.changeset/selfish-feet-camp.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+updated OR/cline provider to automate gemini models caching

.changeset/selfish-garlics-lay.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add Task Favorites and several proto messages related to tasks

.changeset/serious-cameras-pretend.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+getLmStudioModels protobus migration

.changeset/serious-wolves-trade.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+adding quote reply support

.changeset/shiny-falcons-hope.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add enterprise section to new docs

.changeset/shiny-snakes-occur.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Raise Errors when users try to upload images larger than 7500x7500 pixels

.changeset/shy-goats-deliver.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Make Previous Updates in the Announcement a dropdown

.changeset/silly-donkeys-judge.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate prompting section to new docs

.changeset/slimy-icons-sin.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate running models locally section to new docs

.changeset/smart-otters-admire.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+timestamp visualization

.changeset/stupid-hotels-brush.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Allow the user to scroll when Cline is editing a file by disabling auto-scroll when the user scrolls up

.changeset/tall-elephants-sort.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Removed deleteNonFavoritedTasks, moved popup to extension, cleaned up deletion logic

.changeset/tame-mirrors-destroy.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Add image links to docs

.changeset/thirty-needles-tie.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate MCP section to new docs

.changeset/tiny-doors-cover.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate custom model config section to new docs

.changeset/tricky-grapes-accept.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Fixed an issue where loading never finished when using an application inference profile for the model ID

.changeset/twenty-cobras-cry.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Add support for Gemini Implicit Caching

.changeset/two-jobs-notice.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+add ui for windsurf and cursor rules

.changeset/warm-gorillas-beam.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": patch
+---
+
+Batch selection and deletion of tasks in history

.changeset/wicked-seas-drive.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Migrate getting-started section to new docs

.changeset/witty-starfishes-sneeze.md

@@ -0,0 +1,5 @@
+---
+"claude-dev": minor
+---
+
+Task Timeline

.changeset/yellow-gifts-explain.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-host bridge migration - clipboard

.changeset/young-bulldogs-raise.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Refactor task class, moving auto approve

.clinerules/cline-overview.md

@@ -164,7 +164,6 @@ Key providers include:
 - **OpenRouter**: Meta-provider supporting multiple model providers
 - **AWS Bedrock**: Integration with Amazon's AI services
 - **Gemini**: Google's AI models
-- **Cerebras**: High-performance inference with Llama, Qwen, and DeepSeek models
 - **Ollama**: Local model hosting
 - **LM Studio**: Local model hosting
 - **VSCode LM**: VSCode's built-in language models
@@ -210,7 +209,7 @@ class Task {
         switch (chunk.type) {
           case "text":
             // Parse into content blocks
-            this.assistantMessageContent = parseAssistantMessageV2(chunk.text)
+            this.assistantMessageContent = parseAssistantMessage(chunk.text)
             // Present blocks to user
             await this.presentAssistantMessage()
             break

.clinerules/protobuf-development.md

@@ -1,89 +0,0 @@
-# Cline Protobuf Development Guide
-
-This guide outlines how to add new gRPC endpoints for communication between the webview (frontend) and the extension host (backend).
-
-## Overview
-
-Cline uses [Protobuf](https://protobuf.dev/) to define a strongly-typed API, ensuring efficient and type-safe communication. All definitions are in the `/proto` directory. The compiler and plugins are included as project dependencies, so no manual installation is needed.
-
-## Key Concepts & Best Practices
-
--   **File Structure**: Each feature domain should have its own `.proto` file (e.g., `account.proto`, `task.proto`).
--   **Message Design**:
-    -   For simple, single-value data, use the shared types in `proto/common.proto` (e.g., `StringRequest`, `Empty`, `Int64Request`). This promotes consistency.
-    -   For complex data structures, define custom messages within the feature's `.proto` file (see `task.proto` for examples like `NewTaskRequest`).
--   **Naming Conventions**:
-    -   Services: `PascalCaseService` (e.g., `AccountService`).
-    -   RPCs: `camelCase` (e.g., `accountEmailIdentified`).
-    -   Messages: `PascalCase` (e.g., `StringRequest`).
--   **Streaming**: For server-to-client streaming, use the `stream` keyword on the response type. See `subscribeToAuthCallback` in `account.proto` for an example.
-
----
-
-## 4-Step Development Workflow
-
-Here’s how to add a new RPC, using `scrollToSettings` as an example.
-
-### 1. Define the RPC in a `.proto` File
-
-Add your service method to the appropriate file in the `proto/` directory.
-
-**File: `proto/ui.proto`**
-```proto
-service UiService {
-  // ... other RPCs
-  // Scrolls to a specific settings section in the settings view
-  rpc scrollToSettings(StringRequest) returns (KeyValuePair);
-}
-```
-Here, we use the common `StringRequest` and `KeyValuePair` types.
-
-### 2. Compile Definitions
-
-After editing a `.proto` file, regenerate the TypeScript code. From the project root, run:
-```bash
-npm run protos
-```
-This command compiles all `.proto` files and outputs the generated code to `src/generated/` and `src/shared/`. Do not edit these generated files manually.
-
-### 3. Implement the Backend Handler
-
-Create the RPC implementation in the backend. Handlers are located in `src/core/controller/[service-name]/`.
-
-**File: `src/core/controller/ui/scrollToSettings.ts`**
-```typescript
-import { Controller } from ".."
-import { StringRequest, KeyValuePair } from "../../../shared/proto/common"
-
-/**
- * Executes a scroll to settings action
- * @param controller The controller instance
- * @param request The request containing the ID of the settings section to scroll to
- * @returns KeyValuePair with action and value fields for the UI to process
- */
-export async function scrollToSettings(controller: Controller, request: StringRequest): Promise<KeyValuePair> {
-	return KeyValuePair.create({
-		key: "scrollToSettings",
-		value: request.value || "",
-	})
-}
-```
-
-### 4. Call the RPC from the Webview
-
-Call the new RPC from a React component in `webview-ui/`. The generated client makes this simple.
-
-**File: `webview-ui/src/components/browser/BrowserSettingsMenu.tsx`** (Example)
-```tsx
-import { UiServiceClient } from "../../../services/grpc"
-import { StringRequest } from "../../../../shared/proto/common"
-
-// ... inside a React component
-const handleMenuClick = async () => {
-    try {
-        await UiServiceClient.scrollToSettings(StringRequest.create({ value: "browser" }))
-    } catch (error) {
-        console.error("Error scrolling to browser settings:", error)
-    }
-}
-```

.clinerules/workflows/extension-release.md

@@ -1,549 +0,0 @@
-The goal of this workflow is to take a changeset for a release of Cline, an autonomous coding agent extension that plugs right into your IDE, and write the updated announcement component, and the updated changelog. 
-
-
-For reference, here are some examples of how we converted previous changesets to announcement components / changelogs. 
-
-
-- 3.14
-<changeset>
-This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
-
-Releases
-claude-dev@3.14.0
-Minor Changes
-77c9863: create clinerules folder if its currently a file and creating new rule
-0ffb7dd: disabling shift hint for now & improving tooltip behavior
-79b76fd: Add support for custom model ID in AWS Bedrock provider, enabling use of Application Inference Profile.
-eb6e481: Full support for LaTeX rendering
-df37f29: Add support for custom API request timeout. Previously, timeouts were hardcoded to 30 seconds for providers like Ollama or 15 seconds for OpenRouter and Cline. Now users can set a custom timeout value in milliseconds through the settings interface.
-e4d26be: allow cursorrules and windsurfrules
-c5de50f: Fix Handle @withRetry() SyntaxError when running extension locally issue
-61d2f42: enabled pricing calculation for gemini and vertex + more robust caching & cache tracking for gemini & vertex
-aed152b: add truncation notice when truncating manually
-2fe2405: Migrate Cline Tools Section to new docs
-19cc8bc: Add a timeout setting for the terminal connection, allowing users to adjust this if they are having timeout issues
-03d4410: Added copy button to code blocks.
-c78fe23: addressed race condition in terminal command usage
-91e222f: add checkpoints after more messages
-14230e7: add newrule slash command
-1c7d33a: Add remote config with posthog allowing for disabling new features until they're reading, making for a better developer experience.
-4196c14: add cache ui for open router and cline provider
-d97424f: showing expanded task by default
-5294e78: Refactor to not pass a message for showing the MCP View from the servers modal
-70cc437: Fix Windows path issue: Correct handling of import.meta.url to avoid leading slash in pathname
-4b697d8: Migrate the addRemoteServer to protobus
-Patch Changes
-c63d9a1: updated drag and drop text to say "drop" instead of "drag"
-459adf0: Add markdown copy to chat
-74ec823: Minor UX improvement to drag and drop ux
-b0961f4: Remove linear pull request action
-e9ce384: searchCommits protobus migration
-5802b68: createRuleFile protobus migration
-df7f9fc: Add dependsOn to more blocks in the tasks.json
-41ae732: Fix for git commit mentions in repos with no git commits
-7e78445: Adding args to allow Cursor to open workspaces (for checkpoint testing/development)
-bdfda6f: feat(bedrock): Introduce Amazon Nova Premier
-65243ad: Introduce UI library for future UI development
-4565e06: checkIsImageURL migrated to protobus
-5a8e9d8: protobus migration for openImage
-deeda6e: Lowering Gemini cache TTL time
-db0b022: Adding UI to show openrouter balance next to provider
-4650ffa: deleteRuleFile protobus migration
-d4bd755: fix cost calculation
-</changeset>
-
-<changelog>
-## [3.14.0]
-
--   Add UI to show openrouter balance next to provider
--   Add support for custom model ID in AWS Bedrock provider, enabling use of Application Inference Profile (Thanks @clicube!)
--   Add more robust caching & cache tracking for gemini & vertex providers
--   Add support for LaTeX rendering
--   Add support for custom API request timeout. Timeouts were 15-30s, but can now be configured via settings for OpenRouter/Cline & Ollama (Thanks @WingsDrafterwork!)
--   Add truncation notice when truncating manually
--   Add a timeout setting for the terminal connection, allowing users to set a time to wait for terminal startup
--   Add copy button to code blocks
--   Add copy button to markdown blocks (Thanks @weshoke!)
--   Add checkpoints to more messages
--   Add slash command to create a new rules file (/newrule)
--   Add cache ui for open router and cline provider
--   Add Amazon Nova Premier model to Bedrock (Thanks @watany!)
--   Add support for cursorrules and windsurfrules
--   Add support for batch history deletion (Thanks @danix800!)
--   Improve Drag & Drop experience
--   Create clinerules folder creating new rule if it's needed
--   Enable pricing calculation for gemini and vertex providers
--   Refactor message handling to not show the MCP View of the server modal
--   Migrate the addRemoteServer to protobus (Thanks @DaveFres!)
--   Update task header to be expanded by default
--   Update Gemini cache TTL time to 15 minutes
--   Fix race condition in terminal command usage
--   Fix to correctly handle `import.meta.url`, avoiding leading slash in pathname for Windows (Thanks @DaveFres!)
--   Fix @withRetry() decoration syntax error when running extension locally (Thanks @DaveFres!)
--   Fix for git commit mentions in repos with no git commits
--   Fix cost calculation (Thanks @BarreiroT!)
-</changelog>
-
-
-<announcement-component>
-const Announcement = ({ version, hideAnnouncement }: AnnouncementProps) => {
-	const minorVersion = version.split(".").slice(0, 2).join(".") // 2.0.0 -> 2.0
-	return (
-		<div style={containerStyle}>
-			<VSCodeButton appearance="icon" onClick={hideAnnouncement} style={closeIconStyle}>
-				<span className="codicon codicon-close"></span>
-			</VSCodeButton>
-			<h3 style={h3TitleStyle}>
-				🎉{"  "}New in v{minorVersion}
-			</h3>
-			<ul style={ulStyle}>
-				<li>
-					<b>Gemini prompt caching:</b> Gemini and Vertex providers now support prompt caching and price tracking for
-					Gemini models.
-				</li>
-				<li>
-					<b>Copy Buttons:</b> Buttons were added to Markdown and Code blocks that allow you to copy their contents
-					easily.
-				</li>
-				<li>
-					<b>/newrule command:</b> New slash command to have cline write your .clinerules for you based on your
-					workflow.
-				</li>
-				<li>
-					<b>Drag and drop improvements:</b> Don't forget to hold shift while dragging files!
-				</li>
-				<li>Added more checkpoints across the task, allowing you to restore from more than just file changes.</li>
-				<li>Added support for rendering LaTeX in message responses. (Try asking Cline to show the quadratic formula)</li>
-			</ul>
-			<Accordion isCompact className="pl-0">
-				<AccordionItem
-					key="1"
-					aria-label="Previous Updates"
-					title="Previous Updates:"
-					classNames={{
-						trigger: "bg-transparent border-0 pl-0 pb-0 w-fit",
-						title: "font-bold text-[var(--vscode-foreground)]",
-						indicator:
-							"text-[var(--vscode-foreground)] mb-0.5 -rotate-180 data-[open=true]:-rotate-90 rtl:rotate-0 rtl:data-[open=true]:-rotate-90",
-					}}>
-					<ul style={ulStyle}>
-						<li>
-							<b>Global Cline Rules:</b> store multiple rules files in Documents/Cline/Rules to share between
-							projects.
-						</li>
-						<li>
-							<b>Cline Rules Popup:</b> New button in the chat area to view workspace and global cline rules files
-							to plug and play specific rules for the task
-						</li>
-						<li>
-							<b>Slash Commands:</b> Type <code>/</code> in chat to see the list of quick actions, like starting a
-							new task (more coming soon!)
-						</li>
-						<li>
-							<b>Edit Messages:</b> You can now edit a message you sent previously by clicking on it. Optionally
-							restore your project when the message was sent!
-						</li>
-					</ul>
-				</AccordionItem>
-			</Accordion>
-
-			{/*
-			// Leave this here for an example of how to structure the announcement
-			<ul style={{ margin: "0 0 8px", paddingLeft: "12px" }}>
-				 <li>
-					OpenRouter now supports prompt caching! They also have much higher rate limits than other providers,
-					so I recommend trying them out.
-					<br />
-					{!apiConfiguration?.openRouterApiKey && (
-						<VSCodeButtonLink
-							href={getOpenRouterAuthUrl(vscodeUriScheme)}
-							style={{
-								transform: "scale(0.85)",
-								transformOrigin: "left center",
-								margin: "4px -30px 2px 0",
-							}}>
-							Get OpenRouter API Key
-						</VSCodeButtonLink>
-					)}
-					{apiConfiguration?.openRouterApiKey && apiConfiguration?.apiProvider !== "openrouter" && (
-						<VSCodeButton
-							onClick={() => {
-								vscode.postMessage({
-									type: "apiConfiguration",
-									apiConfiguration: { ...apiConfiguration, apiProvider: "openrouter" },
-								})
-							}}
-							style={{
-								transform: "scale(0.85)",
-								transformOrigin: "left center",
-								margin: "4px -30px 2px 0",
-							}}>
-							Switch to OpenRouter
-						</VSCodeButton>
-					)}
-				</li>
-				<li>
-					<b>Edit Cline's changes before accepting!</b> When he creates or edits a file, you can modify his
-					changes directly in the right side of the diff view (+ hover over the 'Revert Block' arrow button in
-					the center to undo "<code>{"// rest of code here"}</code>" shenanigans)
-				</li>
-				<li>
-					New <code>search_files</code> tool that lets Cline perform regex searches in your project, letting
-					him refactor code, address TODOs and FIXMEs, remove dead code, and more!
-				</li>
-				<li>
-					When Cline runs commands, you can now type directly in the terminal (+ support for Python
-					environments)
-				</li>
-			</ul>*/}
-			<div style={hrStyle} />
-			<p style={linkContainerStyle}>
-				Join us on{" "}
-				<VSCodeLink style={linkStyle} href="https://x.com/cline">
-					X,
-				</VSCodeLink>{" "}
-				<VSCodeLink style={linkStyle} href="https://discord.gg/cline">
-					discord,
-				</VSCodeLink>{" "}
-				or{" "}
-				<VSCodeLink style={linkStyle} href="https://www.reddit.com/r/cline/">
-					r/cline
-				</VSCodeLink>
-				for more updates!
-			</p>
-		</div>
-	)
-}
-</announcement-component>
-
-- 3.13
-
-<changeset>
-Minor Changes
-2964388: Added copy button to MermaidBlock component
-75143a7: Add the ability to fetch from global cline rules files
-Patch Changes
-a0252e7: convert inline style to tailwind css of file SettingsView.tsx
-ab59bd9: Add stream options back to xai provider
-7276f50: Icons to indicate an action is occuring outside of the users workspace
-0b19ba6: update to NEW model
-</changeset>
-
-<changelog>
-## [3.13.0]
-
--   Add Cline rules popover under the chat field, allowing you to easily add, enable & disable workspace level or global rule files
--   Add new slash command menu letting you type “/“ to do quick actions like creating new tasks
--   Add ability to edit past messages, with options to restore your workspace back to that point
--   Allow sending a message when selecting an option provided by the question or plan tool
--   Add command to jump to Cline's chat input
--   Add support for OpenAI o3 & 4o-mini (Thanks @PeterDaveHello and @arafatkatze!)
--   Add baseURL option for Google Gemini provider (Thanks @owengo and @olivierhub!)
--   Add support for Azure's DeepSeek model. (Thanks @yt3trees!)
--   Add ability for models that support it to receive image responses from MCP servers (Thanks @rikaaa0928!)
--   Improve search and replace diff editing by making it more flexible with models that fail to follow structured output instructions. (Thanks @chi-cat!)
--   Add detection of Ctrl+C termination in terminal, improving output reading issues
--   Fix issue where some commands with large output would cause UI to freeze
--   Fix token usage tracking issues with vertex provider (Thanks @mzsima!)
--   Fix issue with xAI reasoning content not being parsed (Thanks @mrubens!)
-</changelog>
-
-<announcement-component>
-const Announcement = ({ version, hideAnnouncement }: AnnouncementProps) => {
-	const minorVersion = version.split(".").slice(0, 2).join(".") // 2.0.0 -> 2.0
-	return (
-		<div style={containerStyle}>
-			<VSCodeButton appearance="icon" onClick={hideAnnouncement} style={closeIconStyle}>
-				<span className="codicon codicon-close"></span>
-			</VSCodeButton>
-			<h3 style={h3TitleStyle}>
-				🎉{"  "}New in v{minorVersion}
-			</h3>
-			<ul style={ulStyle}>
-				<li>
-					<b>Global Cline Rules:</b> store multiple rules files in Documents/Cline/Rules to share between projects.
-				</li>
-				<li>
-					<b>Cline Rules Popup:</b> New button in the chat area to view workspace and global cline rules files to plug
-					and play specific rules for the task
-				</li>
-				<li>
-					<b>Slash Commands:</b> Type <code>/</code> in chat to see the list of quick actions, like starting a new task
-					(more coming soon!)
-				</li>
-				<li>
-					<b>Edit Messages:</b> You can now edit a message you sent previously by clicking on it. Optionally restore
-					your project when the message was sent!
-				</li>
-			</ul>
-			<h4 style={{ margin: "5px 0 5px" }}>Previous Updates:</h4>
-			<ul style={ulStyle}>
-				<li>
-					<b>Model Favorites:</b> You can now mark your favorite models when using Cline & OpenRouter providers for
-					quick access!
-				</li>
-				<li>
-					<b>Faster Diff Editing:</b> Improved animation performance for large files, plus a new indicator in chat
-					showing the number of edits Cline makes.
-				</li>
-				<li>
-					<b>New Auto-Approve Options:</b> Turn off Cline's ability to read and edit files outside your workspace.
-				</li>
-			</ul>
-			{/*
-			// Leave this here for an example of how to structure the announcement
-			<ul style={{ margin: "0 0 8px", paddingLeft: "12px" }}>
-				 <li>
-					OpenRouter now supports prompt caching! They also have much higher rate limits than other providers,
-					so I recommend trying them out.
-					<br />
-					{!apiConfiguration?.openRouterApiKey && (
-						<VSCodeButtonLink
-							href={getOpenRouterAuthUrl(vscodeUriScheme)}
-							style={{
-								transform: "scale(0.85)",
-								transformOrigin: "left center",
-								margin: "4px -30px 2px 0",
-							}}>
-							Get OpenRouter API Key
-						</VSCodeButtonLink>
-					)}
-					{apiConfiguration?.openRouterApiKey && apiConfiguration?.apiProvider !== "openrouter" && (
-						<VSCodeButton
-							onClick={() => {
-								vscode.postMessage({
-									type: "apiConfiguration",
-									apiConfiguration: { ...apiConfiguration, apiProvider: "openrouter" },
-								})
-							}}
-							style={{
-								transform: "scale(0.85)",
-								transformOrigin: "left center",
-								margin: "4px -30px 2px 0",
-							}}>
-							Switch to OpenRouter
-						</VSCodeButton>
-					)}
-				</li>
-				<li>
-					<b>Edit Cline's changes before accepting!</b> When he creates or edits a file, you can modify his
-					changes directly in the right side of the diff view (+ hover over the 'Revert Block' arrow button in
-					the center to undo "<code>{"// rest of code here"}</code>" shenanigans)
-				</li>
-				<li>
-					New <code>search_files</code> tool that lets Cline perform regex searches in your project, letting
-					him refactor code, address TODOs and FIXMEs, remove dead code, and more!
-				</li>
-				<li>
-					When Cline runs commands, you can now type directly in the terminal (+ support for Python
-					environments)
-				</li>
-			</ul>*/}
-			<div style={hrStyle} />
-			<p style={linkContainerStyle}>
-				Join us on{" "}
-				<VSCodeLink style={linkStyle} href="https://x.com/cline">
-					X,
-				</VSCodeLink>{" "}
-				<VSCodeLink style={linkStyle} href="https://discord.gg/cline">
-					discord,
-				</VSCodeLink>{" "}
-				or{" "}
-				<VSCodeLink style={linkStyle} href="https://www.reddit.com/r/cline/">
-					r/cline
-				</VSCodeLink>
-				for more updates!
-			</p>
-		</div>
-	)
-}
-</announcement-component>
-
-
-We have a changeset PR that automatically generated as new unreleased PRs are merged into main, the PR is always called "Changeset version bump" and the author is github-actions. 
-
-The Changeset PR description looks something like this:
-
-<changeset-pr-description>
-This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
-
-
-# Releases
-## claude-dev@3.16.0
-
-### Minor Changes
-
--   c6e8b04: Recent task list is now collapsible, allowing users to hide their recent tasks (e.g. when sharing their screen).
--   aabe4ae: Add detection for new users to display special components
--   6c18d51: adds global endpoint for vertex ai users
--   080ed7c: Add Tailwind CSS IntelliSense to the the recommended extensions list
--   5147e28: new workflow feature
-
-### Patch Changes
-
--   c0b3c69: fix eternal loading states when the last message is a checkpoint
--   570ece3: selectImages protos migration
--   8d8452e: askResponse protobus migration
--   cd1ff2a: Finishing the migration of Vscode Advanced settings to Settings Webview
-</changeset-pr-description>
-
-The changeset pr is ALWAYS on the following branch: `changeset-release/main`.
-
-I have the `gh` command line tool set up and authenticated, so you have everything you need.
-
-The first step is to get the full diff from the changeset PR to look at the changes that were automatically made to the `CHANGELOG.md` file. By default it will automatically add a new section to the changelog.md file with the new version. The problem with the automatically generated section is that it just takes the text that the developers threw into their changeset files for each corresponding PR, and they can be pretty vague and bad. Additionally there's some stuff that is totally irrelevant for the end user, like minor refactoring changes. So I manually typically go in and update this section to be a proper changelog that will show up in our patchnotes. You can look at how the rest of the file is done because those are all good examples of us updating this to use good language for the end user. We usually put new features up top (and the most exciting flagship features at the very top), and then bug fixes/improvements at the bottom. Having some basic organization to the ordering of the bullet points by content is nice. But use common sense. 
-
-To handle this process effectively, do the following:
-
-For each of the automatically generated bullet points in the Changelog.md, you should
-1. Take the commit hash at the start of the bullet point, and use the `gh` command line tool find the PR that it was associated with. 
-2. Use the `gh` command to get the PR title/description/discussion to understand the context surrounding the PR.
-3. Use the `gh` command line tool to get the full PR diff to fully understand the changes made in the code.
-4. Synthesize that knowledge to determine (a) whether or not this change is relevant to end users and (b) what the text & ordering of the line should be.  
-5. Update the `CHANGELOG.md` accordingly 
-
-Do this for every single item in the list from the autogenerated bullet points. We want to be diligent and have a full understanding of every feature so we can make the best changelog ever!
-
-Here are some principles for good changelogs from keepchangelog.com, a handy guide:
-
-<keepachangelog-pinciples-for-good-changelogs>
-### Guiding Principles
-- Changelogs are for humans, not machines.
-- There should be an entry for every single version.
-- The same types of changes should be grouped.
-- The latest version comes first.
-
-### Bullet points in the changelog should follow these principles:
-- Types of changes
-- Added for new features.
-- Changed for changes in existing functionality.
-- Deprecated for soon-to-be removed features.
-- Removed for now removed features.
-- Fixed for any bug fixes.
-- Security in case of vulnerabilities.
-</keepachangelog-pinciples-for-good-changelogs>
-
-Lastly, when developers make a PR, they typically make a changeset. And they have 3 options when making the changeset:
-
-1. Patch
-2. Minor
-3. Major
-
-Sometimes they label something as minor when really it should just be a patch. Or vice versa. Because of this, the automatic version bump may be incorrect. So when starting out this workflow, you should use the <ask_followup_question> tool to confirm with me whether or not this should be a patch bump (show the old version number and what the proposed new version number would be) or a minor bump. Part of the release process is making sure the version in package.json that is automatically changed actually corresponds with what we decided the bump should actually be based on the features. ALL these modifications happen in the `changeset-release/main` branch btw. 
-
-<important_note>
-Before doing any of this, make sure you check out the `changeset-release/main` and pull the most recent up to date changes. Then perform all this work in that branch. 
-
-New announcement banners should ONLY be made for minor version bumps or higher. That's another reason why double checking if the changelog warrants the bump is important.
-
-Also, SUPER important: For any external contributors that aren't part of the cline github organization, we always want to add a (Thanks @username!) at the end of the changelog to attribute them properly. We're an open source project and it's ethical to do this.
-</important_note>
-
-Once the changelog looks good, and the version number looks good, we gotta double check that the version number in the changelog has the brackets around it. And as a final step, double check the package.json version number matches the latest number in the changelog. And as the ultimate final step we run `npm run install:all` to make sure the package version number permiates through the lock file. 
-
-
-<detailed_sequence_of_steps>
-# Cline Release Process - Detailed Sequence of Steps
-
-## Before Starting
-1. First, examine the changeset PR without checking it out:
-   ```bash
-   gh pr view changeset-release/main
-   ```
-
-2. View the PR diff to see the auto-generated CHANGELOG.md changes:
-   ```bash
-   gh pr diff changeset-release/main > changeset-diff.txt
-   cat changeset-diff.txt | grep -A 50 "CHANGELOG.md"
-   ```
-
-## Initial Setup
-3. Once you're ready to start, checkout and update the changeset release branch:
-   ```bash
-   git checkout changeset-release/main
-   git pull origin changeset-release/main
-   ```
-
-## Analyzing Each Change
-4. For each commit hash in the auto-generated changelog entries:
-
-   a. Find the PR number associated with a commit hash:
-      ```bash
-      gh pr list --search "<commit-hash>" --state merged
-      ```
-   
-   b. Get PR details for better context:
-      ```bash
-      gh pr view <PR-number>
-      ```
-   
-   c. Check if the contributor is external to determine if attribution is needed:
-      ```bash
-      # Extract username from PR
-      USERNAME=$(gh pr view <PR-number> --json author --jq .author.login)
-      
-      # Check if user is a member of the Cline organization
-	  # this command is a bit finnicky, but it 100% works. 
-	  # if you see a `Error executing command: The command ran successfully, but we couldn't capture its output. Please proceed accordingly.` error, just retry it until you actually get the output
-	  # don't make any assumptions, just retry the command to actually get the output and determine if they're external or not.
-	  # no output means they are an external contributor, otherwise if there is output they are an internal contributor (part of our github org)
-      gh api "orgs/cline/members" --jq "map(.login)" | grep -i "pashpashpash"
-      ```
-   
-   d. View the full PR diff to understand code changes:
-      ```bash
-      gh pr diff <PR-number> > pr-diff-<PR-number>.txt
-      cat pr-diff-<PR-number>.txt
-      ```
-
-## Updating the Changelog
-5. Based on PR analysis, update the CHANGELOG.md with user-friendly descriptions:
-   - Use the `<replace_in_file>` tool to edit the CHANGELOG.md file
-   - Group by feature type (Added, Changed, Fixed)
-   - Put most exciting features at the top
-   - Move bug fixes and small improvements to the bottom
-   - Use clear, end-user focused language
-   - For external contributors, add attribution at the end of the relevant entry: `(Thanks @username!)`
-
-## Version Number Verification
-6. Confirm the version bump is appropriate:
-   - Check package.json to verify the auto-generated version number:
-     ```bash
-     cat package.json | grep "\"version\""
-     ```
-   - If the feature set doesn't warrant a minor bump, use the `<replace_in_file>` tool to modify package.json
-
-7. Ensure the version in CHANGELOG.md has brackets around it:
-   ```
-   ## [3.16.0]
-   ```
-
-## Creating the Announcement (for minor/major versions only)
-8. If this is a minor version bump, create/update the announcement component:
-   - Use the `<replace_in_file>` tool to edit the src/views/components/announcement.tsx file
-   - Update the highlights based on key features
-   - Move previous version highlights to the "Previous Updates" section
-   - Use the previous announcement components as reference for structure
-
-## Finalizing the Release
-9. Update dependencies with the new version number:
-   ```bash
-   npm run install:all
-   ```
-
-10. Commit your changes:
-    ```bash
-    git add CHANGELOG.md package.json package-lock.json src/views/components/announcement.tsx
-    git commit -m "Update CHANGELOG.md and announcement for version 3.16.0"
-    ```
-
-11. Push your changes to the changeset branch:
-    ```bash
-    git push origin changeset-release/main
-    ```
-
-12. Check that your changes pushed successfully:
-    ```bash
-    git status
-    ```
-</detailed_sequence_of_steps>

.clinerules/workflows/pr-review.md

@@ -1,351 +0,0 @@
-You have access to the `gh` terminal command. I already authenticated it for you. Please review it to use the PR that I asked you to review. You're already in the `cline` repo.
-
-<detailed_sequence_of_steps>
-# GitHub PR Review Process - Detailed Sequence of Steps
-
-## 1. Gather PR Information
-1. Get the PR title, description, and comments:
-   ```bash
-   gh pr view <PR-number> --json title,body,comments
-   ```
-
-2. Get the full diff of the PR:
-   ```bash
-   gh pr diff <PR-number>
-   ```
-
-## 2. Understand the Context
-1. Identify which files were modified in the PR:
-   ```bash
-   gh pr view <PR-number> --json files
-   ```
-
-2. Examine the original files in the main branch to understand the context:
-   ```xml
-   <read_file>
-   <path>path/to/file</path>
-   </read_file>
-   ```
-
-3. For specific sections of a file, you can use search_files:
-   ```xml
-   <search_files>
-   <path>path/to/directory</path>
-   <regex>search term</regex>
-   <file_pattern>*.ts</file_pattern>
-   </search_files>
-   ```
-
-## 3. Analyze the Changes
-1. For each modified file, understand:
-   - What was changed
-   - Why it was changed (based on PR description)
-   - How it affects the codebase
-   - Potential side effects
-
-2. Look for:
-   - Code quality issues
-   - Potential bugs
-   - Performance implications
-   - Security concerns
-   - Test coverage
-
-## 4. Ask for User Confirmation
-1. Before making a decision, ask the user if you should approve the PR, providing your assessment and justification:
-   ```xml
-   <ask_followup_question>
-   <question>Based on my review of PR #<PR-number>, I recommend [approving/requesting changes]. Here's my justification:
-   
-   [Detailed justification with key points about the PR quality, implementation, and any concerns]
-   
-   Would you like me to proceed with this recommendation?</question>
-   <options>["Yes, approve the PR", "Yes, request changes", "No, I'd like to discuss further"]</options>
-   </ask_followup_question>
-   ```
-
-## 5. Ask if User Wants a Comment Drafted
-1. After the user decides on approval/rejection, ask if they would like a comment drafted:
-   ```xml
-   <ask_followup_question>
-   <question>Would you like me to draft a comment for this PR that you can copy and paste?</question>
-   <options>["Yes, please draft a comment", "No, I'll handle the comment myself"]</options>
-   </ask_followup_question>
-   ```
-
-2. If the user wants a comment drafted, provide a well-structured comment they can copy:
-   ```
-   Thank you for this PR! Here's my assessment:
-
-   [Detailed assessment with key points about the PR quality, implementation, and any suggestions]
-
-   [Include specific feedback on code quality, functionality, and testing]
-   ```
-
-## 6. Make a Decision
-1. Approve the PR if it meets quality standards:
-   ```bash
-   # For single-line comments:
-   gh pr review <PR-number> --approve --body "Your approval message"
-   
-   # For multi-line comments with proper whitespace formatting:
-   cat << EOF | gh pr review <PR-number> --approve --body-file -
-   Thanks @username for this PR! The implementation looks good.
-
-   I particularly like how you've handled X and Y.
-
-   Great work!
-   EOF
-   ```
-
-2. Request changes if improvements are needed:
-   ```bash
-   # For single-line comments:
-   gh pr review <PR-number> --request-changes --body "Your feedback message"
-   
-   # For multi-line comments with proper whitespace formatting:
-   cat << EOF | gh pr review <PR-number> --request-changes --body-file -
-   Thanks @username for this PR!
-
-   The implementation looks promising, but there are a few things to address:
-
-   1. Issue one
-   2. Issue two
-
-   Please make these changes and we can merge this.
-   EOF
-   ```
-
-   Note: The `cat << EOF | ... --body-file -` approach preserves all whitespace and formatting without requiring temporary files. The `-` parameter tells the command to read from standard input.
-</detailed_sequence_of_steps>
-
-<example_review_process>
-# Example PR Review Process
-
-Let's walk through a real example of reviewing PR #3627 which fixes the thinking mode calculation for Claude 3.7 models.
-
-## Step 1: Gather PR Information
-
-```bash
-# Get PR details
-gh pr view 3627 --json title,body,comments
-
-# Get the full diff
-gh pr diff 3627
-```
-
-## Step 2: Understand the Context
-
-```xml
-# Examine the original files to understand what's being changed
-<read_file>
-<path>src/shared/api.ts</path>
-</read_file>
-
-# Look at the ThinkingBudgetSlider component implementation
-<read_file>
-<path>webview-ui/src/components/settings/ThinkingBudgetSlider.tsx</path>
-</read_file>
-
-# Check how thinking mode is currently handled in API providers
-<search_files>
-<path>src/api/providers</path>
-<regex>reasoningOn</regex>
-<file_pattern>*.ts</file_pattern>
-</search_files>
-```
-
-## Step 3: Analyze the Changes
-
-From the PR information and code examination, we can see that:
-
-1. The PR fixes an issue with the thinking mode budget calculation for Claude 3.7 models
-2. Currently, the thinking budget is incorrectly calculated as 80% of maxTokens (8192), resulting in 6553 tokens
-3. Claude 3.7 actually supports a much larger thinking budget (up to 64000 tokens)
-4. The PR adds a `thinkingConfig` property with `maxBudget: 64000` to model definitions
-5. It updates API handlers to use this value when reasoning mode is enabled
-6. It enhances the slider component to calculate max values based on model-specific percentages
-7. Comprehensive tests were added to verify the calculations
-
-## Step 4: Ask for User Confirmation
-
-```xml
-<ask_followup_question>
-<question>Based on my review of PR #3627, I recommend approving this PR. Here's my justification:
-
-1. The PR correctly fixes the thinking mode budget calculation for Claude 3.7 models
-2. It properly implements the thinkingConfig.maxBudget property (64000) for Claude 3.7 models
-3. It applies the appropriate percentage (50%) for the slider calculation
-4. The changes are well-tested with comprehensive unit tests
-5. The implementation is clean and follows the project's coding standards
-6. The PR includes helpful screenshots demonstrating the fix
-
-Would you like me to proceed with approving this PR?</question>
-<options>["Yes, approve the PR", "No, I'd like to discuss further", "Let me review it myself first"]</options>
-</ask_followup_question>
-```
-
-## Step 5: Ask if User Wants a Comment Drafted
-
-```xml
-<ask_followup_question>
-<question>Would you like me to draft a comment for this PR that you can copy and paste?</question>
-<options>["Yes, please draft a comment", "No, I'll handle the comment myself"]</options>
-</ask_followup_question>
-```
-
-## Step 6: Make a Decision
-
-```bash
-# Option 1: Simple one-line comment
-gh pr review 3627 --approve --body "This PR looks good! It correctly fixes the thinking mode budget calculation for Claude 3.7 models."
-
-# Option 2: Multi-line comment with proper whitespace formatting
-cat << EOF | gh pr review 3627 --approve --body-file -
-This PR looks good! It correctly fixes the thinking mode budget calculation for Claude 3.7 models.
-
-I particularly like:
-1. The proper implementation of thinkingConfig.maxBudget property (64000)
-2. The appropriate percentage (50%) for the slider calculation
-3. The comprehensive unit tests
-4. The clean implementation that follows project coding standards
-
-Great work!
-EOF
-```
-</example_review_process>
-
-<common_gh_commands>
-# Common GitHub CLI Commands for PR Review
-
-## Basic PR Commands
-```bash
-# List open PRs
-gh pr list
-
-# View a specific PR
-gh pr view <PR-number>
-
-# View PR with specific fields
-gh pr view <PR-number> --json title,body,comments,files,commits
-
-# Check PR status
-gh pr status
-```
-
-## Diff and File Commands
-```bash
-# Get the full diff of a PR
-gh pr diff <PR-number>
-
-# List files changed in a PR
-gh pr view <PR-number> --json files
-
-# Check out a PR locally
-gh pr checkout <PR-number>
-```
-
-## Review Commands
-```bash
-# Approve a PR (single-line comment)
-gh pr review <PR-number> --approve --body "Your approval message"
-
-# Approve a PR (multi-line comment with proper whitespace)
-cat << EOF | gh pr review <PR-number> --approve --body-file -
-Your multi-line
-approval message with
-
-proper whitespace formatting
-EOF
-
-# Request changes on a PR (single-line comment)
-gh pr review <PR-number> --request-changes --body "Your feedback message"
-
-# Request changes on a PR (multi-line comment with proper whitespace)
-cat << EOF | gh pr review <PR-number> --request-changes --body-file -
-Your multi-line
-change request with
-
-proper whitespace formatting
-EOF
-
-# Add a comment review (without approval/rejection)
-gh pr review <PR-number> --comment --body "Your comment message"
-
-# Add a comment review with proper whitespace
-cat << EOF | gh pr review <PR-number> --comment --body-file -
-Your multi-line
-comment with
-
-proper whitespace formatting
-EOF
-```
-
-## Additional Commands
-```bash
-# View PR checks status
-gh pr checks <PR-number>
-
-# View PR commits
-gh pr view <PR-number> --json commits
-
-# Merge a PR (if you have permission)
-gh pr merge <PR-number> --merge
-```
-</common_gh_commands>
-
-<general_guidelines_for_commenting>
-When reviewing a PR, please talk normally and like a friendly reviwer. You should keep it short, and start out by thanking the author of the pr and @ mentioning them. 
-
-Whether or not you approve the PR, you should then give a quick summary of the changes without being too verbose or definitive, staying humble like that this is your understanding of the changes. Kind of how I'm talking to you right now.
-
-If you have any suggestions, or things that need to be changed, request changes instead of approving the PR.
-
-Leaving inline comments in code is good, but only do so if you have something specific to say about the code. And make sure you leave those comments first, and then request changes in the PR with a short comment explaining the overall theme of what you're asking them to change.
-</general_guidelines_for_commenting>
-
-<example_comments_that_i_have_written_before>
-<brief_approve_comment>
-Looks good, though we should make this generic for all providers & models at some point
-</brief_approve_comment>
-<brief_approve_comment>
-Will this work for models that may not match across OR/Gemini? Like the thinking models?
-</brief_approve_comment>
-<approve_comment>
-This looks great! I like how you've handled the global endpoint support - adding it to the ModelInfo interface makes total sense since it's just another capability flag, similar to how we handle other model features.
-
-The filtered model list approach is clean and will be easier to maintain than hardcoding which models work with global endpoints. And bumping the genai library was obviously needed for this to work.
-
-Thanks for adding the docs about the limitations too - good for users to know they can't use context caches with global endpoints but might get fewer 429 errors.
-</approve_comment>
-<requesst_changes_comment>
-This is awesome. Thanks @scottsus.
-
-My main concern though - does this work for all the possible VS Code themes? We struggled with this initially which is why it's not super styled currently. Please test and share screenshots with the different themes to make sure before we can merge
-</request_changes_comment>
-<request_changes_comment>
-Hey, the PR looks good overall but I'm concerned about removing those timeouts. Those were probably there for a reason - VSCode's UI can be finicky with timing.
-
-Could you add back the timeouts after focusing the sidebar? Something like:
-
-```typescript
-await vscode.commands.executeCommand("claude-dev.SidebarProvider.focus")
-await setTimeoutPromise(100)  // Give UI time to update
-visibleWebview = WebviewProvider.getSidebarInstance()
-```
-</request_changes_comment>
-<request_changes_comment>
-Heya @alejandropta thanks for working on this! 
-
-A few notes:
-1 - Adding additional info to the environment variables is fairly problematic because env variables get appended to **every single message**. I don't think this is justifiable for a somewhat niche use case. 
-2 - Adding this option to settings to include that could be an option, but we want our options to be simple and straightforward for new users
-3 - We're working on revisualizing the way our settings page is displayed/organized, and this could potentially be reconciled once that is in and our settings page is more clearly delineated. 
-
-So until the settings page is update, and this is added to settings in a way that's clean and doesn't confuse new users, I don't think we can merge this. Please bear with us.
-</request_changes_comment>
-<request_changes_comment>
-Also, don't forget to add a changeset since this fixes a user-facing bug.
-
-The architectural change is solid - moving the focus logic to the command handlers makes sense. Just don't want to introduce subtle timing issues by removing those timeouts.
-</request_changes_comment>
-</example_comments_that_i_have_written_before>

.eslintrc.json

@@ -5,7 +5,7 @@
 		"ecmaVersion": 6,
 		"sourceType": "module"
 	},
-	"plugins": ["@typescript-eslint", "eslint-rules"],
+	"plugins": ["@typescript-eslint"],
 	"rules": {
 		"@typescript-eslint/naming-convention": [
 			"warn",
@@ -19,16 +19,7 @@
 		"eqeqeq": "warn",
 		"no-throw-literal": "warn",
 		"semi": "off",
-		"react-hooks/exhaustive-deps": "off",
-		"eslint-rules/no-protobuf-object-literals": "error",
-		"eslint-rules/no-grpc-client-object-literals": "error",
-		"no-restricted-syntax": [
-			"error",
-			{
-				"selector": "VariableDeclarator[id.type=\"ObjectPattern\"][init.object.name=\"process\"][init.property.name=\"env\"]",
-				"message": "Use process.env.VARIABLE_NAME directly instead of destructuring"
-			}
-		]
+		"react-hooks/exhaustive-deps": "off"
 	},
 	"ignorePatterns": ["out", "dist", "**/*.d.ts"]
 }

.gitattributes

@@ -1,4 +1,2 @@
 demo.gif filter=lfs diff=lfs merge=lfs -text
 assets/docs/demo.gif filter=lfs diff=lfs merge=lfs -text
-
-* text=auto eol=lf

.github/ISSUE_TEMPLATE/config.yml

@@ -6,3 +6,6 @@ contact_links:
     - name: 👋 Cline Discord
       url: https://discord.gg/cline
       about: Join our Discord community for discussions and support
+    - name: ❓ Other Questions?
+      url: https://x.com/sdrzn
+      about: Contact the developer on X @sdrzn for other inquiries

.github/ISSUE_TEMPLATE/feature_contribution.yml

@@ -1,116 +0,0 @@
-name: 💡 Feature Proposal & Contribution
-description: Propose a new feature or improvement, and optionally offer to implement feature as a contributor
-labels: ["proposal"]
-body:
-    - type: markdown
-      attributes:
-          value: |
-              **Feature Proposal & Contribution for Cline**
-
-              Thank you for proposing a feature or improvement for Cline! This template helps us understand the problem, evaluate the solution, and coordinate implementation.
-
-              **For detailed proposals:** Please provide comprehensive information to enable fast prioritization and discussion.
-              **For contribution offers:** You can indicate your willingness to implement the feature yourself.
-
-              Before submitting:
-              - Search existing [Issues](https://github.com/cline/cline/issues) and [Discussions](https://github.com/cline/cline/discussions) to avoid duplicates
-              - Read the [Contributing Guide](https://github.com/cline/cline/blob/main/CONTRIBUTING.md) if you plan to contribute
-              - Don't start implementation until the proposal is reviewed and approved
-
-    - type: textarea
-      id: problem-description
-      attributes:
-          label: What problem does this solve?
-          description: |
-              Describe the problem clearly from a user's point of view. Focus on why this matters, who it affects, and when it occurs.
-
-              ✅ Good examples:
-              - "LLM provider returns 400 error when nearing the context window instead of truncating"
-              - "Submit button is invisible in dark mode"
-              - "Users can't easily share their Cline configurations with team members"
-
-              ❌ Avoid vague descriptions:
-              - "Performance is bad"
-              - "UI needs work"
-
-              Your description should include:
-              - Who is affected?
-              - When does it happen?
-              - What's the current vs expected behavior?
-              - What is the impact?
-          placeholder: Be specific about the problem, who it affects, and the impact.
-      validations:
-          required: true
-
-    - type: textarea
-      id: proposed-solution
-      attributes:
-          label: What's the proposed solution?
-          description: |
-              Describe how the problem should be solved. Be specific about UX, system behavior, and any flows that would change.
-
-              ✅ Good examples:
-              - "Add error handling immediately after attempting to create the llm stream and retry after manually truncating"
-              - "Update button styling to ensure contrast in all themes"
-              - "Add export/import functionality in settings with JSON format"
-
-              ❌ Avoid vague solutions:
-              - "Improve performance"
-              - "Fix the bug"
-
-              Your solution should include:
-              - What exactly will change?
-              - How will users interact with it?
-              - What's the expected outcome?
-          placeholder: Describe the proposed changes and how they solve the problem.
-      validations:
-          required: false
-
-    - type: dropdown
-      id: contribution-intent
-      attributes:
-          label: Are you interested in implementing this?
-          description: Let us know if you'd like to contribute to this feature
-          options:
-              - "No, just proposing the idea"
-              - "Yes, I'd like to implement this myself"
-              - "Yes, I'd like to collaborate with others"
-              - "Maybe, depending on complexity and guidance"
-      validations:
-          required: false
-
-    - type: textarea
-      id: implementation-approach
-      attributes:
-          label: Implementation approach (if contributing)
-          description: |
-              **Only fill this out if you selected "Yes" above.**
-
-              How do you plan to implement this? Include:
-              - High-level technical approach
-              - Files/components that would be affected
-              - Any new dependencies required
-              - Potential challenges or considerations you've identified
-
-              This helps us provide better guidance and ensures alignment before you start coding.
-          placeholder: "My implementation approach would be..."
-
-    - type: checkboxes
-      id: checklist
-      attributes:
-          label: Proposal checklist
-          options:
-              - label: I've checked for existing issues or related proposals
-                required: true
-              - label: I understand this needs review before implementation can start
-                required: true
-
-    - type: checkboxes
-      id: contribution-checklist
-      attributes:
-          label: Contribution checklist (if contributing)
-          description: Only check these if you plan to contribute
-          options:
-              - label: I've read the [Contributing Guide](https://github.com/cline/cline/blob/main/CONTRIBUTING.md)
-              - label: I'm willing to make changes based on feedback
-              - label: I understand the code review process and requirements

.github/pull_request_template.md

@@ -1,47 +1,10 @@
-<!--
-Thank you for contributing to Cline!
-
-⚠️ Important: Before submitting this PR, please ensure you have:
-- Opened an issue and discussed your proposed changes with the community / contributors
-- Received approval from a core Cline contributor prior to proceeding with the implementation
-- Link the associated issue in the "Related Issue" section
-
-Limited exceptions:
-Small bug fixes, typo corrections, minor wording improvements, or simple type fixes that don't change functionality may be submitted directly.
-
-Why this requirement?
-We deeply appreciate all community contributions - they are the core reason we're able to operate successfully and keep innovating! We welcome community input and want to make it as easy as possible for people to submit quality work. This process helps our core maintainers review new ideas faster and saves contributor time by ensuring you have the go-ahead before spending time on implementation.
--->
-
-### Related Issue
-
-<!-- Replace XXXX with the issue number that this PR addresses -->
-**Issue:** #XXXX
-
 ### Description
 
-<!-- 
-Help reviewers understand your changes by making this PR readable and well-organized:
-
-- What problem does this PR solve?
-- Why were these changes introduced and what purpose do they serve?
-- For larger changes, provide context about your approach and reasoning
-
-Small PRs may need minimal description, but larger changes benefit from explaining where you're coming from. Much of this context can be in the linked issue above, so feel free to reference it rather than repeating everything here.
--->
+<!-- Describe your changes in detail. What problem does this PR solve? -->
 
 ### Test Procedure
 
-<!-- 
-Please walk us through your testing approach and thought process. This helps reviewers understand that you've thoroughly considered the impact of your changes:
-
-- How did you test this change?
-- What could potentially break and how did you verify it doesn't?
-- What existing functionality might be affected and how did you check it still works?
-- Why are you confident this is ready for merge?
-
-We're not looking for exhaustive documentation - just evidence that you've thought through the implications of your changes and tested accordingly.
--->
+<!-- How did you test this? Are you confident that it will not introduce bugs? If so, why? -->
 
 ### Type of Change
 
@@ -66,15 +29,7 @@ We're not looking for exhaustive documentation - just evidence that you've thoug
 
 ### Screenshots
 
-<!-- 
-Help reviewers quickly understand your changes:
-
-- **UI Changes**: Please include screenshots showing before/after states
-- **Complex Workflows**: Consider uploading a screen recording (video) if your changes involve multiple steps or state transitions
-- **Backend Changes**: Not required, but feel free to include terminal output or other evidence that demonstrates functionality
-
-This helps reviewers see what you've built without having to pull down and test your branch first.
--->
+<!-- For UI changes, add screenshots here -->
 
 ### Additional Notes
 

.github/workflows/publish.yml

@@ -11,10 +11,6 @@ on:
                 options:
                     - pre-release
                     - release
-            tag:
-                description: "Enter existing tag to publish (e.g., v3.1.2)"
-                required: true
-                type: string
 
 permissions:
     contents: write
@@ -34,8 +30,6 @@ jobs:
 
         steps:
             - uses: actions/checkout@v4
-              with:
-                  ref: ${{ github.event.inputs.tag }}
 
             - name: Setup Node.js
               uses: actions/setup-node@v4
@@ -75,20 +69,14 @@ jobs:
                   VERSION=$(node -p "require('./package.json').version")
                   echo "version=$VERSION" >> $GITHUB_OUTPUT
 
-            - name: Validate Tag
-              id: validate_tag
+            - name: Create Git Tag
+              id: create_tag
               run: |
-                  TAG="${{ github.event.inputs.tag }}"
-                  echo "tag=$TAG" >> $GITHUB_OUTPUT
-                  echo "Using existing tag: $TAG"
-
-                  # Verify the tag exists
-                  if ! git rev-parse "$TAG" >/dev/null 2>&1; then
-                    echo "Error: Tag '$TAG' does not exist in the repository"
-                    exit 1
-                  fi
-
-                  echo "Tag '$TAG' validated successfully"
+                  VERSION=v${{ steps.get_version.outputs.version }}
+                  echo "tag=$VERSION" >> $GITHUB_OUTPUT
+                  echo "Tagging with $VERSION"
+                  git tag "$VERSION"
+                  git push origin "$VERSION"
 
             - name: Package and Publish Extension
               env:
@@ -118,7 +106,7 @@ jobs:
             - name: Create GitHub Release
               uses: softprops/action-gh-release@v1
               with:
-                  tag_name: ${{ steps.validate_tag.outputs.tag }}
+                  tag_name: ${{ steps.create_tag.outputs.tag }}
                   files: "*.vsix"
                   # body: ${{ steps.changelog.outputs.content }}
                   generate_release_notes: true

.github/workflows/stale.yml

@@ -1,25 +0,0 @@
-# This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit.
-# More info: https://docs.github.com/en/actions/use-cases-and-examples/project-management/closing-inactive-issues
-name: Close inactive issues
-on:
-    schedule:
-        - cron: "30 1 * * *"
-
-jobs:
-    close-issues:
-        runs-on: ubuntu-latest
-        permissions:
-            issues: write
-            pull-requests: write
-        steps:
-            - uses: actions/stale@v9
-              with:
-                  days-before-issue-stale: 60
-                  days-before-issue-close: 14
-                  stale-issue-label: "stale"
-                  stale-issue-message: "This issue is stale because it has been open for 60 days with no activity."
-                  close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
-                  days-before-pr-stale: -1
-                  days-before-pr-close: -1
-                  exempt-issue-labels: "pinned,security"
-                  repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/test-stale.yml

@@ -1,32 +0,0 @@
-name: Test Stale Issues Workflow
-on:
-    workflow_dispatch:
-        inputs:
-            days-before-stale:
-                description: "Days before an issue becomes stale"
-                required: true
-                default: "1"
-            days-before-close:
-                description: "Days before a stale issue is closed"
-                required: true
-                default: "1"
-
-jobs:
-    test-stale:
-        runs-on: ubuntu-latest
-        permissions:
-            issues: write
-            pull-requests: write
-        steps:
-            - uses: actions/stale@28ca103
-              with:
-                  days-before-issue-stale: ${{ github.event.inputs.days-before-stale }}
-                  days-before-issue-close: ${{ github.event.inputs.days-before-close }}
-                  stale-issue-label: "stale"
-                  stale-issue-message: "This issue is stale because it has been open for ${{ github.event.inputs.days-before-stale }} days with no activity."
-                  close-issue-message: "This issue was closed because it has been inactive for ${{ github.event.inputs.days-before-close }} days since being marked as stale."
-                  days-before-pr-stale: -1
-                  days-before-pr-close: -1
-                  exempt-issue-labels: "pinned,security"
-                  repo-token: ${{ secrets.GITHUB_TOKEN }}
-                  debug-only: true

.github/workflows/test.yml

@@ -15,15 +15,7 @@ permissions:
 
 jobs:
     test:
-        strategy:
-            fail-fast: false
-            matrix:
-                os: [ubuntu-latest, windows-latest]
-        runs-on: ${{ matrix.os }}
-        name: ${{ matrix.os == 'ubuntu-latest' && 'test' || format('test ({0})', matrix.os) }}
-        defaults:
-            run:
-                shell: bash
+        runs-on: ubuntu-latest
         steps:
             - name: Checkout code
               uses: actions/checkout@v4
@@ -68,17 +60,6 @@ jobs:
               if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci
 
-            - name: Install local modules on windows
-              if: runner.os == 'Windows' && steps.root-cache.outputs.cache-hit == 'true'
-              run: |
-                  npm install eslint-plugin-eslint-rules 
-                  cd webview-ui/ && npm install eslint-plugin-eslint-rules
-
-            - name: Set up NPM on Windows
-              if: runner.os == 'Windows'
-              run: |
-                  npm config set script-shell "C:\\Program Files\\Git\\bin\\bash.exe"
-
             - name: Type Check
               run: npm run check-types
 
@@ -92,18 +73,16 @@ jobs:
             - name: Build Tests and Extension
               run: npm run pretest
 
-            # Unit Tests disabled due to module system conflicts between backend and webview-ui
-            # - name: Unit Tests
-            #   run: npm run test:unit
+            - name: Unit Tests
+              run: npm run test:unit
 
             # Run extension tests with coverage
             - name: Extension Tests with Coverage
               id: extension_coverage
               continue-on-error: true
               run: |
-                  node ./scripts/test-ci.js > extension_coverage.txt 2>&1
-                  # Default the encoding to UTF-8 - It's not the default on Windows
-                  PYTHONUTF8=1 PYTHONPATH=.github/scripts python -m coverage_check extract-coverage extension_coverage.txt --type=extension --github-output --verbose
+                  xvfb-run -a npm run test:coverage > extension_coverage.txt 2>&1
+                  PYTHONPATH=.github/scripts python -m coverage_check extract-coverage extension_coverage.txt --type=extension --github-output --verbose
 
             # Run webview tests with coverage
             - name: Webview Tests with Coverage
@@ -113,16 +92,13 @@ jobs:
                   cd webview-ui
                   # Ensure coverage dependency is installed
                   npm install --no-save @vitest/coverage-v8
-                  npm run test:coverage > webview_coverage.txt 2>&1
+                  npm run test:coverage > webview_coverage.txt 2>&1 || true
                   cd ..
-                  # Default the encoding to UTF-8 - It's not the default on Windows
-                  PYTHONUTF8=1 PYTHONPATH=.github/scripts python -m coverage_check extract-coverage webview-ui/webview_coverage.txt --type=webview --github-output --verbose
+                  PYTHONPATH=.github/scripts python -m coverage_check extract-coverage webview-ui/webview_coverage.txt --type=webview --github-output --verbose
 
             # Save coverage reports as artifacts (workflow-scoped)
             - name: Save Coverage Reports
               uses: actions/upload-artifact@v4
-              # Only upload artifacts on Linux - We only need coverage from one OS
-              if: runner.os == 'Linux'
               with:
                   name: pr-coverage-reports
                   path: |
@@ -131,18 +107,14 @@ jobs:
                   retention-period: workflow # Artifacts are automatically deleted when the workflow completes
 
             # Set the check as failed if any of the tests failed
-            - name: Print test results and check for failures
+            - name: Check for test failures
               run: |
-                  echo "Extension Tests Result: ${{ steps.extension_coverage.outcome }}"
-                  cat extension_coverage.txt
-
-                  echo "Webview Tests Result: ${{ steps.webview_coverage.outcome }}"
-                  cat webview-ui/webview_coverage.txt
-
                   # Check if any of the test steps failed
                   # https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#steps-context
                   if [ "${{ steps.extension_coverage.outcome }}" != "success" ] || [ "${{ steps.webview_coverage.outcome }}" != "success" ]; then
                       echo "Tests failed."
+                      cat extension_coverage.txt
+                      cat webview-ui/webview_coverage.txt
                       exit 1
                   fi
 

.gitignore

@@ -1,6 +1,5 @@
 out
 dist
-dist-standalone
 node_modules
 tmp
 .vscode-test/
@@ -19,22 +18,4 @@ coverage
 # But don't ignore the coverage scripts in .github/scripts/
 !.github/scripts/coverage/
 
-*evals.env
-
-# Generated files
-src/generated/
-# Core
-src/core/controller/*/methods.ts
-src/core/controller/*/index.ts
-src/core/controller/grpc-service-config.ts
-# Shared
-src/shared/proto/*.ts
-src/shared/proto/host/*.ts
-# Webview
-webview-ui/src/services/grpc-client.ts
-# Host bridge
-src/hosts/vscode/*/methods.ts
-src/hosts/vscode/*/index.ts
-src/hosts/vscode/client/host-grpc-client.ts
-src/hosts/vscode/host-grpc-service-config.ts
-src/standalone/server-setup.ts
+*evals.env

.husky/pre-commit

@@ -9,9 +9,9 @@ npm run lint || {
 
 # Run Prettier
 echo "Running Prettier..."
-npx lint-staged --verbose || {
-     echo "❌ Prettier failed. Please fix the errors and try committing again."
-     exit 1
- }
+npm run format || {
+    echo "❌ Prettier check failed. Run 'npm run format:fix' to automatically fix formatting issues."
+    exit 1
+}
 
 echo "✅ All checks passed!"

.mocharc.json

@@ -1,6 +1,6 @@
 {
 	"extension": ["ts"],
-	"spec": ["src/**/__tests__/*.ts", "eslint-rules/__tests__/**/*.test.ts"],
+	"spec": "src/**/__tests__/*.ts",
 	"require": ["ts-node/register", "source-map-support/register", "./src/test/requires.ts"],
 	"recursive": true
 }

.prettierignore

@@ -3,6 +3,3 @@ node_modules
 webview-ui/build/
 *.md
 package-lock.json
-src/core/prompts/system.ts
-src/core/prompts/model_prompts/claude4.ts
-evals/

.prettierrc.json

@@ -3,6 +3,5 @@
 	"useTabs": true,
 	"printWidth": 130,
 	"semi": false,
-	"bracketSameLine": true,
-	"endOfLine": "lf"
+	"bracketSameLine": true
 }

.vscode/extensions.json

@@ -1,10 +1,5 @@
 {
 	// See http://go.microsoft.com/fwlink/?LinkId=827846
 	// for the documentation about the extensions.json format
-	"recommendations": [
-		"dbaeumer.vscode-eslint",
-		"connor4312.esbuild-problem-matchers",
-		"ms-vscode.extension-test-runner",
-		"bradlc.vscode-tailwindcss"
-	]
+	"recommendations": ["dbaeumer.vscode-eslint", "connor4312.esbuild-problem-matchers", "ms-vscode.extension-test-runner"]
 }

.vscode/launch.json

@@ -16,48 +16,6 @@
 				"IS_DEV": "true",
 				"DEV_WORKSPACE_FOLDER": "${workspaceFolder}"
 			}
-		},
-		{
-			"name": "Run Extension (Fresh Install Mode)",
-			"type": "extensionHost",
-			"request": "launch",
-			"runtimeExecutable": "${execPath}",
-			"args": [
-				"--profile-temp",
-				"--sync",
-				"off",
-				"--disable-extensions",
-				"--extensionDevelopmentPath=${workspaceFolder}",
-				"${workspaceFolder}"
-			],
-			"outFiles": ["${workspaceFolder}/dist/**/*.js"],
-			"preLaunchTask": "clean-sandbox",
-			"internalConsoleOptions": "openOnSessionStart",
-			"postDebugTask": "stop",
-			"env": {
-				"IS_DEV": "true",
-				"DEV_WORKSPACE_FOLDER": "${workspaceFolder}"
-			}
-		},
-		{
-			"type": "node",
-			"request": "launch",
-			"name": "Run Standalone Service",
-			"skipFiles": ["<node_internals>/**"],
-			"sourceMaps": true,
-			"resolveSourceMapLocations": ["${workspaceFolder}/**", "!**/node_modules/**"],
-			"cwd": "${workspaceFolder}/dist-standalone",
-			"outFiles": ["${workspaceFolder}/dist-standalone/**/*.js"],
-			"preLaunchTask": "compile-standalone",
-			"env": {
-				// Turns on grpc debug log.
-				//"GRPC_TRACE": "all",
-				//"GRPC_VERBOSITY": "DEBUG",
-				"NODE_PATH": "${workspaceFolder}/dist-standalone/node_modules",
-
-				"HOST_BRIDGE_ADDRESS": "localhost:50052"
-			},
-			"program": "standalone.js"
 		}
 	]
 }

.vscode/tasks.json

@@ -3,16 +3,6 @@
 {
 	"version": "2.0.0",
 	"tasks": [
-		{
-			"label": "compile-standalone",
-			"type": "npm",
-			"script": "compile-standalone",
-			"group": "build",
-			"problemMatcher": [],
-			"presentation": {
-				"reveal": "always"
-			}
-		},
 		{
 			"label": "npm: protos",
 			"type": "npm",
@@ -128,25 +118,7 @@
 			"type": "npm",
 			"script": "watch:esbuild",
 			"group": "build",
-			"problemMatcher": {
-				"pattern": [
-					{
-						"regexp": "^✘ \\[ERROR\\] (.*)$",
-						"message": 1
-					},
-					{
-						"regexp": "^\\s+(.*):(\\d+):(\\d+):$",
-						"file": 1,
-						"line": 2,
-						"column": 3
-					}
-				],
-				"background": {
-					"activeOnStart": true,
-					"beginsPattern": "^\\[watch\\] build started$",
-					"endsPattern": "^\\[watch\\] build finished$"
-				}
-			},
+			"problemMatcher": "$esbuild-watch",
 			"isBackground": true,
 			"label": "npm: watch:esbuild",
 			"dependsOn": ["npm: protos"],
@@ -164,25 +136,7 @@
 			"type": "npm",
 			"script": "watch:esbuild:test",
 			"group": "build",
-			"problemMatcher": {
-				"pattern": [
-					{
-						"regexp": "^✘ \\[ERROR\\] (.*)$",
-						"message": 1
-					},
-					{
-						"regexp": "^\\s+(.*):(\\d+):(\\d+):$",
-						"file": 1,
-						"line": 2,
-						"column": 3
-					}
-				],
-				"background": {
-					"activeOnStart": true,
-					"beginsPattern": "^\\[watch\\] build started$",
-					"endsPattern": "^\\[watch\\] build finished$"
-				}
-			},
+			"problemMatcher": "$esbuild-watch",
 			"isBackground": true,
 			"label": "npm: watch:esbuild:test",
 			"dependsOn": ["npm: protos"],
@@ -231,12 +185,6 @@
 			"label": "stop",
 			"command": "echo ${input:terminate}",
 			"type": "shell"
-		},
-		{
-			"label": "clean-sandbox",
-			"type": "shell",
-			"dependsOn": ["watch"],
-			"command": "rm -rf .vscode-dev"
 		}
 	],
 	"inputs": [

CHANGELOG.md

@@ -1,254 +1,5 @@
 # Changelog
 
-## [3.18.0]
-
--   Optimized Cline to work with the Claude 4 family of models, resulting in improved performance, reliability, and new capabilities
--   Added a new Gemini CLI provider that allows you to use your local Gemini CLI authentication to access Gemini models for free (Thanks @google-gemini!)
--   Optimized Cline to work with the Gemini 2.5 family of models
--   Updated the default and recommended model to Claude 4 Sonnet for the best performance
--   Fix race condition in Plan/Act mode switching
--   Improve robustness of search and replace parsing
-
-## [3.17.16]
-
--   Fix Claude Code provider error handling for incomplete messages during long-running tasks (Thanks @BarreiroT!)
--   Add taskId as metadata to LiteLLM API requests for better request tracing (Thanks @jorgegarciarey!)
-
-## [3.17.15]
-
--   Fix LiteLLM provider to properly respect selected model IDs when switching between Plan and Act modes (Thanks @sammcj!)
--   Fix chat input being cleared when switching between Plan/Act modes without sending a message (Thanks @BarreiroT!)
--   Fix MCP server name display to avoid showing "undefined" for SSE servers, preventing tool/resource invocation failures (Thanks @ramybenaroya!)
--   Fix AWS Bedrock provider by removing deprecated custom model encoding (Thanks @watany-dev!)
--   Fix timeline tooltips for followup messages and improve color retrieval code (Thanks @char8x!)
--   Improve accessibility by making task header buttons properly announced by screen readers (Thanks @yncat!)
--   Improve accessibility by adding proper state reporting for Plan/Act mode switch for screen readers (Thanks @yncat!)
--   Prevent reading development environment variables from user's environment (Thanks @BarreiroT!)
-
-## [3.17.14]
-
--   Add Claude Code as a new API provider, allowing integration with Anthropic's Claude Code CLI tool and Claude Max Plan (Thanks @BarreiroT!)
--   Add SAP AI Core as a new API provider with support for Claude and GPT models (Thanks @schardosin!)
--   Add configurable default terminal profile setting, allowing users to specify which terminal Cline should use (Thanks @valinha!)
--   Add terminal output size constraint setting to limit how much terminal output is processed
--   Add MCP Rich Display settings to the settings page for persistent configuration (Thanks @Vl4diC0de!)
--   Improve copy button functionality with refactored reusable components (Thanks @shouhanzen!)
--   Improve AWS Bedrock provider by removing deprecated dependency and using standard AWS SDK (Thanks @watany-dev!)
--   Fix list_files tool to properly return files when targeting hidden directories
--   Fix search and replace edge case that could cause file deletion, making the algorithm more lenient for models using different diff formats
--   Fix task restoration issues that could occur when resuming interrupted tasks
--   Fix checkpoint saving to properly track all file changes
--   Improve file context warnings to reduce diff edit errors when resuming restored tasks
--   Clear chat input when switching between Plan/Act modes within a task
--   Exclude .clinerules files from checkpoint tracking
-
-## [3.17.13]
-
--   Add Thinking UX for Gemini models, providing visual feedback during model reasoning
--   Add support for Notifications MCP integration with Cline
--   Add prompt caching indicator for Grok 3 models
--   Sort MCP marketplace by newest listings by default for easier discovery of recent servers
--   Update O3 model family pricing to reflect latest OpenAI rates
--   Remove '-beta' suffix from Grok model identifiers
--   Fix AWS Bedrock provider by removing deprecated Anthropic-Bedrock SDK (Thanks @watany-dev!)
--   Fix menu display issue for terminal timeout settings
--   Improve chat input field styling and behavior
-
-## [3.17.12]
-
--   **Free Grok Model Available!** Access Grok 3 completely free through the Cline provider
--   Add collapsible MCP response panels to keep conversations focused on the main AI responses while still allowing access to detailed MCP output (Thanks @valinha!)
--   Prioritize active files (open tabs) at the top of the file context menu when using @ mentions (Thanks @abeatrix!)
--   Fix context menu to properly default to "File" option instead of incorrectly selecting "Git Commits"
--   Fix diff editing to handle out-of-order SEARCH/REPLACE blocks, improving reliability with models that don't follow strict ordering
--   Fix telemetry warning popup appearing repeatedly for users who have telemetry disabled
-
-## [3.17.11]
-
--   Add support for Gemini 2.5 Pro Preview 06-05 model to Vertex AI and Google Gemini providers
-
-## [3.17.10]
-
--   Add support for Qwen 3 series models with thinking mode options (Thanks @Jonny-china!)
--   Add new AskSage models: Claude 4 Sonnet, Claude 4 Opus, GPT 4.1, Gemini 2.5 Pro (Thanks @swhite24!)
--   Add VSCode walkthrough to help new users get started with Cline
--   Add support for streamable MCP servers
--   Improve Ollama model selection with filterable dropdown instead of radio buttons (Thanks @paulgear!)
--   Add setting to disable aggressive terminal reuse to help users experiencing task lockout issues
--   Fix settings dialog applying changes even when cancel button is clicked
-
-## [3.17.9]
-
--   Aligning Cline to work with Claude 4 model family (Experimental)
--   Add task timeline scrolling feature
--   Add support for uploading CSV and XLSX files for data analysis and processing
--   Add stable Grok-3 models to xAI provider (grok-3, grok-3-fast, grok-3-mini, grok-3-mini-fast) and update default model from grok-3-beta to grok-3 (Thanks @PeterDaveHello!)
--   Add new models to Vertex AI provider
--   Add new model to Nebius AI Studio
--   Remove hard-coded temperature from LM Studio API requests and add support for reasoning_content in LM Studio responses
--   Display delay information when retrying API calls for better user feedback
--   Fix AWS Bedrock credential caching issue where externally updated credentials (e.g., by AWS Identity Manager) were not detected, requiring extension restart (Thanks @DaveFres!)
--   Fix search tool overloading conversation with massive outputs by setting maximum byte limit for responses
--   Fix checkpoints functionality
--   Fix token counting for xAI provider
--   Fix Ollama provider issues
--   Fix window title display for Windows users
--   Improve chat box UI
-
-## [3.17.8]
-
--   Fix bug where terminal would get stuck and output "capture failure"
-
-## [3.17.7]
-
--   Fix diff editing reliability for Claude 4 family models by adding constraints to prevent errors with large replacements
-
-## [3.17.6]
-
--   Add Cerebras as a new API provider with 5 high-performance models including reasoning-capable models (Thanks @kevint-cerebras!)
--   Add support for uploading various file types (XML, JSON, TXT, LOG, MD, DOCX, IPYNB, PDF) alongside images
--   Add improved onboarding experience for new users with guided setup
--   Add prompt cache indicator for Gemini 2.5 Flash models
--   Update SambaNova provider with new model list and documentation links (Thanks @luisfucros!)
--   Fix diff editing support for Claude 4 family of models
--   Improve telemetry and analytics for better user experience insights
-
-## [3.17.5]
-
--   Fix issue with Claude 4 models where after several conversation turns, it would start making invalid diff edits
-
-## [3.17.4]
-
--   Fix thinking budget slider for Claude 4
-
-## [3.17.3]
-
--   Fix diff edit errors with Claude 4 models
-
-## [3.17.2]
-
--   Add support for Claude 4 models (Sonnet 4 and Opus 4) in AWS Bedrock and Vertex AI providers
--   Add support for global workflows, allowing workflows to be shared across workspaces with local workflows taking precedence
--   Fix settings page z-index UI issues that caused display problems
--   Fix AWS Bedrock environment variable handling to properly restore process.env after API calls (Thanks @DaveFres!)
-
-## [3.17.1]
-
--   Add prompt caching for Claude 4 models on Cline and OpenRouter providers
--   Increase max tokens for Claude Opus 4 from 4096 to 8192
-
-## [3.17.0]
-
--   Add support for Anthropic Claude Sonnet 4 and Claude Opus 4 in both Anthropic and Vertex providers
--   Add integration with Nebius AI Studio as a new provider (Thanks @Aktsvigun!)
--   Add custom highlight and hotkey suggestion when the assistant prompts to switch to Act mode
--   Update settings page design, now split into tabs for easier navigation (Thanks Yellow Bat @dlab-anton, and Roo Team!)
--   Fix MCP Server configuration bug
--   Fix model listing for Requesty provider
--   Move all advanced settings to settings page
-
-## [3.16.3]
-
--   Add devstral-small-2505 to the Mistral model list, a new specialized coding model from Mistral AI (Thanks @BarreiroT!)
--   Add documentation links to rules & workflows UI
--   Add support for Streameable HTTP Transport for MCPs (Thanks @alejandropta!)
--   Improve error handling for Mistral SDK API
-
-## [3.16.2]
-
--   Add support for Gemini 2.5 Flash Preview 05-20 model to Vertex AI provider with massive 1M token context window (Thanks @omercelik!)
--   Add keyboard shortcut (Cmd+') to quickly focus Cline from anywhere in VS Code
--   Add lightbulb actions for selected text with options to "Add to Cline", "Explain with Cline", and "Improve with Cline"
--   Automatically focus Cline window after extension updates
-
-## [3.16.1]
-
--   Add Enable auto approve toggle switch, allowing users to easily turn auto-approve functionality on or off without losing their action settings
--   Improve Gemini retry handling with better UI feedback, showing retry progress during API request attempts
--   Fix memory leak issue that could occur during long sessions with multiple tasks
--   Improve UI for Gemini model retry attempts with clearer status updates
--   Fix quick actions functionality in auto-approve settings
--   Update UI styling for auto-approve menu items to conserve space
-
-## [3.16.0]
-
--   Add new workflow feature allowing users to create and manage workflow files that can be injected into conversations via slash commands
--   Add collapsible recent task list, allowing users to hide their task history when sharing their screen (Thanks @cosmix!)
--   Add global endpoint option for Vertex AI users, providing higher availability and reducing 429 errors (Thanks @soniqua!)
--   Add detection for new users to display special components and guidance
--   Add Tailwind CSS IntelliSense to the recommended extensions list
--   Fix eternal loading states when the last message is a checkpoint (Thanks @BarreiroT!)
--   Improve settings organization by migrating VSCode Advanced settings to Settings Webview
-
-## [3.15.5]
-
--   Fix inefficient memory management in the task timeline
--   Fix Gemini rate limitation response not being handled properly (Thanks @BarreiroT!)
-
-## [3.15.4]
-
--   Add gemini model back to vertex provider
--   Add gemini telemetry
--   Add filtering for tasks tied to the current workspace
-
-## [3.15.3]
-
--   Add Fireworks API Provider
--   Fix minor visual issues with auto-approve menu
--   Fix one instance of terminal not getting output
--   Fix 'Chrome was launched but debug port is not responding' error
-
-## [3.15.2]
-
--   Added details to auto approve menu and more sensible default controls
--   Add detailed configuration options for LiteLLM provider
--   Add webview telemetry for users who have opted in to telemetry
--   Update Gemini in OpenRouter/Cline providers to use implicit caching
--   Fix freezing issues during rendering of large streaming text
--   Fix grey screen webview crashes by releasing memory after every diff edit
--   Fix breaking out of diff auto-scroll
--   Fix IME composition Enter auto‑sending edited message
-
-## [3.15.1]
-
--   Fix bug where PowerShell commands weren't given enough time before giving up and showing an error
-
-## [3.15.0]
-
--   Add Task Timeline visualization to tasks (Thanks eomcaleb!)
--   Add cache to ui for OpenAi provider
--   Add FeatureFlagProvider service for the Node.js extension side
--   Add copy buttons to task header and assistant messages
--   Add a more simplified home header was added
--   Add ability to favorite a task, allowing it to be kept when clearing all tasks
--   Add npm script for issue creation (Thanks DaveFres!)
--   Add confirmation dialog to Delete All History button
--   Add ability to allow the user to type their next message into the chat while Cline is taking action
--   Add ability to generate commit message via cline (Thanks zapp88!)
--   Add improvements to caching for gemini models on OpenRouter and Cline providers
--   Add improvements to allow scrolling the file being edited.
--   Add ui for windsurf and cursor rules
--   Add mistral medium-3 model
--   Add option to collect events to send them in a bundle to avoid sending too many events
--   Add support to quote a previous message in chat
--   Add support for Gemini Implicit Caching
--   Add support for batch selection and deletion of tasks in history (Thanks danix800!)
--   Update change suggested models
--   Update fetch cache details from generation endpoint
--   Update converted docs to Mintlify
--   Update the isOminiModel to include o4-mini model (Thanks PeterDaveHello!)
--   Update file size that can be read by Cline, allowing larger files
--   Update defaults for bedrock API models (Thanks Watany!)
--   Update to extend ReasoningEffort to non-o3-mini reasoning models for all providers (Thanks PeterDaveHello!)
--   Update to give error when a user tries to upload an image larger than 7500x7500 pixels
--   Update announcement so that previous updates are in a dropdown
--   Update UI for auto approve with favorited settings
--   Fix bug where certain terminal commands would lock you out of a task
--   Fix only initialize posthog in the webview if the user has opted into telemetry
--   Fix bug where autocapture was on for front-end telemetry
--   Fix for markdown copy excessively escaping characters (Thanks weshoke!)
--   Fix an issue where loading never finished when using an application inference profile for the model ID (Thanks WinterYukky!)
-
 ## [3.14.1]
 
 -   Disables autocaptures when initializing feature flags

CONTRIBUTING.md

@@ -10,77 +10,16 @@ Bug reports help make Cline better for everyone! Before creating a new issue, pl
      🔐 <b>Important:</b> If you discover a security vulnerability, please use the <a href="https://github.com/cline/cline/security/advisories/new">Github security tool to report it privately</a>.
 </blockquote>
 
-
-## Before Contributing
-
-All contributions must begin with a GitHub Issue, unless the change is for small bug fixes, typo corrections, minor wording improvements, or simple type fixes that don't change functionality.
-
-- **Check existing issues**: Search [GitHub Issues](https://github.com/cline/cline/issues).
-- **Create an issue**: Use appropriate templates:
-    - **Contributions:** Use the "Contribution Request" template to propose what you'd like to work on.
-    - **Bugs:** "Bug Report" template for reporting issues.
-    - **Features:** "Detailed Feature Proposal" template for suggesting new features.
-- **Wait for approval**: A core Cline contributor must approve your contribution request before you start implementation.
-- **Claim issues**: Once approved, the issue will be assigned to you.
-
-**PRs without approved issues may be closed.**
-
-
 ## Deciding What to Work On
 
 Looking for a good first contribution? Check out issues labeled ["good first issue"](https://github.com/cline/cline/labels/good%20first%20issue) or ["help wanted"](https://github.com/cline/cline/labels/help%20wanted). These are specifically curated for new contributors and areas where we'd love some help!
 
 We also welcome contributions to our [documentation](https://github.com/cline/cline/tree/main/docs)! Whether it's fixing typos, improving existing guides, or creating new educational content - we'd love to build a community-driven repository of resources that helps everyone get the most out of Cline. You can start by diving into `/docs` and looking for areas that need improvement.
 
+If you're planning to work on a bigger feature, please create a [feature request](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop) first so we can discuss whether it aligns with Cline's vision.
+
 ## Development Setup
 
-
-### Local Development Instructions
-
-1. Clone the repository _(Requires [git-lfs](https://git-lfs.com/))_:
-    ```bash
-    git clone https://github.com/cline/cline.git
-    ```
-2. Open the project in VSCode:
-    ```bash
-    code cline
-    ```
-3. Install the necessary dependencies for the extension and webview-gui:
-    ```bash
-    npm run install:all
-    ```
-4. Launch by pressing `F5` (or `Run`->`Start Debugging`) to open a new VSCode window with the extension loaded. (You may need to install the [esbuild problem matchers extension](https://marketplace.visualstudio.com/items?itemName=connor4312.esbuild-problem-matchers) if you run into issues building the project.)
-
-
-
-
-### Creating a Pull Request
-
-1. Before creating a PR, generate a changeset entry:
-    ```bash
-    npm run changeset
-    ```
-   This will prompt you for:
-   - Type of change (major, minor, patch)
-     - `major` → breaking changes (1.0.0 → 2.0.0)
-     - `minor` → new features (1.0.0 → 1.1.0)
-     - `patch` → bug fixes (1.0.0 → 1.0.1)
-   - Description of your changes
-
-2. Commit your changes and the generated `.changeset` file
-
-3. Push your branch and create a PR on GitHub. Our CI will:
-   - Run tests and checks
-   - Changesetbot will create a comment showing the version impact
-   - When merged to main, changesetbot will create a Version Packages PR
-   - When the Version Packages PR is merged, a new release will be published
-4. Testing
-    - Run `npm run test` to run tests locally. 
-    - Before submitting PR, run `npm run format:fix` to format your code
-    - Run `npm run test:ci` to run tests locally
-
-### Extension
-
 1. **VS Code Extensions**
 
     - When opening the project, VS Code will prompt you to install recommended extensions
@@ -90,26 +29,23 @@ We also welcome contributions to our [documentation](https://github.com/cline/cl
 2. **Local Development**
     - Run `npm run install:all` to install dependencies
     - Run `npm run test` to run tests locally
-    - Run → Start Debugging or `>Debug: Select and Start Debugging` and wait for a new VS Code instance to open
     - Before submitting PR, run `npm run format:fix` to format your code
 
 3. **Linux-specific Setup**
     VS Code extension tests on Linux require the following system libraries:
 
-    - `dbus`
-    - `libasound2`
-    - `libatk-bridge2.0-0`
     - `libatk1.0-0`
-    - `libdrm2`
-    - `libgbm1`
-    - `libgtk-3-0`
-    - `libnss3`
+    - `libatk-bridge2.0-0`
+    - `libxkbfile1`
     - `libx11-xcb1`
     - `libxcomposite1`
     - `libxdamage1`
     - `libxfixes3`
-    - `libxkbfile1`
     - `libxrandr2`
+    - `libgbm1`
+    - `libdrm2`
+    - `libgtk-3-0`
+    - `dbus`
     - `xvfb`
 
     These libraries provide necessary GUI components and system services for the test environment.
@@ -118,23 +54,13 @@ We also welcome contributions to our [documentation](https://github.com/cline/cl
     ```bash
     sudo apt update
     sudo apt install -y \
-      dbus \
-      libasound2 \
-      libatk-bridge2.0-0 \
-      libatk1.0-0 \
-      libdrm2 \
-      libgbm1 \
-      libgtk-3-0 \
-      libnss3 \
-      libx11-xcb1 \
-      libxcomposite1 \
-      libxdamage1 \
-      libxfixes3 \
-      libxkbfile1 \
-      libxrandr2 \
-      xvfb
+      libatk1.0-0 libatk-bridge2.0-0 libxkbfile1 libx11-xcb1 \
+      libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 \
+      libdrm2 libgtk-3-0 dbus xvfb
     ```
 
+    - Run `npm run test:ci` to run tests locally
+
 ## Writing and Submitting Code
 
 Anyone can contribute code to Cline, but we ask that you follow these guidelines to ensure your contributions can be smoothly integrated:

README.md

@@ -30,7 +30,7 @@ English | <a href="https://github.com/cline/cline/blob/main/locales/es/README.md
 </table>
 </div>
 
-Meet Cline (pronounced /klaɪn/, like "Klein"), an AI assistant that can use your **CLI** a**N**d **E**ditor.
+Meet Cline, an AI assistant that can use your **CLI** a**N**d **E**ditor.
 
 Thanks to [Claude 3.7 Sonnet's agentic coding capabilities](https://www.anthropic.com/claude/sonnet), Cline can handle complex software development tasks step-by-step. With tools that let him create & edit files, explore large projects, use the browser, and execute terminal commands (after you grant permission), he can assist you in ways that go beyond code completion or tech support. Cline can even use the Model Context Protocol (MCP) to create new tools and extend his own capabilities. While autonomous AI scripts traditionally run in sandboxed environments, this extension provides a human-in-the-loop GUI to approve every file change and terminal command, providing a safe and accessible way to explore the potential of agentic AI.
 
@@ -51,7 +51,7 @@ Thanks to [Claude 3.7 Sonnet's agentic coding capabilities](https://www.anthrop
 
 ### Use any API and Model
 
-Cline supports API providers like OpenRouter, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure, GCP Vertex, and Cerebras. You can also configure any OpenAI compatible API, or use a local model through LM Studio/Ollama. If you're using OpenRouter, the extension fetches their latest model list, allowing you to use the newest models as soon as they're available.
+Cline supports API providers like OpenRouter, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure, and GCP Vertex. You can also configure any OpenAI compatible API, or use a local model through LM Studio/Ollama. If you're using OpenRouter, the extension fetches their latest model list, allowing you to use the newest models as soon as they're available.
 
 The extension also keeps track of total tokens and API usage cost for the entire task loop and individual requests, keeping you informed of spend every step of the way.
 
@@ -141,6 +141,50 @@ For example, when working with a local web server, you can use 'Restore Workspac
 
 To contribute to the project, start with our [Contributing Guide](CONTRIBUTING.md) to learn the basics. You can also join our [Discord](https://discord.gg/cline) to chat with other contributors in the `#contributors` channel. If you're looking for full-time work, check out our open positions on our [careers page](https://cline.bot/join-us)!
 
+<details>
+<summary>Local Development Instructions</summary>
+
+1. Clone the repository _(Requires [git-lfs](https://git-lfs.com/))_:
+    ```bash
+    git clone https://github.com/cline/cline.git
+    ```
+2. Open the project in VSCode:
+    ```bash
+    code cline
+    ```
+3. Install the necessary dependencies for the extension and webview-gui:
+    ```bash
+    npm run install:all
+    ```
+4. Launch by pressing `F5` (or `Run`->`Start Debugging`) to open a new VSCode window with the extension loaded. (You may need to install the [esbuild problem matchers extension](https://marketplace.visualstudio.com/items?itemName=connor4312.esbuild-problem-matchers) if you run into issues building the project.)
+
+</details>
+
+<details>
+<summary>Creating a Pull Request</summary>
+
+1. Before creating a PR, generate a changeset entry:
+    ```bash
+    npm run changeset
+    ```
+   This will prompt you for:
+   - Type of change (major, minor, patch)
+     - `major` → breaking changes (1.0.0 → 2.0.0)
+     - `minor` → new features (1.0.0 → 1.1.0)
+     - `patch` → bug fixes (1.0.0 → 1.0.1)
+   - Description of your changes
+
+2. Commit your changes and the generated `.changeset` file
+
+3. Push your branch and create a PR on GitHub. Our CI will:
+   - Run tests and checks
+   - Changesetbot will create a comment showing the version impact
+   - When merged to main, changesetbot will create a Version Packages PR
+   - When the Version Packages PR is merged, a new release will be published
+
+</details>
+
+
 ## License
 
 [Apache 2.0 © 2025 Cline Bot Inc.](./LICENSE)

buf.yaml

@@ -1,22 +0,0 @@
-version: v2
-modules:
-    - path: proto
-      name: cline/cline/lint
-
-lint:
-    use:
-        - STANDARD
-
-    except: # Add exceptions for current patterns that contradict STANDARD settings
-        - RPC_PASCAL_CASE # rpcs are camel case (start with lowercase)
-        - PACKAGE_DIRECTORY_MATCH # the protos in the cline package are not in a dir named cline.
-        - RPC_REQUEST_RESPONSE_UNIQUE # request messages are not unique.
-        - RPC_REQUEST_STANDARD_NAME # request messages dont all end with Request
-        - RPC_RESPONSE_STANDARD_NAME # response messages dont all end with Response
-        - PACKAGE_VERSION_SUFFIX # package name does not contain version.
-        - ENUM_VALUE_PREFIX # enum values dont start with the enum name.
-        - ENUM_ZERO_VALUE_SUFFIX # first value does not have to be UNSPECIFIED.
-
-# breaking:
-#   use:
-#     - WIRE_JSON # Detect changes that break the json wire format (this is the minimum recommended level.)

docs/custom-model-configs/aws-bedrock-with-credentials-authentication.mdx

@@ -25,41 +25,12 @@ description: "Learn how to set up AWS Bedrock with Cline using credentials authe
 
 #### 1.2 Attach the Required Policies
 
-To ensure Cline can interact with AWS Bedrock, your IAM user or role needs specific permissions. While the `AmazonBedrockFullAccess` managed policy provides comprehensive access, for a more restricted and secure setup adhering to the principle of least privilege, the following minimal permissions are sufficient for Cline's core model invocation functionality:
-
--   `bedrock:InvokeModel`
--   `bedrock:InvokeModelWithResponseStream`
-
-You can create a custom IAM policy with these permissions and attach it to your IAM user or role.
-
-**Option 1: Minimal Permissions (Recommended for Production & Least Privilege)**
-
-1.  In the AWS IAM console, create a new policy.
-2.  Use the JSON editor to add the following policy document:
-    ```json
-    {
-    	"Version": "2012-10-17",
-    	"Statement": [
-    		{
-    			"Effect": "Allow",
-    			"Action": ["bedrock:InvokeModel", "bedrock:InvokeModelWithResponseStream"],
-    			"Resource": "*" // For enhanced security, scope this to specific model ARNs if possible.
-    		}
-    	]
-    }
-    ```
-3.  Name the policy (e.g., `ClineBedrockInvokeAccess`) and attach it to your IAM user or role.
-
-**Option 2: Using a Managed Policy (Simpler Initial Setup)**
-
--   Alternatively, you can attach the AWS managed policy **`AmazonBedrockFullAccess`**. This grants broader permissions, including the ability to list models, manage provisioning, and other Bedrock features. This might be simpler for initial setup or if you require these wider capabilities.
-    [View AmazonBedrockFullAccess Policy Details](https://docs.aws.amazon.com/bedrock/latest/userguide/security-iam.html)
-
-**Important Considerations:**
-
--   **Model Listing in Cline:** The minimal permissions (`bedrock:InvokeModel`, `bedrock:InvokeModelWithResponseStream`) are sufficient for Cline to _use_ a model if you specify the model ID directly in Cline's settings. If you rely on Cline to dynamically list available Bedrock models, you might need additional permissions like `bedrock:ListFoundationModels`.
--   **AWS Marketplace Subscriptions:** For third-party models (e.g., Anthropic Claude), ensure you have active AWS Marketplace subscriptions. This is typically managed in the AWS Bedrock console under "Model access" and might require `aws-marketplace:Subscribe` permissions if not already handled.
--   _Enterprise Tip:_ Always apply least-privilege practices. Where possible, scope resource ARNs in your IAM policies to specific models or regions. Utilize [Service Control Policies (SCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) for overarching governance in AWS Organizations.
+1. **Attach the Managed Policy:**
+    - Attach the **`AmazonBedrockFullAccess`** managed policy to your user/role.\
+      [View AmazonBedrockFullAccess Policy Details](https://docs.aws.amazon.com/bedrock/latest/userguide/security-iam.html)
+2. **Confirm Additional Permissions:**
+    - Ensure your policy includes permissions for model invocation (e.g., `bedrock:InvokeModel` and `bedrock:InvokeModelWithResponseStream`), model listing, and AWS Marketplace actions (like `aws-marketplace:Subscribe`).
+    - _Enterprise Tip:_ Apply least-privilege practices by scoping resource ARNs and using [Service Control Policies (SCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) to restrict access where necessary.
 
 ---
 

docs/custom-model-configs/gcp-vertex-ai.mdx

@@ -44,16 +44,16 @@ This guide is tailored for organizations with established GCP environments (leve
 
 #### 2.1 Choose and Confirm a Region
 
-Vertex AI supports multiple regions. Select a region that meets your latency, compliance, and capacity needs. Examples include:
+Vertex AI supports eight regions. Select a region that meets your latency, compliance, and capacity needs. Examples include:
 
 -   **us-east5 (Columbus, Ohio)**
+-   **us-east1 (South Carolina)**
+-   **us-east4 (Northern Virginia)**
 -   **us-central1 (Iowa)**
+-   **us-west1 (The Dalles, Oregon)**
+-   **us-west4 (Las Vegas, Nevada)**
 -   **europe-west1 (Belgium)**
--   **europe-west4 (Netherlands)**
 -   **asia-southeast1 (Singapore)**
--   **global (Global)**
-
-The Global endpoint may offer higher availability and reduce resource exhausted errors. Only Gemini models are supported.
 
 #### 2.2 Enable the Claude 3.5 Sonnet v2 Model
 

docs/docs.json

@@ -71,54 +71,15 @@
 				"group": "Improving Your Prompting Skills",
 				"pages": ["prompting/prompt-engineering-guide", "prompting/cline-memory-bank"]
 			},
-			{
-				"group": "Features",
-				"pages": [
-					"features/auto-approve",
-					"features/checkpoints",
-					"features/cline-rules",
-					"features/drag-and-drop",
-					"features/plan-and-act",
-					"features/slash-commands/workflows",
-					"features/editing-messages",
-					{
-						"group": "@ Mentions",
-						"pages": [
-							"features/at-mentions/overview",
-							"features/at-mentions/file-mentions",
-							"features/at-mentions/terminal-mentions",
-							"features/at-mentions/problem-mentions",
-							"features/at-mentions/git-mentions",
-							"features/at-mentions/url-mentions"
-						]
-					},
-					{
-						"group": "Slash Commands",
-						"pages": [
-							"features/slash-commands/new-task",
-							"features/slash-commands/new-rule",
-							"features/slash-commands/smol",
-							"features/slash-commands/report-bug"
-						]
-					},
-					{
-						"group": "Commands & Shortcuts",
-						"pages": [
-							"features/commands-and-shortcuts/overview",
-							"features/commands-and-shortcuts/code-commands",
-							"features/commands-and-shortcuts/terminal-integration",
-							"features/commands-and-shortcuts/git-integration",
-							"features/commands-and-shortcuts/keyboard-shortcuts"
-						]
-					}
-				]
-			},
 			{
 				"group": "Exploring Cline's Tools",
 				"pages": [
 					"exploring-clines-tools/cline-tools-guide",
+					"exploring-clines-tools/plan-and-act-modes-a-guide-to-effective-ai-development",
+					"exploring-clines-tools/checkpoints",
 					"exploring-clines-tools/new-task-tool",
-					"exploring-clines-tools/remote-browser-support"
+					"exploring-clines-tools/remote-browser-support",
+					"exploring-clines-tools/slash-commands"
 				]
 			},
 			{
@@ -143,23 +104,12 @@
 				]
 			},
 			{
-				"group": "Provider Configuration",
+				"group": "Custom Model Configurations",
 				"pages": [
-					"provider-config/anthropic",
-					"provider-config/claude-code",
-					"provider-config/aws-bedrock-with-credentials-authentication",
-					"provider-config/aws-bedrock-with-profile-authentication",
-					"provider-config/gcp-vertex-ai",
-					"provider-config/litellm-and-cline-using-codestral",
-					"provider-config/vscode-language-model-api",
-					"provider-config/xai-grok",
-					"provider-config/mistral-ai",
-					"provider-config/deepseek",
-					"provider-config/ollama",
-					"provider-config/openai",
-					"provider-config/openai-compatible",
-					"provider-config/openrouter",
-					"provider-config/requesty"
+					"custom-model-configs/aws-bedrock-with-credentials-authentication",
+					"custom-model-configs/aws-bedrock-with-profile-authentication",
+					"custom-model-configs/gcp-vertex-ai",
+					"custom-model-configs/litellm-and-cline-using-codestral"
 				]
 			},
 			{

docs/enterprise-solutions/cloud-provider-integration.mdx

@@ -14,9 +14,9 @@ Certain scenarios may warrant using local models, including handling highly sens
 
 #### [IAM Security Best Practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) (For administrators)
 
-#### [AWS Bedrock setup for Legacy IAM (AWS Credentials)](/provider-config/aws-bedrock-with-credentials-authentication)
+#### [AWS Bedrock setup for Legacy IAM (AWS Credentials)](/custom-model-configs/aws-bedrock-with-credentials-authentication.mdx)
 
-#### [AWS Bedrock setup for SSO token (AWS Profile)](/provider-config/aws-bedrock-with-profile-authentication)
+#### [AWS Bedrock setup for SSO token (AWS Profile)](/custom-model-configs/aws-bedrock-with-profile-authentication.mdx)
 
 #### VPC Endpoint Setup
 

docs/exploring-clines-tools/checkpoints.mdx

@@ -0,0 +1,114 @@
+---
+title: "Checkpoints and Messages"
+description: "When working with AI coding assistants, it's easy to lose control as they make rapid changes to your codebase. That's why we built Checkpoints - your safety net for experimenting confidently."
+---
+
+Checkpoints automatically save snapshots of your workspace after each step in a task. This powerful feature lets you:
+
+-   Track and review changes made during a task
+-   Roll back to any previous point if needed
+-   Experiment confidently with auto-approve mode
+-   Maintain full control over your workspace
+
+### ⚙️ How Checkpoints Work
+
+Cline creates a checkpoint after each tool use (file edits, commands, etc.). These checkpoints:
+
+-   Work alongside your Git workflow without interference
+-   Maintain context between restores
+-   Use a shadow Git repository to track changes
+
+For example, if you're working on a feature and Cline makes multiple file changes, each change creates a checkpoint. This means you can review each modification and, if needed, roll back to any point without affecting your main Git repository.
+
+#### Viewing Changes & Restoring to Checkpoint
+
+After each tool use, you can:
+
+1. Click the "Compare" button to see modified files
+2. Click the "Restore" button to open restore options
+
+<Frame>
+	<img
+		src="https://storage.googleapis.com/cline_public_images/docs/assets/image%20(13).png"
+		alt="Checkpoint comparison and restore options"
+	/>
+</Frame>
+
+#### Rolling Back
+
+To restore to a previous point:
+
+1. Click the "Restore" button next to any step
+2. Choose from three options:
+    - **Restore Task and Workspace**: Reset both codebase and task to that point
+    - **Restore Task Only**: Keep codebase changes but revert task context
+    - **Restore Workspace Only**: Reset codebase while preserving task context
+
+Example: If Cline makes changes you don't like while styling a component, you can use "Restore Workspace Only" to revert the code changes while keeping the conversation context, allowing you to try a different approach.
+
+### 💡 Use Cases
+
+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.
+
+#### 1. Using Auto-Approve Mode
+
+-   Provides safety net for rapid iterations
+-   Makes it easy to undo unexpected results
+
+#### 2. Testing Different Approaches
+
+-   Try multiple solutions confidently
+-   Compare different implementations
+-   Quickly revert to working states
+-   Ideal for exploring different design patterns or architectural approaches
+
+<Frame caption="In this case, I didn't like the changes Cline made to my robot dog-walking website (still working on the robots) and I wanted to revert both the codebase and the task to before any changes were made so I could start fresh.">
+	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/checkpointsDemo.gif" alt="Checkpoint restore demo" />
+</Frame>
+
+### ✨ Best Practices
+
+1. Use checkpoints as safety nets when experimenting
+2. Leverage auto-approve mode more confidently, knowing you can always roll back
+3. Restore selectively based on needs:
+
+    - Use "Restore Task and Workspace" for a fresh start, reversing changes to files and the task conversation.
+    - Use "Restore Task Only" to try different prompts, but leave all files as they exist
+    - Use "Restore Workspace Only" to attempt different implementations, or prune context from the task
+
+🛟 Checkpoints are your safety net when working with Cline, enabling you to experiment freely while maintaining full control over your codebase. Whether you're refactoring a complex component, trying different implementation approaches, or using auto-approve mode for rapid development, checkpoints ensure you can always review changes and roll back if needed.
+
+#### 🗑️ Deleting Checkpoints
+
+You can delete all checkpoints by using the **"Delete All History"** button in the task history menu. Note that this will also delete all tasks. Checkpoints are stored in VS Code's globalStorage.
+
+---
+
+## Editing Messages
+
+Cline allows you to edit chat messages in a task after they've been submitted (with the exception of the message that started the task).
+
+Perhaps you didn't get the results you wanted, thought of a better way to phrase your request, or need to add more information. Editing your message allows you to re-submit a request without starting over or restoring your files or workspace with checkpoints. There are two Restore options:
+
+-   **"Restore Chat"** restores just the task state and re-submits an API request to your provider with your edited message.
+
+-   **"Restore All"** restores both the task state and workspace state before re-submitting an API request. "Workspace state" refers to the condition of your workspace (files, content, etc.) at different points in the conversation.
+
+**Interactive Editing:**
+
+-   Messages can be clicked to enter edit mode
+-   Cline automatically selects all text when entering edit mode
+
+**Keyboard Shortcuts:**
+
+-   Escape: Exit edit mode
+-   Enter: Restore just the task
+-   Cmd/Ctrl + Enter: Restore the task and workspace
+-   Shift + Enter: Insert new line / line break
+
+<Frame>
+	<img
+		src="https://storage.googleapis.com/cline_public_images/docs/assets/message-editing.png"
+		alt="Message editing interface"
+	/>
+</Frame>

docs/exploring-clines-tools/new-task-tool.mdx

@@ -29,11 +29,6 @@ As a quick alternative to Cline suggesting the `newtask` tool or defining comple
 -   **Action:** Cline will propose creating a new task, typically suggesting context based on the current session (similar to its default behavior when using the tool). You will still get the `ask_followup_question` prompt to confirm and potentially modify the context before the new task is created.
 -   **Benefit:** Provides a fast, user-initiated way to leverage the `new_task` functionality for branching explorations or managing long sessions without waiting for Cline to suggest it.
 
-<Note>
-	For more details on using the `/newtask` slash command, see the [New Task Command](/features/slash-commands/new-task)
-	documentation.
-</Note>
-
 #### Default Behavior (Without `.clinerules`)
 
 By default, without specific `.clinerules` dictating its behavior:
@@ -120,7 +115,7 @@ Example of context window usage over 50% with a 200K context window:
 # Context Window Usage
 
 105,000 / 200,000 tokens (53%)
-Model: anthropic/claude-sonnet-4 (200K context window)
+Model: anthropic/claude-3.7-sonnet (200K context window)
 \`\`\`
 
 **IMPORTANT**: When you see context window usage at or above 50%, you MUST:

docs/exploring-clines-tools/plan-and-act-modes-a-guide-to-effective-ai-development.mdx

@@ -1,37 +1,33 @@
 ---
-title: "Plan & Act"
-sidebarTitle: "Plan & Act"
+title: "Plan & Act Modes: A Guide to Effective AI Development"
 ---
 
+## 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.
 
 <Frame>
-	<iframe
-		style={{ width: "100%", aspectRatio: "16/9" }}
-		src="https://www.youtube.com/embed/b7o6URFPp64"
-		title="YouTube video player"
-		frameBorder="0"
-		allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-		allowFullScreen></iframe>
+	<img
+		src="https://storage.googleapis.com/cline_public_images/docs/assets/planningThenActing%20(1).gif"
+		alt="Use Plan to gather context before using Act to implement the plan"
+	/>
 </Frame>
 
-#### Plan Mode: Think First
+### Understanding the Modes
 
-Plan mode is where you and Cline figure out what you're trying to build and how you'll build it. In this mode, Cline:
+#### Plan Mode
 
--   Can read your entire codebase to understand the context
--   Won't make any changes to your files
--   Focuses on understanding requirements and creating a strategy
--   Helps identify potential issues before you write a single line of code
+-   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: Build It
+#### Act Mode
 
-Once you've got a plan, you switch to Act mode. Now Cline:
-
--   Has all the building capabilities at its disposal
--   Can make changes to your codebase
--   Still remembers everything from your planning session
--   Executes the strategy you worked out together
+-   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
 
 <Frame>
 	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/image%20(5).png" alt="Act mode capabilities" />
@@ -39,14 +35,6 @@ Once you've got a plan, you switch to Act mode. Now Cline:
 
 ### Workflow Guide
 
-When I'm working on a new feature or fixing a complex bug, here's what works for me:
-
-1. I start in Plan mode and tell Cline what I want to build
-2. Cline helps me explore the codebase, looking at relevant files
-3. Together we figure out the best approach, considering edge cases and potential issues
-4. When I'm confident in our plan, I switch to Act mode
-5. Cline implements the solution based on our planning
-
 #### 1. Start with Plan Mode
 
 Begin every significant development task in Plan mode:
@@ -120,26 +108,24 @@ Complex projects often require multiple plan-act cycles:
 
 -   Use Plan mode to explore edge cases before implementation
 -   Switch back to Plan when encountering unexpected complexity
--   Leverage [file reading](/features/at-mentions/file-mentions) to validate assumptions early
+-   Leverage file reading to validate assumptions early
 -   Have Cline write markdown files of the plan for future reference
 
 ### Common Patterns
 
-#### When to Use Each Mode
+#### When to Use Plan Mode
 
-I've found Plan mode works best when:
+-   Starting new features
+-   Debugging complex issues
+-   Architectural decisions
+-   Requirements analysis
 
--   Starting something new where the approach isn't obvious
--   Debugging a tricky issue where I'm not sure what's wrong
--   Making architectural decisions that will affect multiple parts of the codebase
--   Trying to understand a complex workflow or feature
+#### When to Use Act Mode
 
-And Act mode is perfect for:
-
--   Implementing a solution we've already planned out
--   Making routine changes where the approach is clear
--   Following established patterns in the codebase
--   Running tests and making minor adjustments
+-   Implementing agreed solutions
+-   Making routine changes
+-   Following established patterns
+-   Executing test cases
 
 <Frame>
 	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/image%20(6).png" alt="Mode usage patterns" />
@@ -156,4 +142,4 @@ Share your experiences and improvements:
 
 ---
 
-Remember: The time invested in planning pays dividends in implementation quality and maintenance efficiency.
+Remember: The time invested in planning pays dividends in implementation quality and maintenance efficiency

docs/exploring-clines-tools/slash-commands.mdx

@@ -0,0 +1,57 @@
+---
+title: "Slash Commands"
+---
+
+#### Overview
+
+Cline provides slash commands as a quick way to invoke specific tools or actions directly from the chat input, offering shortcuts for common operations. This page details the available slash commands and their usage.
+
+#### /newtask
+
+The `/newtask` slash command provides a fast, user-initiated way to leverage the `new_task` tool's functionality for branching explorations or managing long sessions without waiting for Cline to suggest it.
+
+**Functionality:**
+
+1. **Initiation:** Typing `/newtask` in the chat input signals Cline to prepare for starting a new task session.
+2. **Context Proposal:** Cline proposes creating a new task and typically suggests context to preload based on the current session (summarizing key aspects like current work, technical concepts, relevant files, problems solved, and next steps).
+3. **User Confirmation:** You will receive a confirmation prompt (via the `ask_followup_question` tool) displaying the proposed context. You can approve it directly or modify the context before the new task begins.
+4. **New Session:** Upon confirmation, Cline ends the current task session and immediately starts a new one, preloaded with the approved context.
+
+**Benefit:** Allows you to cleanly branch your work or start a new phase while carrying over essential background information ("knowledge transfer") without manual copying or losing the thread of the previous session.
+
+#### /smol (alias /compact)
+
+The `/smol` slash command (with `/compact` as an alias) allows you to condense the chat history **within your current task**. This is useful when a conversation becomes very long, potentially impacting performance or making it harder for the model to maintain focus.
+
+**Functionality:**
+
+1. **Initiation:** Typing `/smol` or `/compact` tells Cline you want to condense the current chat history. You can optionally add instructions after the command to guide the summarization process (e.g., `/smol focus only on the database changes` or `/smol be concise, use bullet points`).
+2. **Summarization:** Cline analyzes the conversation history, considering any additional instructions provided, and generates a summary focusing on key elements: recent discussion points, important decisions, technical concepts, relevant files, problems solved, and planned next steps. Cline determines the appropriate length and detail for the summary. It retains the beginning and very recent parts of the chat while summarizing the middle sections.
+3. **User Confirmation:** Cline presents this generated summary to you via a confirmation prompt and asks if it accurately reflects the essential context.
+4. **Condensing:** If you approve the summary, Cline replaces the summarized middle portion of the chat history in its active context with the generated summary. This reduces the overall token count for subsequent interactions within the _same task_.
+5. **Feedback:** If you reject the summary or provide feedback, Cline will retain the original history and incorporate your feedback for future actions.
+
+**Benefit:** Helps maintain focus and manage token usage during very long, continuous tasks (like deep debugging or extended feature development) without needing to start an entirely new task session. Allows user guidance on the summarization focus.
+
+#### When to Use Which?
+
+Choosing between `/newtask` and `/smol` depends on your goal:
+
+-   Use `/smol` (or `/compact`) when:
+    -   You want to continue the **same task**, but the chat history has become very long or costly.
+    -   You need to reduce token usage for upcoming interactions within the current workflow.
+    -   Example: Deep debugging session where you want to summarize previous steps before continuing.
+-   Use `/newtask` when:
+    -   You have finished one phase of work and want to start a **fresh, related task**.
+    -   You want to branch your exploration while preserving key context from the previous session.
+    -   Example: Moving from developing Feature A to starting work on Feature B, carrying over relevant architectural decisions.
+
+#### Why Manage Context?
+
+While Cline supports large context windows, actively managing context using tools and commands like `/newtask` and `/smol` is often beneficial:
+
+-   **Performance:** Large language models can sometimes experience performance degradation or lose focus when context windows become extremely full (e.g., over 50-75% capacity, depending on the model). Condensing or resetting context can help maintain optimal performance.
+-   **Relevance:** Summarizing or starting fresh ensures the most relevant information is prioritized in the context window.
+-   **Cost:** Reducing the number of tokens sent to the model in each turn can help manage costs, especially with more expensive models.
+
+Using `/newtask` and `/smol` provides you with direct control over the conversation context, allowing for more efficient and effective interaction with Cline.

docs/features/at-mentions/file-mentions.mdx

@@ -1,45 +0,0 @@
----
-title: "File Mentions"
-sidebarTitle: "File Mentions"
----
-
-File mentions let you pull any file from your workspace directly into your conversation with Cline. No more copying and pasting code snippets - just type `@/` and point to the file you need help with.
-
-When you type `@/` in the chat, Cline shows your workspace files. Navigate through folders, select the file you want, and it's instantly available to Cline - complete with all imports, related functions, and surrounding context.
-
-I use file mentions constantly when debugging. Instead of trying to figure out which parts of my code to copy over, I just reference the file directly:
-
-```
-I'm getting this error when my form submits: @terminal
-
-Here's my component: @/src/components/ContactForm.jsx
-
-And the API endpoint: @/src/api/contact.js
-
-What am I missing?
-```
-
-This gives Cline everything it needs - the error message, the component code, and the API endpoint - all without me having to copy anything. Cline can see imports, dependencies, and all the surrounding context that might be causing the issue.
-
-File mentions shine when you're dealing with complex bugs that span multiple files. Before, I'd have to carefully copy each relevant file, making sure I didn't miss anything important. Now I just reference each file with `@/` and Cline gets the complete picture.
-
-Next time you're stuck on a problem, try using file mentions instead of copying code. You'll save time and get better answers because Cline has all the context it needs.
-
-## How It Works Under the Hood
-
-When you use a file mention in your message, here's what happens behind the scenes:
-
-1. When you send your message, Cline detects the `@/path/to/file` pattern in your text
-2. The extension resolves the file path relative to your workspace root
-3. It checks if the file is binary (like an image) or text-based
-4. For text files, it reads the complete file content
-5. The file content is appended to your message in a structured format:
-    ```
-    <file_content path="path/to/file">
-    [Complete file content]
-    </file_content>
-    ```
-6. This enhanced message with the embedded file content is sent to the AI
-7. The AI can now "see" the complete file content as if you had copied and pasted it
-
-This seamless process happens automatically whenever you use a file mention, giving the AI full context without you having to manually copy anything.

docs/features/at-mentions/folder-mentions.mdx

@@ -1,58 +0,0 @@
----
-title: "Folder Mentions"
-sidebarTitle: "Folder Mentions"
----
-
-Folder mentions let you bring entire directories into your conversation with Cline. Just type `@/` followed by a folder path ending with a slash, and Cline gets access to the folder structure and its contents.
-
-When you type `@/` in chat, Cline shows your workspace files and folders. Navigate to the folder you want, make sure to include the trailing slash, and Cline will see the folder's structure and contents.
-
-I use folder mentions when I need help understanding or refactoring a whole section of my codebase. Instead of referencing individual files one by one, I can just point to the entire directory:
-
-```
-I'm trying to understand how the authentication flow works in my app.
-Can you explain the structure and relationships between the files in @/src/auth/?
-```
-
-Cline can then see all the files in the auth directory, their contents, and how they relate to each other. This gives it the full context to explain complex interactions between multiple files.
-
-Folder mentions are also perfect for getting help with project organization. When I'm unsure if my project structure makes sense, I'll ask Cline to review it:
-
-```
-I'm setting up a new React project. Does this folder structure make sense? @/src/
-What would you change to make it more maintainable as the project grows?
-```
-
-Next time you're working with multiple related files, try using folder mentions instead of referencing each file individually. You'll get more comprehensive help because Cline can see the bigger picture of how everything fits together.
-
-## How It Works Under the Hood
-
-When you use a folder mention in your message, here's what happens behind the scenes:
-
-1. When you send your message, Cline detects the `@/path/to/folder/` pattern (with trailing slash) in your text
-2. The extension resolves the folder path relative to your workspace root
-3. It calls `fs.readdir()` to get a list of all files and subdirectories in that folder
-4. For each file in the directory, it checks if it's binary or text-based
-5. For text files, it extracts the complete content
-6. The folder structure and file contents are appended to your message in a structured format:
-
-    ```
-    <folder_content path="path/to/folder">
-    ├── file1.txt
-    ├── file2.js
-    └── subfolder/
-
-    <file_content path="path/to/folder/file1.txt">
-    [File content]
-    </file_content>
-
-    <file_content path="path/to/folder/file2.js">
-    [File content]
-    </file_content>
-    </folder_content>
-    ```
-
-7. This enhanced message with the embedded folder structure and file contents is sent to the AI
-8. The AI can now "see" both the directory structure and the content of files within that directory
-
-This process happens automatically whenever you use a folder mention, giving the AI a comprehensive view of your project structure and file contents.

docs/features/at-mentions/git-mentions.mdx

@@ -1,84 +0,0 @@
----
-title: "Git Mentions"
-sidebarTitle: "Git Mentions"
----
-
-Git mentions let you bring your repository's history and changes directly into your conversation with Cline. You can reference uncommitted changes with `@git-changes` or specific commits with `@[commit-hash]`.
-
-When you type `@` in chat, you can select "Git Changes" from the menu or type `@git-changes` directly. For specific commits, type `@` followed by the commit hash (at least 7 characters). Cline will immediately see the git status, diffs, commit messages, and other relevant information.
-
-I use git mentions constantly when I'm trying to understand code changes or troubleshoot issues introduced by recent commits. Instead of trying to copy and paste diffs or commit logs, I just ask:
-
-```
-I think this commit broke our authentication flow: @a1b2c3d
-
-Can you explain what changed and why it might be causing the issue?
-```
-
-This gives Cline the complete commit information, including the commit message, author, date, and the full diff. Cline can then analyze exactly what changed and how it might affect other parts of the codebase.
-
-The `@git-changes` mention is perfect when you're working on changes and want feedback before committing:
-
-```
-Here are my current changes: @git-changes
-
-I'm trying to implement a new feature for user profiles. Does my approach make sense?
-Are there any potential issues or improvements you'd suggest?
-```
-
-This shows Cline all your uncommitted changes, including new files, modified files, and their diffs. Cline can then review your changes and provide feedback on your implementation.
-
-Git mentions are especially powerful when combined with file mentions. When I'm investigating a bug, I'll often reference both:
-
-```
-I think this commit introduced a bug: @a1b2c3d
-
-Here's the current implementation: @/src/components/Auth.jsx
-
-How can I fix the issue while preserving the intended functionality?
-```
-
-Next time you're working with code changes or investigating issues, try using git mentions instead of manually describing or copying changes. You'll get more accurate help because Cline can see exactly what changed and in what context.
-
-## How It Works Under the Hood
-
-When you use git mentions in your message, here's what happens behind the scenes:
-
-### For Git Changes (`@git-changes`)
-
-1. When you send your message, Cline detects the `@git-changes` pattern in your text
-2. The extension runs git commands to get the current working state of your repository
-3. It captures the output of `git status` and `git diff` to see all uncommitted changes
-4. This information is appended to your message in a structured format:
-
-    ```
-    <git_working_state>
-    On branch main
-    Changes not staged for commit:
-      modified: src/components/Button.jsx
-      modified: src/styles/main.css
-
-    [Complete diff output with all changes]
-    </git_working_state>
-    ```
-
-### For Specific Commits (`@[commit-hash]`)
-
-1. When you send your message, Cline detects the `@` followed by a commit hash pattern
-2. The extension runs `git show` and related commands to get information about that commit
-3. It retrieves the commit message, author, date, and the complete diff
-4. This information is appended to your message in a structured format:
-
-    ```
-    <git_commit hash="a1b2c3d">
-    commit a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t
-    Author: Developer Name <dev@example.com>
-    Date: Mon May 20 14:30:45 2025 -0700
-
-    Fix authentication bug in login form
-
-    [Complete diff output showing all changes in the commit]
-    </git_commit>
-    ```
-
-This process happens automatically whenever you use git mentions, giving the AI complete visibility into your code changes without you having to copy and paste diffs or commit logs.

docs/features/at-mentions/overview.mdx

@@ -1,118 +0,0 @@
----
-title: "@ Mentions Overview"
-sidebarTitle: "Overview"
----
-
-@ mentions are one of Cline's most powerful features, letting you seamlessly bring external context into your conversations. Instead of copying and pasting code, error messages, or documentation, you can simply reference them with an @ symbol.
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/at-mentions.png" alt="@ Mentions Overview" />
-</Frame>
-
-When you type `@` in the chat input, Cline shows a menu of available mention types. These mentions let you reference files, folders, problems, terminal output, git changes, and even web content directly in your conversations.
-
-## Available @ Mentions
-
-Cline supports several types of @ mentions, each designed to bring different kinds of context into your conversations:
-
-<Columns cols={2}>
-  <Card title="File Mentions" icon="file" href="/features/at-mentions/file-mentions">
-    Reference any file in your workspace with `@/path/to/file`. Cline sees the complete file content, including imports, related
-    functions, and surrounding context.
-  </Card>
-
-{" "}
-
-<Card title="Folder Mentions" icon="folder" href="/features/at-mentions/folder-mentions">
-	Reference entire directories with `@/path/to/folder/`. Cline sees the folder structure and all file contents, perfect for
-	understanding complex interactions between multiple files.
-</Card>
-
-{" "}
-
-<Card title="Problem Mentions" icon="triangle-exclamation" href="/features/at-mentions/problem-mentions">
-	Use `@problems` to show Cline all the errors and warnings in your workspace. Cline sees the complete list with file locations
-	and error messages.
-</Card>
-
-{" "}
-
-<Card title="Terminal Mentions" icon="terminal" href="/features/at-mentions/terminal-mentions">
-	Use `@terminal` to share your recent terminal output. Cline sees the complete output with formatting preserved, perfect for
-	debugging build errors or test failures.
-</Card>
-
-{" "}
-
-<Card title="Git Mentions" icon="code-branch" href="/features/at-mentions/git-mentions">
-	Reference uncommitted changes with `@git-changes` or specific commits with `@[commit-hash]`. Cline sees the complete diff,
-	commit message, and other relevant information.
-</Card>
-
-  <Card title="URL Mentions" icon="globe" href="/features/at-mentions/url-mentions">
-    Reference web content with `@https://example.com`. Cline fetches and sees the complete webpage content, perfect for
-    referencing documentation or GitHub issues.
-  </Card>
-</Columns>
-
-## Why @ Mentions Matter
-
-@ mentions transform how you interact with Cline by:
-
-1. **Eliminating copy-paste**: No more copying and pasting code, error messages, or terminal output. Just reference them directly.
-
-2. **Preserving context**: Cline sees the complete context, including imports, related functions, and surrounding code that might be relevant.
-
-3. **Maintaining formatting**: Terminal output, error messages, and web content keep their formatting, making them easier to understand.
-
-4. **Enabling complex workflows**: Combine multiple @ mentions to give Cline a complete picture of your problem:
-
-    ```
-    I'm getting these errors: @problems
-
-    Here's my component: @/src/components/Form.jsx
-    And the API endpoint: @/src/api/users.js
-
-    The error happens when I submit: @terminal
-
-    I think this commit might have caused it: @a1b2c3d
-    ```
-
-## Getting Started
-
-To use @ mentions:
-
-1. Type `@` in the chat input
-2. Select the type of mention from the menu or continue typing
-3. For files and folders, navigate through your workspace structure
-4. Send your message as usual
-
-Cline will automatically process the mentions and include the referenced content in the context sent to the AI.
-
-Try using @ mentions in your next conversation with Cline - you'll be amazed at how much more efficient and effective your interactions become when you can seamlessly bring in external context.
-
-## How It Works Under the Hood
-
-When you use @ mentions in your messages, there's a sophisticated process happening behind the scenes:
-
-1. **Detection**: When you send a message, Cline scans the text for @ mention patterns using regular expressions
-2. **Processing**: For each detected mention, Cline:
-    - Determines the mention type (file, folder, problems, terminal, git, URL)
-    - Fetches the relevant content (file contents, terminal output, etc.)
-    - Formats the content appropriately
-3. **Enhancement**: The original message is enhanced with structured data:
-
-    ```
-    Your original message with @/path/to/file
-
-    <file_content path="/path/to/file">
-    [Complete file content]
-    </file_content>
-    ```
-
-4. **Context Inclusion**: This enhanced message with all the embedded content is sent to the AI model
-5. **Seamless Response**: The AI can now "see" all the referenced content as if you had manually copied and pasted it
-
-This entire process happens automatically and seamlessly whenever you use @ mentions, giving the AI complete context without you having to manually copy anything.
-
-Each type of @ mention has its own specific implementation details, which you can find in their respective documentation pages.

docs/features/at-mentions/problem-mentions.mdx

@@ -1,52 +0,0 @@
----
-title: "Problem Mentions"
-sidebarTitle: "Problem Mentions"
----
-
-The problems mention gives Cline instant access to all the errors and warnings in your workspace. Just type `@problems` and Cline can see every diagnostic issue VSCode has detected.
-
-When you type `@` in chat, select "Problems" from the menu or just type `@problems` directly. Cline will immediately see all the errors and warnings from your workspace, complete with file locations and error messages.
-
-I use the problems mention constantly when I'm stuck on build errors or TypeScript issues. Instead of trying to describe the errors or copy them one by one, I just ask:
-
-```
-I'm getting these TypeScript errors and I'm not sure how to fix them: @problems
-
-Can you help me understand what's wrong and how to fix it?
-```
-
-This gives Cline the complete list of errors with their exact locations and messages. Cline can then analyze the patterns across multiple errors and suggest comprehensive solutions.
-
-The problems mention is especially powerful when combined with file mentions. When I'm dealing with complex type errors, I'll reference both:
-
-```
-I'm getting these type errors: @problems
-
-Here's my component: @/src/components/DataTable.tsx
-And the types file: @/src/types/api.ts
-
-How can I fix these issues?
-```
-
-This approach gives Cline everything it needs - the exact errors, the component code, and the type definitions - all without me having to copy anything manually.
-
-Next time you're stuck on errors, try using `@problems` instead of copying error messages. You'll get more accurate help because Cline can see the complete error context and locations.
-
-## How It Works Under the Hood
-
-When you use the problems mention in your message, here's what happens behind the scenes:
-
-1. When you send your message, Cline detects the `@problems` pattern in your text
-2. The extension calls VSCode's built-in `vscode.languages.getDiagnostics()` API to get all errors and warnings
-3. It formats these diagnostics into a structured text representation with file paths, line numbers, and error messages
-4. The formatted problems list is appended to your message in a structured format:
-    ```
-    <workspace_diagnostics>
-    /path/to/file.js:10:5 - error TS2322: Type 'string' is not assignable to type 'number'.
-    /path/to/file.js:15:3 - warning: This variable is never used.
-    </workspace_diagnostics>
-    ```
-5. This enhanced message with the embedded diagnostics is sent to the AI
-6. The AI can now "see" all the errors and warnings in your workspace, complete with their locations and messages
-
-This process happens automatically whenever you use the problems mention, giving the AI a comprehensive view of all the issues in your workspace without you having to copy them manually.

docs/features/at-mentions/terminal-mentions.mdx

@@ -1,60 +0,0 @@
----
-title: "Terminal Mentions"
-sidebarTitle: "Terminal Mentions"
----
-
-The terminal mention lets you bring your terminal output directly into your conversation with Cline. Just type `@terminal` and Cline can see the recent output from your terminal.
-
-When you type `@` in chat, select "Terminal" from the menu or just type `@terminal` directly. Cline will immediately see the recent output from your active terminal, including error messages, build logs, or command results.
-
-I use the terminal mention all the time when I'm dealing with build errors, test failures, or debugging output. Instead of trying to copy and paste terminal output (which often loses formatting), I just ask:
-
-```
-I'm getting this error when running my tests: @terminal
-
-What's causing this and how can I fix it?
-```
-
-This gives Cline the complete terminal output with all its formatting intact. Cline can then analyze the error messages, stack traces, and surrounding context to provide more accurate help.
-
-The terminal mention is especially powerful when combined with file mentions. When I'm debugging a failed API call, I'll reference both:
-
-```
-I'm getting this error when calling my API: @terminal
-
-Here's my API client code: @/src/api/client.js
-And the endpoint implementation: @/src/server/routes/users.js
-
-What am I doing wrong?
-```
-
-This approach gives Cline everything it needs - the exact error output, the client code, and the server implementation - all without me having to copy anything manually.
-
-Next time you're running into issues with command output or build errors, try using `@terminal` instead of copying the output. You'll get more accurate help because Cline can see the complete terminal context with proper formatting.
-
-## How It Works Under the Hood
-
-When you use the terminal mention in your message, here's what happens behind the scenes:
-
-1. When you send your message, Cline detects the `@terminal` pattern in your text
-2. The extension calls `getLatestTerminalOutput()` which accesses VSCode's terminal API
-3. It captures the recent output buffer from your active terminal
-4. The terminal output is appended to your message in a structured format:
-
-    ```
-    <terminal_output>
-    $ npm run test
-    > project@1.0.0 test
-    > jest
-
-    FAIL src/components/__tests__/Button.test.js
-    ● Button component › renders correctly
-
-    [Complete terminal output with formatting preserved]
-    </terminal_output>
-    ```
-
-5. This enhanced message with the embedded terminal output is sent to the AI
-6. The AI can now "see" the complete terminal output with all formatting preserved
-
-This process happens automatically whenever you use the terminal mention, giving the AI access to your command results, error messages, and other terminal output without you having to copy it manually.

docs/features/at-mentions/url-mentions.mdx

@@ -1,65 +0,0 @@
----
-title: "URL Mentions"
-sidebarTitle: "URL Mentions"
----
-
-URL mentions let you bring web content directly into your conversation with Cline. Just type `@` followed by any URL, and Cline can see the content of that webpage without you having to copy and paste anything.
-
-When you type `@` in chat followed by a URL (like `@https://example.com`), Cline will fetch the content of that webpage and include it in the context. This works for documentation pages, GitHub issues, Stack Overflow questions, or any other web content you want to reference.
-
-I use URL mentions constantly when I'm working with external APIs or libraries. Instead of trying to explain how an API works or copying documentation snippets, I just reference the docs directly:
-
-```
-I'm trying to implement authentication with this API: @https://api.example.com/docs/auth
-
-Can you help me write the code to get an access token based on these docs?
-```
-
-This gives Cline the complete documentation page, so it can see all the authentication requirements, endpoints, parameters, and examples. Cline can then provide more accurate and comprehensive help based on the official documentation.
-
-URL mentions are especially useful for referencing GitHub issues or discussions:
-
-```
-I'm trying to fix this issue in our project: @https://github.com/our-org/our-repo/issues/123
-
-Here's my current implementation: @/src/components/Feature.jsx
-
-What changes do I need to make to address the issue?
-```
-
-This shows Cline the complete GitHub issue, including the description, comments, and any code snippets or screenshots. Cline can then help you implement a solution that directly addresses the reported issue.
-
-Next time you're working with external documentation or online resources, try using URL mentions instead of copying and pasting content. You'll get more accurate help because Cline can see the complete context of the webpage, including formatting, code examples, and surrounding information.
-
-## How It Works Under the Hood
-
-When you use a URL mention in your message, here's what happens behind the scenes:
-
-1. When you send your message, Cline detects the `@http://...` or `@https://...` pattern in your text
-2. The extension launches a headless browser (Puppeteer) in the background
-3. It navigates to the URL and waits for the page to load completely
-4. The browser captures the page content, including text, formatting, and code examples
-5. The content is converted to a Markdown format that preserves the structure
-6. This content is appended to your message in a structured format:
-
-    ```
-    <url_content url="https://example.com/docs">
-    # Example API Documentation
-
-    ## Authentication
-
-    To authenticate with the API, you need to...
-
-    const token = await api.authenticate({
-      username: 'user',
-      password: 'pass'
-    });
-
-    [Complete webpage content in Markdown format]
-    </url_content>
-    ```
-
-7. The browser is then closed to free up resources
-8. This enhanced message with the embedded webpage content is sent to the AI
-
-This process happens automatically whenever you use a URL mention, giving the AI access to the complete content of the webpage without you having to copy and paste anything.

docs/features/auto-approve.mdx

@@ -1,59 +0,0 @@
-The Auto Approve menu lets you set fine-grained permissions on what you allow Cline to do in an automated way.
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/auto-approve.png" alt="Auto Approve" />
-</Frame>
-
-## How it works
-
-By default, Cline will ask for your permission before calling any tool, including reading or writing files.
-
-If you want to allow Cline to do something without asking, you can set the Auto Approve permission for that tool.
-
-## Permission Options
-
--   **Read project files**
-
-    -   Allows Cline to read files within your current workspace without asking
-    -   **Read all files**
-        -   Extends read permission to files outside your workspace (system files, config files, etc.)
-
--   **Edit project files**
-
-    -   Allows Cline to modify files within your current workspace without confirmation
-    -   **Edit all files**
-        -   Extends modification permission to files outside your workspace
-
--   **Execute safe commands**
-
-    -   Allows execution of terminal commands that the model deems non-destructive
-    -   **Execute all commands**
-        -   Permits execution of any terminal command without asking
-
--   **Use the browser**
-
-    -   Allows Cline to use the browser tool to fetch web content
-
--   **Use MCP servers**
-
-    -   Permits connection to and usage of MCP servers for extended functionality
-
--   **Maximum requests**
-    -   Sets the number of consecutive automated actions Cline can take before requiring your input
-
-## Best Practices
-
-Personally, I like to keep auto-editing disabled because it gives me a chance to review changes every step of the way.
-
-For most serious development workflows, I recommend starting with:
-
--   Auto-approving read access to project files
--   Setting a reasonable maximum request limit (10-20)
-
-This gives Cline enough freedom to explore your codebase without constant interruptions, while still requiring permission for edits or potentially destructive actions.
-
-As you build more trust in Cline's capabilities with your specific projects, you can gradually increase the permissions to match your comfort level.
-
-Remember that you can always adjust these settings as your needs change - tighten permissions for critical production work, or loosen them when prototyping and exploring.
-
-You can even use the quick "star" actions to quickly toggle your auto-approved selections on and off as you go.

docs/features/checkpoints.mdx

@@ -1,79 +0,0 @@
----
-title: "Checkpoints"
-sidebarTitle: "Checkpoints"
----
-
-Checkpoints automatically save snapshots of your workspace after each step in a task. This feature lets you track changes, roll back when needed, and experiment confidently with your code.
-
-## How Checkpoints Work
-
-Cline creates a checkpoint after each tool use (file edits, commands, etc.). These checkpoints:
-
--   Work alongside your Git workflow without interference
--   Maintain context between restores
--   Use a shadow Git repository to track changes
-
-For example, if you're working on a feature and Cline makes multiple file changes, each change creates a checkpoint. This means you can review each modification and, if needed, roll back to any point without affecting your main Git repository.
-
-## Viewing Changes & Restoring
-
-After each tool use, you can:
-
-1. Click the "Compare" button to see modified files
-2. Click the "Restore" button to open restore options
-
-<Frame>
-	<img
-		src="https://storage.googleapis.com/cline_public_images/docs/assets/image%20(13).png"
-		alt="Checkpoint comparison and restore options"
-	/>
-</Frame>
-
-## Restore Options
-
-To restore to a previous point:
-
-1. Click the "Restore" button next to any step
-2. Choose from three options:
-    - **Restore Task and Workspace**: Reset both codebase and task to that point
-    - **Restore Task Only**: Keep codebase changes but revert task context
-    - **Restore Workspace Only**: Reset codebase while preserving task context
-
-Example: If Cline makes changes you don't like while styling a component, you can use "Restore Workspace Only" to revert the code changes while keeping the conversation context, allowing you to try a different approach.
-
-<Frame caption="Reverting both codebase and task to before any changes were made to start fresh">
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/checkpointsDemo.gif" alt="Checkpoint restore demo" />
-</Frame>
-
-## Use Cases
-
-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.
-
-### Using Auto-Approve Mode
-
--   Provides safety net for rapid iterations
--   Makes it easy to undo unexpected results
-
-### Testing Different Approaches
-
--   Try multiple solutions confidently
--   Compare different implementations
--   Quickly revert to working states
--   Ideal for exploring different design patterns or architectural approaches
-
-## Best Practices
-
-1. Use checkpoints as safety nets when experimenting
-2. Leverage auto-approve mode more confidently, knowing you can always roll back
-3. Restore selectively based on needs:
-    - Use "Restore Task and Workspace" for a fresh start
-    - Use "Restore Task Only" to try different prompts, but keep file changes
-    - Use "Restore Workspace Only" to attempt different implementations while preserving conversation context
-
-## Relationship with Message Editing
-
-The [message editing feature](/features/editing-messages) uses checkpoints under the hood when you select the "Restore All" option. This allows you to not only edit and resubmit your message but also restore your workspace to the state it was in at that point in the conversation.
-
-## Deleting Checkpoints
-
-You can delete all checkpoints by using the **"Delete All History"** button in the task history menu. Note that this will also delete all tasks. Checkpoints are stored in VS Code's globalStorage.

docs/features/cline-rules.mdx

@@ -1,162 +0,0 @@
-Cline Rules allow you to provide Cline with system-level guidance. Think of them as a persistent way to include context and preferences for your projects or globally for every conversation.
-
-## Creating a Rule
-
-You can create a rule by clicking the `+` button in the Rules tab. This will open a new file in your IDE which you can use to write your rule.
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/cline-rules.png" alt="Create a Rule" />
-</Frame>
-
-Once you save the file:
-
--   Your rule will be stored in the `.clinerules/` directory in your project (if it's a Workspace Rule)
--   Or in the `Documents/Cline/Rules` directory (if it's a Global Rule).
-
-You can also have Cline create a rule for you by using the [`/newrule` slash command](/features/slash-commands/new-rule) in the chat.
-
-```markdown Example Cline Rule Structure [expandable]
-# Project Guidelines
-
-## Documentation Requirements
-
--   Update relevant documentation in /docs when modifying features
--   Keep README.md in sync with new capabilities
--   Maintain changelog entries in CHANGELOG.md
-
-## Architecture Decision Records
-
-Create ADRs in /docs/adr for:
-
--   Major dependency changes
--   Architectural pattern changes
--   New integration patterns
--   Database schema changes
-    Follow template in /docs/adr/template.md
-
-## Code Style & Patterns
-
--   Generate API clients using OpenAPI Generator
--   Use TypeScript axios template
--   Place generated code in /src/generated
--   Prefer composition over inheritance
--   Use repository pattern for data access
--   Follow error handling pattern in /src/utils/errors.ts
-
-## Testing Standards
-
--   Unit tests required for business logic
--   Integration tests for API endpoints
--   E2E tests for critical user flows
-```
-
-### Key Benefits
-
-1. **Version Controlled**: The `.clinerules` file becomes part of your project's source code
-2. **Team Consistency**: Ensures consistent behavior across all team members
-3. **Project-Specific**: Rules and standards tailored to each project's needs
-4. **Institutional Knowledge**: Maintains project standards and practices in code
-
-Place the `.clinerules` file in your project's root directory:
-
-```
-your-project/
-├── .clinerules
-├── src/
-├── docs/
-└── ...
-```
-
-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).
-
-### Tips for Writing Effective Cline Rules
-
--   Be Clear and Concise: Use simple language and avoid ambiguity.
--   Focus on Desired Outcomes: Describe the results you want, not the specific steps.
--   Test and Iterate: Experiment to find what works best for your workflow.
-
-### .clinerules/ Folder System
-
-```
-your-project/
-├── .clinerules/              # Folder containing active rules
-│   ├── 01-coding.md          # Core coding standards
-│   ├── 02-documentation.md   # Documentation requirements
-│   └── current-sprint.md     # Rules specific to current work
-├── src/
-└── ...
-```
-
-Cline automatically processes **all Markdown files** inside the `.clinerules/` directory, combining them into a unified set of rules. The numeric prefixes (optional) help organize files in a logical sequence.
-
-#### Using a Rules Bank
-
-For projects with multiple contexts or teams, maintain a rules bank directory:
-
-```
-your-project/
-├── .clinerules/              # Active rules - automatically applied
-│   ├── 01-coding.md
-│   └── client-a.md
-│
-├── clinerules-bank/          # Repository of available but inactive rules
-│   ├── clients/              # Client-specific rule sets
-│   │   ├── client-a.md
-│   │   └── client-b.md
-│   ├── frameworks/           # Framework-specific rules
-│   │   ├── react.md
-│   │   └── vue.md
-│   └── project-types/        # Project type standards
-│       ├── api-service.md
-│       └── frontend-app.md
-└── ...
-```
-
-#### Benefits of the Folder Approach
-
-1. **Contextual Activation**: Copy only relevant rules from the bank to the active folder
-2. **Easier Maintenance**: Update individual rule files without affecting others
-3. **Team Flexibility**: Different team members can activate rules specific to their current task
-4. **Reduced Noise**: Keep the active ruleset focused and relevant
-
-#### Usage Examples
-
-Switch between client projects:
-
-```bash
-# Switch to Client B project
-rm .clinerules/client-a.md
-cp clinerules-bank/clients/client-b.md .clinerules/
-```
-
-Adapt to different tech stacks:
-
-```bash
-# Frontend React project
-cp clinerules-bank/frameworks/react.md .clinerules/
-```
-
-#### Implementation Tips
-
--   Keep individual rule files focused on specific concerns
--   Use descriptive filenames that clearly indicate the rule's purpose
--   Consider git-ignoring the active `.clinerules/` folder while tracking the `clinerules-bank/`
--   Create team scripts to quickly activate common rule combinations
-
-The folder system transforms your Cline rules from a static document into a dynamic knowledge system that adapts to your team's changing contexts and requirements.
-
-### Managing Rules with the Toggleable Popover
-
-To make managing both single `.clinerules` files and the folder system even easier, Cline v3.13 introduces a dedicated popover UI directly accessible from the chat interface.
-
-Located conveniently under the chat input field, this popover allows you to:
-
--   **Instantly See Active Rules:** View which global rules (from your user settings) and workspace rules (`.clinerules` file or folder contents) are currently active.
--   **Quickly Toggle Rules:** Enable or disable specific rule files within your workspace `.clinerules/` folder with a single click. This is perfect for activating context-specific rules (like `react-rules.md` or `memory-bank.md`) only when needed.
--   **Easily Add/Manage Rules:** Quickly create a workspace `.clinerules` file or folder if one doesn't exist, or add new rule files to an existing folder.
-
-This UI significantly simplifies switching contexts and managing different sets of instructions without needing to manually edit files or configurations during a conversation.
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/image%20(1).png" alt="Cline Logo" />
-</Frame>

docs/features/commands-and-shortcuts/code-commands.mdx

@@ -1,129 +0,0 @@
----
-title: "Code Commands"
-sidebarTitle: "Code Commands"
----
-
-Cline's code commands bring AI assistance directly into your editor, letting you interact with your code without leaving your workflow. With a simple right-click, you can add code to Cline, and through the lightbulb menu, you can fix errors, get explanations, or improve your code.
-
-## Available Code Commands
-
-When you interact with code in your editor, you can access Cline commands in two ways:
-
-### Right-Click Context Menu
-
-When you right-click on selected code, you'll see:
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/code-commands.png" alt="Right Click Menu" />
-</Frame>
-
-#### Add to Cline
-
-The "Add to Cline" command sends your selected code to the Cline chat panel. This is perfect for:
-
--   Asking questions about specific code snippets
--   Requesting improvements or optimizations
--   Getting explanations of complex logic
-
-When you use this command, Cline automatically includes:
-
--   The file path (as a file mention)
--   The selected code with proper formatting
--   The programming language for accurate syntax highlighting
-
-### Lightbulb Menu (Code Actions)
-
-When you see a lightbulb icon in your editor, click it to access these Cline commands:
-
-<Frame>
-	<img src="https://storage.googleapis.com/cline_public_images/docs/assets/lightbulb-actions.png" alt="Lightbulb Menu" />
-</Frame>
-
-#### Fix with Cline
-
-The "Fix with Cline" command appears in the lightbulb menu when your code has errors or warnings. This command:
-
-1. Captures the selected code
-2. Identifies the errors or warnings from VSCode's diagnostics
-3. Sends both to Cline with a request to fix the issues
-4. Provides a solution that addresses the specific problems
-
-This is incredibly useful for quickly resolving syntax errors, linter warnings, or type issues without having to manually describe the problem.
-
-#### Explain with Cline
-
-The "Explain with Cline" command helps you understand complex code. When you select code and use this command from the lightbulb menu, Cline:
-
-1. Analyzes the selected code
-2. Provides a clear explanation of what the code does
-3. Breaks down complex logic into understandable parts
-4. Highlights important patterns or techniques used
-
-#### Improve with Cline
-
-The "Improve with Cline" command helps you enhance your code. When you select code and use this command from the lightbulb menu, Cline:
-
-1. Analyzes the selected code for potential improvements
-2. Suggests optimizations, refactorings, or better practices
-3. Explains the reasoning behind the suggested changes
-4. Provides improved code that maintains the original functionality
-
-## How to Use Code Commands
-
-Using Cline's code commands is simple:
-
-### For Right-Click Commands:
-
-1. Select the code you want to work with
-2. Right-click to open the context menu
-3. Choose "Add to Cline"
-4. View the result in the Cline chat panel
-
-### For Lightbulb Menu Commands:
-
-1. Select the code you want to work with
-2. Look for the lightbulb icon that appears in the editor gutter
-3. Click the lightbulb to see available actions
-4. Choose the appropriate Cline command (Fix, Explain, or Improve)
-5. View the result in the Cline chat panel
-
-After using any command, you can:
-
--   Ask follow-up questions
--   Request modifications to the solution
--   Apply the changes back to your code
-
-## How It Works Under the Hood
-
-When you use a code command, here's what happens behind the scenes:
-
-1. **Code Selection**: The extension captures your selected code and its context
-2. **Metadata Collection**: Cline gathers important metadata:
-
-    - File path and name
-    - Programming language
-    - Any associated diagnostics (errors/warnings)
-    - Surrounding code context when relevant
-
-3. **Command Processing**:
-
-    - For "Add to Cline," the code is formatted and sent to the chat panel
-    - For "Fix with Cline," the code and diagnostics are analyzed and a fix is generated
-    - For "Explain with Cline," the code is analyzed to provide a clear explanation
-    - For "Improve with Cline," the code is analyzed for potential optimizations and improvements
-
-4. **Integration with Chat**: The results appear in the Cline chat panel, where you can:
-    - See the AI's response
-    - Ask follow-up questions
-    - Apply suggested changes
-
-This seamless integration between your editor and Cline's AI capabilities makes it easy to get assistance without disrupting your coding flow.
-
-## Tips for Effective Use
-
--   **Select complete logical units**: When possible, select entire functions, classes, or modules to give Cline complete context
--   **Include imports**: For language-specific help, include relevant imports so Cline understands dependencies
--   **Combine with @ mentions**: For complex issues, use code commands along with file or problem mentions for more context
--   **Use keyboard shortcuts**: Speed up your workflow by [assigning keyboard shortcuts](/features/commands-and-shortcuts/keyboard-shortcuts) to common code commands
-
-Next time you're struggling with a piece of code, try using Cline's code commands instead of switching to a separate chat interface. You'll be amazed at how much more efficient your workflow becomes when AI assistance is integrated directly into your editor.