Simplify symbol formatting: omit () from all symbol names

Appending () is language-specific and can mislead for TypeScript,
Obj-C, etc. The kind suffix (— function, — class, etc.) already
communicates the symbol type clearly.

.agents/skills/create-pull-request/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: create-pull-request
-description: Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.
+description: Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.
 ---
 
 # Create Pull Request
@@ -147,14 +147,29 @@ When filling out the template:
 
 ### Create PR with gh CLI
 
+**Use a temporary file for the PR body** to avoid shell escaping issues, newline problems, and other command-line flakiness:
+
+1. Write the PR body to a temporary file:
+   ```
+   /tmp/pr-body.md
+   ```
+
+2. Create the PR using the file:
+   ```bash
+   gh pr create --title "PR_TITLE" --body-file /tmp/pr-body.md --base main
+   ```
+
+3. Clean up the temporary file:
+   ```bash
+   rm /tmp/pr-body.md
+   ```
+
+For draft PRs:
 ```bash
-gh pr create --title "PR_TITLE" --body "PR_BODY" --base main
+gh pr create --title "PR_TITLE" --body-file /tmp/pr-body.md --base main --draft
 ```
 
-Alternatively, create as draft if the user wants review before marking ready:
-```bash
-gh pr create --title "PR_TITLE" --body "PR_BODY" --base main --draft
-```
+**Why use a file?** Passing complex markdown with newlines, special characters, and checkboxes directly via `--body` is error-prone. The `--body-file` flag handles all content reliably.
 
 ## Post-Creation
 

.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/big-cows-ring.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Add claude 4.5 haiku

.changeset/clean-shrimps-repeat.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: finalize document content during approval flow

.changeset/config.json

@@ -1,11 +0,0 @@
-{
-	"$schema": "https://unpkg.com/@changesets/config@3.0.5/schema.json",
-	"changelog": "@changesets/cli/changelog",
-	"commit": false,
-	"fixed": [],
-	"linked": [],
-	"access": "restricted",
-	"baseBranch": "main",
-	"updateInternalDependencies": "patch",
-	"ignore": []
-}

.changeset/eleven-experts-win.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Expose --version in cline cli command

.changeset/fine-wombats-pump.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Log Persistence errors to PostHog

.changeset/five-years-nail.md

@@ -1,13 +0,0 @@
----
-"claude-dev": patch
----
-
-feat: add OpenAI Codex (ChatGPT Plus/Pro) provider
-
-Users with ChatGPT Plus or Pro subscriptions can now use GPT-5 models directly through Cline without needing an API key. Authentication is handled via OAuth through OpenAI's authentication system.
-
-Models available:
-- gpt-5.2-codex (default)
-- gpt-5.1-codex-max
-- gpt-5.1-codex-mini
-- gpt-5.2

.changeset/fix-diff-boundary-validation.md

@@ -1,9 +0,0 @@
----
-"claude-dev": patch
----
-
-Fix two bugs in DiffViewProvider file editing:
-
-1. **Line boundary validation**: Add `safelyTruncateDocument()` to prevent out-of-bounds line errors on JetBrains hosts (fixes #8423, #8429). The gRPC protocol strictly validates line numbers, causing "truncateDocument INTERNAL: Wrong line" errors when `truncateDocument()` was called with a line number >= document line count.
-
-2. **Content concatenation on final update**: When replacing content without a trailing newline, the old content at line N+1 was concatenated to the new content. Fixed by extending the replacement range to cover the entire document on final update.

.changeset/fix-ollama-model-names.md

@@ -1,9 +0,0 @@
----
-"claude-dev": patch
----
-
-docs: fix outdated Ollama model names in documentation
-
-Updated recommended Ollama models to use correct identifiers:
-- Changed qwen3-coder-30b to qwen2.5-coder:32b
-- Changed devstral-small to codellama:34b-code

.changeset/flat-doodles-kiss.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-OpenAI GPT-5 Codex models are now using Apply Patch tool for diff edits.

.changeset/gold-tigers-wish.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Fix issue where tool call ids are invalid when switching between models using the chat completion format and the responses api format.

.changeset/lucky-worlds-stand.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: add chat output on skill use

.changeset/quiet-lions-visit.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Adding telemetry for background exec terminal

.changeset/ready-doodles-try.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-This pull request introduces comprehensive Jupyter Notebook support for Cline, enabling AI-assisted editing of `.ipynb` files with full cell-level context awareness. The feature allows users to seamlessly work with Jupyter notebooks using Cline's AI capabilities while preserving the notebook's JSON structure.

.changeset/small-foxes-shine.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: removes retry message from UI after retry succeeds

.changeset/smart-paws-sip.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Support native tool calling for LM Studio and Ollama provider

.changeset/solid-rats-flash.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-add claude 4.5 opus into sap provider.

.changeset/stale-emus-hug.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Limite Vertex and LiteLLM options when they're remote configured

.changeset/sweet-coins-rush.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Fix crash when the Context Menu has a type but no options

.changeset/wicked-icons-fix.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Throttle the remote config fetch

.changeset/wild-ears-poke.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Improve history view filter menu

.changeset/worktree-management-ui.md

@@ -1,5 +0,0 @@
----
-"cline": patch
----
-
-Add git worktree management UI for running parallel Cline sessions

.changie.yaml

@@ -1,26 +0,0 @@
-changesDir: .changes
-unreleasedDir: unreleased
-headerPath: header.tpl.md
-changelogPath: CHANGELOG.md
-versionExt: md
-versionFormat: '## {{.Version}} - {{.Time.Format "2006-01-02"}}'
-kindFormat: "### {{.Kind}}"
-changeFormat: "* {{.Body}}"
-kinds:
-    - label: Added
-      auto: minor
-    - label: Changed
-      auto: major
-    - label: Deprecated
-      auto: minor
-    - label: Removed
-      auto: major
-    - label: Fixed
-      auto: patch
-    - label: Security
-      auto: patch
-newlines:
-    afterChangelogHeader: 1
-    beforeChangelogVersion: 1
-    endOfVersion: 1
-envPrefix: CHANGIE_

.clinerules/cli.md

@@ -0,0 +1,33 @@
+# CLI Development
+
+The CLI lives in `cli/` and uses React Ink for terminal UI.
+
+- If needed, look at `cli/src/constants/colors.ts` for re-used terminal colors, e.g. `COLORS.primaryBlue` highlight color (selections, spinners, success states).
+- Never use `dimColor` with gray (e.g. `<Text color="gray" dimColor>`) - it's too hard to read. Use `color="gray"` for secondary text and normal foreground (no color) for primary text.
+- When thinking about how to handle state or messages from core, look at webview for how it communicates with the vs code extension.
+- When updating the webview, consider and suggest to the user to update the CLI TUI since we want to provide a similar experience to our terminal users as we do our vs code extension users.
+
+## Adding New API Providers
+
+When adding a new API provider to the extension, you must also update the CLI:
+
+1. **Update `cli/src/components/ModelPicker.tsx`**: Add the provider to the `providerModels` map so `getDefaultModelId()` returns the correct default model. Import the models and default ID from `@shared/api`:
+   ```typescript
+   import { newProviderDefaultModelId, newProviderModels } from "@/shared/api"
+
+   export const providerModels = {
+     // ...existing providers
+     "new-provider": { models: newProviderModels, defaultId: newProviderDefaultModelId },
+   }
+   ```
+
+2. **Use `applyProviderConfig()` for auth flows**: When implementing OAuth or other auth flows for the provider, use the shared utility at `cli/src/utils/provider-config.ts`:
+   ```typescript
+   import { applyProviderConfig } from "../utils/provider-config"
+
+   // After successful auth:
+   await applyProviderConfig({ providerId: "new-provider", controller })
+   ```
+   This handles setting provider, default model, API key mapping, state persistence, and rebuilding the API handler.
+
+3. **Provider-specific auth**: If the provider uses OAuth (like `openai-codex`), add handling in `SettingsPanelContent.tsx`'s `handleProviderSelect` callback. See the existing Codex OAuth flow as a reference.

.clinerules/general.md

@@ -14,7 +14,7 @@ This file is the secret sauce for working effectively in this codebase. It captu
 
 ## Miscellaneous
 - This is a VS Code extension—check `package.json` for available scripts before trying to verify builds (e.g., `npm run compile`, not `npm run build`).
-- When creating PRs, if the change is user-facing and significant enough to warrant a changelog entry, run `npm run changeset` and create a patch changeset. Never create minor or major version bumps. Skip changesets for trivial fixes, internal refactors, or minor UI tweaks that users wouldn't notice.
+- When creating PRs, contributors should not create changelog-entry files. Maintainers handle release versioning and changelog curation during the release process.
 - When adding new feature flags, see this PR as a reference https://github.com/cline/cline/pull/7566
 - Additional instructions about making requests: @.clinerules/network.md
 
@@ -147,6 +147,17 @@ Required steps:
 
 Common mistake: Adding only the return value without the `context.globalState.get()` call. This compiles but the value is always `undefined` on load.
 
+Settings plumbing gotcha: if a key is user-toggleable from settings, wire both controller update paths:
+- `src/core/controller/state/updateSettings.ts` for webview `updateSetting(...)`
+- `src/core/controller/state/updateSettingsCli.ts` for CLI/ACP settings updates
+Missing one path causes a toggle to appear to change in one surface while the backend state stays unchanged.
+
+Webview toggle gotcha: settings changes must also round-trip back in state payloads.
+- Add the field to `UpdateSettingsRequest` in `proto/cline/state.proto` (for webview update requests), then run `npm run protos`
+- Include the key in `Controller.getStateToPostToWebview()` (`src/core/controller/index.ts`)
+- Ensure `ExtensionState` and webview defaults include the key (`src/shared/ExtensionMessage.ts`, `webview-ui/src/context/ExtensionStateContext.tsx`)
+If this round-trip wiring is missing, the backend value can update but the toggle in webview appears stuck or reverts.
+
 ## StateManager Cache vs Direct globalState Access
 StateManager uses an in-memory cache populated during `StateManager.initialize(context)` in `common.ts`. For most state, use `controller.stateManager.setGlobalState()`/`getGlobalStateKey()`.
 

.clinerules/hooks/PostToolUse.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "PostToolUse running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "PostToolUse response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "PostToolUse hook custom errorMessage"
-}
-EOF

.clinerules/hooks/PreToolUse.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "PreToolUse running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "PreToolUse response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "PreToolUse hook custom errorMessage"
-}
-EOF

.clinerules/hooks/TaskCancel.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "TaskCancel running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "TaskCancel response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "TaskCancel hook custom errorMessage"
-}
-EOF

.clinerules/hooks/TaskResume.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "TaskResume running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "TaskResume response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "TaskResume hook custom errorMessage"
-}
-EOF

.clinerules/hooks/TaskStart.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "TaskStart running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "TaskStart response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "TaskStart hook custom errorMessage"
-}
-EOF

.clinerules/hooks/UserPromptSubmit.example

@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-echo "UserPromptSubmit running inside local cline/.clinerules/hooks/ directory"
-
-input=$(cat)
-echo $input | jq .
-
-for i in {1..5}; do
-  sleep 1
-  echo "$i"
-done
-
-cat <<EOF
-{
-  "cancel": false,
-  "contextModification": "UserPromptSubmit response from the local cline/.clinerules/hooks/ directory.",
-  "errorMessage": "UserPromptSubmit hook custom errorMessage"
-}
-EOF

.clinerules/storage.md

@@ -0,0 +1,64 @@
+# Storage Architecture
+
+Global settings, secrets and workspace state are stored in **file-backed JSON stores** under `~/.cline/data/`. This is the shared storage layer used by VSCode, CLI, and JetBrains.
+
+## Key Abstractions
+
+### `StorageContext` (src/shared/storage/storage-context.ts)
+The entry point. Created via `createStorageContext()` and passed to `StateManager.initialize()`. Contains three `ClineFileStorage` instances:
+- `globalState` → `~/.cline/data/globalState.json`
+- `secrets` → `~/.cline/data/secrets.json` (mode 0o600)
+- `workspaceState` → `~/.cline/data/workspaces/<hash>/workspaceState.json`
+
+### `ClineFileStorage` (src/shared/storage/ClineFileStorage.ts)
+Synchronous JSON key-value store backed by a single file. Supports `get()`, `set()`, `setBatch()`, `delete()`. Writes are atomic (write-then-rename).
+
+### `StateManager` (src/core/storage/StateManager.ts)
+In-memory cache on top of `StorageContext`. All runtime reads hit the cache; writes update cache immediately and debounce-flush to disk.
+
+## ⚠️ Do NOT Use VSCode's ExtensionContext for Storage
+
+**Do not** read from or write to `context.globalState`, `context.workspaceState`, or `context.secrets` for persistent data. These are VSCode-specific and not available on CLI or JetBrains.
+
+Instead, use:
+```typescript
+// Reading state
+StateManager.get().getGlobalStateKey("myKey")
+StateManager.get().getSecretKey("mySecretKey")
+StateManager.get().getWorkspaceStateKey("myWsKey")
+
+// Writing state
+StateManager.get().setGlobalState("myKey", value)
+StateManager.get().setSecret("mySecretKey", value)
+StateManager.get().setWorkspaceState("myWsKey", value)
+```
+
+Remember that your data may be read by a different client than the one that wrote it. For example, a value written by Cline in JetBrains may be read by Cline CLI.
+
+## VSCode Migration (src/hosts/vscode/vscode-to-file-migration.ts)
+
+On VSCode startup, a migration copies data from VSCode's `ExtensionContext` storage into the file-backed stores. This runs in `src/common.ts` before `StateManager.initialize()`.
+
+- **Sentinel**: `__vscodeMigrationVersion` key in global state and workspace state — prevents re-migration.
+- **Merge strategy**: File store wins. Existing values are never overwritten.
+- **Safe downgrade**: VSCode storage is NOT cleared, so older extension versions still work.
+
+## Adding New Storage Keys
+
+1. Add to `src/shared/storage/state-keys.ts` (see existing patterns)
+2. Read/write via `StateManager` (NOT via `context.globalState`)
+3. If adding a secret, add to `SecretKeys` array in `state-keys.ts`
+
+## File Layout
+
+```
+~/.cline/
+  data/
+    globalState.json          # Global settings & state
+    secrets.json              # API keys (mode 0o600)
+    tasks/
+      taskHistory.json        # Task history (separate file)
+    workspaces/
+      <hash>/
+        workspaceState.json   # Per-workspace toggles
+```

.clinerules/workflows/address-pr-comments.md

@@ -19,7 +19,7 @@ Review and address all comments on the current branch's PR.
    - Inline comments: `gh api repos/{owner}/{repo}/pulls/{pr_number}/comments`
    - General comments: `gh pr view {pr_number} --json comments,reviews`
 
-4. Present a summary of all comments with your recommendation for each (apply, skip, or respond). Ignore bot noise (changeset-bot, CI status, etc.).
+4. Present a summary of all comments with your recommendation for each (apply, skip, or respond). Ignore bot noise (release automation, CI status, etc.).
 
 5. **Wait for my approval** before proceeding.
 

.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-(--vscode-foreground)",
-						indicator:
-							"text-(--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/hotfix-release.md

@@ -89,16 +89,9 @@ On the main branch, create a commit that updates:
 
 2. **package.json** - Update the version field to the new version
 
-3. **Delete changesets** for the commits being included in the hotfix. This prevents the changeset bot from including duplicate entries in the next regular release.
+3. No changelog-entry file cleanup is needed. Contributors do not create changelog-entry files in this repo.
 
-   Find and delete the changeset files associated with the selected commits:
-   ```bash
-   ls .changeset/
-   ```
-
-   Each changeset file in `.changeset/` corresponds to a PR. Read them to identify which ones belong to the commits you're hotfixing, then delete those files.
-
-**Skip running `npm run install:all`** - the automation handles outdated lockfiles.
+**Skip running `npm run install:all`** - release automation handles lockfile consistency as needed.
 
 Commit with message format: `v{VERSION} Release Notes (hotfix)`
 
@@ -107,7 +100,7 @@ In the commit body, mention:
 - List the cherry-picked commits that will be included
 
 ```bash
-git add CHANGELOG.md package.json .changeset/
+git add CHANGELOG.md package.json
 git commit -m "v3.40.1 Release Notes (hotfix)
 
 Hotfix release including:

.clinerules/workflows/pr-review.md

@@ -347,8 +347,6 @@ A few notes:
 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>

.clinerules/workflows/release.md

@@ -1,232 +1,64 @@
 # Release
 
-Prepare and publish a release from the open changeset PR.
+Prepare and publish a release directly from `main`.
 
 ## Overview
 
 This workflow helps you:
-1. Find and checkout the open changeset PR
-2. Clean up the changelog (fix version format, wordsmith entries)
-3. Push changes back to the PR branch
-4. Merge with proper commit message format
-5. Tag and push the release (after verifying the commit)
-6. Trigger the publish workflow
-7. Update GitHub release notes
-8. Provide final summary with Slack announcement
+1. Select/confirm the target version
+2. Curate `CHANGELOG.md` entries manually for end users
+3. Ensure `package.json` version matches the changelog
+4. Create and push a release commit + tag
+5. Trigger publish workflow
+6. Update GitHub release notes and share a summary
 
-## Step 1: Find the Changeset PR
+## Process
 
-Look for the open changeset PR:
-
-```bash
-gh pr list --search "Changeset version bump" --state open --json number,title,headRefName,url
-```
-
-If no PR is found, inform the user there's no changeset PR ready. They may need to:
-- Merge PRs with changesets to main first
-- Manually trigger the Changeset Converter workflow at: https://github.com/cline/cline/actions/workflows/changeset-converter.yml
-
-## Step 2: Gather PR Information
-
-Get the PR details:
-
-```bash
-PR_NUMBER=<number from step 1>
-gh pr view $PR_NUMBER --json body,files,headRefName
-```
-
-Checkout the PR branch:
-
-```bash
-git fetch origin changeset-release/main
-git checkout changeset-release/main
-```
-
-If the branch has diverged from remote, reset to the remote version:
-
-```bash
-git reset --hard origin/changeset-release/main
-```
-
-## Step 3: Analyze the Changes
-
-Read the current CHANGELOG.md to see what the automation generated:
-
-```bash
-head -50 CHANGELOG.md
-```
-
-Get the version from package.json:
-
-```bash
-cat package.json | grep '"version"'
-```
-
-**Present to the user:**
-- The version number that will be released
-- The raw changelog entries from the changeset PR
-- Whether this is a patch, minor, or major release
-
-## Step 4: Clean Up the Changelog
-
-The changelog needs these fixes:
-
-1. **Add brackets to version number**: Change `## 3.44.1` to `## [3.44.1]`
-
-2. **No category headers**: Don't use `### Added`, `### Fixed`, etc. Just a flat list of bullet points.
-
-3. **Order entries from most important to least important**:
-   - Lead with major new features or significant fixes users care about
-   - End with minor fixes or internal changes
-
-4. **Write user-friendly descriptions**:
-   - This is for end users, not developers—explain what changed in plain language
-   - Remove commit hashes from the beginning of lines (the automation adds these)
-   - Look at the actual commit diffs (`git show <hash>`) and PRs to understand what changed
-   - Write colorful descriptions that explain the value and impact, not just technical details
-   - Consolidate related changes into single entries when appropriate
-
-**Ask the user** to review the proposed changelog changes before applying them. Show them:
-- Current (raw) changelog section
-- Proposed (cleaned) changelog section
-
-Once approved, apply the changes to CHANGELOG.md.
-
-## Step 5: Commit and Push Changes
-
-After making changelog edits:
-
-```bash
-git add CHANGELOG.md
-git commit -m "Clean up changelog formatting"
-git push origin changeset-release/main
-```
-
-## Step 6: Merge the PR
-
-**Ask the user to confirm** they're ready to merge.
-
-Merge the PR with the proper commit message format:
-
-```bash
-VERSION=<version from package.json>
-gh pr merge $PR_NUMBER --squash --subject "v${VERSION} Release Notes" --body ""
-```
-
-**If merge is blocked by branch protection:**
-- Users with admin privileges can add the `--admin` flag to bypass
-- Users without admin privileges need to get the PR approved through normal review first before merging
-
-## Step 7: Tag the Release
-
-After the merge completes, checkout main and pull:
+### 1) Sync and determine version
 
 ```bash
 git checkout main
 git pull origin main
+cat package.json | grep '"version"'
 ```
 
-**IMPORTANT: Verify the latest commit is the release commit before tagging:**
+Confirm the release version with the maintainer (patch/minor/major).
+
+### 2) Curate changelog and version
+
+- Edit `CHANGELOG.md` for the target version using human-friendly release notes.
+- Ensure version headers use bracket format, e.g. `## [3.66.1]`.
+- Update `package.json` version to the same value.
+
+### 3) Commit and tag
 
 ```bash
-git log -1 --oneline
+git add CHANGELOG.md package.json package-lock.json
+git commit -m "v<version> Release Notes"
+git push origin main
+git tag v<version>
+git push origin v<version>
 ```
 
-Confirm the commit message matches `v{VERSION} Release Notes` (e.g., `v3.44.1 Release Notes`). Do NOT blindly tag HEAD without verification.
+### 4) Trigger publish workflow
 
-Once verified, tag and push:
+Tell the maintainer to run:
+https://github.com/cline/cline/actions/workflows/publish.yml
+
+Use `v<version>` as the release tag.
+
+### 5) Update GitHub release notes
+
+After publish completes:
 
 ```bash
-VERSION=<version>
-git tag v${VERSION}
-git push origin v${VERSION}
+gh release view v<version> --json body --jq '.body'
+gh release edit v<version> --notes "<final curated release notes>"
 ```
 
-## Step 8: Trigger Publish Workflow
+### 6) Final summary
 
-**Copy the tag to clipboard** so the user can easily paste it into the GitHub Actions workflow:
-
-```bash
-echo -n "v{VERSION}" | pbcopy
-```
-
-**Tell the user to trigger the publish workflow:**
-1. Go to: https://github.com/cline/cline/actions/workflows/publish.yml
-2. Select **"release"** for release-type
-3. Paste **`v{VERSION}`** as the tag (already in clipboard)
-
-**Wait for the user** to confirm the publish workflow has completed before proceeding.
-
-## Step 9: Update GitHub Release Notes
-
-Once the user confirms the publish workflow is done, fetch the auto-generated release content:
-
-```bash
-VERSION=<version>
-gh release view v${VERSION} --json body --jq '.body'
-```
-
-The auto-generated release has:
-- `## What's Changed` - PR list (we'll replace this with our changelog)
-- `## New Contributors` - First-time contributors (keep this if present)
-- `**Full Changelog**` - Comparison link (keep this)
-
-Build the new release body:
-1. Start with `## What's Changed` header
-2. Add our changelog content (from CHANGELOG.md for this version)
-3. Keep the `## New Contributors` section if it exists
-4. Keep the `**Full Changelog**` link
-
-Update the release:
-
-```bash
-gh release edit v${VERSION} --notes "<new body content>"
-```
-
-Verify the release was updated:
-
-```bash
-gh release view v${VERSION}
-```
-
-## Step 10: Final Summary
-
-**Copy a Slack announcement message to clipboard** (include the full changelog, not just highlights):
-
-```bash
-echo "VS Code v{VERSION} Released
-
-- Changelog entry 1
-- Changelog entry 2
-- Changelog entry 3" | pbcopy
-```
-
-**Present a final summary:**
-- Version released: v{VERSION}
-- PR merged: #{PR_NUMBER}
-- Tag pushed: v{VERSION}
-- Release: https://github.com/cline/cline/releases/tag/v{VERSION}
-- Slack message copied to clipboard
-
-**Final reminder:**
-Post the Slack message to announce the release
-
-## Handling Edge Cases
-
-### No changesets found
-If the changeset PR body shows no changes, inform the user they need to merge PRs with changesets first.
-
-### Merge conflicts
-If there are conflicts on the changeset branch, help the user resolve them:
-```bash
-git fetch origin main
-git rebase origin/main
-# resolve conflicts
-git push origin changeset-release/main --force-with-lease
-```
-
-### User wants to add more changes
-If the user wants to include additional PRs before releasing:
-1. Ask them to merge those PRs to main first
-2. The changeset automation will update the PR automatically
-3. Re-run this workflow after the PR is updated
+Provide:
+- Released version/tag
+- Link to release page
+- Summary of top end-user changes

.codex/environments/environment.toml

@@ -0,0 +1,49 @@
+# THIS IS AUTOGENERATED. DO NOT EDIT MANUALLY
+version = 1
+name = "cline"
+
+[setup]
+script = '''
+if [ ! -d "node_modules" ]; then
+  MAIN_WORKTREE="$(git worktree list | head -n1 | awk '{print $1}')"
+  ln -s "$MAIN_WORKTREE/node_modules" node_modules
+  ln -s "$MAIN_WORKTREE/webview-ui/node_modules" webview-ui/node_modules
+fi
+'''
+
+[[actions]]
+name = "VS Code"
+icon = "run"
+command = "chmod +x ./scripts/run-extension-host.sh && ./scripts/run-extension-host.sh production"
+
+[[actions]]
+name = "CLI"
+icon = "run"
+command = '''
+npm run cli:build
+npm run cli:run
+'''
+
+[[actions]]
+name = "npm install"
+icon = "tool"
+command = '''
+rm node_modules
+rm webview-ui/node_modules
+npm run install:all
+'''
+
+[[actions]]
+name = "pull main"
+icon = "tool"
+command = '''
+git fetch origin main                                                                                                                                                             
+                                                                                                                                                                                
+if ! git merge-base --is-ancestor main origin/main; then                                                                                                                          
+  echo "Local main has commits not on origin/main. Aborting..."                                                                                                                     
+  exit 1                                                                                                                                                                          
+fi
+
+git update-ref refs/heads/main refs/remotes/origin/main
+echo "main updated to $(git rev-parse --short main)"
+'''

.env.example

@@ -16,13 +16,6 @@
 TELEMETRY_SERVICE_API_KEY=your-posthog-telemetry-api-key
 ERROR_SERVICE_API_KEY=your-posthog-error-tracking-api-key
 
-# ============================================================================
-# TELEMETRY PROVIDER CONTROL
-# ============================================================================
-# Control which telemetry providers are active
-POSTHOG_TELEMETRY_ENABLED=true          # Enable PostHog telemetry (default: true)
-                                        # Set to false to disable Telemetry completely
-
 # ============================================================================
 # OPENTELEMETRY (Optional - for advanced telemetry)
 # ============================================================================

.gitattributes

@@ -1,4 +1,5 @@
 demo.gif filter=lfs diff=lfs merge=lfs -text
 assets/docs/demo.gif filter=lfs diff=lfs merge=lfs -text
+webview-ui/src/assets/cline_kanban_demo.webm filter=lfs diff=lfs merge=lfs -text
 
 * text=auto eol=lf

.github/CODEOWNERS

@@ -1,3 +1,2 @@
-/docs/
-/.github/   @saoudrizwan @garoth @sjf
-/README.md  @saoudrizwan @nickbaumann98
+/.github/   @saoudrizwan @arafatkatze @maxpaulus43 @candieduniverse
+/README.md  @saoudrizwan @juanpflores

.github/copilot-instructions.md

@@ -0,0 +1,58 @@
+# Copilot Instructions for Cline
+
+This is a VS Code extension. Read `.clinerules/general.md` for tribal knowledge and nuanced patterns.
+
+## Architecture
+- **Core** (`src/`): `extension.ts` → `WebviewProvider` → `Controller` (single source of truth) → `Task` (agent loop).
+- **Webview** (`webview-ui/`): React/Vite app. State via `ExtensionStateContext.tsx`, synced through message passing.
+- **CLI** (`cli/`): React Ink terminal UI sharing core logic. Update CLI when changing webview features.
+- **Communication**: Protobuf-defined gRPC-like protocol over VS Code message passing. Schemas in `proto/`.
+- **MCP**: `src/services/mcp/McpHub.ts`.
+
+## Build & Test (Critical — non-obvious commands)
+- **Build**: `npm run compile` — NOT `npm run build`.
+- **Watch**: `npm run watch` (extension + webview).
+- **Protos**: `npm run protos` — run **immediately** after any `.proto` change. Generates into `src/shared/proto/`, `src/generated/`.
+- **Tests**: `npm run test:unit`. After prompt/tool changes: `UPDATE_SNAPSHOTS=true npm run test:unit`.
+
+## Protobuf RPC Workflow (4 steps)
+1. **Define** in `proto/cline/*.proto`. Naming: `PascalCaseService`, `camelCase` RPCs, `PascalCase` Messages. Use `common.proto` shared types for simple data.
+2. **Generate**: `npm run protos`.
+3. **Backend handler**: `src/core/controller/<domain>/`. 
+4. **Frontend call**: `UiServiceClient.myMethod(Request.create({...}))`.
+- Adding enums (e.g. `ClineSay`) → also update `src/shared/proto-conversions/cline-message.ts`.
+
+## Adding API Providers (silent failure risk)
+Three proto conversion updates are **required** or the provider silently resets to Anthropic:
+1. `proto/cline/models.proto` — add to `ApiProvider` enum.
+2. `convertApiProviderToProto()` in `src/shared/proto-conversions/models/api-configuration-conversion.ts`.
+3. `convertProtoToApiProvider()` in the same file.
+
+Also update: `src/shared/api.ts`, `src/shared/providers/providers.json`, `src/core/api/index.ts`, `webview-ui/.../providerUtils.ts`, `webview-ui/.../validate.ts`, `webview-ui/.../ApiOptions.tsx`, and `cli/src/components/ModelPicker.tsx`.
+
+For Responses API providers: add to `isNextGenModelProvider()` in `src/utils/model-utils.ts` and set `apiFormat: ApiFormat.OPENAI_RESPONSES` on models.
+
+## Adding Tools to System Prompt (5+ file chain)
+1. Add enum to `ClineDefaultTool` in `src/shared/tools.ts`.
+2. Create definition in `src/core/prompts/system-prompt/tools/` (export `[GENERIC]` minimum).
+3. Register in `src/core/prompts/system-prompt/tools/init.ts`.
+4. Whitelist in `src/core/prompts/system-prompt/variants/*/config.ts` for each model family.
+5. Handler in `src/core/task/tools/handlers/`, wire in `ToolExecutor.ts`.
+6. If tool has UI: add `ClineSay` enum in proto → `ExtensionMessage.ts` → `cline-message.ts` → `ChatRow.tsx`.
+7. Regenerate snapshots: `UPDATE_SNAPSHOTS=true npm run test:unit`.
+
+## Modifying System Prompt
+Modular: `components/` (shared) + `variants/` (model-specific) + `templates/` (`{{PLACEHOLDER}}`). Variants override components via `componentOverrides` in `config.ts` or custom `template.ts`. XS variant is heavily condensed inline. Always regenerate snapshots after changes.
+
+## Global State Keys (silent failure risk)
+Adding a key requires: type in `src/shared/storage/state-keys.ts`, read via `context.globalState.get()` in `src/core/storage/utils/state-helpers.ts` `readGlobalStateFromDisk()`, and add to return object. Missing the `.get()` call compiles fine but value is always `undefined`.
+
+## Slash Commands (3 places)
+- `src/core/slash-commands/index.ts` — definitions.
+- `src/core/prompts/commands.ts` — system prompt integration.
+- `webview-ui/src/utils/slash-commands.ts` — webview autocomplete.
+
+## Conventions
+- **Paths**: Always use `src/utils/path` helpers (`toPosixString`) for cross-platform compatibility.
+- **Logging**: `src/shared/services/Logger.ts`.
+- **Feature flags**: See PR #7566 as reference pattern.

.github/pull_request_template.md

@@ -60,7 +60,6 @@ We're not looking for exhaustive documentation - just evidence that you've thoug
 
 -   [ ] Changes are limited to a single feature, bugfix or chore (split larger changes into separate PRs)
 -   [ ] Tests are passing (`npm test`) and code is formatted and linted (`npm run format && npm run lint`)
--   [ ] I have created a changeset using `npm run changeset` (required for user-facing changes)
 -   [ ] I have reviewed [contributor guidelines](https://github.com/cline/cline/blob/main/CONTRIBUTING.md)
 
 ### Screenshots

.github/scripts/overwrite_changeset_changelog.py

@@ -1,79 +0,0 @@
-"""
-This script updates a specific version's release notes section in CHANGELOG.md with new content
-or reformats existing content.
-
-The script:
-1. Takes a version number, changelog path, and optionally new content as input from environment variables
-2. Finds the section in the changelog for the specified version
-3. Either:
-   a) Replaces the content with new content if provided, or
-   b) Reformats existing content by:
-      - Removing the first two lines of the changeset format
-      - Ensuring version numbers are wrapped in square brackets
-4. Writes the updated changelog back to the file
-
-Environment Variables:
-    CHANGELOG_PATH: Path to the changelog file (defaults to 'CHANGELOG.md')
-    VERSION: The version number to update/format
-    PREV_VERSION: The previous version number (used to locate section boundaries)
-    NEW_CONTENT: Optional new content to insert for this version
-"""
-
-#!/usr/bin/env python3
-
-import os
-
-CHANGELOG_PATH = os.environ.get("CHANGELOG_PATH", "CHANGELOG.md")
-VERSION = os.environ['VERSION']
-PREV_VERSION = os.environ.get("PREV_VERSION", "")
-NEW_CONTENT = os.environ.get("NEW_CONTENT", "")
-
-def overwrite_changelog_section(changelog_text: str, new_content: str):
-    # Find the section for the specified version
-    version_pattern = f"## {VERSION}\n"
-    unformmatted_prev_version_pattern = f"## {PREV_VERSION}\n"
-    prev_version_pattern = f"## [{PREV_VERSION}]\n"
-    print(f"latest version: {VERSION}")
-    print(f"prev_version: {PREV_VERSION}")
-
-    notes_start_index = changelog_text.find(version_pattern) + len(version_pattern)
-    notes_end_index = changelog_text.find(prev_version_pattern, notes_start_index) if PREV_VERSION and (prev_version_pattern in changelog_text or unformmatted_prev_version_pattern in changelog_text) else len(changelog_text)
-
-    if new_content:
-        return changelog_text[:notes_start_index] + f"{new_content}\n" + changelog_text[notes_end_index:]
-    else:
-        changeset_lines = changelog_text[notes_start_index:notes_end_index].split("\n")
-        filtered_lines = []
-        for line in changeset_lines:
-            # If the previous line is a changeset format
-            if len(filtered_lines) > 1 and filtered_lines[-1].startswith("### "):
-                # Remove the last two lines from the filted_lines
-                filtered_lines.pop()
-                filtered_lines.pop()
-            else:
-                filtered_lines.append(line.strip())
-
-        # Prepend a new line to the first line of filtered_lines
-        if filtered_lines:
-            filtered_lines[0] = "\n" + filtered_lines[0]
-
-        # Print filted_lines wiht a "\n" at the end of each line
-        for line in filtered_lines:
-            print(line.strip())
-
-        parsed_lines = "\n".join(line for line in filtered_lines)
-        updated_changelog = changelog_text[:notes_start_index] + parsed_lines + changelog_text[notes_end_index:]
-        return updated_changelog
-
-with open(CHANGELOG_PATH, 'r') as f:
-    changelog_content = f.read()
-
-new_changelog = overwrite_changelog_section(changelog_content, NEW_CONTENT)
-# print("----------------------------------------------------------------------------------")
-# print(new_changelog)
-# print("----------------------------------------------------------------------------------")
-# Write back to CHANGELOG.md
-with open(CHANGELOG_PATH, 'w') as f:
-    f.write(new_changelog)
-
-print(f"{CHANGELOG_PATH} updated successfully!")

.github/workflows/changeset-converter.yml

@@ -1,113 +0,0 @@
-name: Changeset Converter
-run-name: Changeset Conversion
-
-on:
-    workflow_dispatch:
-    pull_request:
-        types: [closed]
-
-env:
-    REPO_PATH: ${{ github.repository }}
-    GIT_REF: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || 'main' }}
-    NODE_VERSION: 20.18.1
-
-jobs:
-    # Job 1: Create version bump PR when changesets are merged to main
-    changeset-pr-version-bump:
-        if: |
-            github.event_name == 'workflow_dispatch' ||
-            (
-                github.event_name == 'pull_request' &&
-                github.event.pull_request.merged == true &&
-                github.event.pull_request.base.ref == 'main' &&
-                github.actor != 'github-actions'
-            )
-        runs-on: ubuntu-latest
-        permissions:
-            contents: write
-            pull-requests: write
-        steps:
-            - name: Check user for team affiliation
-              id: team_check
-              if: github.event_name == 'workflow_dispatch'
-              uses: morfien101/actions-authorized-user@4a3cfbf0bcb3cafe4a71710a278920c5d94bb38b
-              with:
-                  username: ${{ github.actor }}
-                  org: ${{ github.repository_owner }}
-                  team: "deployer"
-                  github_token: ${{ secrets.GITHUB_TOKEN }}
-
-            - name: Check if user is authorized
-              if: github.event_name == 'workflow_dispatch'
-              run: |
-                  if [ "${{ steps.team_check.outputs.authorized }}" != "true" ]; then
-                      echo "User is not authorized to run this workflow."
-                      exit 1
-                  fi
-
-            - name: Git Checkout
-              uses: actions/checkout@v4
-              with:
-                  fetch-depth: 0
-                  ref: ${{ env.GIT_REF }}
-
-            - name: Setup Node.js
-              uses: actions/setup-node@v4
-              with:
-                  node-version: ${{ env.NODE_VERSION }}
-                  cache: "npm"
-
-            - name: Install Dependencies
-              run: npm ci
-
-            # Check if there are any new changesets to process
-            - name: Check for changesets
-              id: check-changesets
-              run: |
-                  NEW_CHANGESETS=$(find .changeset -name "*.md" ! -name "README.md" | wc -l | tr -d ' ')
-                  echo "Changesets diff with previous version: $NEW_CHANGESETS"
-                  echo "new_changesets=$NEW_CHANGESETS" >> $GITHUB_OUTPUT
-
-            # Create version bump PR using changesets/action if there are new changesets
-            - name: Create Changeset Pull Request
-              if: steps.check-changesets.outputs.new_changesets != '0'
-              uses: changesets/action@v1
-              with:
-                  commit: "changeset version bump"
-                  title: "Changeset version bump"
-                  version: npm run version-packages # This performs the changeset version bump
-              env:
-                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-            # Get current and previous versions to edit changelog entry
-            - name: Get version
-              id: get_version
-              run: |
-                  VERSION=$(git show HEAD:package.json | jq -r '.version')
-                  echo "version=$VERSION" >> $GITHUB_OUTPUT
-                  PREV_VERSION=$(git show origin/main:package.json | jq -r '.version')
-                  echo "prev_version=$PREV_VERSION" >> $GITHUB_OUTPUT
-                  echo "version=$VERSION"
-                  echo "prev_version=$PREV_VERSION"
-
-            # Update CHANGELOG.md with proper format
-            - name: Update Changelog Format
-              env:
-                  VERSION: ${{ steps.get_version.outputs.version }}
-                  PREV_VERSION: ${{ steps.get_version.outputs.prev_version }}
-              run: python .github/scripts/overwrite_changeset_changelog.py
-
-            # Commit and push changelog updates
-            - name: Push Changelog updates to Pull Request
-              run: |
-                  git config user.name "github-actions"
-                  git config user.email github-actions@github.com
-                  echo "Running git add and commit..."
-                  git add CHANGELOG.md
-                  git commit -m "Updating CHANGELOG.md format"
-                  git status
-                  echo "--------------------------------------------------------------------------------"
-                  echo "Pushing to remote..."
-                  echo "--------------------------------------------------------------------------------"
-                  CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
-                  git push origin $CURRENT_BRANCH

.github/workflows/claude-issue-triage.yml

@@ -1,173 +0,0 @@
-name: Claude Issue Triage
-
-on:
-  issues:
-    types: [opened]
-  # Manual trigger for backfilling existing issues. Run from terminal:
-  #   gh workflow run claude-issue-triage.yml -f issue_number=1234
-  # Or batch process:
-  #   gh issue list --state open --limit 10 --json number --jq '.[].number' | while read num; do
-  #     gh workflow run claude-issue-triage.yml -f issue_number=$num
-  #     sleep 60
-  #   done
-  workflow_dispatch:
-    inputs:
-      issue_number:
-        description: 'Issue number to triage'
-        required: true
-        type: string
-
-jobs:
-  claude-issue-triage:
-
-    runs-on: ubuntu-latest
-    timeout-minutes: 120
-    # SECURITY: These permissions are intentionally restrictive.
-    # - contents: read  -> Claude can read the codebase but CANNOT write/push any code
-    # - issues: write   -> Claude can comment and add labels (the only write access needed)
-    # - pull-requests: read -> Claude can view PR context but CANNOT create PRs
-    # This ensures that even if a malicious user attempts prompt injection via issue content,
-    # Claude cannot modify repository code, create branches, or open PRs.
-    permissions:
-      contents: read
-      issues: write
-      pull-requests: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Run Issue Response & Triage
-        id: triage
-        uses: anthropics/claude-code-action@v1
-        with:
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          allowed_non_write_users: "*"
-          # Allow all tools - security is enforced by GitHub permissions above (contents: read, issues: write)
-          claude_args: --model claude-opus-4-5-20251101 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,WebFetch,WebSearch"
-          prompt: |
-            You're a GitHub issue first responder for the open source Cline repository.
-
-            **Issue:** #${{ github.event.issue.number || inputs.issue_number }}
-            **Title:** ${{ github.event.issue.title || 'See issue details below' }}
-            **Author:** @${{ github.event.issue.user.login || 'See issue details below' }}
-
-            ## Your job
-
-            Investigate this issue thoroughly, then post a single helpful comment that helps the user and gives maintainers the context they need.
-
-            ## Investigation
-
-            Start by reading the full issue:
-            gh issue view ${{ github.event.issue.number || inputs.issue_number }}
-
-            ### Search for duplicates and related issues
-
-            Search thoroughly for existing issues that match this one:
-            gh issue list --search "<keywords from the issue>" --state all --limit 30
-            gh issue list --search "<error messages>" --state all --limit 20
-            gh issue list --search "<affected feature/component>" --state all --limit 20
-
-            For each relevant issue you find, read it including its comments:
-            gh issue view <number> --comments
-
-            You're looking for:
-            - **Duplicates**: Issues describing the same problem. Link to them and explain why you think they're duplicates. If closed, check how they were resolved - the solution might apply here.
-            - **Related issues**: Similar problems or context that could help. Pull useful information from their comments (workarounds others found, debugging steps that helped, maintainer explanations). Link to them and explain the connection.
-
-            If there are closed issues with solutions, surface those solutions prominently - this might immediately solve the user's problem.
-
-            ### Analyze recent changes (ALWAYS DO THIS)
-
-            Many issues are regressions from recent releases. **Always** check what changed recently:
-            gh release list --limit 10
-            gh pr list --state merged --limit 50 --json number,title,mergedAt,author,body
-
-            Look for PRs merged in the last few weeks that might correlate with the issue. If you find a likely connection:
-            gh pr view <number>
-            gh pr diff <number>
-            git log --since="1 month ago" --oneline -- <relevant paths>
-            git show <commit>
-
-            **Always include your findings in your comment:**
-            - If you find a regression, call it out explicitly: which PR/commit likely caused it, who authored it, what changed, and suggest a fix direction if you can see one.
-            - If you don't find anything related, still mention it: "I analyzed recent PRs and releases but didn't find any changes that seem related to this issue."
-
-            ### Search the codebase
-
-            Find the relevant code:
-            - Use grep/find to locate code related to the issue
-            - Key areas: `src/api/` (providers/models), `src/core/prompts/` (tools/prompts), platform-specific code for VS Code vs JetBrains
-
-            ### Find documentation
-
-            Cline docs are at **https://docs.cline.bot/** and built with Mintlify from the `docs/` directory.
-
-            The URL structure maps directly to the file structure:
-            - `docs/getting-started/selecting-your-model.mdx` → https://docs.cline.bot/getting-started/selecting-your-model
-            - `docs/troubleshooting.mdx` → https://docs.cline.bot/troubleshooting
-            - Headings become anchors: `## Which Model` → `#which-model`
-
-            Search the `docs/` directory to find relevant documentation, then construct URLs to link users to:
-            ```bash
-            ls docs/
-            grep -r "keyword" docs/ --include="*.mdx" -l
-            ```
-
-            ### Identify subject matter experts
-
-            For issues that clearly need engineering attention:
-            git log --since="6 months ago" --format="%an" -- <relevant paths> | sort | uniq -c | sort -rn | head -5
-
-            Cross-reference with GitHub usernames. Include in your response (@mention, do NOT assign):
-
-            | SME | Reason |
-            |-----|--------|
-            | @username1 | Authored PR #X which modified this area |
-            | @username2 | Primary contributor to affected file |
-
-            ## Weak model detection
-
-            Many issues are caused by users running small or non-frontier models that don't tool-call reliably. Signs include:
-            - Model failing to use tools correctly
-            - Nonsensical or malformed responses
-            - User is running a small/local model or older model version
-
-            If this looks like a weak model issue, kindly suggest they try reproducing with Claude Sonnet and report back if it persists. Link to https://docs.cline.bot/getting-started/selecting-your-model if helpful. Still label and triage normally.
-
-            ## Your comment
-
-            Write a single comment as a helpful community member. Be conversational, not robotic. Include what's relevant:
-
-            - **Helpful response** - Answer their question, suggest a fix, provide a workaround. If you found solutions in related closed issues, surface those prominently.
-            - **Duplicates and related issues** - Link to any you found and explain why they're duplicates/related. Summarize useful context from their comments.
-            - **Regression analysis** - If this looks like a regression, explain what change likely caused it, link to the PR/commit, and tag the author.
-            - **Clarifying questions** - If you need more info, ask specific questions. Don't ask for things already provided.
-            - **SME table** - Include the table above if this needs engineering attention. Don't tag people for questions with obvious answers or weak-model issues.
-            - **Context for maintainers** - Relevant code paths, what you found. Keep it concise.
-            - **Docs links** - If there's relevant documentation, link to it naturally in your response as a recommendation (e.g., "For more details, check out [the Ollama setup guide](url)"). Do NOT add a "Sources" section at the end - integrate doc links into your response where they're helpful.
-            - **Possible Duplicates section** - ALWAYS include a "Possible Duplicates" section at the end of your comment listing issues that might be duplicates so maintainers can quickly close if appropriate. If none found, say "No obvious duplicates found."
-
-            ## Labels
-            First, retrieve all available labels and read their descriptions to understand what each is for:
-            gh label list --json name,description --limit 100
-
-            Then apply the appropriate labels based on your analysis. Only use labels from the list above—do not create new labels.
-            gh issue edit ${{ github.event.issue.number || inputs.issue_number }} --add-label "label1,label2"
-
-            If your regression analysis found a likely culprit (a recent PR/commit that probably caused this issue), add the "Regression" label:
-            gh issue edit ${{ github.event.issue.number || inputs.issue_number }} --add-label "Regression"
-
-            IMPORTANT: After posting your comment, add the "Bot Responded" label to indicate this issue has received an automated response:
-            gh issue edit ${{ github.event.issue.number || inputs.issue_number }} --add-label "Bot Responded"
-
-            ## Remember
-
-            - **This is a one-time automated response** - you will NOT see their reply or respond again. Never say things like "I can help you", "let me know", "once I have that info", or "I can give you more targeted help" - you won't be there to follow up. If you ask clarifying questions, frame them for the maintainers who will follow up, e.g., "If you can share X, that would help the maintainers diagnose this."
-            - Don't be formulaic. Respond to what the issue actually needs.
-            - Surface solutions from past issues - often the fastest path to helping.
-            - Connecting regressions to specific changes is extremely valuable.
-            - Link issues with #number so they're clickable.

.github/workflows/claude-pr-review.yml

@@ -1,272 +0,0 @@
-name: Claude PR Review
-
-on:
-  pull_request:
-    types: [opened, ready_for_review]
-  # Manual trigger for backfilling existing PRs. Run from terminal:
-  #   gh workflow run claude-pr-review.yml -f pr_number=1234
-  # Or batch process open PRs:
-  #   gh pr list --state open --limit 10 --json number --jq '.[].number' | while read num; do
-  #     gh workflow run claude-pr-review.yml -f pr_number=$num
-  #     sleep 60
-  #   done
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: 'PR number to review'
-        required: true
-        type: string
-
-jobs:
-  claude-pr-review:
-    # Runs on PR opened/ready_for_review (skips drafts) or manual trigger for backfilling
-    if: |
-      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-      github.event_name == 'workflow_dispatch'
-
-    runs-on: ubuntu-latest
-    timeout-minutes: 120
-
-    # SECURITY: These permissions are intentionally restrictive.
-    # - contents: read  -> Claude can read the codebase but CANNOT write/push any code
-    # - pull-requests: write -> Claude can post reviews and inline suggestions
-    # - issues: read -> Claude can search for related issues
-    # NOTE: Even with pull-requests: write, Claude CANNOT merge PRs because branch protection
-    # requires 1 approval from a Code Owner. The GITHUB_TOKEN cannot bypass this.
-    permissions:
-      contents: read
-      pull-requests: write
-      issues: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Get PR number
-        id: pr
-        run: |
-          if [ "${{ github.event_name }}" == "workflow_dispatch" ]; then
-            echo "number=${{ inputs.pr_number }}" >> $GITHUB_OUTPUT
-          else
-            echo "number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Run PR Review
-        id: review
-        uses: anthropics/claude-code-action@v1
-        with:
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          allowed_non_write_users: "*"
-          claude_args: --model claude-opus-4-5-20251101 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,WebFetch,WebSearch"
-          prompt: |
-            You're a GitHub PR reviewer for the open source Cline repository. Your goal is to give the PR author helpful feedback and give maintainers the context they need to review efficiently.
-
-            PR: #${{ steps.pr.outputs.number }}
-
-            ## Gather context
-
-            ```bash
-            # Get full PR details
-            gh pr view ${{ steps.pr.outputs.number }} --json number,title,body,author,createdAt,updatedAt,isDraft,labels,commits,files,additions,deletions,changedFiles,baseRefName,headRefName,mergeable,reviewDecision
-
-            # Get the diff
-            gh pr diff ${{ steps.pr.outputs.number }}
-
-            # Check CI status
-            gh pr checks ${{ steps.pr.outputs.number }}
-
-            # Get existing review comments (to understand context and your previous feedback)
-            gh api repos/${{ github.repository }}/pulls/${{ steps.pr.outputs.number }}/comments --jq '.[] | {user: .user.login, body: .body, path: .path, created_at: .created_at}'
-
-            # Get conversation comments
-            gh pr view ${{ steps.pr.outputs.number }} --comments
-            ```
-
-            If this is a re-review (workflow_dispatch event):
-            Read your previous comments carefully. Understand what you asked for before.
-            Check if new commits or comments address your previous feedback.
-
-            ## Check contributing guidelines
-
-            Flag (but don't block) if:
-            - Missing changeset - For user-facing changes, check if there's a `.changeset/` file:
-              ```bash
-              gh pr diff ${{ steps.pr.outputs.number }} --name-only | grep '.changeset/' || echo "No changeset found"
-              ```
-              If missing, ask them to run `npm run changeset`
-            - Missing tests - New features should have tests
-
-            ## Find related issues and PRs
-
-            Search thoroughly for context that might help with the review:
-
-            ```bash
-            # Find related issues for context
-            gh issue list --search "<keywords from the PR>" --state all --limit 30
-            gh issue list --search "<error messages or feature names>" --state all --limit 20
-
-            # Find similar PRs for reference
-            gh pr list --search "<keywords>" --state all --limit 30
-            ```
-
-            For each relevant issue or PR you find, read it including comments:
-            ```bash
-            gh issue view <number> --comments
-            gh pr view <number> --comments
-            ```
-
-            Look for:
-            - Open issues this PR might fix that weren't linked in the description
-            - Similar PRs that went through review - what feedback did they get? What patterns did they follow?
-            - Context from maintainer discussions that could inform your review
-
-            ## Find subject matter experts
-
-            For files changed in this PR, find who knows the code best:
-            ```bash
-            # Get files changed
-            gh pr diff ${{ steps.pr.outputs.number }} --name-only
-
-            # For each relevant path, find contributors
-            git log --since="6 months ago" --format="%an" -- <path> | sort | uniq -c | sort -rn | head -5
-            ```
-
-            Cross-reference git authors with GitHub usernames. Include an SME table in your response:
-
-            | SME | Reason |
-            |-----|--------|
-            | @username1 | Authored PR #X which modified this area |
-            | @username2 | Primary contributor to affected file (15 commits in 6 months) |
-            | @username3 | Reviewed similar PR #Y with extensive feedback |
-
-            ## Deep code review
-
-            This is the most important part. Don't just look for syntax issues - understand what the PR is trying to achieve and whether the implementation is the right approach.
-
-            Step 1: Understand the intent
-            Read the PR description and understand what the author is trying to accomplish. What problem are they solving? What feature are they adding?
-
-            Step 2: Form your own opinion first
-            Before analyzing their code, think about how YOU would implement this feature or fix. What files would you touch? What patterns would you follow? What edge cases would you handle?
-
-            Step 3: Compare approaches
-            Now look at their implementation. How does it compare to what you would have done?
-            - Is their approach better in some ways? Note what they did well.
-            - Is their approach missing something? Be specific about what and why.
-            - Are there edge cases they haven't considered?
-            - Does it follow the patterns established in similar parts of the codebase?
-
-            Step 4: Look at the bigger picture
-            - What other files or systems does this change interact with?
-            - Could this break anything else?
-            - Is there additional work needed beyond this PR to complete the feature?
-            - Does this fit well with the overall architecture?
-
-            Step 5: Find reference implementations
-            Look for similar changes in the codebase:
-            ```bash
-            git log --oneline --all --grep="<relevant keywords>" | head -20
-            git log --oneline -- <similar files> | head -20
-            ```
-
-            If this is adding a new API provider, look at how other providers are implemented.
-            If this is adding a new feature, look at how similar features were added.
-            Note where their implementation aligns with or diverges from established patterns.
-
-            Step 6: Standard code review checks
-            - DRY: Is there duplicated code that could be extracted?
-            - Error handling: Are errors handled appropriately?
-            - Security: Any injection risks, credential exposure, unsafe dependencies?
-            - Performance: Any obvious inefficiencies, memory leaks, N+1 patterns?
-            - Types: Is TypeScript used correctly? Any unsafe type assertions?
-            - Naming: Are variables and functions named clearly?
-            - Comments: Is complex logic explained? Are there outdated comments?
-
-            ## Inline code suggestions
-
-            For specific code improvements, use GitHub's suggestion syntax via `gh api`.
-            This creates suggestions the author can commit with one click.
-
-            Single-line suggestion:
-            ```bash
-            gh api repos/${{ github.repository }}/pulls/${{ steps.pr.outputs.number }}/reviews \
-              -X POST \
-              -f commit_id="$(gh pr view ${{ steps.pr.outputs.number }} --json headRefOid -q .headRefOid)" \
-              -f event="COMMENT" \
-              -f body="" \
-              -F comments='[
-                {
-                  "path": "src/example.ts",
-                  "line": 42,
-                  "body": "Consider simplifying:\n\n```suggestion\nconst result = items.filter(Boolean);\n```"
-                }
-              ]'
-            ```
-
-            Multi-line suggestion (replacing lines 40-45):
-            ```bash
-            gh api repos/${{ github.repository }}/pulls/${{ steps.pr.outputs.number }}/reviews \
-              -X POST \
-              -f commit_id="$(gh pr view ${{ steps.pr.outputs.number }} --json headRefOid -q .headRefOid)" \
-              -f event="COMMENT" \
-              -f body="" \
-              -F comments='[
-                {
-                  "path": "src/example.ts",
-                  "start_line": 40,
-                  "line": 45,
-                  "body": "This can be simplified:\n\n```suggestion\nconst simplified = doThing();\n```"
-                }
-              ]'
-            ```
-
-            Use inline suggestions for concrete improvements. Use regular comments for questions or broader feedback.
-
-            ## Post your review
-
-            After your investigation, post a single helpful comment that helps the author and gives maintainers context.
-
-            Start with a warm thank you for their contribution. Be conversational, not robotic.
-
-            Include what's relevant:
-            - In-depth explanation of what the PR does - Be comprehensive. A maintainer should be able to read this section and fully understand the author's intent, why they made the changes, how they implemented it, and what files/systems are affected. Don't just summarize - explain.
-            - Related issues/PRs you found that provide useful context (link to them)
-            - Your review findings (issues to address, suggestions, etc.)
-            - Clear next steps for the author
-
-            Include a "For Maintainers" section with:
-            - Anything else useful to help the maintainer resolve this PR
-            - Related issues/PRs with context on why they're relevant
-            - Open issues this PR might fix that weren't linked in the description
-            - Your recommendation: merge as-is, needs changes, needs discussion, close, etc.
-            - SME table - who should review this and why
-
-            For the SME table:
-            | SME | Reason |
-            |-----|--------|
-            | @username | Primary contributor to affected files |
-
-            ## Update labels
-
-            Add appropriate labels based on your analysis:
-            ```bash
-            gh label list --json name,description --limit 100
-            gh pr edit ${{ steps.pr.outputs.number }} --add-label "label1,label2"
-            ```
-
-            When done, add the reviewed label:
-            ```bash
-            gh pr edit ${{ steps.pr.outputs.number }} --add-label "Bot Reviewed"
-            ```
-
-            ## Remember
-
-            - This is a one-time automated response - you will NOT see their reply or respond again. Never say things like "let me know if you have questions", "I can help you with", or "feel free to ask" - you won't be there to follow up. Frame any questions for the maintainers who will follow up.
-            - Be helpful and welcoming - Many contributors are new to the project
-            - Be specific - Point to exact lines and suggest fixes, don't give vague feedback
-            - Think deeply - Don't just surface-level review, understand the intent and evaluate the approach
-            - Use inline suggestions - Make it easy for authors to accept changes
-            - You're a first-pass reviewer - A human maintainer will do final approval

.github/workflows/cli-tui-tests.yml

@@ -0,0 +1,83 @@
+name: CLI TUI Tests
+
+on:
+  pull_request:
+    branches:
+      - main
+  workflow_dispatch:
+  workflow_call:
+
+permissions:
+  contents: read
+
+jobs:
+  cli-tui-tests:
+    name: CLI TUI Tests
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Install dependencies
+        run: npm ci
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build CLI
+        run: npm run cli:build
+
+      - name: Run TUI Tests
+        id: tui_tests
+        run: |
+          npm run test:e2e:cli:tui 2>&1 | tee tui-test-output.log
+          exit_code=${PIPESTATUS[0]}
+          echo "tui_exit_code=$exit_code" >> $GITHUB_OUTPUT
+          exit $exit_code
+
+      - name: Write failure summary
+        if: always() && steps.tui_tests.outcome != 'success' && steps.tui_tests.outcome != 'skipped'
+        run: |
+          echo "## ❌ CLI TUI Tests Failed" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "**Step outcome:** \`${{ steps.tui_tests.outcome }}\`" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "### Test Output" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo '```' >> $GITHUB_STEP_SUMMARY
+          if [ -f tui-test-output.log ]; then
+            cat tui-test-output.log >> $GITHUB_STEP_SUMMARY
+          else
+            echo "(no test output captured — process may have been killed before output was flushed)" >> $GITHUB_STEP_SUMMARY
+          fi
+          echo '```' >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "### Debugging" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "- **TUI traces** are attached as artifacts below — download and inspect them to see terminal state at the point of failure." >> $GITHUB_STEP_SUMMARY
+          echo "- **To view a trace replay/Run a TUI Trace: ** run \`npx tui-test show-trace path/to/trace/file\` in your terminal" >> $GITHUB_STEP_SUMMARY
+          echo "- **Full test log** is also attached as an artifact." >> $GITHUB_STEP_SUMMARY
+          echo "- Tests run with \`retries: 2\` so any failure shown is a consistent failure, not a flake." >> $GITHUB_STEP_SUMMARY
+
+      - name: Upload TUI traces
+        if: always() && steps.tui_tests.outcome != 'success' && steps.tui_tests.outcome != 'skipped'
+        uses: actions/upload-artifact@v4
+        with:
+          name: tui-test-traces
+          path: tests/e2e/cli/tui-traces/
+          retention-days: 14
+          if-no-files-found: warn
+
+      - name: Upload test log
+        if: always() && steps.tui_tests.outcome != 'success' && steps.tui_tests.outcome != 'skipped'
+        uses: actions/upload-artifact@v4
+        with:
+          name: tui-test-log
+          path: tui-test-output.log
+          retention-days: 14
+          if-no-files-found: warn

.github/workflows/cline-evals-regression.yml

@@ -0,0 +1,85 @@
+name: Smoke Tests
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'src/core/**'
+      - 'src/shared/**'
+      - 'proto/**'
+      - 'evals/**'
+      - '.github/workflows/cline-evals-regression.yml'
+  pull_request:
+    paths:
+      - 'src/core/**'
+      - 'src/shared/**'
+      - 'proto/**'
+      - 'evals/**'
+      - '.github/workflows/cline-evals-regression.yml'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: smoke-tests-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  smoke-tests:
+    name: Smoke Tests
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build and install CLI
+        run: |
+          npm run protos
+          cd cli && npm install && npm run build && npm link
+          echo "$(npm config get prefix)/bin" >> $GITHUB_PATH
+
+      - name: Verify CLI
+        run: cline --version
+
+      - name: Run smoke tests
+        env:
+          CLINE_API_KEY: ${{ secrets.CLINE_API_KEY }}
+        run: |
+          cline auth -p cline -k "$CLINE_API_KEY" -m "anthropic/claude-sonnet-4.5"
+          max_attempts=3
+          for attempt in $(seq 1 $max_attempts); do
+            echo "::group::Attempt $attempt of $max_attempts"
+            if npx tsx evals/smoke-tests/run-smoke-tests.ts --trials 1 --parallel; then
+              echo "::endgroup::"
+              echo "Smoke tests passed on attempt $attempt"
+              exit 0
+            fi
+            echo "::endgroup::"
+            if [ $attempt -lt $max_attempts ]; then
+              echo "::warning::Smoke tests failed on attempt $attempt, retrying..."
+              sleep 10
+            fi
+          done
+          echo "::error::Smoke tests failed after $max_attempts attempts"
+          exit 1
+
+      - name: Generate summary
+        if: always()
+        run: cat evals/smoke-tests/results/latest/summary.md >> $GITHUB_STEP_SUMMARY
+
+      - name: Upload results
+        uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: smoke-test-results-${{ github.run_id }}
+          path: evals/smoke-tests/results/latest/
+          retention-days: 30

.github/workflows/cline-pr-review.yml

@@ -1,312 +0,0 @@
-name: Cline PR Code Review
-
-on:
-  pull_request:
-    types:
-      [opened, ready_for_review]
-      # Manual trigger for backfilling existing PRs. Run from terminal:
-      #   gh workflow run cline-pr-review.yml -f pr_number=1234
-      # Or batch process open PRs:
-      #   gh pr list --state open --limit 10 --json number --jq '.[].number' | while read num; do
-      #     gh workflow run cline-pr-review.yml -f pr_number=$num
-      #     sleep 60
-      #   done
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: "PR number to review"
-        required: true
-        type: string
-
-concurrency:
-  group: pr-review-${{ github.event.pull_request.number || inputs.pr_number }}
-  cancel-in-progress: true
-
-jobs:
-  cline-pr-review:
-    # Runs on PR opened/ready_for_review (skips drafts) or manual trigger for backfilling
-    if: |
-      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-      github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-
-    # SECURITY: These permissions are intentionally restrictive.
-    # - contents: read  -> cline can read the codebase but CANNOT write/push any code
-    # - pull-requests: write -> cline can post reviews and inline suggestions
-    # - issues: read -> cline can search for related issues
-    # NOTE: Even with pull-requests: write, cline CANNOT merge PRs because branch protection
-    # requires 1 approval from a Code Owner. The GITHUB_TOKEN cannot bypass this.
-    permissions:
-      contents: read
-      pull-requests: write
-      issues: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: "npm"
-
-      - name: Install and Verify Cline CLI
-        run: |
-          npx cline version # verify installation
-
-      - name: Configure Cline with Anthropic
-        run: |
-          npx cline auth --provider anthropic \
-            --apikey "${{ secrets.ANTHROPIC_API_KEY }}" \
-            --modelid claude-opus-4-5-20251101
-
-      - name: Get PR number
-        id: pr
-        run: |
-          if [ "${{ github.event_name }}" == "workflow_dispatch" ]; then
-            echo "number=${{ inputs.pr_number }}" >> $GITHUB_OUTPUT
-          else
-            echo "number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Review PR with Cline
-        env:
-          PR_NUMBER: ${{ steps.pr.outputs.number }}
-          GITHUB_REPO: ${{ github.repository }}
-          GH_TOKEN: ${{ github.token }}
-          CLINE_COMMAND_PERMISSIONS: |
-            {
-              "allow": [
-                "gh pr diff *",
-                "gh pr view *",
-                "gh pr checks *",
-                "gh pr list *",
-                "gh label list *",
-                "gh issue list *",
-                "gh issue view *",
-                "git log *",
-                "gh pr comment ${{ steps.pr.outputs.number }} *",
-                "gh pr edit ${{ steps.pr.outputs.number }} *",
-                "gh api repos/${{ github.repository }}/pulls/${{ steps.pr.outputs.number }}/comments *",
-                "gh api repos/${{ github.repository }}/pulls/${{ steps.pr.outputs.number }}/reviews *"
-              ]
-            }
-        run: |
-          npx cline --yolo 'You'\''re a GitHub PR reviewer for the open source Cline repository. Your goal is to give the PR author helpful feedback and give maintainers the context they need to review efficiently.
-
-          PR: #'"${PR_NUMBER}"'
-
-          ## Gather context
-
-          ```bash
-          # Get full PR details
-          gh pr view '"${PR_NUMBER}"' --json number,title,body,author,createdAt,updatedAt,isDraft,labels,commits,files,additions,deletions,changedFiles,baseRefName,headRefName,mergeable,reviewDecision
-
-          # Get the diff
-          gh pr diff '"${PR_NUMBER}"'
-
-          # Check CI status
-          gh pr checks '"${PR_NUMBER}"'
-
-          # Get existing review comments (to understand context and your previous feedback)
-          gh api repos/'"${GITHUB_REPO}"'/pulls/'"${PR_NUMBER}"'/comments --jq '\''.[] | {user: .user.login, body: .body, path: .path, created_at: .created_at}'\''
-
-          # Get conversation comments
-          gh pr view '"${PR_NUMBER}"' --comments
-          ```
-
-          If this is a re-review (workflow_dispatch event):
-          Read your previous comments carefully. Understand what you asked for before.
-          Check if new commits or comments address your previous feedback.
-
-          ## Check contributing guidelines
-
-          Flag (but don'\''t block) if:
-          - Missing changeset - For user-facing changes, check if there'\''s a `.changeset/` file:
-            ```bash
-            gh pr diff '"${PR_NUMBER}"' --name-only | grep '\''.changeset/'\'' || echo '\''No changeset found'\''
-            ```
-            If missing, ask them to run `npm run changeset`
-          - Missing tests - New features should have tests
-
-          ## Find related issues and PRs
-
-          Search thoroughly for context that might help with the review:
-
-          ```bash
-          # Find related issues for context
-          gh issue list --search '\''<keywords from the PR>'\'' --state all --limit 30
-          gh issue list --search '\''<error messages or feature names>'\'' --state all --limit 20
-
-          # Find similar PRs for reference
-          gh pr list --search '\''<keywords>'\'' --state all --limit 30
-          ```
-
-          For each relevant issue or PR you find, read it including comments:
-          ```bash
-          gh issue view <number> --comments
-          gh pr view <number> --comments
-          ```
-
-          Look for:
-          - Open issues this PR might fix that weren'\''t linked in the description
-          - Similar PRs that went through review - what feedback did they get? What patterns did they follow?
-          - Context from maintainer discussions that could inform your review
-
-          ## Find subject matter experts
-
-          For files changed in this PR, find who knows the code best:
-          ```bash
-          # Get files changed
-          gh pr diff '"${PR_NUMBER}"' --name-only
-
-          # For each relevant path, find contributors
-          git log --since='\''6 months ago'\'' --format='\''%an'\'' -- <path> | sort | uniq -c | sort -rn | head -5
-          ```
-
-          Cross-reference git authors with GitHub usernames. Include an SME table in your response:
-
-          | SME | Reason |
-          |-----|--------|
-          | @username1 | Authored PR #X which modified this area |
-          | @username2 | Primary contributor to affected file (15 commits in 6 months) |
-          | @username3 | Reviewed similar PR #Y with extensive feedback |
-
-          ## Bash command usage
-
-          Don'\''t use operators like `|`, `&&`, or `;` - run each command separately and analyze the output.
-
-          When referencing command outputs, quote them properly to avoid formatting issues.
-
-          ## Deep code review
-
-          This is the most important part. Don'\''t just look for syntax issues - understand what the PR is trying to achieve and whether the implementation is the right approach.
-
-          Step 1: Understand the intent
-          Read the PR description and understand what the author is trying to accomplish. What problem are they solving? What feature are they adding?
-
-          Step 2: Form your own opinion first
-          Before analyzing their code, think about how YOU would implement this feature or fix. What files would you touch? What patterns would you follow? What edge cases would you handle?
-
-          Step 3: Compare approaches
-          Now look at their implementation. How does it compare to what you would have done?
-          - Is their approach better in some ways? Note what they did well.
-          - Is their approach missing something? Be specific about what and why.
-          - Are there edge cases they haven'\''t considered?
-          - Does it follow the patterns established in similar parts of the codebase?
-
-          Step 4: Look at the bigger picture
-          - What other files or systems does this change interact with?
-          - Could this break anything else?
-          - Is there additional work needed beyond this PR to complete the feature?
-          - Does this fit well with the overall architecture?
-
-          Step 5: Find reference implementations
-          Look for similar changes in the codebase:
-          ```bash
-          git log --oneline --all --grep='\''<relevant keywords>'\'' | head -20
-          git log --oneline -- <similar files> | head -20
-          ```
-
-          If this is adding a new API provider, look at how other providers are implemented.
-          If this is adding a new feature, look at how similar features were added.
-          Note where their implementation aligns with or diverges from established patterns.
-
-          Step 6: Standard code review checks
-          - DRY: Is there duplicated code that could be extracted?
-          - Error handling: Are errors handled appropriately?
-          - Security: Any injection risks, credential exposure, unsafe dependencies?
-          - Performance: Any obvious inefficiencies, memory leaks, N+1 patterns?
-          - Types: Is TypeScript used correctly? Any unsafe type assertions?
-          - Naming: Are variables and functions named clearly?
-          - Comments: Is complex logic explained? Are there outdated comments?
-
-          ## Inline code suggestions
-
-          For specific code improvements, use GitHub'\''s suggestion syntax via `gh api`.
-          This creates suggestions the author can commit with one click.
-
-          Single-line suggestion:
-          ```bash
-          gh api repos/'"${GITHUB_REPO}"'/pulls/'"${PR_NUMBER}"'/reviews \
-            -X POST \
-            -f commit_id="$(gh pr view '"${PR_NUMBER}"' --json headRefOid -q .headRefOid)" \
-            -f event='\''COMMENT'\'' \
-            -f body='\'''\'' \
-            -F comments='\''[
-              {
-                "path": "src/example.ts",
-                "line": 42,
-                "body": "Consider simplifying:\n\n```suggestion\nconst result = items.filter(Boolean);\n```"
-              }
-            ]'\''
-          ```
-
-          Multi-line suggestion (replacing lines 40-45):
-          ```bash
-          gh api repos/'"${GITHUB_REPO}"'/pulls/'"${PR_NUMBER}"'/reviews \
-            -X POST \
-            -f commit_id="$(gh pr view '"${PR_NUMBER}"' --json headRefOid -q .headRefOid)" \
-            -f event='\''COMMENT'\'' \
-            -f body='\'''\'' \
-            -F comments='\''[
-              {
-                "path": "src/example.ts",
-                "start_line": 40,
-                "line": 45,
-                "body": "This can be simplified:\n\n```suggestion\nconst simplified = doThing();\n```"
-              }
-            ]'\''
-          ```
-
-          Use inline suggestions for concrete improvements. Use regular comments for questions or broader feedback.
-
-          ## Post your review
-
-          After your investigation, post a single helpful comment that helps the author and gives maintainers context.
-
-          Start with a warm thank you for their contribution. Be conversational, not robotic.
-
-          Include what'\''s relevant:
-          - In-depth explanation of what the PR does - Be comprehensive. A maintainer should be able to read this section and fully understand the author'\''s intent, why they made the changes, how they implemented it, and what files/systems are affected. Don'\''t just summarize - explain.
-          - Related issues/PRs you found that provide useful context (link to them)
-          - Your review findings (issues to address, suggestions, etc.)
-          - Clear next steps for the author
-
-          Include a '\''For Maintainers'\'' section with:
-          - Anything else useful to help the maintainer resolve this PR
-          - Related issues/PRs with context on why they'\''re relevant
-          - Open issues this PR might fix that weren'\''t linked in the description
-          - Your recommendation: merge as-is, needs changes, needs discussion, close, etc.
-          - SME table - who should review this and why
-
-          For the SME table:
-          | SME | Reason |
-          |-----|--------|
-          | @username | Primary contributor to affected files |
-
-          ## Update labels
-
-          Add appropriate labels based on your analysis:
-          ```bash
-          gh label list --json name,description --limit 100
-          gh pr edit '"${PR_NUMBER}"' --add-label '\''label1,label2'\''
-          ```
-
-          When done, add the reviewed label:
-          ```bash
-          gh pr edit '"${PR_NUMBER}"' --add-label '\''Bot Reviewed'\''
-          ```
-
-          ## Remember
-
-          - This is a one-time automated response - you will NOT see their reply or respond again. Never say things like '\''let me know if you have questions'\'', '\''I can help you with'\'', or '\''feel free to ask'\'' - you won'\''t be there to follow up. Frame any questions for the maintainers who will follow up.
-          - Be helpful and welcoming - Many contributors are new to the project
-          - Be specific - Point to exact lines and suggest fixes, don'\''t give vague feedback
-          - Think deeply - Don'\''t just surface-level review, understand the intent and evaluate the approach
-          - Use inline suggestions - Make it easy for authors to accept changes
-          - You'\''re a first-pass reviewer - A human maintainer will do final approval'

.github/workflows/e2e.yml

@@ -80,13 +80,16 @@ jobs:
                       playwright-browsers-${{ runner.os }}-
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm ci
+              env:
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci
 
+            - name: Install vsce
+              run: npm install -g @vscode/vsce
+
             - name: Install xvfb on Linux
               if: matrix.runner == 'ubuntu'
               run: sudo apt-get update && sudo apt-get install -y xvfb

.github/workflows/npm-main.yaml

@@ -1,7 +1,7 @@
 name: Publish NPM Release
 
 on:
-  workflow_dispatch:
+  workflow_call:
     inputs:
       confirm_publish:
         description: 'Type "publish" to confirm you want to publish to NPM'
@@ -9,9 +9,10 @@ on:
         type: string
 
 permissions:
-  contents: read
-  checks: write  # Required by test workflow
-  pull-requests: write  # Required by test workflow
+  contents: write # Required for pushing tags
+  id-token: write # Required for npm trusted publishing (OIDC)
+  checks: write # Required by test workflow
+  pull-requests: write # Required by test workflow
 
 jobs:
   test:
@@ -20,7 +21,7 @@ jobs:
   publish-npm-release:
     needs: test
     name: Publish Cline CLI to NPM
-    if: github.repository == 'cline/cline' && github.ref == 'refs/heads/main' && github.event.inputs.confirm_publish == 'publish'
+    if: github.repository == 'cline/cline' && github.ref == 'refs/heads/main' && inputs.confirm_publish == 'publish'
     runs-on: ubuntu-latest
 
     steps:
@@ -30,62 +31,23 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20.x'
-          registry-url: 'https://registry.npmjs.org'
+          node-version: "24.x"
+          registry-url: "https://registry.npmjs.org"
 
-      - name: Setup Go
-        uses: actions/setup-go@v5
-        with:
-          go-version: '1.24'
-          cache-dependency-path: cli/go.sum
+      - name: Install root dependencies and CLI dependencies
+        run: npm ci --include=optional # this will also install cli deps because "cli" in included in root package.json workspaces field
 
-      # Cache root dependencies - only reuse if package-lock.json exactly matches
-      - name: Cache root dependencies
-        uses: actions/cache@v4
-        id: root-cache
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-      # Cache webview-ui dependencies - only reuse if package-lock.json exactly matches
-      - name: Cache webview-ui dependencies
-        uses: actions/cache@v4
-        id: webview-cache
-        with:
-          path: webview-ui/node_modules
-          key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
-
-      - name: Install root dependencies
-        if: steps.root-cache.outputs.cache-hit != 'true'
-        run: npm ci --include=optional
-
-      - name: Install webview-ui dependencies
-        if: steps.webview-cache.outputs.cache-hit != 'true'
-        run: cd webview-ui && npm ci --include=optional
+      - name: Generate Protos
+        run: npm run protos
 
       - name: Read release version
         id: version
         run: |
-          # Read version from cli/package.json (stable version)
+          # Read version from cli/package.json
           VERSION=$(node -p "require('./cli/package.json').version")
           echo "Release version: $VERSION"
           echo "version=$VERSION" >> $GITHUB_OUTPUT
 
-      - name: Download ripgrep binaries
-        run: npm run download-ripgrep
-
-      - name: Clean previous builds
-        run: rm -rf dist-standalone
-
-      - name: Generate Protos (First Pass)
-        run: npm run protos && npm run protos-go
-
-      - name: Compile CLI
-        run: npm run compile-cli
-
-      - name: Compile CLI for all platforms
-        run: npm run compile-cli-all-platforms
-
       - name: Build standalone NPM package
         env:
           TELEMETRY_SERVICE_API_KEY: ${{ secrets.TELEMETRY_SERVICE_API_KEY }}
@@ -97,31 +59,32 @@ jobs:
           OTEL_EXPORTER_OTLP_PROTOCOL: ${{ secrets.OTEL_EXPORTER_OTLP_PROTOCOL }}
           OTEL_EXPORTER_OTLP_ENDPOINT: ${{ secrets.OTEL_EXPORTER_OTLP_ENDPOINT }}
           OTEL_EXPORTER_OTLP_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_HEADERS }}
-          POSTHOG_TELEMETRY_ENABLED: "true"
-        run: npm run compile-standalone-npm
-
-      - name: Generate Protos (Second Pass - Bug Workaround)
-        run: npm run protos && npm run protos-go
+        run: node scripts/package-npm.mjs
 
       - name: Verify build output
         run: |
           echo "Checking dist-standalone directory..."
           ls -la dist-standalone/
-          
+
           echo "Verifying CLI binaries..."
           ls -lh cli/bin/cline-* || echo "Warning: CLI binaries not found"
-          
+
           echo "Checking package.json in dist-standalone..."
           cat dist-standalone/package.json | grep version
 
       - name: Publish to NPM with latest tag
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_RELEASE_TOKEN }}
         run: |
           echo "Publishing version ${{ steps.version.outputs.version }} to NPM with tag 'latest'..."
           cd dist-standalone
           npm publish --tag latest --access public
 
+      - name: Tag release
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git tag "v${{ steps.version.outputs.version }}-cli"
+          git push origin "v${{ steps.version.outputs.version }}-cli"
+
       - name: Summary
         run: |
           echo "✅ Successfully published cline@${{ steps.version.outputs.version }} to NPM with tag 'latest'"

.github/workflows/npm-nightly.yaml

@@ -1,14 +1,19 @@
 name: Publish NPM Nightly
 
 on:
-  schedule:
-    - cron: '0 12 * * *'  # 4 AM PST (UTC-8) = 12 UTC
-  workflow_dispatch:
+  workflow_call:
+    inputs:
+      force_publish:
+        description: "Force publish even if there are no commits in the last 24 hours"
+        required: false
+        type: boolean
+        default: false
 
 permissions:
   contents: read
-  checks: write  # Required by test workflow
-  pull-requests: write  # Required by test workflow
+  id-token: write # Required for npm trusted publishing (OIDC)
+  checks: write # Required by test workflow
+  pull-requests: write # Required by test workflow
 
 jobs:
   test:
@@ -27,6 +32,12 @@ jobs:
       - name: Check for recent commits
         id: check_commits
         run: |
+          if [ "${{ inputs.force_publish }}" = "true" ]; then
+            echo "force_publish enabled, proceeding with publish"
+            echo "skip=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
           if [ $(git rev-list --count HEAD --since="24 hours ago") -eq 0 ]; then
             echo "No commits in last 24 hours, skipping publish"
             echo "skip=true" >> $GITHUB_OUTPUT
@@ -39,55 +50,30 @@ jobs:
         if: steps.check_commits.outputs.skip != 'true'
         uses: actions/setup-node@v4
         with:
-          node-version: '20.x'
-          registry-url: 'https://registry.npmjs.org'
+          node-version: "24.x"
+          registry-url: "https://registry.npmjs.org"
 
-      - name: Setup Go
+      - name: Install root dependencies and CLI dependencies
         if: steps.check_commits.outputs.skip != 'true'
-        uses: actions/setup-go@v5
-        with:
-          go-version: '1.24'
-          cache-dependency-path: cli/go.sum
+        run: npm ci --include=optional # this will also install cli deps because "cli" in included in root package.json workspaces field
 
-      # Cache root dependencies - only reuse if package-lock.json exactly matches
-      - name: Cache root dependencies
+      - name: Generate Protos
         if: steps.check_commits.outputs.skip != 'true'
-        uses: actions/cache@v4
-        id: root-cache
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-      # Cache webview-ui dependencies - only reuse if package-lock.json exactly matches
-      - name: Cache webview-ui dependencies
-        if: steps.check_commits.outputs.skip != 'true'
-        uses: actions/cache@v4
-        id: webview-cache
-        with:
-          path: webview-ui/node_modules
-          key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
-
-      - name: Install root dependencies
-        if: steps.check_commits.outputs.skip != 'true' && steps.root-cache.outputs.cache-hit != 'true'
-        run: npm ci --include=optional
-
-      - name: Install webview-ui dependencies
-        if: steps.check_commits.outputs.skip != 'true' && steps.webview-cache.outputs.cache-hit != 'true'
-        run: cd webview-ui && npm ci --include=optional
+        run: npm run protos
 
       - name: Generate nightly version with timestamp
         if: steps.check_commits.outputs.skip != 'true'
         id: version
         run: |
-          # Read base version from cli/package.json (e.g., "1.0.9")
+          # Read base version from cli/package.json (e.g., "2.0.0")
           BASE_VERSION=$(node -p "require('./cli/package.json').version")
-          
+
           # Generate timestamp (Unix epoch seconds)
           TIMESTAMP=$(date +%s)
-          
+
           # Create unique nightly version: 1.0.9-nightly.1736365200
           VERSION="${BASE_VERSION}-nightly.${TIMESTAMP}"
-          
+
           echo "Base version: $BASE_VERSION"
           echo "Generated nightly version: $VERSION"
           echo "version=$VERSION" >> $GITHUB_OUTPUT
@@ -102,31 +88,11 @@ jobs:
             pkg.version = '${{ steps.version.outputs.version }}';
             fs.writeFileSync('cli/package.json', JSON.stringify(pkg, null, '\t'));
           "
-          
+
           echo "Using version ${{ steps.version.outputs.version }} for build"
           cat cli/package.json | grep '"version"'
 
-      - name: Download ripgrep binaries
-        if: steps.check_commits.outputs.skip != 'true'
-        run: npm run download-ripgrep
-
-      - name: Clean previous builds
-        if: steps.check_commits.outputs.skip != 'true'
-        run: rm -rf dist-standalone
-
-      - name: Generate Protos (First Pass)
-        if: steps.check_commits.outputs.skip != 'true'
-        run: npm run protos && npm run protos-go
-
-      - name: Compile CLI
-        if: steps.check_commits.outputs.skip != 'true'
-        run: npm run compile-cli
-
-      - name: Compile CLI for all platforms
-        if: steps.check_commits.outputs.skip != 'true'
-        run: npm run compile-cli-all-platforms
-
-      - name: Build standalone NPM package
+      - name: Build and package CLI
         if: steps.check_commits.outputs.skip != 'true'
         env:
           TELEMETRY_SERVICE_API_KEY: ${{ secrets.TELEMETRY_SERVICE_API_KEY }}
@@ -138,29 +104,22 @@ jobs:
           OTEL_EXPORTER_OTLP_PROTOCOL: ${{ secrets.OTEL_EXPORTER_OTLP_PROTOCOL }}
           OTEL_EXPORTER_OTLP_ENDPOINT: ${{ secrets.OTEL_EXPORTER_OTLP_ENDPOINT }}
           OTEL_EXPORTER_OTLP_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_HEADERS }}
-          POSTHOG_TELEMETRY_ENABLED: "true"
-        run: npm run compile-standalone-npm
-
-      - name: Generate Protos (Second Pass - Bug Workaround)
-        if: steps.check_commits.outputs.skip != 'true'
-        run: npm run protos && npm run protos-go
+        run: node scripts/package-npm.mjs
 
       - name: Verify build output
         if: steps.check_commits.outputs.skip != 'true'
         run: |
           echo "Checking dist-standalone directory..."
           ls -la dist-standalone/
-          
+
           echo "Verifying CLI binaries..."
           ls -lh cli/bin/cline-* || echo "Warning: CLI binaries not found"
-          
+
           echo "Checking package.json in dist-standalone..."
           cat dist-standalone/package.json | grep version
 
       - name: Publish to NPM with nightly tag
         if: steps.check_commits.outputs.skip != 'true'
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_RELEASE_TOKEN }}
         run: |
           echo "Publishing version ${{ steps.version.outputs.version }} to NPM with tag 'nightly'..."
           cd dist-standalone

.github/workflows/pack-cli.yml

@@ -0,0 +1,215 @@
+# Build and Pack CLI
+#
+# Builds a CLI tarball from any branch/commit and publishes it as a GitHub Release.
+# Requires write access to the repository (maintainers/collaborators only).
+#
+# Security: Split into two jobs to isolate untrusted build code from write tokens.
+# The build job runs arbitrary ref code with zero permissions. The release job
+# only runs trusted GitHub Actions with write scope.
+#
+# Usage (helper script, auto-detects current branch):
+#   ./scripts/build-cli-artifact.sh
+#   ./scripts/build-cli-artifact.sh feature/my-changes
+#   ./scripts/build-cli-artifact.sh feature/my-changes 1234  # comments on PR
+#
+# Usage (gh CLI directly):
+#   gh workflow run pack-cli.yml -f ref=main
+#   gh workflow run pack-cli.yml -f ref=abc123 -f pr_number=1234
+#
+# Install the built CLI (no auth required):
+#   npm install -g https://github.com/cline/cline/releases/download/cli-build-<sha>/cline-<ver>.tgz
+#
+# Find releases:
+#   gh release list --limit 10
+
+name: Build and Pack CLI
+
+permissions:
+  contents: read
+
+on:
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: 'Branch, tag, or commit SHA to build (leave empty for default branch)'
+        required: false
+        type: string
+      pr_number:
+        description: 'PR number to comment on with install instructions (optional)'
+        required: false
+        type: number
+
+jobs:
+  # ── Build job: runs untrusted ref code with ZERO permissions ──
+  build:
+    name: Build CLI
+    runs-on: ubuntu-latest
+    permissions: {}
+    outputs:
+      commit_sha: ${{ steps.commit.outputs.sha }}
+      tarball: ${{ steps.pack.outputs.tarball }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.ref || github.ref }}
+          persist-credentials: false
+
+      - name: Get commit SHA
+        id: commit
+        run: |
+          COMMIT_SHA=$(git rev-parse --short HEAD)
+          echo "sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
+          echo "Building from commit: $COMMIT_SHA"
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20.x"
+
+      - name: Install dependencies
+        run: npm ci --include=optional
+
+      - name: Generate Protos
+        run: npm run protos
+
+      - name: Build standalone package
+        run: node scripts/package-npm.mjs
+
+      - name: Create Tarball
+        id: pack
+        run: |
+          cd dist-standalone
+          TARBALL=$(npm pack)
+          echo "tarball=$TARBALL" >> $GITHUB_OUTPUT
+          echo "Created tarball: $TARBALL"
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: cli-tarball
+          path: dist-standalone/*.tgz
+
+  # ── Release job: only trusted Actions code, with write permissions ──
+  release:
+    name: Release CLI
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+    steps:
+      - name: Download artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: cli-tarball
+          path: dist-standalone
+
+      - name: Create GitHub Release
+        id: create_release
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const fs = require('fs');
+            const path = require('path');
+            const commit = '${{ needs.build.outputs.commit_sha }}';
+            const tarball = '${{ needs.build.outputs.tarball }}';
+
+            // Delete existing release/tag if re-running for the same commit
+            const tagName = `cli-build-${commit}`;
+            try {
+              const existing = await github.rest.repos.getReleaseByTag({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                tag: tagName
+              });
+              await github.rest.repos.deleteRelease({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                release_id: existing.data.id
+              });
+              await github.rest.git.deleteRef({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                ref: `tags/${tagName}`
+              });
+              core.info(`Deleted existing release for ${tagName}`);
+            } catch (e) {
+              // Release doesn't exist yet, that's fine
+            }
+
+            // Create a release
+            const release = await github.rest.repos.createRelease({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              tag_name: tagName,
+              name: `CLI Build (${commit})`,
+              body: `Automated CLI build from commit ${commit}\n\nInstall with:\n\`\`\`bash\nnpm install -g https://github.com/${context.repo.owner}/${context.repo.repo}/releases/download/${tagName}/${tarball}\n\`\`\``,
+              draft: false,
+              prerelease: true
+            });
+
+            // Upload the tarball as a release asset
+            const tarballPath = path.join('dist-standalone', tarball);
+            const tarballData = fs.readFileSync(tarballPath);
+
+            await github.rest.repos.uploadReleaseAsset({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              release_id: release.data.id,
+              name: tarball,
+              data: tarballData
+            });
+
+            const downloadUrl = `https://github.com/${context.repo.owner}/${context.repo.repo}/releases/download/${tagName}/${tarball}`;
+            core.setOutput('release_url', release.data.html_url);
+            core.setOutput('download_url', downloadUrl);
+
+      - name: Comment on PR with download instructions
+        if: inputs.pr_number != ''
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const commit = '${{ needs.build.outputs.commit_sha }}';
+            const releaseUrl = '${{ steps.create_release.outputs.release_url }}';
+            const downloadUrl = '${{ steps.create_release.outputs.download_url }}';
+            const prNumber = ${{ inputs.pr_number || 0 }};
+            if (!prNumber) return;
+
+            const comment = `## 📦 CLI Build Ready
+
+            A CLI build has been created for commit \`${commit}\`.
+
+            ### Install Directly from URL (No Authentication Required!)
+
+            \`\`\`bash
+            npm install -g ${downloadUrl}
+            \`\`\`
+
+            ### Alternative: Download and Install
+
+            \`\`\`bash
+            curl -L ${downloadUrl} -o cline.tgz
+            npm install -g ./cline.tgz
+            \`\`\`
+
+            📦 [View Release](${releaseUrl})
+            `;
+
+            await github.rest.issues.createComment({
+              issue_number: prNumber,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: comment
+            });
+
+      - name: Summary
+        run: |
+          echo "✅ CLI build complete!"
+          echo ""
+          echo "📦 Release: ${{ steps.create_release.outputs.release_url }}"
+          echo "🔗 Download URL: ${{ steps.create_release.outputs.download_url }}"
+          echo ""
+          echo "Install from anywhere (no authentication required):"
+          echo "  npm install -g ${{ steps.create_release.outputs.download_url }}"

.github/workflows/publish-cli-trusted.yaml

@@ -0,0 +1,60 @@
+name: Publish CLI (Trusted)
+
+on:
+  schedule:
+    - cron: "0 12 * * *" # 4 AM PST (UTC-8) = 12 UTC
+  workflow_dispatch:
+    inputs:
+      publish_target:
+        description: "Which publish flow to run"
+        required: true
+        default: "main"
+        type: choice
+        options:
+          - main
+          - nightly
+      confirm_publish:
+        description: 'Required when publish_target=main. Type "publish" to confirm release publish.'
+        required: false
+        type: string
+      force_nightly_publish:
+        description: "Force nightly publish even with no commits in last 24h"
+        required: false
+        type: boolean
+        default: false
+
+permissions:
+  id-token: write # Required for npm trusted publishing (OIDC)
+  contents: write # Required because npm-main creates/pushes git tags
+  checks: write # Required by nested reusable test workflow
+  pull-requests: write # Required by nested reusable test workflow
+
+jobs:
+  cli-tui-tests:
+    uses: ./.github/workflows/cli-tui-tests.yml
+
+  publish-main:
+    needs: cli-tui-tests
+    if: |
+      github.repository == 'cline/cline' && (
+        github.event_name == 'workflow_dispatch' &&
+        github.event.inputs.publish_target == 'main' &&
+        github.event.inputs.confirm_publish == 'publish' &&
+        !endsWith(github.actor, '[bot]')
+      )
+    uses: ./.github/workflows/npm-main.yaml
+    secrets: inherit
+    with:
+      confirm_publish: ${{ github.event.inputs.confirm_publish }}
+
+  publish-nightly:
+    needs: cli-tui-tests
+    if: |
+      github.repository == 'cline/cline' && (
+        github.event_name == 'schedule' ||
+        (github.event_name == 'workflow_dispatch' && github.event.inputs.publish_target == 'nightly')
+      )
+    uses: ./.github/workflows/npm-nightly.yaml
+    secrets: inherit
+    with:
+      force_publish: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.force_nightly_publish == 'true' }}

.github/workflows/publish-nightly.yml

@@ -24,6 +24,8 @@ jobs:
 
         steps:
             - uses: actions/checkout@v4
+              with:
+                  lfs: true
 
             - name: Check for recent commits
               run: |
@@ -36,35 +38,27 @@ jobs:
             - name: Setup Node.js
               uses: actions/setup-node@v4
               with:
-                  node-version: "lts/*"
-
-            # Cache root dependencies - only reuse if package-lock.json exactly matches
-            - name: Cache root dependencies
-              uses: actions/cache@v4
-              id: root-cache
-              with:
-                  path: node_modules
-                  key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-            # Cache webview-ui dependencies - only reuse if package-lock.json exactly matches
-            - name: Cache webview-ui dependencies
-              uses: actions/cache@v4
-              id: webview-cache
-              with:
-                  path: webview-ui/node_modules
-                  key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
+                  # Keep publish environment aligned with test workflow/tooling lockfile expectations.
+                  # Newer LTS (Node 24 / npm 11) can make `npm list` fail with ELSPROBLEMS during vsce packaging.
+                  node-version: 22
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm ci --include=optional
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci --include=optional
 
             - name: Install Publishing Tools
               run: npm install -g @vscode/vsce ovsx
 
+            - name: Verify LFS media assets are resolved
+              run: |
+                  FILE="webview-ui/src/assets/cline_kanban_demo.webm"
+                  if grep -q "git-lfs.github.com/spec/v1" "$FILE"; then
+                    echo "Error: $FILE is still a Git LFS pointer in CI checkout"
+                    exit 1
+                  fi
+
             - name: Publish Extension as Pre-release
               env:
                   VSCE_PAT: ${{ secrets.VSCE_PAT }}

.github/workflows/publish.yml

@@ -11,8 +11,13 @@ on:
                 options:
                     - pre-release
                     - release
+            auto_create_tag_from_main:
+                description: "Auto-create and push the provided tag from the tested main commit (recommended)"
+                required: true
+                default: true
+                type: boolean
             tag:
-                description: "Enter existing tag to publish (e.g., v3.1.2)"
+                description: "Tag to publish (required in both modes, e.g., v3.1.2)"
                 required: true
                 type: string
 
@@ -35,37 +40,79 @@ jobs:
         steps:
             - uses: actions/checkout@v4
               with:
-                  ref: ${{ github.event.inputs.tag }}
+                  ref: main
                   fetch-depth: 0
                   fetch-tags: true
+                  lfs: true
+
+            - name: Resolve Release Tag
+              id: resolve_tag
+              run: |
+                  TAG="${{ github.event.inputs.tag }}"
+                  AUTO_CREATE="${{ github.event.inputs.auto_create_tag_from_main }}"
+                  TESTED_SHA="${{ github.sha }}"
+                  WORKFLOW_REF="${{ github.ref }}"
+
+                  if [[ -z "$TAG" ]]; then
+                    echo "Error: tag input is required"
+                    exit 1
+                  fi
+
+                  if [[ ! "$TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+([-.][0-9A-Za-z.]+)?$ ]]; then
+                    echo "Error: tag must match vX.Y.Z (optionally with -suffix or .suffix)"
+                    exit 1
+                  fi
+                  TAG_REF="refs/tags/$TAG"
+
+                  git fetch origin main --tags
+
+                  if [[ "$AUTO_CREATE" == "true" ]]; then
+                    if [[ "$WORKFLOW_REF" != "refs/heads/main" ]]; then
+                      echo "Error: auto-create mode requires dispatching from main (current ref: $WORKFLOW_REF)"
+                      exit 1
+                    fi
+                    echo "Auto-create enabled. Using tested workflow SHA: $TESTED_SHA"
+
+                    if ! git merge-base --is-ancestor "$TESTED_SHA" origin/main; then
+                      echo "Error: tested SHA $TESTED_SHA is not on origin/main"
+                      exit 1
+                    fi
+
+                    if git show-ref --verify --quiet "$TAG_REF"; then
+                      TAG_SHA=$(git rev-list -n 1 "$TAG_REF^{commit}")
+                      if [[ "$TAG_SHA" != "$TESTED_SHA" ]]; then
+                        echo "Error: tag '$TAG' already exists at $TAG_SHA, not at tested SHA ($TESTED_SHA)"
+                        exit 1
+                      fi
+                      echo "Tag '$TAG' already exists at tested SHA. Continuing."
+                    else
+                      git config user.name "github-actions[bot]"
+                      git config user.email "github-actions[bot]@users.noreply.github.com"
+                      git tag "$TAG" "$TESTED_SHA"
+                      git push origin "$TAG_REF"
+                      echo "Created and pushed tag '$TAG' from tested SHA $TESTED_SHA."
+                    fi
+                  else
+                    if ! git show-ref --verify --quiet "$TAG_REF"; then
+                      echo "Error: tag '$TAG' does not exist in the repository"
+                      exit 1
+                    fi
+                    echo "Using existing tag '$TAG'."
+                  fi
+
+                  git checkout --detach "$TAG_REF^{commit}"
+                  echo "tag=$TAG" >> $GITHUB_OUTPUT
+                  echo "resolved_sha=$(git rev-parse HEAD)" >> $GITHUB_OUTPUT
 
             - name: Setup Node.js
               uses: actions/setup-node@v4
               with:
-                  node-version: "lts/*"
-
-            # Cache root dependencies - only reuse if package-lock.json exactly matches
-            - name: Cache root dependencies
-              uses: actions/cache@v4
-              id: root-cache
-              with:
-                  path: node_modules
-                  key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-            # Cache webview-ui dependencies - only reuse if package-lock.json exactly matches
-            - name: Cache webview-ui dependencies
-              uses: actions/cache@v4
-              id: webview-cache
-              with:
-                  path: webview-ui/node_modules
-                  key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
+                  node-version: 22
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm install --include=optional
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm install --include=optional
 
             - name: Install Publishing Tools
@@ -77,20 +124,23 @@ jobs:
                   VERSION=$(node -p "require('./package.json').version")
                   echo "version=$VERSION" >> $GITHUB_OUTPUT
 
-            - name: Validate Tag
-              id: validate_tag
+            - name: Verify Tag Matches Package Version
               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"
+                  TAG="${{ steps.resolve_tag.outputs.tag }}"
+                  VERSION="v${{ steps.get_version.outputs.version }}"
+                  if [[ "$TAG" != "$VERSION" ]]; then
+                    echo "Error: tag '$TAG' does not match package version '$VERSION'"
                     exit 1
                   fi
+                  echo "Tag and package version match: $TAG"
 
-                  echo "Tag '$TAG' validated successfully"
+            - name: Verify LFS media assets are resolved
+              run: |
+                  FILE="webview-ui/src/assets/cline_kanban_demo.webm"
+                  if grep -q "git-lfs.github.com/spec/v1" "$FILE"; then
+                    echo "Error: $FILE is still a Git LFS pointer in CI checkout"
+                    exit 1
+                  fi
 
             - name: Package and Publish Extension
               env:
@@ -121,7 +171,7 @@ jobs:
             - name: Get Previous Tag
               id: prev_tag
               run: |
-                  CURRENT_TAG="${{ steps.validate_tag.outputs.tag }}"
+                  CURRENT_TAG="${{ steps.resolve_tag.outputs.tag }}"
                   PREV_TAG=$(git describe --tags --abbrev=0 "$CURRENT_TAG^" 2>/dev/null || echo "")
                   echo "prev_tag=$PREV_TAG" >> $GITHUB_OUTPUT
 
@@ -137,12 +187,12 @@ jobs:
             - name: Create GitHub Release
               uses: softprops/action-gh-release@v1
               with:
-                  tag_name: ${{ steps.validate_tag.outputs.tag }}
+                  tag_name: ${{ steps.resolve_tag.outputs.tag }}
                   files: "*.vsix"
                   body: |
                       ${{ steps.changelog.outputs.content }}
 
-                      **Full Changelog**: https://github.com/${{ github.repository }}/compare/${{ steps.prev_tag.outputs.prev_tag }}...${{ steps.validate_tag.outputs.tag }}
+                      **Full Changelog**: https://github.com/${{ github.repository }}/compare/${{ steps.prev_tag.outputs.prev_tag }}...${{ steps.resolve_tag.outputs.tag }}
                   prerelease: ${{ github.event.inputs.release-type == 'pre-release' }}
               env:
                   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/test.yml

@@ -28,27 +28,17 @@ jobs:
               uses: actions/setup-node@v4
               with:
                   node-version: 22
-
-            - name: Cache root dependencies
-              uses: actions/cache@v4
-              id: root-cache
-              with:
-                  path: node_modules
-                  key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-            - name: Cache webview-ui dependencies
-              uses: actions/cache@v4
-              id: webview-cache
-              with:
-                  path: webview-ui/node_modules
-                  key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
+                  cache: 'npm'
+                  cache-dependency-path: |
+                      package-lock.json
+                      webview-ui/package-lock.json
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm ci
+              env:
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci
 
             - name: Run Quality Checks (Parallel)
@@ -73,27 +63,17 @@ jobs:
               uses: actions/setup-node@v4
               with:
                   node-version: 22
-
-            - name: Cache root dependencies
-              uses: actions/cache@v4
-              id: root-cache
-              with:
-                  path: node_modules
-                  key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-            - name: Cache webview-ui dependencies
-              uses: actions/cache@v4
-              id: webview-cache
-              with:
-                  path: webview-ui/node_modules
-                  key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
+                  cache: 'npm'
+                  cache-dependency-path: |
+                      package-lock.json
+                      webview-ui/package-lock.json
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm ci
+              env:
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci
 
             - name: Set up NPM on Windows
@@ -135,6 +115,11 @@ jobs:
                   cd webview-ui
                   npm run test:coverage
 
+            - name: CLI Tests
+              id: cli_tests
+              if: ${{ !cancelled() && steps.build_step.outcome == 'success' }}
+              run: cd cli && npm run test:run
+
             - name: Save Coverage Reports
               uses: actions/upload-artifact@v4
               # Only upload artifacts on Linux - We only need coverage from one OS
@@ -156,64 +141,32 @@ jobs:
               uses: actions/setup-node@v4
               with:
                   node-version: 22
-                  
-            - name: Cache root dependencies
-              uses: actions/cache@v4
-              id: root-cache
-              with:
-                  path: node_modules
-                  key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-            - name: Cache webview-ui dependencies
-              uses: actions/cache@v4
-              id: webview-cache
-              with:
-                  path: webview-ui/node_modules
-                  key: ${{ runner.os }}-npm-webview-${{ hashFiles('webview-ui/package-lock.json') }}
-
-            # Cache testing-platform dependencies
-            - name: Cache testing-platform dependencies
-              uses: actions/cache@v4
-              id: testing-platform-cache
-              with:
-                path: testing-platform/node_modules
-                key: ${{ runner.os }}-npm-testing-platform-${{ hashFiles('testing-platform/package-lock.json') }}
+                  cache: 'npm'
+                  cache-dependency-path: |
+                      package-lock.json
+                      webview-ui/package-lock.json
+                      testing-platform/package-lock.json
 
             - name: Install root dependencies
-              if: steps.root-cache.outputs.cache-hit != 'true'
               run: npm ci
+              env:
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
             - name: Install webview-ui dependencies
-              if: steps.webview-cache.outputs.cache-hit != 'true'
               run: cd webview-ui && npm ci
 
-            - name: Setup Go
-              uses: actions/setup-go@v5
-              with:
-                  go-version: '1.24'
-                  cache-dependency-path: cli/go.sum
-
-            - name: Build CLI binaries
-              run: npm run compile-cli-all-platforms
-
             - name: Download ripgrep binaries
               run: npm run download-ripgrep
 
-            - name: Compile NPM package
-              run: npm run compile-standalone-npm
+            - name: Compile Standalone
+              run: npm run compile-standalone
 
             - name: Install testing platform dependencies
-              if: steps.testing-platform-cache.outputs.cache-hit != 'true'
               run: cd testing-platform && npm ci
 
             - name: Running testing platform integration spec tests
-              continue-on-error: true
               timeout-minutes: 7
-              # Temporarily wrapping the test command to always return a neutral exit code.
-              # This prevents the job from showing as failed and avoids distracting developers
-              # until the integration tests are ready to be enforced.
-              run: |
-                npm run test:tp-orchestrator -- tests/specs/ --count=1 --coverage || true
+              run: npm run test:tp-orchestrator -- tests/specs/ --count=1 --coverage
 
             - name: Save Coverage Reports
               uses: actions/upload-artifact@v4

.github/workflows/trigger-jetbrains-tests.yml

@@ -20,7 +20,8 @@ jobs:
       github.event_name == 'pull_request_target' ||
       (github.event_name == 'issue_comment' &&
        github.event.issue.pull_request &&
-       contains(github.event.comment.body, '/test-jetbrains'))
+       contains(github.event.comment.body, '/test-jetbrains') &&
+       contains(fromJSON('["MEMBER","OWNER","COLLABORATOR"]'), github.event.comment.author_association))
     steps:
       - name: Generate GitHub App Token
         id: app-token

.gitignore

@@ -38,6 +38,7 @@ coverage-unit
 src/generated/
 src/shared/proto/
 webview-ui/src/services/grpc-client.ts
+*.tsbuildinfo
 
 # E2E Tests
 test-results
@@ -46,3 +47,12 @@ test-results
 /pkg
 .secrets
 
+*.tsbuildinfo
+
+# Smoke test results (generated)
+evals/smoke-tests/results/
+
+.tui-test
+secrets.json
+tui-traces
+tests/**/cache

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "evals/cline-bench"]
+	path = evals/cline-bench
+	url = https://github.com/cline/cline-bench.git

.vscode/launch.json

@@ -16,7 +16,8 @@
 				"saoudrizwan.claude-dev", // Avoid conflicts with installed Cline
 				"--disable-extension",
 				"saoudrizwan.cline-nightly", // Avoid conflicts with installed Cline Nightly
-				"${workspaceFolder}"
+				"${workspaceFolder}",
+				"--disable-extensions"
 			],
 			"outFiles": [
 				"${workspaceFolder}/dist/**/*.js"

.vscodeignore

@@ -35,11 +35,9 @@ cli/**
 eslint-rules/
 old_docs/
 evals/
-.changie.yaml
 .codespellrc
 .mocharc.json
 buf.yaml
-.changeset/
 .clinerules/
 
 # Ignore all webview-ui files except the build directory (https://github.com/microsoft/vscode-webview-ui-toolkit-samples/blob/main/frameworks/hello-world-react-cra/.vscodeignore)

CHANGELOG.md

@@ -1,10 +1,388 @@
 # Changelog
 
+## [3.76.0]
+
+### Added
+
+- Add Cline Kanban launch modal in webview; CLI now launches Kanban by default with a migration view
+- Add toggle to disable feature tips in chat
+- Add repeated tool call loop detection to prevent infinite loops wasting tokens
+
+### Fixed
+
+- Fix CLI Kanban spawn on Windows by enabling shell mode for `npx.cmd`
+
+## [3.75.0]
+
+### Added
+
+- Latency improvements for remote workspaces
+
+### Fixed
+
+- Stabilize flaky hooks tests
+
+### Changed
+
+- Remove example hooks in favor of reading the docs
+
+## [3.74.0]
+
+### Added
+- Implement dynamic free model detection for Cline API
+- Add file read deduplication cache to prevent repeated reads
+- Add feature tips tooltip during thinking state
+
+### Fixed
+- Replace error message when not logged in to Cline
+- Align ClineRulesToggleModal padding with ServersToggleModal
+- Skip WebP for GLM and Devstral models running through llama.cpp
+- Respect user-configured context window in LiteLLM getModel()
+- Honor explicit model IDs outside static catalog in W&B provider
+- Add missing Fireworks serverless models and pricing
+
+## [3.73.0]
+
+### Added
+
+- Added W&B Inference by CoreWeave as a new API provider with 17 models
+- Improved parallel tool calling support for OpenRouter and Cline providers
+
+### Fixed
+
+- Claude Code Provider: handle rate limit events, empty content arrays, error results, and unknown content types without crashing
+- Tool handlers (`read_file`, `list_files`, `list_code_definition_names`, `search_files`) now return graceful errors instead of crashing
+
+## [3.72.0]
+
+### Added
+
+- Added Anthropic Opus 4.6 fast mode variants
+
+### Fixed
+
+- Resolved native tool placeholder interpolation in prompts
+- Gemini: capped Flash output tokens to 8192 across providers
+- Fixed Windows unit test path normalization
+- Fixed flaky hooks tests on Windows
+- Bedrock: handle thinking and redacted_thinking blocks correctly in message conversion and streaming
+- Prevent crash when `list_files` or `list_code_definition_names` receives a file path
+
+### Changed
+
+- Updated Jupyter Notebook GIFs
+- Markdown image loading now requires user consent
+- Added `.github/copilot-instructions.md` for coding agents
+- Hooks: reintroduced feature toggle
+
+## [3.71.0]
+
+### Added
+
+- Added GPT-5.4 models for ChatGPT subscription users
+- Hooks: Added a `Notification` hook for attention and completion boundaries
+
+### Fixed
+
+- Handle streamable HTTP MCP reconnects more reliably after disconnects
+
+## [3.70.0]
+
+### Added
+
+- New Cline API docs: Getting Started, Auth, Chat Completions, Models, Errors, and SDK Examples
+- Hook payloads now include `model.provider` and `model.slug` 
+- Token/cost updates now happen immediately as usage chunks arrive, not after tool execution
+
+### Fixed
+
+- Improve subagent context compaction logic
+- Subagent stream retry delay increased to reduce noise from transient failures
+- State serialization errors are now caught and logged instead of crashing
+- Removed incorrect `max_tokens` from OpenRouter requests
+
+### Changed
+
+- Windows test cleanup now retries on locked files and applies per-test timeouts
+- Updated hooks docs 
+
+
+## [3.69.0]
+
+### Added
+
+- Add `User-Agent` header to requests sent to the Cline backend
+- Add default auto-tag workflow for publish release flow
+- Show Cline SDK docs on the Cline page
+
+### Fixed
+
+- Retry nested git restore and prevent silent `.git_disabled` leftovers in checkpoints
+- Prevent Chinese filename escaping in diff view
+- Trigger auto-compaction on OpenRouter context overflow errors
+- Restore GPT-OSS native file editing on OpenAI-compatible models
+
+### Changed
+
+- Update Cline SDK docs
+- Improve hooks support for Windows PowerShell
+
+## [3.68.0]
+
+### Added
+
+- Add dynamic Cline provider model fetching from Cline endpoint
+- Add additional Markdown formatting in CLI
+- Add focus indicator on action buttons in extension
+
+### Fixed
+
+- Clear all OCA secrets on auth refresh failure to prevent re-auth loops
+- Resolve "Could not find the file context" error in Explain Changes
+- Use `JSON_SCHEMA` for `yaml.load` to prevent unsafe deserialization
+- Fetch model info from API in CLI headless auth for Cline and Vercel providers
+- Generate commit message from staged changes only when staging exists
+- Update stale `maxTokens` values for Claude 3.7+ models across Anthropic, Bedrock, Vertex, and SAP AI Core
+- Use `model.info.maxTokens` for OpenRouter instead of hardcoded `8192`
+
+### Changed
+
+- Increase timeout for a flaky test to reduce short-term test instability
+
+## [3.67.1]
+
+### Added
+
+- Added Cline SDK API interface for programmatic access to Cline features and tools, enabling integration into custom applications.
+- Added Codex 5.3 model support
+
+### Fixed
+
+- Fix OpenAI Codex by setting `store` to `false`
+- Use `isLocatedInPath()` instead of string matching for path containment checks
+
+## [3.67.0]
+
+### Added
+
+- Add support for skills and optional modelId in subagent configuration
+- Add AgentConfigLoader for file-based agent configs
+- Add Responses API support for OpenAI native provider
+- Preconnect websocket to reduce response latency
+- Fetch featured models from backend with local fallback
+- Add /q command to quit CLI
+- Add MCP enterprise configuration details
+- Pull Cline's recommended models from internal endpoint
+- Add dynamic flag to adjust banner cache duration
+
+### Fixed
+
+- Fix reasoning delta crash on usage-only stream chunks
+- Fix OpenAI tool ID transformation restricted to native provider only
+- Fix auth check for ACP mode
+- Fix CLI yolo mode to not persist yolo setting to disk
+- Fix inline focus-chain slider within its feature row
+- Fix Gemini 3.1 Pro compatibility
+- Fix Cline auth with ACP flag
+
+### Changed
+
+- Move PR skill to .agents/skills
+- SambaNova provider: update models list
+- Remove changeset-converter GitHub Action and npm run changeset
+
+## [3.66.0]
+
+### Added
+
+- Gemini-3.1 Pro Preview
+
+
+## [3.65.0]
+
+### Added
+
+- Add /skills slash command to CLI for viewing and managing installed skills
+
+### Fixed
+
+- Fix aggressive context compaction caused by accidental clicks on the context window progress bar silently setting a very low auto-condense threshold
+- Fix infinite retry loop when write_to_file fails with missing content parameter.
+- Fixed default claude model
+
+## [3.64.0]
+
+### Added
+- Added sonnet 4.6
+
+
+## [3.63.0]
+
+### Added
+
+- added zai GLM 5 Free promo
+
+### Fixed
+
+- Restore reasoning trace visibility in chat and improve the thinking row UX so reasoning is visible, then collapsible after completion.
+
+## [3.62.0]
+
+### Fixed
+
+- Banners now display immediately when opening the extension instead of requiring user interaction first
+- Resolved 17 security vulnerabilities including high-severity DoS issues in dependencies (body-parser, axios, qs, tar, and others)
+
+## [3.61.0]
+
+- UI/UX fixes with minimax model family
+
+## [3.60.0]
+
+- Fixes for Minimax model family
+
+## [3.59.0]
+
+- Added Minimax 2.5 Free Promo
+- Fixed Response chaining for OpenAI's Responses API
+
+## [3.58.0]
+
+### Added
+
+- Subagent: replace legacy subagents with the native `use_subagents` tool
+- Bundle `endpoints.json` support so packaged distributions can ship required endpoints out-of-the-box
+- Amazon Bedrock: support parallel tool calling
+- New "double-check completion" experimental feature to verify work before marking tasks complete
+- CLI: new task controls/flags including custom `--thinking` token budget and `--max-consecutive-mistakes` for yolo runs
+- Remote config: new UI/options (including connection/test buttons) and support for syncing deletion of remotely configured MCP servers
+- Vertex / Claude Code: add 1M context model options for Claude Opus 4.6
+- ZAI/GLM: add GLM-5
+
+### Fixed
+
+- CLI: handle stdin redirection correctly in CI/headless environments
+- CLI: preserve OAuth callback paths during auth redirects
+- VS Code Web: generate auth callback URLs via `vscode.env.asExternalUri` (OAuth callback reliability)
+- Terminal: surface command exit codes in results and improve long-running `execute_command` timeout behavior
+- UI: add loading indicator and fix `api_req_started` rendering
+- Task streaming: prevent duplicate streamed text rows after completion
+- API: preserve selected Vercel model when model metadata is missing
+- Telemetry: route PostHog networking through proxy-aware shared fetch and ensure telemetry flushes on shutdown
+- CI: increase Windows E2E test timeout to reduce flakiness
+
+### Changed
+
+- Settings/model UX: move "reasoning effort" into model configuration and expose it in settings
+- CLI provider selection: limit provider list to those remotely configured
+- UI: consolidate ViewHeader component/styling across views
+- Tools: add auto-approval support for `attempt_completion` commands
+- Remotely configured MCP server schema now supports custom headers
+
+## [3.57.1]
+
+### Fixed
+
+- Fixed Opus 4.6 for bedrock provider
+
+## [3.57.0]
+
+### Added
+
+- Cline CLI 2.0 now available. Install with `npm install -g cline`
+- Anthopic Opus 4.6
+- Minimax-2.1 and Kimi-k2.5 now available for free for a limited time promo
+- Codex-5.3 through ChatGPT subscription
+
+### Fixed
+
+- Fix read file tool to support reading large files
+- Fix decimal input crash in OpenAI Compatible price fields (#8129)
+- Fix build complete handlers when updating the api config
+- Fixed missing provider from list
+- Fixed Favorite Icon / Star from getting clipped in the task history view
+
+### Changed
+
+- Make skills always enabled and remove feature toggle setting
+
+## [3.56.0]
+
+### Added
+
+- **CLI authentication:** Added Vercel AI Gateway and Cline API key provider support for headless CI/automation workflows
+- **New model:** Added Kimi-K2.5 model to Moonshot provider (262K context, image support, prompt caching)
+- **Prompt variant:** Added Trinity Large prompt variant for improved tool-calling support
+- **OpenTelemetry:** Added support for custom headers on metrics and logs endpoints
+- **Social links:** Added community icons (X, Discord, GitHub, Reddit, LinkedIn) to the What's New modal
+
+### Fixed
+
+- **LiteLLM:** Fixed thinking configuration not appearing for reasoning-capable models
+- **OpenTelemetry:** Fixed endpoint path handling (no longer incorrectly appends `/v1/logs` or `/v1/metrics`) and ensured logs are sent regardless of VSCode telemetry settings
+- **CLI auth:** Fixed `cline auth` displaying incorrect provider information after configuration
+
+### Changed
+
+- **Hooks:** Hook scripts now run from the workspace repository root instead of filesystem root
+- **Default settings:** Enabled multi-root workspaces, parallel tool calling, and skills by default; disabled strict plan mode by default
+- **Settings UI:** Refreshed feature settings section with collapsible design
+
+## [3.55.0]
+
+- Add new model: Arcee Trinity Large Preview
+- Add new model: Moonshot Kimi K2.5
+- Add MCP prompts support - prompts from connected MCP servers now appear in slash command autocomplete as `/mcp:<server>:<prompt>`
+
+## [3.54.0]
+
+### Added
+
+- Native tool calls support for Ollama provider
+- Sonnet 4.5 is now the default Amazon Bedrock model id
+
+### Fixed
+
+- Prevent infinite retry loops when replace_in_file fails repeatedly. The system now detects repeated failures and provides better guidance to break out of retry cycles.
+- Skip diff error UI handling during streaming to prevent flickering. Error handling is deferred until streaming completes.
+- Strip notebook cell outputs when extracting text content from Jupyter notebooks, significantly reducing context size sent to the LLM.
+- Throttle diff view updates during streaming to reduce UI flickering and improve performance.
+
+### Changed
+
+- Removed Mistral's Devstral-2512 free from the free models list
+- Removed deprecated zai-glm-4.6 model from Cerebras provider
+
+## [3.53.1]
+
+### Fixed
+
+- Bug in responses API
+
+## [3.53.0]
+
+### Fixed
+
+- Removed grok model from free tier
+
+## [3.52.0]
+
+### Added
+
+- Users with ChatGPT Plus or Pro subscriptions can now use GPT-5 models directly through Cline without needing an API key. Authentication is handled via OAuth through OpenAI's authentication system.
+- Grok models are now moving out of free tier and into paid plans.
+- Introduces comprehensive Jupyter Notebook support for Cline, enabling AI-assisted editing of `.ipynb` files with full cell-level context awareness.
+
+### Fixed
+
+- Bugs in DiffViewProvider for file editing
+- Ollama's recommended models to use correct identifiers
+
 ## [3.51.0]
 
 ### Added
 
-- Adding OpenAI gpt-5.2-codex  model to the model picker
+- Adding OpenAI gpt-5.2-codex model to the model picker
 
 ## [3.50.0]
 
@@ -1737,4 +2115,4 @@ Add Opus 4.1 through Claude Code
 
 ## [0.0.6]
 
-- Initial release
+- Initial release

CLAUDE.md

@@ -1,2 +1,3 @@
 @.clinerules/general.md
 @.clinerules/network.md
+@.clinerules/cli.md

CONTRIBUTING.md

@@ -57,25 +57,11 @@ We also welcome contributions to our [documentation](https://github.com/cline/cl
 
 ### 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
+1. Commit your changes.
 
-2. Commit your changes and the generated `.changeset` file
-
-3. Push your branch and create a PR on GitHub. Our CI will:
+2. 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
+3. Testing
     - Run `npm run test` to run tests locally. 
     - Before submitting PR, run `npm run format:fix` to format your code
 
@@ -192,15 +178,10 @@ Anyone can contribute code to Cline, but we ask that you follow these guidelines
       - Temporary workspaces with test fixtures
       - Video recording for failed tests
 
-4. **Version Management with Changesets**
+4. **Versioning & Changelog Notes**
 
-    - Create a changeset for any user-facing changes using `npm run changeset`
-    - Choose the appropriate version bump:
-        - `major` for breaking changes (1.0.0 → 2.0.0)
-        - `minor` for new features (1.0.0 → 1.1.0)
-        - `patch` for bug fixes (1.0.0 → 1.0.1)
-    - Write clear, descriptive changeset messages that explain the impact
-    - Documentation-only changes don't require changesets
+    - Contributors do not need to create changelog-entry files as part of PRs.
+    - Maintainers handle release versioning and changelog curation during the release process.
 
 5. **Commit Guidelines**
 

LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2025 Cline Bot Inc.
+   Copyright 2026 Cline Bot Inc.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

README.md

@@ -148,4 +148,4 @@ Get the same Cline experience with enterprise-grade controls: SSO (SAML/OIDC), g
 
 ## License
 
-[Apache 2.0 © 2025 Cline Bot Inc.](./LICENSE)
+[Apache 2.0 © 2026 Cline Bot Inc.](./LICENSE)

SECURITY.md

@@ -0,0 +1,27 @@
+# Security Policy
+
+## Supported Versions
+
+We actively patch only the most recent minor release of Cline. Older versions receive fixes at our discretion.
+
+## Reporting a Vulnerability
+
+We appreciate your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions.
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/cline/cline/security/advisories/new) tab.
+
+The team will send a response indicating the next steps in handling your report. After the initial reply, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
+
+When reporting, please include:
+
+- A short summary of the issue
+- Steps to reproduce or a proof of concept
+- Any logs, stack traces, or screenshots that might help us understand the problem
+
+We acknowledge reports within 48 hours and aim to release a fix or mitigation within 30 days. While we work on a resolution, please keep the details private.
+
+## Escalation
+
+If you do not receive an acknowledgement of your report within 5 business days, you may send an email to security@cline.bot.
+
+Thank you for helping us keep Cline users safe.

assets/icons/social/discord.svg

@@ -0,0 +1,3 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M20.317 4.15557C18.7873 3.45369 17.147 2.93658 15.4319 2.6404C15.4007 2.63469 15.3695 2.64897 15.3534 2.67754C15.1424 3.05276 14.9087 3.54225 14.7451 3.927C12.9004 3.65083 11.0652 3.65083 9.25832 3.927C9.09465 3.5337 8.85248 3.05276 8.64057 2.67754C8.62449 2.64992 8.59328 2.63564 8.56205 2.6404C6.84791 2.93563 5.20756 3.45275 3.67693 4.15557C3.66368 4.16129 3.65233 4.17082 3.64479 4.18319C0.533392 8.83155 -0.31895 13.3657 0.0991801 17.8436C0.101072 17.8655 0.11337 17.8864 0.130398 17.8997C2.18321 19.4073 4.17171 20.3225 6.12328 20.9291C6.15451 20.9386 6.18761 20.9272 6.20748 20.9015C6.66913 20.2711 7.08064 19.6063 7.43348 18.9073C7.4543 18.8664 7.43442 18.8178 7.39186 18.8016C6.73913 18.554 6.1176 18.2521 5.51973 17.9093C5.47244 17.8816 5.46865 17.814 5.51216 17.7816C5.63797 17.6873 5.76382 17.5893 5.88396 17.4902C5.90569 17.4721 5.93598 17.4683 5.96153 17.4797C9.88928 19.273 14.1415 19.273 18.023 17.4797C18.0485 17.4674 18.0788 17.4712 18.1015 17.4893C18.2216 17.5883 18.3475 17.6873 18.4742 17.7816C18.5177 17.814 18.5149 17.8816 18.4676 17.9093C17.8697 18.2588 17.2482 18.554 16.5945 18.8006C16.552 18.8168 16.533 18.8664 16.5538 18.9073C16.9143 19.6054 17.3258 20.2701 17.7789 20.9005C17.7978 20.9272 17.8319 20.9386 17.8631 20.9291C19.8241 20.3225 21.8126 19.4073 23.8654 17.8997C23.8834 17.8864 23.8948 17.8664 23.8967 17.8445C24.3971 12.6676 23.0585 8.17064 20.3482 4.18414C20.3416 4.17082 20.3303 4.16129 20.317 4.15557ZM8.02002 15.117C6.8375 15.117 5.86313 14.0313 5.86313 12.6981C5.86313 11.3648 6.8186 10.2791 8.02002 10.2791C9.23087 10.2791 10.1958 11.3743 10.1769 12.6981C10.1769 14.0313 9.22141 15.117 8.02002 15.117ZM15.9947 15.117C14.8123 15.117 13.8379 14.0313 13.8379 12.6981C13.8379 11.3648 14.7933 10.2791 15.9947 10.2791C17.2056 10.2791 18.1705 11.3743 18.1516 12.6981C18.1516 14.0313 17.2056 15.117 15.9947 15.117Z" fill="#FAFAFA"/>
+</svg>

assets/icons/social/github.svg

@@ -0,0 +1,3 @@
+        <svg viewBox="0 0 24 24" fill="black" xmlns="http://www.w3.org/2000/svg">
+          <path d="M12 2C6.477 2 2 6.477 2 12C2 16.418 4.865 20.166 8.84 21.49C9.34 21.58 9.52 21.27 9.52 21C9.52 20.77 9.51 20.14 9.51 19.31C6.73 19.91 6.14 17.97 6.14 17.97C5.68 16.81 5.03 16.5 5.03 16.5C4.12 15.88 5.1 15.9 5.1 15.9C6.1 15.97 6.63 16.93 6.63 16.93C7.5 18.45 8.97 18 9.54 17.76C9.63 17.11 9.89 16.67 10.17 16.42C7.95 16.17 5.62 15.31 5.62 11.5C5.62 10.39 6 9.5 6.65 8.79C6.55 8.54 6.2 7.5 6.75 6.15C6.75 6.15 7.59 5.88 9.5 7.17C10.29 6.95 11.15 6.84 12 6.84C12.85 6.84 13.71 6.95 14.5 7.17C16.41 5.88 17.25 6.15 17.25 6.15C17.8 7.5 17.45 8.54 17.35 8.79C18 9.5 18.38 10.39 18.38 11.5C18.38 15.32 16.04 16.16 13.81 16.41C14.17 16.72 14.5 17.33 14.5 18.26C14.5 19.6 14.49 20.68 14.49 21C14.49 21.27 14.67 21.59 15.17 21.49C19.14 20.16 22 16.42 22 12C22 6.477 17.523 2 12 2Z" fill="white"/>
+        </svg>

assets/icons/social/linkedin.svg

@@ -0,0 +1,10 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0_2001_1428)">
+<path d="M22.2234 0H1.77187C0.792187 0 0 0.773438 0 1.72969V22.2656C0 23.2219 0.792187 24 1.77187 24H22.2234C23.2031 24 24 23.2219 24 22.2703V1.72969C24 0.773438 23.2031 0 22.2234 0ZM7.12031 20.4516H3.55781V8.99531H7.12031V20.4516ZM5.33906 7.43438C4.19531 7.43438 3.27188 6.51094 3.27188 5.37187C3.27188 4.23281 4.19531 3.30937 5.33906 3.30937C6.47813 3.30937 7.40156 4.23281 7.40156 5.37187C7.40156 6.50625 6.47813 7.43438 5.33906 7.43438ZM20.4516 20.4516H16.8937V14.8828C16.8937 13.5562 16.8703 11.8453 15.0422 11.8453C13.1906 11.8453 12.9094 13.2937 12.9094 14.7891V20.4516H9.35625V8.99531H12.7687V10.5609H12.8156C13.2891 9.66094 14.4516 8.70938 16.1813 8.70938C19.7859 8.70938 20.4516 11.0813 20.4516 14.1656V20.4516Z" fill="#FAFAFA"/>
+</g>
+<defs>
+<clipPath id="clip0_2001_1428">
+<rect width="24" height="24" fill="white"/>
+</clipPath>
+</defs>
+</svg>

assets/icons/social/reddit.svg

@@ -0,0 +1,3 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M15.0512 4.07466C15.3113 5.17727 16.301 5.99866 17.4829 5.99866C18.8627 5.99866 19.9813 4.87965 19.9813 3.49933C19.9813 2.11902 18.8627 1 17.4829 1C16.2764 1 15.2703 1.85537 15.036 2.99314C13.0155 3.20991 11.4378 4.92417 11.4378 7.00167C11.4378 7.00636 11.4378 7.00988 11.4378 7.01456C9.24041 7.10713 7.23397 7.73284 5.641 8.72062C5.04949 8.26247 4.30688 7.98945 3.50102 7.98945C1.5672 7.98945 0 9.55725 0 11.4918C0 12.8955 0.824597 14.1048 2.01581 14.6637C2.13177 18.7297 6.56047 22 12.0082 22C17.4559 22 21.8905 18.7261 22.0006 14.6567C23.1824 14.0942 24 12.8885 24 11.493C24 9.55842 22.4328 7.99063 20.499 7.99063C19.6966 7.99063 18.9575 8.2613 18.3672 8.71594C16.7602 7.72113 14.7315 7.09541 12.5119 7.01222C12.5119 7.0087 12.5119 7.00636 12.5119 7.00285C12.5119 5.51473 13.6176 4.27971 15.0512 4.077V4.07466ZM5.50044 13.7146C5.559 12.4444 6.40234 11.4695 7.38272 11.4695C8.3631 11.4695 9.11274 12.4995 9.05417 13.7697C8.99561 15.0398 8.26354 15.5015 7.28199 15.5015C6.30044 15.5015 5.44187 14.9848 5.50044 13.7146ZM16.6348 11.4695C17.6164 11.4695 18.4597 12.4444 18.5171 13.7146C18.5757 14.9848 17.716 15.5015 16.7356 15.5015C15.7552 15.5015 15.022 15.041 14.9634 13.7697C14.9048 12.4995 15.6533 11.4695 16.6348 11.4695ZM15.4682 16.6533C15.6521 16.6721 15.7693 16.8631 15.6978 17.0341C15.0946 18.4766 13.6703 19.4901 12.0082 19.4901C10.3461 19.4901 8.92299 18.4766 8.31859 17.0341C8.24714 16.8631 8.36427 16.6721 8.54817 16.6533C9.62577 16.5444 10.7912 16.4846 12.0082 16.4846C13.2252 16.4846 14.3895 16.5444 15.4682 16.6533Z" fill="#FAFAFA"/>
+</svg>

assets/icons/social/x.svg

@@ -0,0 +1,3 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M18.3263 1.90393H21.6998L14.3297 10.3274L23 21.7899H16.2112L10.894 14.838L4.80995 21.7899H1.43443L9.31743 12.78L1 1.90393H7.96111L12.7674 8.25826L18.3263 1.90393ZM17.1423 19.7707H19.0116L6.94539 3.81706H4.93946L17.1423 19.7707Z" fill="#FAFAFA"/>
+</svg>

biome.jsonc

@@ -1,5 +1,5 @@
 {
-	"$schema": "https://biomejs.dev/schemas/2.1.4/schema.json",
+	"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
 	"vcs": {
 		"enabled": true,
 		"clientKind": "git",
@@ -28,58 +28,59 @@
 		"rules": {
 			"recommended": true,
 			"correctness": {
-				"useExhaustiveDependencies": "off",
+				"useExhaustiveDependencies": "info",
 				"noUndeclaredVariables": "off",
-				"noEmptyPattern": "off",
+				"noEmptyPattern": "info",
 				"useJsxKeyInIterable": "off",
 				"noInnerDeclarations": "off",
-				"useHookAtTopLevel": "off",
-				"useYield": "off",
+				"useHookAtTopLevel": "info",
+				"useYield": "info",
 				"noConstructorReturn": "off",
 				"noInvalidPositionAtImportRule": "off",
 				"noSwitchDeclarations": "off",
 				"noUnusedImports": "error"
 			},
-			"a11y": "off",
+			"a11y": "info",
 			"style": {
 				"useNodejsImportProtocol": "off",
 				"useImportType": "off",
-				"useBlockStatements": "warn",
+				"useBlockStatements": "off",
 				"useNamingConvention": "off",
 				"useThrowOnlyError": "info",
 				"useConsistentArrayType": "off",
 				"noParameterAssign": "off",
 				"useAsConstAssertion": "off",
 				"useDefaultParameterLast": "off",
-				"noNonNullAssertion": "off",
+				"noNonNullAssertion": "info",
 				"useEnumInitializers": "off",
-				"useSelfClosingElements": "off",
+				"useSelfClosingElements": "info",
 				"useSingleVarDeclarator": "off",
-				"useNumberNamespace": "off",
-				"noInferrableTypes": "off",
-				"useTemplate": "off",
-				"noUselessElse": "off"
+				"useNumberNamespace": "info",
+				"noInferrableTypes": "info",
+				"useTemplate": "info",
+				"noUselessElse": "info"
 			},
 			"suspicious": {
 				"noDoubleEquals": "warn",
 				"noImplicitAnyLet": "info",
 				"noThenProperty": "off",
-				"noAsyncPromiseExecutor": "off",
+				"noAsyncPromiseExecutor": "info",
 				"noImportAssign": "off",
-				"noExplicitAny": "off",
-				"noControlCharactersInRegex": "off",
+				"noExplicitAny": "info",
+				"noControlCharactersInRegex": "warn",
 				"noShadowRestrictedNames": "off",
 				"noArrayIndexKey": "info",
-				"noAssignInExpressions": "info"
+				"noAssignInExpressions": "info",
+				"useIterableCallbackReturn": "info"
 			},
 			"complexity": {
-				"noUselessConstructor": "off",
-				"useOptionalChain": "off",
-				"noBannedTypes": "off",
-				"useLiteralKeys": "off",
-				"noUselessCatch": "off",
-				"noUselessSwitchCase": "off",
-				"noStaticOnlyClass": "off"
+				"noUselessConstructor": "info",
+				"useOptionalChain": "info",
+				"noBannedTypes": "warn",
+				"useLiteralKeys": "info",
+				"noUselessCatch": "info",
+				"noUselessSwitchCase": "info",
+				"noStaticOnlyClass": "info"
 			},
 			"security": {
 				"noDangerouslySetInnerHtml": "info"
@@ -94,6 +95,11 @@
 		"lineEnding": "lf",
 		"formatWithErrors": true
 	},
+	"css": {
+		"parser": {
+			"tailwindDirectives": true
+		}
+	},
 	"javascript": {
 		"formatter": {
 			"semicolons": "asNeeded",
@@ -112,19 +118,21 @@
 		}
 	},
 	"files": {
+		"ignoreUnknown": true,
 		"includes": [
 			"**",
-			"!**/dist",
-			"!**/dist-*",
-			"!**/out",
-			"!**/evals",
-			"!**/playwright",
-			"!**/test-results",
-			"!**/node_modules",
-			"!**/webview-ui/build",
-			"!**/generated",
-			"!**/proto",
-			"!**/tests/specs"
+			// explicitly force files to be ignored by the scanner with !!
+			"!!**/dist",
+			"!!**/dist-*",
+			"!!**/out",
+			"!!**/evals",
+			"!!**/playwright",
+			"!!**/test-results",
+			"!!**/node_modules",
+			"!!**/webview-ui/build",
+			"!!**/generated",
+			"!!**/proto",
+			"!!**/tests/specs"
 		]
 	},
 	"plugins": [
@@ -134,29 +142,58 @@
 		{
 			"includes": [
 				"**",
-				"!**/hosts/vscode/**",
-				"!**/test/**",
-				"!**/*.test.ts",
-				"!src/dev/**",
-				"!src/extension.ts",
-				"!src/integrations/git/commit-message-generator.ts",
-				"!src/integrations/terminal/**",
-				"!src/core/controller/ui/openWalkthrough.ts"
+				"!!**/dist",
+				"!!**/hosts/vscode/**",
+				"!!**/test/**",
+				"!!**/*.test.ts",
+				"!!src/dev/**",
+				"!!src/extension.ts",
+				"!!src/integrations/git/commit-message-generator.ts",
+				"!!src/integrations/terminal/**",
+				"!!src/core/controller/ui/openWalkthrough.ts"
 			],
 			"plugins": [
 				"src/dev/grit/vscode-api.grit"
 			]
 		},
 		{
+			// Do not use console logging directly, use the Logger service instead.
+			"plugins": [
+				"src/dev/grit/console-log.grit"
+			],
 			"includes": [
 				"**",
-				"!src/core/storage/state-migrations.ts",
-				"!src/core/storage/FileContextTracker.ts",
-				"!src/core/context/context-tracking/FileContextTracker.ts",
-				"!src/common.ts",
-				"!src/services/logging/distinctId.ts",
-				"!src/core/storage/utils/state-helpers.ts",
-				"!src/extension.ts"
+				"!!**/esbuild.*",
+				"!!**/*.mts",
+				"!!**/webview-ui/**",
+				"!!**/evals/**",
+				"!!**/standalone/**",
+				"!!**/cli/**",
+				"!!**/e2e/**",
+				"!!**/test/**",
+				"!!**/__tests__/**",
+				"!!**/*.test.ts",
+				"!!**/*.stories.ts",
+				"!!src/dev/**",
+				"!!**/*.mjs",
+				"!!**/*.js",
+				"!!**/scripts/**",
+				"!!**/*.tsx",
+				"!!**/testing-platform/**",
+				// ACP mode must redirect console to stderr - this is intentional
+				"!!cli/src/acp/index.ts"
+			]
+		},
+		{
+			"includes": [
+				"**",
+				"!!src/core/storage/state-migrations.ts",
+				"!!src/core/storage/FileContextTracker.ts",
+				"!!src/core/context/context-tracking/FileContextTracker.ts",
+				"!!src/common.ts",
+				"!!src/services/logging/distinctId.ts",
+				"!!src/core/storage/utils/state-helpers.ts",
+				"!!src/extension.ts"
 			],
 			"plugins": [
 				"src/dev/grit/use-cache-service.grit"

cli-ts/.mocharc.json

@@ -1,18 +0,0 @@
-{
-	"extension": [
-		"ts"
-	],
-	"spec": [
-		"tests/unit/core/**/*.test.ts",
-		"tests/unit/commands/version.test.ts"
-	],
-	"ignore": [
-		"tests/unit/commands/auth/**",
-		"tests/unit/commands/task/**"
-	],
-	"node-option": [
-		"import=tsx",
-		"experimental-specifier-resolution=node"
-	],
-	"timeout": 10000
-}

cli-ts/CLI_FEATURES_PLAN.md

@@ -1,473 +0,0 @@
-# CLI Features Implementation Plan
-
-Based on the cline.1.md man page, this document outlines the implementation plan for all CLI features. The Cline man page indicates that cline cli runs as a client-server architecture where **Cline Core** runs as a standalone service, but for the typescript version of the CLI, that won't be the case. The Typescript CLI will just import the necessary objects it needs from cline core src directly.
-
-## Overview
-
-The TypeScript CLI scaffold is complete. This plan covers implementing the full feature set from the man page, prioritized by dependency order and user value.
-
----
-
-## Phase 1: Core Infrastructure (Prerequisites)
-**Status: ✅ Completed (tests passing)**
-
-### 1.1 Output Formatting System
-**Priority: High** | **Complexity: Medium**
-
-Implement the `-F/--output-format` global option to support `rich`, `json`, and `plain` output formats.
-
-**Files to create:**
-- `cli-ts/src/core/output/formatter.ts` - Base formatter interface
-- `cli-ts/src/core/output/rich-formatter.ts` - Rich terminal output with colors/styling
-- `cli-ts/src/core/output/json-formatter.ts` - JSON output for scripting
-- `cli-ts/src/core/output/plain-formatter.ts` - Plain text output
-
-**Types:**
-```typescript
-interface OutputFormatter {
-  message(msg: ClineMessage): void
-  error(err: Error): void
-  success(text: string): void
-  table(data: Record<string, unknown>[]): void
-  list(items: string[]): void
-}
-
-interface ClineMessage {
-  type: 'ask' | 'say'
-  text: string
-  ts: number // Unix epoch milliseconds
-  reasoning?: string
-  say?: string // say subtype
-  ask?: string // ask subtype
-  partial?: boolean
-  images?: string[]
-  files?: string[]
-  lastCheckpointHash?: string
-  isCheckpointCheckedOut?: boolean
-  isOperationOutsideWorkspace?: boolean
-}
-```
-
-**Tests:**
-- JSON formatter outputs valid JSON per message
-- Rich formatter uses colors when TTY available
-- Plain formatter strips all formatting
-
----
-
-### 1.2 Configuration System
-**Priority: High** | **Complexity: Medium**
-
-Implement persistent configuration storage and the `cline config` command group.
-
-**Commands:**
-- `cline config set <key> <value>`
-- `cline config get <key>`
-- `cline config list`
-
-**Files to create:**
-- `cli-ts/src/core/config-storage.ts` - Persistent config storage (JSON file in ~/.cline)
-- `cli-ts/src/commands/config/index.ts` - Config command group
-- `cli-ts/src/commands/config/set.ts`
-- `cli-ts/src/commands/config/get.ts`
-- `cli-ts/src/commands/config/list.ts`
-
-**Config storage location:** `~/.cline/config.json`
-
-**Tests:**
-- Config persists across CLI invocations
-- Config values can be overridden
-- Invalid keys produce helpful errors
-
----
-
-### 1.3 Instance Registry & Lifecycle (DEPRECATED -- DO NOT IMPLEMENT)
-**Priority: Deprecated** | **Complexity: High**
-
-Implement the instance management system for tracking running Cline Core instances.
-
-**Files to create:**
-- `cli-ts/src/core/instance-registry.ts` - Track running instances (SQLite or JSON)
-- `cli-ts/src/core/instance-client.ts` - gRPC client for communicating with Cline Core
-- `cli-ts/src/commands/instance/index.ts` - Instance command group
-- `cli-ts/src/commands/instance/new.ts`
-- `cli-ts/src/commands/instance/list.ts`
-- `cli-ts/src/commands/instance/default.ts`
-- `cli-ts/src/commands/instance/kill.ts`
-
-**Commands:**
-- `cline instance new [--default]` / `cline i n`
-- `cline instance list` / `cline i l`
-- `cline instance default <address>` / `cline i d`
-- `cline instance kill <address> [--all]` / `cline i k`
-
-**Architecture notes:**
-- The CLI spawns `cline-core` as a child process
-- Instances are tracked in `~/.cline/instances.json` with addresses and PIDs
-- Default instance is stored in config
-
-**Tests:**
-- New instance spawns cline-core process
-- List shows all running instances
-- Kill terminates specific or all instances
-- Default instance is used when --address not specified
-
----
-
-## Phase 2: Authentication
-**Status: ✅ Completed (tests passing)**
-
-### 2.1 Auth Command
-**Priority: High** | **Complexity: Medium**
-
-Implement provider authentication system.
-
-**Commands:**
-- `cline auth [provider] [key]` / `cline a`
-
-**Files to create:**
-- `cli-ts/src/commands/auth/index.ts` - Auth command with interactive wizard
-- `cli-ts/src/core/auth/providers.ts` - Provider definitions (Anthropic, OpenRouter, etc.)
-- `cli-ts/src/core/auth/wizard.ts` - Interactive provider selection
-- `cli-ts/src/core/auth/oauth.ts` - OAuth flow handler (for providers that support it)
-
-**Behavior:**
-- No args: Launch interactive wizard
-- Provider only: Prompt for key or launch OAuth
-- Provider + key: Store key directly
-
-**Storage:** Keys stored in `~/.cline/secrets.json` (with appropriate permissions)
-
-**Tests:**
-- Interactive wizard presents provider choices
-- API keys are securely stored
-- Keys can be updated
-
----
-
-## Phase 3: Task Management
-**Status: ✅ Completed (207 tests passing)**
-
-### 3.1 Task Command Group Base
-**Priority: High** | **Complexity: Medium** | **Status: ✅ Complete**
-
-Implement the task command infrastructure.
-
-**Files created:**
-- `cli-ts/src/commands/task/index.ts` - Task command group
-- `cli-ts/src/core/task-client.ts` - Task storage and management
-- `cli-ts/src/types/task.ts` - Task-related types
-
-**Commands:**
-- `cline task` / `cline t` - Display help
-
----
-
-### 3.2 Task Creation & History
-**Priority: High** | **Complexity: Medium** | **Status: ✅ Complete**
-
-**Commands:**
-- `cline task new <prompt> [options]` / `cline t n`
-- `cline task list` / `cline t l` / `cline t ls`
-- `cline task open <task-id>` / `cline t o`
-
-**Files created:**
-- `cli-ts/src/commands/task/new.ts`
-- `cli-ts/src/commands/task/list.ts`
-- `cli-ts/src/commands/task/open.ts`
-
-**Options for task new/open:**
-- `-s, --setting <key=value>` - Override settings (repeatable)
-- `-y, --yolo` / `--no-interactive` - Autonomous mode
-- `-m, --mode <mode>` - Starting mode (act/plan)
-- `-w, --workspace <path>` - Working directory (new only)
-
-**Options for task list:**
-- `-n, --limit <number>` - Limit results (default: 20)
-- `-a, --all` - Show all tasks
-- `--status <status>` - Filter by status
-
-**Tests (53 new tests):**
-- ✅ TaskStorage: create, get, update, delete, list, findByPartialId
-- ✅ task new: creates task, validates mode, parses settings
-- ✅ task list: shows history, respects limit, filters by status, JSON output
-- ✅ task open: finds by full/partial ID, overrides mode/settings, resumes paused tasks
-
----
-
-### 3.3 Task Communication - Embedded Controller Architecture
-**Priority: High** | **Complexity: High**
-
-**Architecture Decision: In-Process Embedded Controller**
-
-The CLI chat REPL will embed the Cline Controller directly in the CLI process (not via gRPC). This approach:
-- Uses direct method calls instead of gRPC serialization
-- Reuses infrastructure from `src/standalone/cline-core.ts`
-- Shares state via `~/.cline/` with VSCode extension
-- Outputs to terminal instead of webview
-
-```
-┌──────────────────────────────────────────────────────────┐
-│                    CLI Process                            │
-│                                                          │
-│  ┌────────────┐    ┌────────────┐    ┌──────────────────┐│
-│  │  CLI Chat  │───>│ Controller │───>│ Task + AI API    ││
-│  │   REPL     │<───│            │<───│                  ││
-│  └────────────┘    └────────────┘    └──────────────────┘│
-│        │                 │                               │
-│        v                 v                               │
-│  ┌────────────┐    ┌──────────────┐                     │
-│  │  Terminal  │    │ StateManager │                     │
-│  │   Output   │    │ (~/.cline/)  │                     │
-│  └────────────┘    └──────────────┘                     │
-└──────────────────────────────────────────────────────────┘
-```
-
-**Key Source Files to Understand:**
-- `src/core/controller/index.ts` - Controller class with initTask(), cancelTask(), postStateToWebview()
-- `src/standalone/cline-core.ts` - Shows how to run Controller outside VSCode
-- `src/standalone/vscode-context.ts` - initializeContext() creates mock ExtensionContext
-- `src/standalone/protobus-service.ts` - Shows Controller methods exposed via gRPC
-- `src/generated/hosts/standalone/protobus-server-setup.ts` - All available RPC methods
-
-**Key Controller Methods for CLI:**
-- `controller.initTask(prompt)` - Start a new task with prompt
-- `controller.task?.handleWebviewAskResponse('messageResponse', userInput)` - Send user input
-- `controller.task?.messageStateHandler.getClineMessages()` - Get conversation messages
-- `controller.cancelTask()` - Cancel current task
-- `controller.getStateToPostToWebview()` - Get full state (clineMessages, etc.)
-
-**Commands:**
-- `cline task chat` / `cline t c` - Interactive chat mode with embedded Controller
-- `cline task send [message] [options]` / `cline t s` - Send single message
-- `cline task view [--follow] [--follow-complete]` / `cline t v` - View/stream conversation
-
-**Files to create/modify:**
-- `cli-ts/src/core/embedded-controller.ts` - Initialize Controller in CLI process
-- `cli-ts/src/core/cli-webview-adapter.ts` - Adapter that outputs to terminal instead of webview
-- `cli-ts/src/commands/task/chat.ts` - Updated to use embedded Controller
-- `cli-ts/src/commands/task/send.ts` - Updated to use embedded Controller
-- `cli-ts/src/commands/task/view.ts` - Updated to use embedded Controller
-
-**Existing file to leverage:**
-- `cli-ts/src/core/host-provider-setup.ts` - Already sets up HostProvider for CLI
-
-**Options for task send:**
-- `-a, --approve` - Approve proposed action
-- `-d, --deny` - Deny proposed action
-- `-f, --file <FILE>` - Attach file
-- `-y, --no-interactive, --yolo` - Autonomous mode
-- `-m, --mode <mode>` - Switch mode
-
-**Options for task view:**
-- `-f, --follow` - Stream updates in real-time
-- `-c, --follow-complete` - Follow until completion
-
-**Implementation Steps:**
-1. Create `embedded-controller.ts` to initialize Controller using:
-   - `initializeContext()` from `src/standalone/vscode-context.ts`
-   - `setupHostProvider()` from `cli-ts/src/core/host-provider-setup.ts`
-   - Direct Controller import from `src/core/controller/index.ts`
-
-2. Create `cli-webview-adapter.ts` to handle state updates:
-   - Listen to `controller.task?.messageStateHandler` events
-   - Format ClineMessages for terminal output
-   - Handle streaming partial messages
-
-3. Update `chat.ts` to use embedded Controller:
-   - Initialize Controller on command start
-   - Send prompts via `controller.initTask(prompt)`
-   - Receive messages via state handler events
-   - Handle user input via `handleWebviewAskResponse()`
-
-4. Update `send.ts` and `view.ts` similarly
-
-**Tests:**
-- Chat mode provides REPL interface with real Controller
-- Messages stream to terminal in real-time
-- Approve/deny call correct Controller methods
-- State persists to ~/.cline/ and is readable by VSCode
-
----
-
-### 3.4 Task Control
-**Priority: Medium** | **Complexity: Medium**
-
-**Commands:**
-- `cline task restore <checkpoint>` / `cline t r`
-- `cline task pause` / `cline t p`
-
-**Files to create:**
-- `cli-ts/src/commands/task/restore.ts`
-- `cli-ts/src/commands/task/pause.ts`
-
-**Tests:**
-- Restore reverts to checkpoint
-- Pause suspends execution
-
----
-
-## Phase 4: Instant Task Mode
-
-### 4.1 Instant Task Shorthand
-**Priority: High** | **Complexity: Medium**
-
-Implement `cline "prompt"` instant task mode that combines instance + task + chat.
-
-**Modify:**
-- `cli-ts/src/index.ts` - Detect prompt argument and route to instant task
-
-**Options:**
-- `-o, --oneshot` - Complete and stop
-- `-s, --setting <key> <value>` - Override settings
-- `-y, --no-interactive, --yolo` - Autonomous mode
-- `-m, --mode <mode>` - Starting mode
-- `-w, --workspace <path>` - Additional workspace paths (can repeat)
-
-**Behavior:**
-1. Get or spawn default instance
-2. Create new task with prompt
-3. Enter chat mode (or oneshot if -o)
-
-**Tests:**
-- Instant task spawns instance if needed
-- Oneshot completes and exits
-- Workspace paths are passed correctly
-
----
-
-## Phase 5: Global Options Enhancement
-
-### 5.1 Address Flag
-**Priority: Medium** | **Complexity: Low**
-
-Add `-a, --address <ADDR>` global option to specify which Cline Core instance to use.
-
-**Modify:**
-- `cli-ts/src/index.ts` - Add --address option
-- All task commands to use address or default
-
----
-
-### 5.2 Verbose Flag Enhancement
-**Priority: Low** | **Complexity: Low**
-
-Enhance `-v, --verbose` to show debug output including gRPC communication details.
-
----
-
-## Implementation Order (Recommended)
-
-### Sprint 1: Foundation (Completed)
-1. [x] 1.1 Output Formatting System
-2. [x] 1.2 Configuration System
-3. [x] 2.1 Auth Command
-
-### Sprint 2: Instance Management (Deprecated)
-4. [x] 1.3 Instance Registry & Lifecycle (Deprecated, skipped)
-
-### Sprint 3: Task Basics (Completed)
-5. [x] 3.1 Task Command Group Base
-6. [x] 3.2 Task Creation & History
-
-### Sprint 4: Task Communication (✅ Complete)
-7. [x] 3.3 Task Communication (chat, send, view) - Embedded Controller architecture implemented
-
-### Sprint 5: Advanced Features
-8. [ ] 4.1 Instant Task Mode
-9. [ ] 3.4 Task Control
-10. [ ] 5.1 Address Flag
-11. [ ] 5.2 Verbose Flag Enhancement
-
----
-
-## File Structure Summary
-
-```
-cli-ts/
-├── src/
-│   ├── index.ts                    # Main entry (enhanced)
-│   ├── commands/
-│   │   ├── version.ts              # ✓ Complete
-│   │   ├── auth/
-│   │   │   └── index.ts
-│   │   ├── config/
-│   │   │   ├── index.ts
-│   │   │   ├── set.ts
-│   │   │   ├── get.ts
-│   │   │   └── list.ts
-│   │   ├── instance/
-│   │   │   ├── index.ts
-│   │   │   ├── new.ts
-│   │   │   ├── list.ts
-│   │   │   ├── default.ts
-│   │   │   └── kill.ts
-│   │   └── task/
-│   │       ├── index.ts
-│   │       ├── new.ts
-│   │       ├── list.ts
-│   │       ├── open.ts
-│   │       ├── chat.ts
-│   │       ├── send.ts
-│   │       ├── view.ts
-│   │       ├── restore.ts
-│   │       └── pause.ts
-│   ├── core/
-│   │   ├── config.ts               # ✓ Complete
-│   │   ├── logger.ts               # ✓ Complete
-│   │   ├── context.ts              # ✓ Complete
-│   │   ├── host-provider-setup.ts  # ✓ Complete
-│   │   ├── config-storage.ts       # NEW
-│   │   ├── instance-registry.ts    # NEW
-│   │   ├── instance-client.ts      # NEW
-│   │   ├── task-client.ts          # NEW
-│   │   ├── output/
-│   │   │   ├── formatter.ts
-│   │   │   ├── rich-formatter.ts
-│   │   │   ├── json-formatter.ts
-│   │   │   └── plain-formatter.ts
-│   │   └── auth/
-│   │       ├── providers.ts
-│   │       ├── wizard.ts
-│   │       └── oauth.ts
-│   └── types/
-│       ├── config.ts               # ✓ Complete
-│       ├── logger.ts               # ✓ Complete
-│       ├── task.ts                 # NEW
-│       └── message.ts              # NEW (ClineMessage)
-└── tests/
-    └── unit/
-        ├── commands/
-        │   └── version.test.ts     # ✓ Complete
-        ├── core/
-        │   ├── config.test.ts      # ✓ Complete
-        │   └── logger.test.ts      # ✓ Complete
-        └── ... (new tests for each module)
-```
-
----
-
-## Next Steps
-
-1. Start Sprint 3: Task Basics (Task Command Group Base + Task Creation & History)
-2. Follow with Sprint 4: Task Communication (chat/send/view)
-3. Finish with Sprint 5: Advanced Features (instant task mode, task control, address flag, verbose enhancement)
-
-The plan is designed so each phase delivers working functionality that can be tested independently before moving to the next phase.
-
-### New Task (Phase 3 Kickoff)
-**Objective:** Implement Task Command Group Base and Task Creation & History.
-
-**Planned files to create/modify:**
-- `cli-ts/src/commands/task/index.ts`
-- `cli-ts/src/core/task-client.ts`
-- `cli-ts/src/types/task.ts`
-- `cli-ts/src/commands/task/new.ts`
-- `cli-ts/src/commands/task/list.ts`
-- `cli-ts/src/commands/task/open.ts`
-- Update `cli-ts/src/index.ts` to register the task command group
-
-**Test requirements:**
-- New task creates task in instance
-- List shows task history with IDs and snippets
-- Open resumes task with saved settings

cli-ts/esbuild.mjs

@@ -1,305 +0,0 @@
-import fs from "node:fs"
-import path from "node:path"
-import { fileURLToPath } from "node:url"
-import * as esbuild from "esbuild"
-
-const __filename = fileURLToPath(import.meta.url)
-const __dirname = path.dirname(__filename)
-const rootDir = path.resolve(__dirname, "..")
-
-const production = process.argv.includes("--production")
-const watch = process.argv.includes("--watch")
-
-/**
- * Alias resolver plugin - resolves path aliases from tsconfig.json
- * This is adapted from the root esbuild.mjs to work with the CLI's directory structure
- * @type {import('esbuild').Plugin}
- */
-/**
- * Plugin to resolve 'vscode' imports to the standalone shim
- * The shim provides stub implementations for vscode APIs in standalone mode
- * @type {import('esbuild').Plugin}
- */
-const vscodeShimPlugin = {
-	name: "vscode-shim",
-	setup(build) {
-		const vscodeShimPath = path.resolve(rootDir, "standalone/runtime-files/vscode/index.js")
-
-		// Resolve 'vscode' to our virtual shim entry
-		build.onResolve({ filter: /^vscode$/ }, () => {
-			return {
-				path: vscodeShimPath,
-				// Use sideEffects: false to avoid issues with initialization order
-			}
-		})
-
-		// The vscode-stubs.js uses implicit global assignment (vscode = {})
-		// which fails in strict mode. We need to load it without strict mode
-		// by marking it and its dependencies as external
-		build.onLoad({ filter: /vscode-stubs\.js$/ }, async (args) => {
-			const contents = fs.readFileSync(args.path, "utf8")
-			// Wrap the contents to declare vscode as a local variable
-			return {
-				contents: `var vscode;\n${contents}`,
-				loader: "js",
-			}
-		})
-	},
-}
-
-const aliasResolverPlugin = {
-	name: "alias-resolver",
-	setup(build) {
-		// Aliases point to the root src directory (parent of cli-ts)
-		const aliases = {
-			"@": path.resolve(rootDir, "src"),
-			"@core": path.resolve(rootDir, "src/core"),
-			"@integrations": path.resolve(rootDir, "src/integrations"),
-			"@services": path.resolve(rootDir, "src/services"),
-			"@shared": path.resolve(rootDir, "src/shared"),
-			"@utils": path.resolve(rootDir, "src/utils"),
-			"@packages": path.resolve(rootDir, "src/packages"),
-			"@hosts": path.resolve(rootDir, "src/hosts"),
-			"@generated": path.resolve(rootDir, "src/generated"),
-			"@api": path.resolve(rootDir, "src/core/api"),
-			// CLI-specific aliases
-			"@cli": path.resolve(__dirname, "src"),
-		}
-
-		// For each alias entry, create a resolver
-		Object.entries(aliases).forEach(([alias, aliasPath]) => {
-			const aliasRegex = new RegExp(`^${alias}($|/.*)`)
-			build.onResolve({ filter: aliasRegex }, (args) => {
-				const importPath = args.path.replace(alias, aliasPath)
-
-				// First, check if the path exists as is
-				if (fs.existsSync(importPath)) {
-					const stats = fs.statSync(importPath)
-					if (stats.isDirectory()) {
-						// If it's a directory, try to find index files
-						const extensions = [".ts", ".tsx", ".js", ".jsx"]
-						for (const ext of extensions) {
-							const indexFile = path.join(importPath, `index${ext}`)
-							if (fs.existsSync(indexFile)) {
-								return { path: indexFile }
-							}
-						}
-					} else {
-						// It's a file that exists, so return it
-						return { path: importPath }
-					}
-				}
-
-				// If the path doesn't exist, try appending extensions
-				const extensions = [".ts", ".tsx", ".js", ".jsx"]
-				for (const ext of extensions) {
-					const pathWithExtension = `${importPath}${ext}`
-					if (fs.existsSync(pathWithExtension)) {
-						return { path: pathWithExtension }
-					}
-				}
-
-				// If nothing worked, return the original path and let esbuild handle the error
-				return { path: importPath }
-			})
-		})
-	},
-}
-
-/**
- * Problem matcher plugin for watch mode
- */
-const esbuildProblemMatcherPlugin = {
-	name: "esbuild-problem-matcher",
-	setup(build) {
-		build.onStart(() => {
-			console.log("[watch] build started")
-		})
-		build.onEnd((result) => {
-			result.errors.forEach(({ text, location }) => {
-				console.error(`✘ [ERROR] ${text}`)
-				if (location) {
-					console.error(`    ${location.file}:${location.line}:${location.column}:`)
-				}
-			})
-			console.log("[watch] build finished")
-		})
-	},
-}
-
-/**
- * Plugin to copy tree-sitter WASM files to dist directory
- * These are required at runtime for code parsing functionality
- * @type {import('esbuild').Plugin}
- */
-const copyWasmFiles = {
-	name: "copy-wasm-files",
-	setup(build) {
-		build.onEnd(() => {
-			const targetDir = path.resolve(__dirname, "dist")
-
-			// Copy tree-sitter.wasm from web-tree-sitter
-			const treeSitterSource = path.join(rootDir, "node_modules", "web-tree-sitter", "tree-sitter.wasm")
-			if (fs.existsSync(treeSitterSource)) {
-				fs.copyFileSync(treeSitterSource, path.join(targetDir, "tree-sitter.wasm"))
-			} else {
-				console.warn("Warning: tree-sitter.wasm not found in node_modules/web-tree-sitter")
-			}
-
-			// Copy language-specific WASM files from tree-sitter-wasms
-			const languageWasmDir = path.join(rootDir, "node_modules", "tree-sitter-wasms", "out")
-			const languages = [
-				"typescript",
-				"tsx",
-				"python",
-				"rust",
-				"javascript",
-				"go",
-				"cpp",
-				"c",
-				"c_sharp",
-				"ruby",
-				"java",
-				"php",
-				"swift",
-				"kotlin",
-			]
-
-			if (fs.existsSync(languageWasmDir)) {
-				languages.forEach((lang) => {
-					const filename = `tree-sitter-${lang}.wasm`
-					const sourcePath = path.join(languageWasmDir, filename)
-					if (fs.existsSync(sourcePath)) {
-						fs.copyFileSync(sourcePath, path.join(targetDir, filename))
-					}
-				})
-			} else {
-				console.warn("Warning: tree-sitter-wasms/out directory not found")
-			}
-		})
-	},
-}
-
-// Read package.json for version injection
-const rootPackageJson = JSON.parse(fs.readFileSync(path.resolve(rootDir, "package.json"), "utf8"))
-
-// Build environment variables
-const buildEnvVars = {
-	"import.meta.url": "_importMetaUrl",
-	"process.env.IS_STANDALONE": JSON.stringify("true"),
-	// Inject the Cline version at build time to avoid runtime package.json loading
-	__CLINE_VERSION__: JSON.stringify(rootPackageJson.version),
-}
-
-if (production) {
-	buildEnvVars["process.env.IS_DEV"] = "false"
-}
-
-/**
- * Plugin to handle package.json requires by bundling them inline
- * This handles JSON files that may have broken relative paths after bundling
- * @type {import('esbuild').Plugin}
- */
-const jsonResolverPlugin = {
-	name: "json-resolver",
-	setup(build) {
-		// Handle requires to package.json files by resolving and loading them inline
-		build.onResolve({ filter: /\.json$/ }, (args) => {
-			// Only handle relative paths
-			if (args.path.startsWith(".")) {
-				const resolvedPath = path.resolve(args.resolveDir, args.path)
-				if (fs.existsSync(resolvedPath)) {
-					return {
-						path: resolvedPath,
-						namespace: "json-inline",
-					}
-				}
-			}
-			return null
-		})
-
-		// Load JSON files and emit them as CommonJS modules with the JSON data
-		build.onLoad({ filter: /.*/, namespace: "json-inline" }, (args) => {
-			const contents = fs.readFileSync(args.path, "utf8")
-			return {
-				contents: `module.exports = ${contents}`,
-				loader: "js",
-			}
-		})
-	},
-}
-
-// CLI-specific configuration
-const cliConfig = {
-	entryPoints: [path.resolve(__dirname, "src/index.ts")],
-	outfile: path.resolve(__dirname, "dist/index.cjs"),
-	bundle: true,
-	minify: production,
-	sourcemap: !production,
-	logLevel: "silent",
-	define: buildEnvVars,
-	tsconfig: path.resolve(__dirname, "tsconfig.json"),
-	plugins: [vscodeShimPlugin, jsonResolverPlugin, aliasResolverPlugin, copyWasmFiles, esbuildProblemMatcherPlugin],
-	format: "cjs",
-	sourcesContent: false,
-	platform: "node",
-	loader: {
-		".json": "json", // Bundle JSON files inline
-	},
-	banner: {
-		js: "const _importMetaUrl=require('url').pathToFileURL(__filename)",
-	},
-	// These modules need to load files from the module directory at runtime,
-	// so they cannot be bundled. Note: vscode is handled by vscodeShimPlugin
-	// @vscode/ripgrep provides platform-specific binaries that must be resolved at runtime
-	external: ["@grpc/reflection", "grpc-health-check", "better-sqlite3", "@vscode/ripgrep"],
-}
-
-/**
- * Copy runtime files needed for standalone mode
- * The vscode-context.ts expects package.json at INSTALL_DIR/extension/package.json
- */
-async function copyRuntimeFiles() {
-	const extensionDir = path.resolve(__dirname, "dist/extension")
-
-	// Create extension directory
-	if (!fs.existsSync(extensionDir)) {
-		fs.mkdirSync(extensionDir, { recursive: true })
-	}
-
-	// Copy package.json from standalone/runtime-files to dist/extension
-	const sourcePackageJson = path.resolve(rootDir, "standalone/runtime-files/package.json")
-	const destPackageJson = path.resolve(extensionDir, "package.json")
-
-	if (fs.existsSync(sourcePackageJson)) {
-		fs.copyFileSync(sourcePackageJson, destPackageJson)
-	} else {
-		console.warn(`Warning: ${sourcePackageJson} not found, creating minimal package.json`)
-		// Fallback: create a minimal package.json with version from root
-		const minimalPackageJson = {
-			name: "cline",
-			version: rootPackageJson.version,
-			displayName: "Cline",
-		}
-		fs.writeFileSync(destPackageJson, JSON.stringify(minimalPackageJson, null, 2))
-	}
-}
-
-async function main() {
-	const ctx = await esbuild.context(cliConfig)
-	if (watch) {
-		await ctx.watch()
-		await copyRuntimeFiles()
-		console.log("Watching for changes...")
-	} else {
-		await ctx.rebuild()
-		await copyRuntimeFiles()
-		await ctx.dispose()
-		console.log("Build completed successfully!")
-	}
-}
-
-main().catch((e) => {
-	console.error(e)
-	process.exit(1)
-})

cli-ts/package.json

@@ -1,45 +0,0 @@
-{
-	"name": "@cline/cli",
-	"version": "1.0.0",
-	"description": "Cline CLI - Command-line interface for Cline AI assistant",
-	"main": "dist/index.cjs",
-	"bin": {
-		"clt": "./dist/index.cjs"
-	},
-	"type": "module",
-	"scripts": {
-		"build": "node esbuild.mjs",
-		"build:watch": "node esbuild.mjs --watch",
-		"build:prod": "node esbuild.mjs --production",
-		"start": "node dist/index.cjs",
-		"dev": "node esbuild.mjs && node dist/index.cjs",
-		"test": "mocha",
-		"test:watch": "mocha --watch",
-		"test:coverage": "c8 mocha"
-	},
-	"dependencies": {
-		"@vscode/ripgrep": "^1.15.9",
-		"chalk": "^5.3.0",
-		"commander": "^12.1.0",
-		"marked": "^15.0.12",
-		"marked-terminal": "^7.3.0"
-	},
-	"devDependencies": {
-		"@types/chai": "^4.3.16",
-		"@types/marked-terminal": "^6.1.1",
-		"@types/mocha": "^10.0.7",
-		"@types/node": "^20.14.10",
-		"@types/sinon": "^17.0.3",
-		"c8": "^10.1.2",
-		"chai": "^4.4.1",
-		"esbuild": "^0.27.0",
-		"mocha": "^10.6.0",
-		"sinon": "^17.0.1",
-		"tsconfig-paths": "^4.2.0",
-		"tsx": "^4.16.2",
-		"typescript": "^5.5.3"
-	},
-	"engines": {
-		"node": ">=20.0.0"
-	}
-}

cli-ts/src/commands/config/index.ts

@@ -1,290 +0,0 @@
-/**
- * Config command group - manage persistent CLI configuration
- *
- * This command uses Cline's StateManager to read/write settings directly,
- * ensuring CLI config changes are reflected in the extension and vice versa.
- */
-
-import { Command } from "commander"
-import { disposeEmbeddedController, getEmbeddedController } from "../../core/embedded-controller.js"
-import type { OutputFormatter } from "../../core/output/types.js"
-import type { CliConfig } from "../../types/config.js"
-import type { Logger } from "../../types/logger.js"
-
-/**
- * Parse a string value into the appropriate type based on the key
- */
-export function parseValue(key: string, value: string): unknown {
-	// Handle boolean values
-	const lowerValue = value.toLowerCase()
-	if (lowerValue === "true" || lowerValue === "1" || lowerValue === "yes") {
-		return true
-	}
-	if (lowerValue === "false" || lowerValue === "0" || lowerValue === "no") {
-		return false
-	}
-
-	// Try to parse as JSON (for arrays and objects)
-	const trimmed = value.trim()
-	if ((trimmed.startsWith("[") && trimmed.endsWith("]")) || (trimmed.startsWith("{") && trimmed.endsWith("}"))) {
-		try {
-			return JSON.parse(value)
-		} catch {
-			// If JSON parsing fails, fall through to other parsing
-		}
-	}
-
-	// Handle numeric values - try to parse as number
-	const numValue = Number(value)
-	if (!Number.isNaN(numValue) && value.trim() !== "") {
-		return numValue
-	}
-
-	// Default: return as string
-	return value
-}
-
-/**
- * Get a nested value from an object using dot notation
- * e.g., getNestedValue(obj, "browserSettings.viewport.width")
- */
-export function getNestedValue(obj: Record<string, unknown>, path: string): unknown {
-	const parts = path.split(".")
-	let current: unknown = obj
-
-	for (const part of parts) {
-		if (current === null || current === undefined || typeof current !== "object") {
-			return undefined
-		}
-		current = (current as Record<string, unknown>)[part]
-	}
-
-	return current
-}
-
-/**
- * Set a nested value in an object using dot notation
- * e.g., setNestedValue(obj, "browserSettings.viewport.width", 1200)
- * Returns the modified root object for the top-level key
- */
-export function setNestedValue(
-	obj: Record<string, unknown>,
-	path: string,
-	value: unknown,
-): { rootKey: string; rootValue: unknown } {
-	const parts = path.split(".")
-	const rootKey = parts[0]
-
-	if (parts.length === 1) {
-		// Simple case: top-level key
-		return { rootKey, rootValue: value }
-	}
-
-	// Clone the root object to avoid mutating the original
-	const rootValue = JSON.parse(JSON.stringify(obj[rootKey] ?? {}))
-
-	// Navigate to the parent of the target, creating objects as needed
-	let current = rootValue as Record<string, unknown>
-	for (let i = 1; i < parts.length - 1; i++) {
-		const part = parts[i]
-		if (current[part] === undefined || current[part] === null || typeof current[part] !== "object") {
-			current[part] = {}
-		}
-		current = current[part] as Record<string, unknown>
-	}
-
-	// Set the final value
-	current[parts[parts.length - 1]] = value
-	return { rootKey, rootValue }
-}
-
-/**
- * Create the config set command
- */
-function createConfigSetCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	return new Command("set")
-		.description("Set a configuration value (supports dot notation for nested values, e.g., browserSettings.viewport.width)")
-		.argument("<key>", "Configuration key to set")
-		.argument("<value>", "Value to set")
-		.action(async (key: string, value: string) => {
-			logger.debug(`Setting config: ${key} = ${value}`)
-
-			try {
-				// Initialize embedded controller to access StateManager
-				const controller = await getEmbeddedController(logger, config.configDir)
-
-				// Parse value to appropriate type
-				const parsedValue = parseValue(key, value)
-
-				// Check if this is a nested path
-				if (key.includes(".")) {
-					// For nested paths, get the current root object, modify it, and save the whole thing
-					const rootKey = key.split(".")[0]
-					let rootValue = controller.stateManager.getGlobalSettingsKey(rootKey as any)
-					if (rootValue === undefined) {
-						rootValue = controller.stateManager.getGlobalStateKey(rootKey as any)
-					}
-
-					// Build the updated root object
-					const currentRoot = rootValue !== undefined && typeof rootValue === "object" ? rootValue : {}
-					const { rootValue: newRootValue } = setNestedValue({ [rootKey]: currentRoot }, key, parsedValue)
-
-					// Save the updated root object
-					controller.stateManager.setGlobalState(rootKey as any, newRootValue as any)
-				} else {
-					// Simple top-level key
-					controller.stateManager.setGlobalState(key as any, parsedValue as any)
-				}
-
-				// Flush pending state to ensure changes are persisted before exit
-				await controller.stateManager.flushPendingState()
-
-				formatter.success(`Set ${key} = ${String(parsedValue)}`)
-
-				// Cleanup and exit
-				await disposeEmbeddedController(logger)
-				process.exit(0)
-			} catch (err) {
-				formatter.error(err as Error)
-				await disposeEmbeddedController(logger)
-				process.exit(1)
-			}
-		})
-}
-
-/**
- * Create the config get command
- */
-function createConfigGetCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	return new Command("get")
-		.description("Get a configuration value (supports dot notation for nested values, e.g., browserSettings.viewport.width)")
-		.argument("<key>", "Configuration key to get")
-		.action(async (key: string) => {
-			logger.debug(`Getting config: ${key}`)
-
-			try {
-				// Initialize embedded controller to access StateManager
-				const controller = await getEmbeddedController(logger, config.configDir)
-
-				let value: unknown
-
-				// Check if this is a nested path
-				if (key.includes(".")) {
-					// For nested paths, get the root object first
-					const rootKey = key.split(".")[0]
-					let rootValue = controller.stateManager.getGlobalSettingsKey(rootKey as any)
-					if (rootValue === undefined) {
-						rootValue = controller.stateManager.getGlobalStateKey(rootKey as any)
-					}
-
-					if (rootValue !== undefined && typeof rootValue === "object") {
-						// Get the nested value
-						value = getNestedValue({ [rootKey]: rootValue }, key)
-					}
-				} else {
-					// Simple top-level key
-					value = controller.stateManager.getGlobalSettingsKey(key as any)
-					if (value === undefined) {
-						value = controller.stateManager.getGlobalStateKey(key as any)
-					}
-				}
-
-				if (value === undefined) {
-					formatter.info(`${key} is not set`)
-				} else {
-					// Format objects/arrays as JSON for display
-					const displayValue = typeof value === "object" ? JSON.stringify(value, null, 2) : value
-					formatter.keyValue({ [key]: displayValue })
-				}
-
-				// Cleanup and exit
-				await disposeEmbeddedController(logger)
-				process.exit(0)
-			} catch (err) {
-				formatter.error(err as Error)
-				await disposeEmbeddedController(logger)
-				process.exit(1)
-			}
-		})
-}
-
-/**
- * Create the config list command
- */
-function createConfigListCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	return new Command("list").description("List all configuration values").action(async () => {
-		logger.debug("Listing all config")
-
-		try {
-			// Read the globalState.json file directly to get all settings
-			const fs = await import("fs")
-			const path = await import("path")
-			const globalStatePath = path.join(config.configDir || `${process.env.HOME}/.cline`, "data", "globalState.json")
-
-			let allSettings: Record<string, unknown> = {}
-			if (fs.existsSync(globalStatePath)) {
-				const content = fs.readFileSync(globalStatePath, "utf-8")
-				allSettings = JSON.parse(content)
-			}
-
-			formatter.raw("")
-			formatter.raw(JSON.stringify(allSettings, null, 2))
-			formatter.raw("")
-
-			// Cleanup and exit
-			process.exit(0)
-		} catch (err) {
-			formatter.error(err as Error)
-			process.exit(1)
-		}
-	})
-}
-
-/**
- * Create the config delete command
- */
-function createConfigDeleteCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	return new Command("delete")
-		.alias("rm")
-		.description("Delete a configuration value (reset to default)")
-		.argument("<key>", "Configuration key to delete")
-		.action(async (key: string) => {
-			logger.debug(`Deleting config: ${key}`)
-
-			try {
-				// Initialize embedded controller to access StateManager
-				const controller = await getEmbeddedController(logger, config.configDir)
-
-				// Set the value to undefined to reset to default
-				// Using type assertion since key is dynamic
-				controller.stateManager.setGlobalState(key as any, undefined)
-
-				// Flush pending state to ensure changes are persisted before exit
-				await controller.stateManager.flushPendingState()
-
-				formatter.success(`Reset ${key} to default`)
-
-				// Cleanup and exit
-				await disposeEmbeddedController(logger)
-				process.exit(0)
-			} catch (err) {
-				formatter.error(err as Error)
-				await disposeEmbeddedController(logger)
-				process.exit(1)
-			}
-		})
-}
-
-/**
- * Create the config command group
- */
-export function createConfigCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	const configCommand = new Command("config").alias("c").description("Manage CLI configuration")
-
-	configCommand.addCommand(createConfigSetCommand(config, logger, formatter))
-	configCommand.addCommand(createConfigGetCommand(config, logger, formatter))
-	configCommand.addCommand(createConfigListCommand(config, logger, formatter))
-	configCommand.addCommand(createConfigDeleteCommand(config, logger, formatter))
-
-	return configCommand
-}

cli-ts/src/commands/task/chat/command.ts

@@ -1,124 +0,0 @@
-/**
- * Task chat command - interactive REPL mode with embedded Controller
- *
- * This command provides an interactive chat interface using Cline's
- * embedded Controller, allowing real-time AI interactions directly
- * from the terminal.
- */
-
-import { Command } from "commander"
-import { disposeEmbeddedController, getEmbeddedController } from "../../../core/embedded-controller.js"
-import type { OutputFormatter } from "../../../core/output/types.js"
-import { parseAtPaths, processExplicitFiles, processExplicitImages } from "../../../core/path-parser.js"
-import type { CliConfig } from "../../../types/config.js"
-import type { Logger } from "../../../types/logger.js"
-import { startRepl } from "./repl.js"
-import { createSession } from "./session.js"
-
-/**
- * Collect multiple option values into an array
- * Used for -f and -i options that can be specified multiple times
- */
-function collectOption(value: string, previous: string[]): string[] {
-	return previous.concat([value])
-}
-
-/**
- * Create the task chat command
- */
-export function createTaskChatCommand(config: CliConfig, logger: Logger, formatter: OutputFormatter): Command {
-	const chatCommand = new Command("chat")
-		.alias("c")
-		.description("Interactive chat mode with embedded Cline Controller")
-		.argument("[prompt]", "Initial prompt to start a new task (optional)")
-		.option("-m, --mode <mode>", "Start in specific mode: act or plan")
-		.option("-t, --task <id>", "Resume an existing task by ID")
-		.option("-f, --file <path>", "Attach file to initial prompt (can be repeated)", collectOption, [])
-		.option("-i, --image <path>", "Attach image to initial prompt (can be repeated)", collectOption, [])
-		.option("-y, --yolo", "Enable autonomous mode (no confirmations)", false)
-		.action(async (promptArg: string | undefined, options) => {
-			logger.debug("Task chat command called", { promptArg, options })
-
-			try {
-				// Process explicit file and image attachments from CLI options
-				const cwd = process.cwd()
-				let initialFiles: string[] = []
-				let initialImages: string[] = []
-
-				// Process -f/--file options (can be files or images, auto-detected)
-				if (options.file && options.file.length > 0) {
-					const processed = processExplicitFiles(options.file, cwd)
-					initialFiles = processed.files
-					initialImages = processed.images
-				}
-
-				// Process -i/--image options (must be images)
-				if (options.image && options.image.length > 0) {
-					const images = processExplicitImages(options.image, cwd)
-					initialImages = initialImages.concat(images)
-				}
-
-				// Parse @path references from the initial prompt if provided
-				let processedPrompt = promptArg
-				if (promptArg) {
-					const parsed = parseAtPaths(promptArg, cwd)
-
-					// Show warnings for any files that couldn't be processed
-					for (const warning of parsed.warnings) {
-						formatter.warn(warning)
-					}
-
-					processedPrompt = parsed.cleanedMessage
-					initialFiles = initialFiles.concat(parsed.files)
-					initialImages = initialImages.concat(parsed.images)
-				}
-
-				// Initialize embedded controller
-				const controller = await getEmbeddedController(logger, config.configDir)
-
-				// Set up mode if specified
-				if (options.mode) {
-					if (options.mode !== "plan" && options.mode !== "act") {
-						throw new Error(`Invalid mode: "${options.mode}". Valid options are: act, plan`)
-					}
-					await controller.togglePlanActMode(options.mode as "plan" | "act")
-				}
-
-				if (options.yolo) {
-					controller.stateManager.setGlobalState("yoloModeToggled", true)
-					// Increase mistake limit for autonomous operation (matches Go CLI behavior)
-					controller.stateManager.setGlobalState("maxConsecutiveMistakes", 6)
-					// Ensure we're in Act mode for autonomous execution (unless user explicitly chose Plan mode)
-					if (!options.mode) {
-						await controller.togglePlanActMode("act")
-					}
-				}
-
-				// Create chat session with yolo mode if specified
-				const session = createSession(options.yolo)
-
-				if (options.yolo) {
-					formatter.info("[YOLO] Autonomous mode enabled - no confirmations required")
-				}
-
-				// Start the REPL
-				await startRepl({
-					session,
-					controller,
-					formatter,
-					logger,
-					config,
-					initialPrompt: processedPrompt,
-					initialImages: initialImages.length > 0 ? initialImages : undefined,
-					initialFiles: initialFiles.length > 0 ? initialFiles : undefined,
-					resumeTaskId: options.task,
-				})
-			} catch (error) {
-				formatter.error((error as Error).message)
-				await disposeEmbeddedController(logger)
-				process.exit(1)
-			}
-		})
-
-	return chatCommand
-}

cli-ts/src/commands/task/chat/completer.ts

@@ -1,199 +0,0 @@
-/**
- * Tab completion for @ file/folder mentions in chat REPL
- *
- * Provides file and folder path completion when users type @ followed by a partial path.
- */
-
-import fs from "fs"
-import path from "path"
-
-/**
- * Result of finding an @ mention to complete
- */
-interface AtMentionMatch {
-	/** The text before the @ mention (to preserve in completion) */
-	prefix: string
-	/** The partial path after @ that needs completion */
-	partial: string
-	/** Character index where the @ starts */
-	atIndex: number
-}
-
-/**
- * Find the @ mention being completed in the input line
- *
- * Handles multiple @ mentions by finding the last one that appears
- * to be incomplete (user is still typing it).
- */
-function findAtMentionToComplete(line: string): AtMentionMatch | null {
-	// Find the last @ that could be a file mention
-	// We look for @ that's either at start or preceded by whitespace
-	let atIndex = -1
-	for (let i = line.length - 1; i >= 0; i--) {
-		if (line[i] === "@") {
-			// Check if it's at start or preceded by whitespace
-			if (i === 0 || /\s/.test(line[i - 1])) {
-				atIndex = i
-				break
-			}
-		}
-	}
-
-	if (atIndex === -1) {
-		return null
-	}
-
-	// Extract the partial path after @
-	const afterAt = line.slice(atIndex + 1)
-
-	// If there's whitespace after @, this mention is complete, not being typed
-	if (/\s/.test(afterAt)) {
-		return null
-	}
-
-	return {
-		prefix: line.slice(0, atIndex),
-		partial: afterAt,
-		atIndex,
-	}
-}
-
-/**
- * Get completions for a partial file/folder path
- */
-function getPathCompletions(partial: string, cwd: string): string[] {
-	try {
-		// Determine the directory to search and the prefix to match
-		let searchDir: string
-		let namePrefix: string
-
-		if (partial === "") {
-			// Empty partial - list cwd contents
-			searchDir = cwd
-			namePrefix = ""
-		} else if (partial.endsWith("/")) {
-			// Ends with / - list that directory's contents
-			searchDir = path.resolve(cwd, partial)
-			namePrefix = ""
-		} else {
-			// Partial filename - list parent directory and filter
-			const partialPath = path.resolve(cwd, partial)
-			searchDir = path.dirname(partialPath)
-			namePrefix = path.basename(partial)
-		}
-
-		// Check if directory exists
-		if (!fs.existsSync(searchDir) || !fs.statSync(searchDir).isDirectory()) {
-			return []
-		}
-
-		// Read directory contents
-		const entries = fs.readdirSync(searchDir, { withFileTypes: true })
-
-		// Filter and map entries
-		const completions: string[] = []
-		for (const entry of entries) {
-			// Skip hidden files unless explicitly searching for them
-			if (entry.name.startsWith(".") && !namePrefix.startsWith(".")) {
-				continue
-			}
-
-			// Check if name matches prefix
-			if (!entry.name.toLowerCase().startsWith(namePrefix.toLowerCase())) {
-				continue
-			}
-
-			// Build the completion path
-			let completionPath: string
-			if (partial === "") {
-				completionPath = entry.name
-			} else if (partial.endsWith("/")) {
-				completionPath = partial + entry.name
-			} else {
-				// Replace the partial filename with the full name
-				const dirPart = partial.slice(0, partial.length - namePrefix.length)
-				completionPath = dirPart + entry.name
-			}
-
-			// Append / for directories
-			if (entry.isDirectory()) {
-				completionPath += "/"
-			}
-
-			completions.push(completionPath)
-		}
-
-		// Sort: directories first, then alphabetically
-		completions.sort((a, b) => {
-			const aIsDir = a.endsWith("/")
-			const bIsDir = b.endsWith("/")
-			if (aIsDir && !bIsDir) return -1
-			if (!aIsDir && bIsDir) return 1
-			return a.localeCompare(b)
-		})
-
-		return completions
-	} catch {
-		// If anything goes wrong, return no completions
-		return []
-	}
-}
-
-/**
- * Options for creating a completer
- */
-export interface CompleterOptions {
-	/** The current working directory for path resolution */
-	cwd: string
-	/** Callback invoked when Tab is pressed on an empty line */
-	onEmptyTab?: () => void
-}
-
-/**
- * Create a readline completer function for @ file mentions
- *
- * Also supports triggering a callback when Tab is pressed on an empty line,
- * which is used for mode toggling.
- *
- * @param options - Completer options including cwd and callbacks
- * @returns A completer function compatible with readline
- */
-export function createCompleter(options: CompleterOptions): (line: string) => [string[], string] {
-	const { cwd, onEmptyTab } = options
-
-	return (line: string): [string[], string] => {
-		// Check for empty input - trigger mode toggle callback if provided
-		if (line === "" && onEmptyTab) {
-			onEmptyTab()
-			return [[], line]
-		}
-
-		const match = findAtMentionToComplete(line)
-
-		if (!match) {
-			// No @ mention being typed - no completions
-			return [[], line]
-		}
-
-		const pathCompletions = getPathCompletions(match.partial, cwd)
-
-		if (pathCompletions.length === 0) {
-			return [[], line]
-		}
-
-		// Build full line completions (prefix + @ + completed path)
-		const fullCompletions = pathCompletions.map((p) => `${match.prefix}@${p}`)
-
-		// The "substring" is what readline uses to determine what to replace
-		// We want to replace from the @ onwards
-		const substring = `@${match.partial}`
-
-		// Return format: [completions, substring being completed]
-		// If there's only one completion, readline will auto-complete
-		// If multiple, it will show them as options
-		return [fullCompletions, line]
-	}
-}
-
-// Export for testing
-export { findAtMentionToComplete, getPathCompletions }

cli-ts/src/commands/task/chat/index.ts

@@ -1,13 +0,0 @@
-/**
- * Chat command module
- *
- * Re-exports the main command factory for backward compatibility.
- */
-
-export { createTaskChatCommand } from "./command.js"
-
-// Also export utilities for testing
-export { checkForPendingInput, isCompletionState, isFailureState, type PendingInputState } from "./input-checker.js"
-export { getModelIdForProvider, getModelIdKey } from "./model-utils.js"
-export { buildPromptString } from "./prompt.js"
-export { type ChatSession, createSession } from "./session.js"

cli-ts/src/commands/task/chat/input-checker.ts

@@ -1,168 +0,0 @@
-/**
- * Input state checker for chat REPL
- *
- * Analyzes message history to determine if user input is needed.
- */
-
-import type { ClineMessage, ClineSayTool } from "@shared/ExtensionMessage"
-
-/**
- * Auto-approval action keys that can be enabled for "don't ask again" functionality
- */
-export type AutoApprovalAction = "readFiles" | "editFiles" | "executeAllCommands" | "useBrowser" | "useMcp"
-
-/**
- * Result of checking for pending input
- */
-export interface PendingInputState {
-	awaitingApproval: boolean
-	awaitingInput: boolean
-}
-
-/**
- * Check if the last message requires user input
- */
-export function checkForPendingInput(messages: ClineMessage[]): PendingInputState {
-	if (messages.length === 0) {
-		return { awaitingApproval: false, awaitingInput: false }
-	}
-
-	const lastMessage = messages[messages.length - 1]
-
-	// Skip partial messages
-	if (lastMessage.partial) {
-		return { awaitingApproval: false, awaitingInput: false }
-	}
-
-	// Check if this is an "ask" type message
-	if (lastMessage.type === "ask") {
-		const ask = lastMessage.ask
-
-		// These require approval (yes/no response)
-		const approvalAsks = ["command", "tool", "browser_action_launch", "use_mcp_server"]
-
-		// These require free-form input
-		const inputAsks = ["followup", "plan_mode_respond", "act_mode_respond"]
-
-		if (approvalAsks.includes(ask || "")) {
-			return { awaitingApproval: true, awaitingInput: false }
-		}
-
-		if (inputAsks.includes(ask || "")) {
-			return { awaitingApproval: false, awaitingInput: true }
-		}
-
-		// Special cases
-		if (ask === "api_req_failed") {
-			return { awaitingApproval: true, awaitingInput: false }
-		}
-
-		if (ask === "completion_result" || ask === "resume_task" || ask === "resume_completed_task") {
-			return { awaitingApproval: false, awaitingInput: true }
-		}
-	}
-
-	return { awaitingApproval: false, awaitingInput: false }
-}
-
-/**
- * Check if the last message indicates a failure state (for yolo mode)
- */
-export function isFailureState(messages: ClineMessage[]): { isFailure: boolean; actionKey: string | null } {
-	if (messages.length === 0) {
-		return { isFailure: false, actionKey: null }
-	}
-
-	const lastMessage = messages[messages.length - 1]
-
-	// Skip partial messages
-	if (lastMessage.partial) {
-		return { isFailure: false, actionKey: null }
-	}
-
-	// Check for failure indicators
-	if (
-		lastMessage.ask === "api_req_failed" ||
-		lastMessage.ask === "mistake_limit_reached" ||
-		lastMessage.say === "error" ||
-		lastMessage.say === "diff_error"
-	) {
-		// Use the message text as the action key for tracking consecutive failures
-		const actionKey = lastMessage.text || lastMessage.ask || lastMessage.say || "unknown"
-		return { isFailure: true, actionKey }
-	}
-
-	return { isFailure: false, actionKey: null }
-}
-
-/**
- * Check if the last message indicates task completion (for yolo mode)
- */
-export function isCompletionState(messages: ClineMessage[]): boolean {
-	if (messages.length === 0) {
-		return false
-	}
-
-	const lastMessage = messages[messages.length - 1]
-
-	// Skip partial messages
-	if (lastMessage.partial) {
-		return false
-	}
-
-	return lastMessage.ask === "completion_result" || lastMessage.say === "completion_result"
-}
-
-/**
- * Determine which auto-approval action to enable based on the ask message
- *
- * @param msg - The pending ask message
- * @returns The auto-approval action key, or null if not applicable
- */
-export function determineAutoApprovalAction(msg: ClineMessage): AutoApprovalAction | null {
-	const ask = msg.ask
-
-	switch (ask) {
-		case "tool": {
-			// Parse tool message to determine if it's a read or edit operation
-			if (!msg.text) {
-				return null
-			}
-			try {
-				const tool = JSON.parse(msg.text) as ClineSayTool
-				switch (tool.tool) {
-					case "readFile":
-					case "listFilesTopLevel":
-					case "listFilesRecursive":
-					case "listCodeDefinitionNames":
-					case "searchFiles":
-					case "webFetch":
-					case "webSearch":
-						return "readFiles"
-					case "editedExistingFile":
-					case "newFileCreated":
-						return "editFiles"
-					case "fileDeleted":
-						// File deletion uses editFiles permission
-						return "editFiles"
-					default:
-						return null
-				}
-			} catch {
-				return null
-			}
-		}
-
-		case "command":
-			return "executeAllCommands"
-
-		case "browser_action_launch":
-			return "useBrowser"
-
-		case "use_mcp_server":
-			return "useMcp"
-
-		default:
-			return null
-	}
-}

cli-ts/src/commands/task/chat/model-utils.ts

@@ -1,135 +0,0 @@
-/**
- * Model ID utilities for chat command
- *
- * Functions to map providers to their corresponding model ID configuration keys.
- */
-
-import type { ApiConfiguration, ApiProvider } from "@shared/api"
-import type { Mode } from "@shared/storage/types"
-
-/**
- * Get the model ID for the current provider and mode
- */
-export function getModelIdForProvider(
-	apiConfiguration: ApiConfiguration | undefined,
-	provider: ApiProvider | undefined,
-	mode: Mode,
-): string | undefined {
-	if (!apiConfiguration || !provider) {
-		return undefined
-	}
-
-	const prefix = mode === "plan" ? "planMode" : "actMode"
-
-	// Map provider to the corresponding model ID field
-	switch (provider) {
-		case "openrouter":
-		case "cline":
-			return apiConfiguration[`${prefix}OpenRouterModelId`]
-		case "anthropic":
-		case "claude-code":
-		case "bedrock":
-		case "vertex":
-		case "gemini":
-		case "openai-native":
-		case "deepseek":
-		case "qwen":
-		case "qwen-code":
-		case "doubao":
-		case "mistral":
-		case "asksage":
-		case "xai":
-		case "moonshot":
-		case "nebius":
-		case "sambanova":
-		case "cerebras":
-		case "sapaicore":
-		case "zai":
-		case "fireworks":
-		case "minimax":
-			return apiConfiguration[`${prefix}ApiModelId`]
-		case "openai":
-			return apiConfiguration[`${prefix}OpenAiModelId`]
-		case "ollama":
-			return apiConfiguration[`${prefix}OllamaModelId`]
-		case "lmstudio":
-			return apiConfiguration[`${prefix}LmStudioModelId`]
-		case "requesty":
-			return apiConfiguration[`${prefix}RequestyModelId`]
-		case "together":
-			return apiConfiguration[`${prefix}TogetherModelId`]
-		case "litellm":
-			return apiConfiguration[`${prefix}LiteLlmModelId`]
-		case "groq":
-			return apiConfiguration[`${prefix}GroqModelId`]
-		case "baseten":
-			return apiConfiguration[`${prefix}BasetenModelId`]
-		case "huggingface":
-			return apiConfiguration[`${prefix}HuggingFaceModelId`]
-		case "huawei-cloud-maas":
-			return apiConfiguration[`${prefix}HuaweiCloudMaasModelId`]
-		case "oca":
-			return apiConfiguration[`${prefix}OcaModelId`]
-		case "hicap":
-			return apiConfiguration[`${prefix}HicapModelId`]
-		case "aihubmix":
-			return apiConfiguration[`${prefix}AihubmixModelId`]
-		case "nousResearch":
-			return apiConfiguration[`${prefix}NousResearchModelId`]
-		case "vercel-ai-gateway":
-			return apiConfiguration[`${prefix}VercelAiGatewayModelId`]
-		case "vscode-lm":
-		case "dify":
-		default:
-			return undefined
-	}
-}
-
-/**
- * Get the model ID state key for a given provider and mode
- * Some providers use provider-specific model ID keys (e.g., openRouterModelId),
- * while others use the generic apiModelId
- */
-export function getModelIdKey(provider: string | undefined, mode: Mode): string {
-	const modePrefix = mode === "plan" ? "planMode" : "actMode"
-
-	switch (provider) {
-		case "openrouter":
-		case "cline":
-			return `${modePrefix}OpenRouterModelId`
-		case "openai":
-			return `${modePrefix}OpenAiModelId`
-		case "ollama":
-			return `${modePrefix}OllamaModelId`
-		case "lmstudio":
-			return `${modePrefix}LmStudioModelId`
-		case "litellm":
-			return `${modePrefix}LiteLlmModelId`
-		case "requesty":
-			return `${modePrefix}RequestyModelId`
-		case "together":
-			return `${modePrefix}TogetherModelId`
-		case "fireworks":
-			return `${modePrefix}FireworksModelId`
-		case "groq":
-			return `${modePrefix}GroqModelId`
-		case "baseten":
-			return `${modePrefix}BasetenModelId`
-		case "huggingface":
-			return `${modePrefix}HuggingFaceModelId`
-		case "huawei-cloud-maas":
-			return `${modePrefix}HuaweiCloudMaasModelId`
-		case "oca":
-			return `${modePrefix}OcaModelId`
-		case "hicap":
-			return `${modePrefix}HicapModelId`
-		case "aihubmix":
-			return `${modePrefix}AihubmixModelId`
-		case "nousResearch":
-			return `${modePrefix}NousResearchModelId`
-		case "vercel-ai-gateway":
-			return `${modePrefix}VercelAiGatewayModelId`
-		default:
-			return `${modePrefix}ApiModelId`
-	}
-}

cli-ts/src/commands/task/chat/prompt.ts

@@ -1,33 +0,0 @@
-/**
- * Prompt string builder for chat REPL
- *
- * Builds the CLI prompt that shows current mode, provider, and model.
- */
-
-import type { ApiProvider } from "@shared/api"
-import type { Mode } from "@shared/storage/types"
-import chalk from "chalk"
-
-/**
- * Build the CLI prompt string with mode, provider, and model
- * Format: [mode] provider/model >
- */
-export function buildPromptString(mode: Mode, provider: ApiProvider | undefined, modelId: string | undefined): string {
-	const modeStr = mode === "plan" ? chalk.yellow("[plan]") : chalk.cyan("[act]")
-	const providerStr = provider || "unknown"
-
-	// Shorten very long model IDs for display (keep last part after last /)
-	let modelStr = modelId || "unknown"
-	if (modelStr.length > 40) {
-		const lastSlash = modelStr.lastIndexOf("/")
-		if (lastSlash > 0 && lastSlash < modelStr.length - 1) {
-			modelStr = "..." + modelStr.substring(lastSlash)
-		} else {
-			modelStr = modelStr.substring(0, 37) + "..."
-		}
-	}
-
-	const providerModelStr = chalk.dim(`${providerStr}/${modelStr}`)
-
-	return `${modeStr} ${providerModelStr} ${chalk.white(">")} `
-}

cli-ts/src/commands/task/chat/repl.ts

@@ -1,491 +0,0 @@
-/**
- * REPL (Read-Eval-Print Loop) for chat command
- *
- * Handles readline setup, event handling, and the main interaction loop.
- */
-
-import type { ApiProvider } from "@shared/api"
-import type { Mode } from "@shared/storage/types"
-import readline from "readline"
-import type { Controller } from "@/core/controller"
-import { CliWebviewAdapter } from "../../../core/cli-webview-adapter.js"
-import { disposeEmbeddedController } from "../../../core/embedded-controller.js"
-import type { OutputFormatter } from "../../../core/output/types.js"
-import { parseAtPaths } from "../../../core/path-parser.js"
-import type { CliConfig } from "../../../types/config.js"
-import type { Logger } from "../../../types/logger.js"
-import { createCompleter } from "./completer.js"
-import { checkForPendingInput, determineAutoApprovalAction, isCompletionState, isFailureState } from "./input-checker.js"
-import { getModelIdForProvider } from "./model-utils.js"
-import { buildPromptString } from "./prompt.js"
-import type { ChatSession } from "./session.js"
-import { processSlashCommand } from "./slash-commands/index.js"
-
-/** Yolo mode timeout: 5 minutes in milliseconds */
-const YOLO_TIMEOUT_MS = 5 * 60 * 1000
-
-/** Yolo mode max consecutive failures before abort */
-const YOLO_MAX_FAILURES = 3
-
-/**
- * Options for starting the REPL
- */
-export interface ReplOptions {
-	session: ChatSession
-	controller: Controller
-	formatter: OutputFormatter
-	logger: Logger
-	config: CliConfig
-	initialPrompt?: string
-	initialImages?: string[]
-	initialFiles?: string[]
-	resumeTaskId?: string
-}
-
-/**
- * Start the interactive REPL loop
- */
-export async function startRepl(options: ReplOptions): Promise<void> {
-	const { session, controller, formatter, logger, config, initialPrompt, initialImages, initialFiles, resumeTaskId } = options
-
-	// Create webview adapter for output
-	session.adapter = new CliWebviewAdapter(controller, formatter)
-
-	// Track if we started with a prompt (AI will be processing)
-	let startedWithPrompt = false
-
-	// Start or resume task
-	if (resumeTaskId) {
-		// Resume existing task
-		const history = await controller.getTaskWithId(resumeTaskId)
-		if (!history) {
-			throw new Error(`Task not found: ${resumeTaskId}`)
-		}
-		session.taskId = await controller.initTask(undefined, undefined, undefined, history.historyItem)
-		formatter.info(`Resumed task: ${session.taskId}`)
-	} else if (initialPrompt) {
-		// Start new task with prompt and any initial attachments
-		startedWithPrompt = true
-
-		// Log attachment info
-		if (initialFiles && initialFiles.length > 0) {
-			formatter.info(`Attaching ${initialFiles.length} file(s)`)
-		}
-		if (initialImages && initialImages.length > 0) {
-			formatter.info(`Attaching ${initialImages.length} image(s)`)
-		}
-
-		session.taskId = await controller.initTask(
-			initialPrompt,
-			initialImages && initialImages.length > 0 ? initialImages : undefined,
-			initialFiles && initialFiles.length > 0 ? initialFiles : undefined,
-		)
-		formatter.info(`Started task: ${session.taskId}`)
-		// Enable spinner since AI will be processing
-		session.adapter?.setProcessing(true)
-	}
-
-	// Display welcome message
-	displayWelcome(formatter, session, controller)
-
-	// Output existing messages if resuming
-	if (session.taskId && session.adapter) {
-		session.adapter.outputAllMessages()
-	}
-
-	// Helper to toggle between act and plan mode
-	const toggleMode = async (): Promise<void> => {
-		// Only toggle when awaiting user input (not while AI is processing)
-		if (isProcessing) {
-			return
-		}
-		const state = await controller.getStateToPostToWebview()
-		const currentMode = (state.mode || "act") as Mode
-		const newMode = currentMode === "act" ? "plan" : "act"
-		await controller.togglePlanActMode(newMode)
-		await updatePromptString()
-		showPrompt()
-	}
-
-	// Create readline interface with @ file completion and mode toggle on empty Tab
-	const rl = readline.createInterface({
-		input: process.stdin,
-		output: process.stdout,
-		prompt: "> ", // Default prompt, will be updated dynamically
-		completer: createCompleter({
-			cwd: process.cwd(),
-			onEmptyTab: () => {
-				// Use setImmediate to allow async operation outside completer
-				setImmediate(() => toggleMode())
-			},
-		}),
-	})
-
-	// Track if we're currently processing (AI is working)
-	let isProcessing = startedWithPrompt
-	// Track previous awaiting states to detect transitions
-	let wasAwaitingInput = false
-
-	// Helper to set processing state and update spinner
-	function setProcessingState(processing: boolean): void {
-		isProcessing = processing
-		session.adapter?.setProcessing(processing)
-	}
-
-	// Helper to update the prompt string (but not necessarily show it)
-	async function updatePromptString(): Promise<void> {
-		const currentState = await controller.getStateToPostToWebview()
-		const mode = (currentState.mode || "act") as Mode
-		const provider = (
-			mode === "plan"
-				? currentState.apiConfiguration?.planModeApiProvider
-				: currentState.apiConfiguration?.actModeApiProvider
-		) as ApiProvider | undefined
-		const modelId = getModelIdForProvider(currentState.apiConfiguration, provider, mode)
-		const promptStr = buildPromptString(mode, provider, modelId)
-		rl.setPrompt(promptStr)
-	}
-
-	// Helper to show the prompt (call after updating)
-	function showPrompt(): void {
-		rl.prompt()
-	}
-
-	// Start listening for state updates
-	session.adapter.startListening((messages) => {
-		const pendingState = checkForPendingInput(messages)
-		session.awaitingApproval = pendingState.awaitingApproval
-		session.awaitingInput = pendingState.awaitingInput
-
-		// Store the pending ask message for auto-approval determination
-		if (pendingState.awaitingApproval && messages.length > 0) {
-			const lastMessage = messages[messages.length - 1]
-			if (lastMessage.type === "ask" && !lastMessage.partial) {
-				session.pendingAskMessage = lastMessage
-			}
-		} else if (!pendingState.awaitingApproval) {
-			session.pendingAskMessage = null
-		}
-
-		// YOLO MODE: Auto-respond to pending inputs
-		if (session.yoloMode && controller.task && !session.yoloCompleted) {
-			// Check for task completion first
-			if (isCompletionState(messages)) {
-				// Guard against processing completion multiple times
-				session.yoloCompleted = true
-				formatter.success("\n[YOLO] Task completed!")
-				// Respond to the completion_result ask to unblock the handler
-				const task = controller.task
-				task.handleWebviewAskResponse("yesButtonClicked")
-				// Schedule exit after brief delay to let response process
-				setTimeout(async () => {
-					try {
-						await task.abortTask()
-					} catch {
-						// Task may already be cleaned up, ignore
-					}
-					// Exit successfully - task has completed
-					process.exit(0)
-				}, 200)
-				return
-			}
-
-			// Check for timeout (5 minutes)
-			if (session.yoloActionStartTime && Date.now() - session.yoloActionStartTime > YOLO_TIMEOUT_MS) {
-				formatter.error("\n[YOLO] Action timed out after 5 minutes. Aborting.")
-				session.isRunning = false
-				rl.close()
-				process.exit(0)
-				return
-			}
-
-			// Check for failure state
-			const failureCheck = isFailureState(messages)
-			if (failureCheck.isFailure) {
-				if (session.yoloLastFailedAction === failureCheck.actionKey) {
-					session.yoloFailureCount++
-				} else {
-					session.yoloLastFailedAction = failureCheck.actionKey
-					session.yoloFailureCount = 1
-				}
-
-				if (session.yoloFailureCount >= YOLO_MAX_FAILURES) {
-					formatter.error(`\n[YOLO] Same action failed ${YOLO_MAX_FAILURES} times. Aborting.`)
-					session.isRunning = false
-					rl.close()
-					process.exit(0)
-					return
-				}
-
-				// Auto-retry: approve the retry
-				formatter.warn(`[YOLO] Action failed (attempt ${session.yoloFailureCount}/${YOLO_MAX_FAILURES}), retrying...`)
-				session.yoloActionStartTime = Date.now()
-				setProcessingState(true)
-				wasAwaitingInput = false
-				controller.task.handleWebviewAskResponse("yesButtonClicked")
-				return
-			} else {
-				// Reset failure tracking on success
-				session.yoloFailureCount = 0
-				session.yoloLastFailedAction = null
-			}
-
-			// Auto-approve pending approvals
-			if (pendingState.awaitingApproval) {
-				logger.debug("[YOLO] Auto-approving action")
-				session.yoloActionStartTime = Date.now()
-				setProcessingState(true)
-				wasAwaitingInput = false
-				controller.task.handleWebviewAskResponse("yesButtonClicked")
-				session.awaitingApproval = false
-				return
-			}
-
-			// Auto-respond to input requests with "proceed"
-			if (pendingState.awaitingInput) {
-				logger.debug("[YOLO] Auto-responding with 'proceed'")
-				session.yoloActionStartTime = Date.now()
-				setProcessingState(true)
-				wasAwaitingInput = false
-				controller.task.handleWebviewAskResponse("messageResponse", "proceed")
-				session.awaitingInput = false
-				return
-			}
-		}
-
-		// Normal mode: Detect transition from processing to awaiting input
-		const nowAwaitingInput = pendingState.awaitingApproval || pendingState.awaitingInput
-		if (isProcessing && nowAwaitingInput && !wasAwaitingInput) {
-			// AI just finished and is now waiting for input - show prompt
-			setProcessingState(false)
-			updatePromptString().then(() => showPrompt())
-		}
-		wasAwaitingInput = nowAwaitingInput
-	})
-
-	// Build command context
-	const commandContext = {
-		session,
-		fmt: formatter,
-		logger,
-		config,
-		controller,
-	}
-
-	// Handle line input
-	rl.on("line", async (line: string) => {
-		const input = line.trim()
-
-		if (!input) {
-			// Empty input - just show prompt again
-			await updatePromptString()
-			showPrompt()
-			return
-		}
-
-		// Check for chat commands
-		if (input.startsWith("/")) {
-			await processSlashCommand(input, commandContext)
-			if (!session.isRunning) {
-				rl.close()
-				return
-			}
-			// Commands complete immediately, show prompt
-			await updatePromptString()
-			showPrompt()
-			return
-		}
-
-		// Handle approval shortcuts
-		if (session.awaitingApproval) {
-			const lowerInput = input.toLowerCase()
-
-			// Check for "don't ask again" approval (yy, yes!, or approve!)
-			const isAutoApprove = lowerInput === "yy" || lowerInput === "yes!" || lowerInput === "approve!"
-			if (isAutoApprove) {
-				if (controller.task && session.pendingAskMessage) {
-					// Determine which auto-approval action to enable
-					const actionKey = determineAutoApprovalAction(session.pendingAskMessage)
-					if (actionKey) {
-						// Enable auto-approval for this action type
-						const currentAutoApproval = controller.stateManager.getGlobalSettingsKey("autoApprovalSettings")
-						const updatedActions = {
-							...currentAutoApproval.actions,
-							[actionKey]: true,
-						}
-						controller.stateManager.setTaskSettings(session.taskId!, "autoApprovalSettings", {
-							...currentAutoApproval,
-							actions: updatedActions,
-						})
-						formatter.info(`Auto-approval enabled for ${actionKey}`)
-					}
-
-					setProcessingState(true) // AI will start processing
-					wasAwaitingInput = false
-					await controller.task.handleWebviewAskResponse("yesButtonClicked")
-					session.awaitingApproval = false
-					session.pendingAskMessage = null
-				}
-				// Don't show prompt - wait for AI to finish
-				return
-			}
-
-			if (lowerInput === "y" || lowerInput === "yes" || lowerInput === "approve") {
-				if (controller.task) {
-					setProcessingState(true) // AI will start processing
-					wasAwaitingInput = false
-					await controller.task.handleWebviewAskResponse("yesButtonClicked")
-					session.awaitingApproval = false
-					session.pendingAskMessage = null
-				}
-				// Don't show prompt - wait for AI to finish
-				return
-			}
-			if (lowerInput === "n" || lowerInput === "no" || lowerInput === "deny") {
-				if (controller.task) {
-					setProcessingState(true) // AI will start processing
-					wasAwaitingInput = false
-					await controller.task.handleWebviewAskResponse("noButtonClicked")
-					session.awaitingApproval = false
-					session.pendingAskMessage = null
-				}
-				// Don't show prompt - wait for AI to finish
-				return
-			}
-		}
-
-		// If no active task, start a new one
-		if (!session.taskId) {
-			// Parse @path references from the input
-			const parsed = parseAtPaths(input, process.cwd())
-
-			// Show warnings for any files that couldn't be processed
-			for (const warning of parsed.warnings) {
-				formatter.warn(warning)
-			}
-
-			// Log attachment info
-			if (parsed.files.length > 0) {
-				formatter.info(`Attaching ${parsed.files.length} file(s)`)
-			}
-			if (parsed.images.length > 0) {
-				formatter.info(`Attaching ${parsed.images.length} image(s)`)
-			}
-
-			setProcessingState(true) // AI will start processing
-			wasAwaitingInput = false
-			session.taskId = await controller.initTask(
-				parsed.cleanedMessage,
-				parsed.images.length > 0 ? parsed.images : undefined,
-				parsed.files.length > 0 ? parsed.files : undefined,
-			)
-			formatter.info(`Started task: ${session.taskId}`)
-			session.adapter?.resetMessageCounter()
-			// Don't show prompt - wait for AI to finish
-		} else if (controller.task) {
-			// Check if input is a numbered option selection
-			let messageToSend = input
-			let imagesToSend: string[] | undefined
-			let filesToSend: string[] | undefined
-
-			if (session.awaitingInput && session.adapter) {
-				const options = session.adapter.currentOptions
-				const num = parseInt(input, 10)
-				if (!Number.isNaN(num) && num >= 1 && num <= options.length) {
-					messageToSend = options[num - 1]
-				}
-			}
-
-			// Parse @path references from the input (unless it's a numbered option)
-			if (messageToSend === input) {
-				const parsed = parseAtPaths(input, process.cwd())
-
-				// Show warnings for any files that couldn't be processed
-				for (const warning of parsed.warnings) {
-					formatter.warn(warning)
-				}
-
-				// Log attachment info
-				if (parsed.files.length > 0) {
-					formatter.info(`Attaching ${parsed.files.length} file(s)`)
-				}
-				if (parsed.images.length > 0) {
-					formatter.info(`Attaching ${parsed.images.length} image(s)`)
-				}
-
-				messageToSend = parsed.cleanedMessage
-				imagesToSend = parsed.images.length > 0 ? parsed.images : undefined
-				filesToSend = parsed.files.length > 0 ? parsed.files : undefined
-			}
-
-			setProcessingState(true) // AI will start processing
-			wasAwaitingInput = false
-			// Send message to existing task with any attachments
-			await controller.task.handleWebviewAskResponse("messageResponse", messageToSend, imagesToSend, filesToSend)
-			// Don't show prompt - wait for AI to finish
-		}
-	})
-
-	// Handle close
-	rl.on("close", async () => {
-		formatter.raw("")
-		formatter.info("Chat session ended")
-
-		// Reset yolo mode settings if they were enabled for this session
-		if (session.yoloMode) {
-			controller.stateManager.setGlobalState("yoloModeToggled", false)
-			// Reset maxConsecutiveMistakes to default
-			controller.stateManager.setGlobalState("maxConsecutiveMistakes", 3)
-		}
-
-		// Stop listening and cleanup
-		session.adapter?.stopListening()
-		await disposeEmbeddedController(logger)
-
-		process.exit(0)
-	})
-
-	// Handle Ctrl+C
-	rl.on("SIGINT", () => {
-		formatter.raw("")
-		formatter.info("Chat session ended (interrupted)")
-		rl.close()
-	})
-
-	// Start prompt with current state (only if not already processing)
-	await updatePromptString()
-	if (!isProcessing) {
-		showPrompt()
-	}
-}
-
-/**
- * Display the welcome message
- */
-async function displayWelcome(formatter: OutputFormatter, session: ChatSession, controller: Controller): Promise<void> {
-	formatter.raw("")
-	formatter.info("═".repeat(60))
-	if (session.yoloMode) {
-		formatter.info("  Cline Interactive Chat Mode [YOLO]")
-	} else {
-		formatter.info("  Cline Interactive Chat Mode")
-	}
-	formatter.info("═".repeat(60))
-	if (session.taskId) {
-		formatter.info(`Task: ${session.taskId}`)
-	}
-	const state = await controller.getStateToPostToWebview()
-	formatter.info(`Mode: ${state.mode || "act"}`)
-	if (session.yoloMode) {
-		formatter.info("YOLO: Auto-approving all actions (5min timeout, 3 retries max)")
-	}
-	formatter.raw("")
-	if (!session.yoloMode) {
-		formatter.info("Type your message and press Enter to send.")
-		formatter.info("Use @path to attach files (e.g., @./file.txt, @image.png)")
-		formatter.info("Press Tab to toggle between act/plan mode or complete @paths.")
-		formatter.info("Type /help for available commands, /quit to exit.")
-	}
-	formatter.raw("─".repeat(60))
-	formatter.raw("")
-}

cli-ts/src/commands/task/chat/session.ts

@@ -1,45 +0,0 @@
-/**
- * Chat session state management
- *
- * Defines the session interface and factory function.
- */
-
-import type { ClineMessage } from "@shared/ExtensionMessage"
-import type { CliWebviewAdapter } from "../../../core/cli-webview-adapter.js"
-
-/**
- * Chat session state
- */
-export interface ChatSession {
-	taskId: string | null
-	isRunning: boolean
-	awaitingApproval: boolean
-	awaitingInput: boolean
-	adapter: CliWebviewAdapter | null
-	yoloMode: boolean
-	yoloFailureCount: number
-	yoloLastFailedAction: string | null
-	yoloActionStartTime: number | null
-	yoloCompleted: boolean
-	/** The current pending ask message (for determining auto-approval action type) */
-	pendingAskMessage: ClineMessage | null
-}
-
-/**
- * Create a new chat session with default state
- */
-export function createSession(yoloMode = false): ChatSession {
-	return {
-		taskId: null,
-		isRunning: true,
-		awaitingApproval: false,
-		awaitingInput: false,
-		adapter: null,
-		yoloMode,
-		yoloFailureCount: 0,
-		yoloLastFailedAction: null,
-		yoloActionStartTime: null,
-		yoloCompleted: false,
-		pendingAskMessage: null,
-	}
-}

cli-ts/src/commands/task/chat/slash-commands/checkpoints.ts

@@ -1,48 +0,0 @@
-/**
- * Checkpoints command handler - list available checkpoints
- */
-
-import { formatCheckpointList } from "../../restore.js"
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /checkpoints command - list available checkpoints in current task
- */
-export const handleCheckpoints: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	if (!ctx.controller.task) {
-		ctx.fmt.warn("No active task")
-		return true
-	}
-
-	const messages = ctx.controller.task.messageStateHandler.getClineMessages()
-	const checkpoints = formatCheckpointList(messages)
-
-	if (checkpoints.length === 0) {
-		ctx.fmt.info("No checkpoints found in current task")
-		return true
-	}
-
-	ctx.fmt.info(`Checkpoints (${checkpoints.length}):\n`)
-
-	const idWidth = 16
-	const timeWidth = 16
-	const wsWidth = 12
-
-	const header = "ID".padEnd(idWidth) + "Time".padEnd(timeWidth) + "Workspace".padEnd(wsWidth) + "Context"
-	ctx.fmt.raw(header)
-	ctx.fmt.raw("-".repeat(header.length + 30))
-
-	for (const cp of checkpoints) {
-		const row =
-			String(cp.id).padEnd(idWidth) +
-			cp.timeAgo.padEnd(timeWidth) +
-			(cp.hasWorkspaceRestore ? "Yes" : "No").padEnd(wsWidth) +
-			cp.context
-		ctx.fmt.raw(row)
-	}
-
-	ctx.fmt.raw("")
-	ctx.fmt.info('Use "/restore <checkpoint-id>" to restore')
-
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/config.ts

@@ -1,130 +0,0 @@
-/**
- * Config command handler
- */
-
-import fs from "fs"
-import path from "path"
-import { getNestedValue, parseValue, setNestedValue } from "../../../config/index.js"
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /config, /cfg commands
- */
-export const handleConfig: CommandHandler = async (args: string[], ctx: CommandContext): Promise<boolean> => {
-	const subCmd = args[0]?.toLowerCase()
-	const configKey = args[1]
-	const configValue = args.slice(2).join(" ")
-
-	if (!subCmd || subCmd === "list" || subCmd === "ls") {
-		// List all config values
-		try {
-			const configDir = ctx.config.configDir || `${process.env.HOME}/.cline`
-			const globalStatePath = path.join(configDir, "data", "globalState.json")
-
-			if (fs.existsSync(globalStatePath)) {
-				const content = fs.readFileSync(globalStatePath, "utf-8")
-				const allSettings = JSON.parse(content)
-				ctx.fmt.raw("")
-				ctx.fmt.raw(JSON.stringify(allSettings, null, 2))
-				ctx.fmt.raw("")
-			} else {
-				ctx.fmt.info("No configuration file found")
-			}
-		} catch (err) {
-			ctx.fmt.error(`Failed to list config: ${(err as Error).message}`)
-		}
-		return true
-	}
-
-	if (subCmd === "get") {
-		if (!configKey) {
-			ctx.fmt.error("Usage: /config get <key>")
-			return true
-		}
-
-		try {
-			let value: unknown
-
-			if (configKey.includes(".")) {
-				// For nested paths, get the root object first
-				const rootKey = configKey.split(".")[0]
-				let rootValue = ctx.controller.stateManager.getGlobalSettingsKey(rootKey as any)
-				if (rootValue === undefined) {
-					rootValue = ctx.controller.stateManager.getGlobalStateKey(rootKey as any)
-				}
-
-				if (rootValue !== undefined && typeof rootValue === "object") {
-					value = getNestedValue({ [rootKey]: rootValue }, configKey)
-				}
-			} else {
-				value = ctx.controller.stateManager.getGlobalSettingsKey(configKey as any)
-				if (value === undefined) {
-					value = ctx.controller.stateManager.getGlobalStateKey(configKey as any)
-				}
-			}
-
-			if (value === undefined) {
-				ctx.fmt.info(`${configKey} is not set`)
-			} else {
-				const displayValue = typeof value === "object" ? JSON.stringify(value, null, 2) : String(value)
-				ctx.fmt.keyValue({ [configKey]: displayValue })
-			}
-		} catch (err) {
-			ctx.fmt.error(`Failed to get config: ${(err as Error).message}`)
-		}
-		return true
-	}
-
-	if (subCmd === "set") {
-		if (!configKey || !configValue) {
-			ctx.fmt.error("Usage: /config set <key> <value>")
-			return true
-		}
-
-		try {
-			const parsedValue = parseValue(configKey, configValue)
-
-			if (configKey.includes(".")) {
-				// For nested paths, get the current root object, modify it, and save the whole thing
-				const rootKey = configKey.split(".")[0]
-				let rootValue = ctx.controller.stateManager.getGlobalSettingsKey(rootKey as any)
-				if (rootValue === undefined) {
-					rootValue = ctx.controller.stateManager.getGlobalStateKey(rootKey as any)
-				}
-
-				const currentRoot = rootValue !== undefined && typeof rootValue === "object" ? rootValue : {}
-				const { rootValue: newRootValue } = setNestedValue({ [rootKey]: currentRoot }, configKey, parsedValue)
-
-				ctx.controller.stateManager.setGlobalState(rootKey as any, newRootValue as any)
-			} else {
-				ctx.controller.stateManager.setGlobalState(configKey as any, parsedValue as any)
-			}
-
-			await ctx.controller.stateManager.flushPendingState()
-			ctx.fmt.success(`Set ${configKey} = ${String(parsedValue)}`)
-		} catch (err) {
-			ctx.fmt.error(`Failed to set config: ${(err as Error).message}`)
-		}
-		return true
-	}
-
-	if (subCmd === "delete" || subCmd === "rm") {
-		if (!configKey) {
-			ctx.fmt.error("Usage: /config delete <key>")
-			return true
-		}
-
-		try {
-			ctx.controller.stateManager.setGlobalState(configKey as any, undefined)
-			await ctx.controller.stateManager.flushPendingState()
-			ctx.fmt.success(`Reset ${configKey} to default`)
-		} catch (err) {
-			ctx.fmt.error(`Failed to delete config: ${(err as Error).message}`)
-		}
-		return true
-	}
-
-	ctx.fmt.error(`Unknown config subcommand: ${subCmd}`)
-	ctx.fmt.raw("Usage: /config <list|get|set|delete> [key] [value]")
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/help.ts

@@ -1,36 +0,0 @@
-/**
- * Help command handler
- */
-
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /help, /h, /? commands
- */
-export const handleHelp: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	ctx.fmt.raw("")
-	ctx.fmt.info("Chat commands:")
-	ctx.fmt.raw("  /help, /h, /?      - Show this help")
-	ctx.fmt.raw("  /plan              - Switch to plan mode")
-	ctx.fmt.raw("  /act               - Switch to act mode")
-	ctx.fmt.raw("  /mode <plan|act>   - Switch mode")
-	ctx.fmt.raw("  /model             - Show current model")
-	ctx.fmt.raw("    /model <id>        - Set model for current mode")
-	ctx.fmt.raw("    /model list        - List available models (OpenRouter/Cline)")
-	ctx.fmt.raw("  /status, /s        - Show task status")
-	ctx.fmt.raw("  /usage, /u         - Show token usage and cost")
-	ctx.fmt.raw("  /cancel            - Cancel current task")
-	ctx.fmt.raw("  /approve, /a, /y   - Approve pending action")
-	ctx.fmt.raw("  /deny, /d, /n      - Deny pending action")
-	ctx.fmt.raw("  /checkpoints, /cp  - List available checkpoints")
-	ctx.fmt.raw("  /restore, /r <id> [type] - Restore to checkpoint")
-	ctx.fmt.raw("    types: task (default), workspace, taskAndWorkspace")
-	ctx.fmt.raw("  /config, /cfg      - Manage configuration")
-	ctx.fmt.raw("    /config list     - List all configuration values")
-	ctx.fmt.raw("    /config get <key>    - Get a config value")
-	ctx.fmt.raw("    /config set <key> <value> - Set a config value")
-	ctx.fmt.raw("    /config delete <key> - Reset a config value")
-	ctx.fmt.raw("  /quit, /q, /exit   - Exit chat mode")
-	ctx.fmt.raw("")
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/index.ts

@@ -1,92 +0,0 @@
-/**
- * Command dispatcher for chat REPL
- *
- * Maps command names to their handlers and dispatches incoming commands.
- */
-
-import { handleCheckpoints } from "./checkpoints.js"
-import { handleConfig } from "./config.js"
-import { handleHelp } from "./help.js"
-import { handleAct, handleMode, handlePlan } from "./mode.js"
-import { handleModel } from "./model.js"
-import { handleQuit } from "./quit.js"
-import { handleRestore } from "./restore.js"
-import { handleStatus } from "./status.js"
-import { handleApprove, handleCancel, handleDeny } from "./task.js"
-import type { CommandContext, CommandHandler } from "./types.js"
-import { handleUsage } from "./usage.js"
-
-/**
- * Map of command names to their handlers
- */
-const handlers: Record<string, CommandHandler> = {
-	// Help
-	help: handleHelp,
-	h: handleHelp,
-	"?": handleHelp,
-
-	// Mode
-	plan: handlePlan,
-	act: handleAct,
-	mode: handleMode,
-	m: handleMode,
-
-	// Model
-	model: handleModel,
-
-	// Status
-	status: handleStatus,
-	s: handleStatus,
-
-	// Task control
-	cancel: handleCancel,
-	approve: handleApprove,
-	a: handleApprove,
-	y: handleApprove,
-	deny: handleDeny,
-	d: handleDeny,
-	n: handleDeny,
-
-	// Config
-	config: handleConfig,
-	cfg: handleConfig,
-
-	// Usage
-	usage: handleUsage,
-	u: handleUsage,
-
-	// Quit
-	quit: handleQuit,
-	q: handleQuit,
-	exit: handleQuit,
-
-	// Checkpoints
-	checkpoints: handleCheckpoints,
-	cp: handleCheckpoints,
-	restore: handleRestore,
-	r: handleRestore,
-}
-
-/**
- * Process a chat command (input starting with /)
- *
- * @param input - Full command input including the leading /
- * @param ctx - Command context
- * @returns true if the command was handled
- */
-export async function processSlashCommand(input: string, ctx: CommandContext): Promise<boolean> {
-	const parts = input.slice(1).split(/\s+/)
-	const cmd = parts[0].toLowerCase()
-	const args = parts.slice(1)
-
-	const handler = handlers[cmd]
-	if (!handler) {
-		ctx.fmt.warn(`Unknown command: /${cmd}. Type /help for available commands.`)
-		return true
-	}
-
-	return handler(args, ctx)
-}
-
-// Re-export types for convenience
-export type { CommandContext, CommandHandler } from "./types.js"

cli-ts/src/commands/task/chat/slash-commands/mode.ts

@@ -1,42 +0,0 @@
-/**
- * Mode command handlers
- */
-
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /plan command
- */
-export const handlePlan: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	await ctx.controller.togglePlanActMode("plan")
-	ctx.fmt.success("Switched to plan mode")
-	return true
-}
-
-/**
- * Handle /act command
- */
-export const handleAct: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	await ctx.controller.togglePlanActMode("act")
-	ctx.fmt.success("Switched to act mode")
-	return true
-}
-
-/**
- * Handle /mode command
- */
-export const handleMode: CommandHandler = async (args: string[], ctx: CommandContext): Promise<boolean> => {
-	if (args.length === 0) {
-		const state = await ctx.controller.getStateToPostToWebview()
-		ctx.fmt.info(`Current mode: ${state.mode || "unknown"}`)
-	} else {
-		const newMode = args[0].toLowerCase()
-		if (newMode !== "plan" && newMode !== "act") {
-			ctx.fmt.error("Invalid mode. Use 'plan' or 'act'")
-		} else {
-			await ctx.controller.togglePlanActMode(newMode as "plan" | "act")
-			ctx.fmt.success(`Switched to ${newMode} mode`)
-		}
-	}
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/model.ts

@@ -1,94 +0,0 @@
-/**
- * Model command handler
- */
-
-import type { Mode } from "@shared/storage/types"
-import { getModelIdForProvider, getModelIdKey } from "../model-utils.js"
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /model command
- */
-export const handleModel: CommandHandler = async (args: string[], ctx: CommandContext): Promise<boolean> => {
-	const state = await ctx.controller.getStateToPostToWebview()
-	const currentMode: Mode = (state.mode as Mode) || "act"
-	const apiConfig = state.apiConfiguration
-
-	// Get current provider for this mode
-	const provider = currentMode === "plan" ? apiConfig?.planModeApiProvider : apiConfig?.actModeApiProvider
-
-	const subCmd = args[0]?.toLowerCase()
-
-	if (!subCmd) {
-		// Show current model
-		const modelId = getModelIdForProvider(apiConfig, provider, currentMode)
-		ctx.fmt.raw("")
-		ctx.fmt.info(`Mode: ${currentMode}`)
-		ctx.fmt.info(`Provider: ${provider || "(not set)"}`)
-		ctx.fmt.info(`Model: ${modelId || "(not set)"}`)
-		ctx.fmt.raw("")
-		return true
-	}
-
-	if (subCmd === "list") {
-		// Fetch models from OpenRouter if applicable
-		if (provider === "openrouter" || provider === "cline") {
-			ctx.fmt.info("Fetching models from OpenRouter...")
-			try {
-				const response = await fetch("https://openrouter.ai/api/v1/models")
-				if (!response.ok) {
-					throw new Error(`HTTP ${response.status}`)
-				}
-				const data = (await response.json()) as {
-					data?: Array<{
-						id: string
-						name?: string
-						pricing?: { prompt?: string; completion?: string }
-					}>
-				}
-				const models = (data.data || []).sort((a, b) => a.id.localeCompare(b.id))
-
-				ctx.fmt.raw("")
-				ctx.fmt.info(`Available models (${models.length} total):`)
-				ctx.fmt.raw("")
-
-				// Show all models with pricing info (alphabetized)
-				for (const model of models) {
-					const promptPrice = model.pricing?.prompt
-						? `$${(parseFloat(model.pricing.prompt) * 1_000_000).toFixed(2)}/M`
-						: "N/A"
-					const completionPrice = model.pricing?.completion
-						? `$${(parseFloat(model.pricing.completion) * 1_000_000).toFixed(2)}/M`
-						: "N/A"
-					ctx.fmt.raw(`  ${model.id}`)
-					ctx.fmt.raw(`    Input: ${promptPrice}, Output: ${completionPrice}`)
-				}
-
-				ctx.fmt.raw("")
-				ctx.fmt.info("Use '/model <model-id>' to set the model")
-				ctx.fmt.raw("")
-			} catch (err) {
-				ctx.fmt.error(`Failed to fetch models: ${(err as Error).message}`)
-			}
-		} else {
-			ctx.fmt.warn(`Model listing not available for provider: ${provider || "none"}`)
-			ctx.fmt.info("Model listing is only supported for OpenRouter and Cline providers.")
-		}
-		return true
-	}
-
-	// Set model - args is the model ID (may contain slashes like "anthropic/claude-3")
-	const newModelId = args.join(" ")
-
-	if (!provider) {
-		ctx.fmt.error("No provider configured for current mode.")
-		ctx.fmt.info("Run 'cline auth' to configure a provider first.")
-		return true
-	}
-
-	const modelIdKey = getModelIdKey(provider, currentMode)
-	ctx.controller.stateManager.setGlobalState(modelIdKey as any, newModelId)
-	await ctx.controller.stateManager.flushPendingState()
-	ctx.fmt.success(`Set ${currentMode} mode model to: ${newModelId}`)
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/quit.ts

@@ -1,13 +0,0 @@
-/**
- * Quit command handler
- */
-
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /quit, /q, /exit commands
- */
-export const handleQuit: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	ctx.session.isRunning = false
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/restore.ts

@@ -1,144 +0,0 @@
-/**
- * Restore command handler - restore task to a checkpoint
- */
-
-import { validateCheckpoint } from "../../restore.js"
-import { handleCheckpoints } from "./checkpoints.js"
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/** Valid restore types */
-type RestoreType = "task" | "workspace" | "taskAndWorkspace"
-
-const VALID_RESTORE_TYPES: RestoreType[] = ["task", "workspace", "taskAndWorkspace"]
-
-/**
- * Get relative time string (e.g., "2 hours ago")
- */
-function getTimeAgo(timestamp: number): string {
-	const now = Date.now()
-	const diff = now - timestamp
-	const seconds = Math.floor(diff / 1000)
-	const minutes = Math.floor(seconds / 60)
-	const hours = Math.floor(minutes / 60)
-	const days = Math.floor(hours / 24)
-
-	if (days > 0) {
-		return days === 1 ? "1 day ago" : `${days} days ago`
-	}
-	if (hours > 0) {
-		return hours === 1 ? "1 hour ago" : `${hours} hours ago`
-	}
-	if (minutes > 0) {
-		return minutes === 1 ? "1 minute ago" : `${minutes} minutes ago`
-	}
-	return "just now"
-}
-
-/**
- * Handle /restore command - restore task to a checkpoint
- *
- * Usage:
- *   /restore <checkpoint-id> [type]
- *   /restore list  - List available checkpoints (alias for /checkpoints)
- *
- * Types:
- *   task            - Restore conversation only (default)
- *   workspace       - Restore files only
- *   taskAndWorkspace - Restore both
- */
-export const handleRestore: CommandHandler = async (args: string[], ctx: CommandContext): Promise<boolean> => {
-	// Handle "list" subcommand
-	if (args[0] === "list" || args[0] === "ls") {
-		return handleCheckpoints(args.slice(1), ctx)
-	}
-
-	// Check for active task
-	if (!ctx.controller.task) {
-		ctx.fmt.warn("No active task")
-		return true
-	}
-
-	// Validate arguments
-	if (args.length === 0) {
-		ctx.fmt.warn("Usage: /restore <checkpoint-id> [type]")
-		ctx.fmt.info("  checkpoint-id: The timestamp ID of the checkpoint")
-		ctx.fmt.info("  type: task (default), workspace, or taskAndWorkspace")
-		ctx.fmt.info("")
-		ctx.fmt.info('Use "/checkpoints" or "/restore list" to see available checkpoints')
-		return true
-	}
-
-	// Parse checkpoint ID
-	const checkpointIdArg = args[0]
-	const checkpointId = parseInt(checkpointIdArg, 10)
-	if (isNaN(checkpointId)) {
-		ctx.fmt.error(`Invalid checkpoint ID: "${checkpointIdArg}". Must be a number (timestamp).`)
-		return true
-	}
-
-	// Parse restore type (default: task)
-	let restoreType: RestoreType = "task"
-	if (args[1]) {
-		const providedType = args[1].toLowerCase()
-		if (!VALID_RESTORE_TYPES.includes(providedType as RestoreType)) {
-			ctx.fmt.error(`Invalid restore type: "${args[1]}". Valid options: ${VALID_RESTORE_TYPES.join(", ")}`)
-			return true
-		}
-		restoreType = providedType as RestoreType
-	}
-
-	// Get messages and validate checkpoint exists
-	const messages = ctx.controller.task.messageStateHandler.getClineMessages()
-	const checkpoint = validateCheckpoint(messages, checkpointId)
-
-	if (!checkpoint) {
-		// Check if the timestamp exists but is not a checkpoint
-		const anyMessage = messages.find((m) => m.ts === checkpointId)
-		if (anyMessage) {
-			ctx.fmt.error(`Timestamp ${checkpointId} exists but is not a checkpoint (type: ${anyMessage.say || anyMessage.ask})`)
-		} else {
-			ctx.fmt.error(`Checkpoint ${checkpointId} not found in task history`)
-		}
-		ctx.fmt.info('Use "/checkpoints" to see available checkpoints')
-		return true
-	}
-
-	// Check if workspace restore is possible
-	if ((restoreType === "workspace" || restoreType === "taskAndWorkspace") && !checkpoint.lastCheckpointHash) {
-		ctx.fmt.warn("Warning: This checkpoint does not have workspace restore data.")
-		if (restoreType === "workspace") {
-			ctx.fmt.error("Cannot restore workspace: no checkpoint hash available")
-			return true
-		}
-		ctx.fmt.info("Falling back to task-only restore.")
-		restoreType = "task"
-	}
-
-	// Perform the restore
-	ctx.fmt.info(`Restoring to checkpoint ${checkpointId} (${getTimeAgo(checkpointId)})...`)
-	ctx.fmt.info(`Restore type: ${restoreType}`)
-
-	try {
-		// Cancel any active task first (required before restore)
-		await ctx.controller.cancelTask()
-
-		// Call restoreCheckpoint on the checkpoint manager
-		const checkpointManager = ctx.controller.task?.checkpointManager
-		if (!checkpointManager) {
-			ctx.fmt.error("Checkpoint manager not available")
-			return true
-		}
-
-		await checkpointManager.restoreCheckpoint(checkpointId, restoreType)
-
-		ctx.fmt.success("Checkpoint restored successfully")
-
-		// Show post-restore state
-		const newMessages = ctx.controller.task?.messageStateHandler.getClineMessages() || []
-		ctx.fmt.info(`Task now has ${newMessages.length} messages`)
-	} catch (error) {
-		ctx.fmt.error(`Failed to restore checkpoint: ${(error as Error).message}`)
-	}
-
-	return true
-}

cli-ts/src/commands/task/chat/slash-commands/status.ts

@@ -1,24 +0,0 @@
-/**
- * Status command handler
- */
-
-import type { CommandContext, CommandHandler } from "./types.js"
-
-/**
- * Handle /status, /s commands
- */
-export const handleStatus: CommandHandler = async (_args: string[], ctx: CommandContext): Promise<boolean> => {
-	const state = await ctx.controller.getStateToPostToWebview()
-	ctx.fmt.raw("")
-	ctx.fmt.info(`Task ID: ${ctx.session.taskId || "none"}`)
-	ctx.fmt.info(`Mode: ${state.mode || "unknown"}`)
-	ctx.fmt.info(`Messages: ${state.clineMessages?.length || 0}`)
-	if (ctx.session.awaitingApproval) {
-		ctx.fmt.warn("Awaiting approval (use /approve or /deny)")
-	}
-	if (ctx.session.awaitingInput) {
-		ctx.fmt.warn("Awaiting user input")
-	}
-	ctx.fmt.raw("")
-	return true
-}