Get the build working

All 24 issues now in Fixed section with condensed descriptions.
Only #15 (MCP tools not visible to agent) remains as Open Issue.

.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/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/endpoint-config-file.md

@@ -1,7 +0,0 @@
----
-"claude-dev": patch
----
-
-Add endpoint configuration file support for on-premise deployments
-
-Enterprise customers can now configure custom API endpoints by creating a `~/.cline/endpoints.json` file with custom URLs for `appBaseUrl`, `apiBaseUrl`, and `mcpBaseUrl`. When this file is present, Cline runs in on-premise mode with the custom endpoints.

.changeset/fix-prevent-infinite-retry-loops.md

@@ -1,7 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: prevent infinite retry loops when replace_in_file fails repeatedly
-
-Add safeguards to prevent the LLM from getting stuck in infinite retry loops when `replace_in_file` operations fail repeatedly. The system now detects repeated failures and provides better guidance to break out of retry cycles.

.changeset/fix-skip-diff-error-during-streaming.md

@@ -1,7 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: skip diff error UI handling during streaming to prevent flickering
-
-Suppress diff view error notifications while content is actively streaming to prevent visual flickering and improve user experience. Error handling is deferred until streaming completes.

.changeset/fix-strip-notebook-outputs.md

@@ -1,7 +0,0 @@
----
-"claude-dev": patch
----
-
-fix(extract-text): strip notebook outputs to reduce context size
-
-Strip notebook cell outputs when extracting text content from Jupyter notebooks, significantly reducing the amount of context sent to the LLM while preserving the essential code and markdown content.

.changeset/fix-throttle-diff-updates.md

@@ -1,7 +0,0 @@
----
-"claude-dev": patch
----
-
-fix: throttle diff view updates during streaming
-
-Add throttling to diff view updates during content streaming to reduce UI flickering and improve performance. Updates are now batched at reasonable intervals instead of firing on every token received.

.changeset/flat-owls-sit.md

@@ -1,5 +0,0 @@
----
-"claude-dev": minor
----
-
-Disable PostHog telemetry, error tracking, and feature flags in self-hosted mode

.changeset/remove-zai-glm-4-6.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Remove deprecated zai-glm-4.6 model from Cerebras provider

.changeset/silent-hounds-read.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Make Sonnet 4.5 the default Amazon Bedrock model id

.changeset/violet-parrots-tell.md

@@ -1,5 +0,0 @@
----
-"claude-dev": patch
----
-
-Disable PostHog and build-time OpenTelemetry telemetry in self-hosted/on-premise mode. Enterprise customers running self-hosted deployments will no longer send any telemetry to Cline's collectors. Runtime environment OTEL and remote config OTEL remain available for enterprises to configure their own telemetry collection.

.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

@@ -1,8 +1,8 @@
 # CLI Development
 
-The CLI lives in `cli-ts/` and uses React Ink for terminal UI.
+The CLI lives in `cli/` and uses React Ink for terminal UI.
 
-- If needed, look at `cli-ts/src/constants/colors.ts` for re-used terminal colors, e.g. `COLORS.primaryBlue` highlight color (selections, spinners, success states).
+- 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.
@@ -11,7 +11,7 @@ The CLI lives in `cli-ts/` and uses React Ink for terminal UI.
 
 When adding a new API provider to the extension, you must also update the CLI:
 
-1. **Update `cli-ts/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`:
+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"
 
@@ -21,7 +21,7 @@ When adding a new API provider to the extension, you must also update the CLI:
    }
    ```
 
-2. **Use `applyProviderConfig()` for auth flows**: When implementing OAuth or other auth flows for the provider, use the shared utility at `cli-ts/src/utils/provider-config.ts`:
+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"
 

.clinerules/debug-harness.md

@@ -0,0 +1,45 @@
+# Debug Harness
+
+HTTP-controlled debugger for the VSCode extension at `src/dev/debug-harness/server.ts`.
+
+## Quick start
+
+```bash
+# Build extension first if needed (protos + esbuild):
+npm run protos && IS_DEV=true node esbuild.mjs
+
+# Launch (skip-build if already built):
+npx tsx src/dev/debug-harness/server.ts --skip-build --auto-launch
+
+# In another terminal:
+curl localhost:19229/api -d '{"method":"status"}'
+```
+
+## Key commands
+
+All via `POST localhost:19229/api` with `{"method":"...", "params":{...}}`:
+
+- **`launch`** / **`shutdown`** — lifecycle
+- **`ui.screenshot`** — screenshot to `/tmp/cline-debug/`
+- **`ui.open_sidebar`** — open the Cline sidebar
+- **`ext.set_breakpoint`** `{file, line, condition?}` — breakpoint by source file (sourcemap-resolved)
+- **`ext.evaluate`** `{expression, callFrameId?}` — eval in extension host
+- **`ext.resume`** / **`ext.step_over`** / **`ext.step_into`** — stepping
+- **`ext.call_stack`** — inspect when paused
+- **`web.evaluate`** `{expression}` — eval in webview
+- **`web.post_message`** `{message}` — send postMessage to extension host via exposed vsCodeApi
+- **`wait_for_pause`** `{timeout?}` — block until breakpoint hit
+- **`ui.locator`** `{role?, testId?, text?, action?, frame?}` — Playwright locator (auto-retries on stale sidebar frame)
+- **`ui.react_input`** `{text, selector?, clear?, submit?}` — set React textarea value via `execCommand('insertText')`; works reliably across multiple tasks
+- **`ui.send_message`** `{text, images?, files?, responseType?}` — send chat message bypassing the textarea entirely (via gRPC postMessage)
+- **`ui.command_palette`** `{command}` — run VSCode command
+
+## Caveats
+
+- **Scripts count = 0 after launch**: CDP connects after extension host starts, so scripts parsed during startup aren't tracked. Breakpoints still work via sourcemap resolution.
+- **Port 9230**: Extension host inspector. If another VSCode instance uses this port, the harness will fail to connect. Kill other debug instances first.
+- **macOS only** for now (Playwright Electron launch behavior).
+- **Webview CDP**: `connect_webview` may fail depending on Electron version. `web.evaluate` still works via Playwright's `frame.evaluate()` fallback.
+- **Sourcemap paths**: esbuild outputs relative paths like `../src/extension.ts` in the sourcemap. The resolver handles this, but if a file isn't found, use `ext.source_files` to see exact paths.
+
+See `src/dev/debug-harness/README.md` for full API 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,6 @@
 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.mp4 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,32 +31,11 @@ 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"
 
-      # Cache root dependencies
-      - name: Cache root dependencies
-        uses: actions/cache@v4
-        id: root-cache
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-npm-${{ hashFiles('package-lock.json') }}
-
-      # Cache cli-ts dependencies
-      - name: Cache cli-ts dependencies
-        uses: actions/cache@v4
-        id: cli-ts-cache
-        with:
-          path: cli-ts/node_modules
-          key: ${{ runner.os }}-npm-cli-ts-${{ hashFiles('cli-ts/package-lock.json') }}
-
-      - name: Install root dependencies
-        if: steps.root-cache.outputs.cache-hit != 'true'
-        run: npm ci --include=optional
-
-      - name: Install cli-ts dependencies
-        if: steps.cli-ts-cache.outputs.cache-hit != 'true'
-        run: cd cli-ts && npm ci
+      - 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
 
       - name: Generate Protos
         run: npm run protos
@@ -63,15 +43,12 @@ jobs:
       - name: Read release version
         id: version
         run: |
-          # Read version from cli-ts/package.json
-          VERSION=$(node -p "require('./cli-ts/package.json').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: Clean previous builds
-        run: rm -rf dist-standalone
-
-      - name: Build and package CLI
+      - name: Build standalone NPM package
         env:
           TELEMETRY_SERVICE_API_KEY: ${{ secrets.TELEMETRY_SERVICE_API_KEY }}
           ERROR_SERVICE_API_KEY: ${{ secrets.ERROR_SERVICE_API_KEY }}
@@ -82,7 +59,6 @@ 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: node scripts/package-npm.mjs
 
       - name: Verify build output
@@ -90,23 +66,46 @@ jobs:
           echo "Checking dist-standalone directory..."
           ls -la dist-standalone/
 
-          echo "Checking dist-standalone/dist..."
-          ls -la dist-standalone/dist/
+          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
+          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'"
           echo ""
           echo "📦 Install with: npm install -g cline"
           echo "🔗 NPM: https://www.npmjs.com/package/cline/v/${{ steps.version.outputs.version }}"
+
+      - name: Post release to Slack
+        uses: slackapi/slack-github-action@v3.0.1
+        with:
+          method: chat.postMessage
+          token: ${{ secrets.SLACK_RELEASE_BOT_TOKEN }}
+          payload: |
+            channel: "C0APVKGGZFC"
+            text: "Cline CLI v${{ steps.version.outputs.version }}"
+            blocks:
+              - type: "section"
+                text:
+                  type: "mrkdwn"
+                  text: "*Cline CLI v${{ steps.version.outputs.version }}*"
+              - type: "context"
+                elements:
+                  - type: "mrkdwn"
+                    text: "<https://www.npmjs.com/package/cline/v/${{ steps.version.outputs.version }}|View on npm>"

.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,34 +50,12 @@ 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"
 
-      # Cache root dependencies
-      - name: Cache root dependencies
+      - name: Install root dependencies and CLI dependencies
         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 cli-ts dependencies
-      - name: Cache cli-ts dependencies
-        if: steps.check_commits.outputs.skip != 'true'
-        uses: actions/cache@v4
-        id: cli-ts-cache
-        with:
-          path: cli-ts/node_modules
-          key: ${{ runner.os }}-npm-cli-ts-${{ hashFiles('cli-ts/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 cli-ts dependencies
-        if: steps.check_commits.outputs.skip != 'true' && steps.cli-ts-cache.outputs.cache-hit != 'true'
-        run: cd cli-ts && npm ci
+        run: npm ci --include=optional # this will also install cli deps because "cli" in included in root package.json workspaces field
 
       - name: Generate Protos
         if: steps.check_commits.outputs.skip != 'true'
@@ -76,36 +65,32 @@ jobs:
         if: steps.check_commits.outputs.skip != 'true'
         id: version
         run: |
-          # Read base version from cli-ts/package.json (e.g., "2.0.0")
-          BASE_VERSION=$(node -p "require('./cli-ts/package.json').version")
+          # 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: 2.0.0-nightly.1736365200
+          # 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
 
-      - name: Update cli-ts/package.json with nightly version
+      - name: Update cli/package.json with nightly version
         if: steps.check_commits.outputs.skip != 'true'
         run: |
           # Update version with timestamp-based nightly version
           node -e "
             const fs = require('fs');
-            const pkg = JSON.parse(fs.readFileSync('cli-ts/package.json', 'utf8'));
+            const pkg = JSON.parse(fs.readFileSync('cli/package.json', 'utf8'));
             pkg.version = '${{ steps.version.outputs.version }}';
-            fs.writeFileSync('cli-ts/package.json', JSON.stringify(pkg, null, '\t'));
+            fs.writeFileSync('cli/package.json', JSON.stringify(pkg, null, '\t'));
           "
 
           echo "Using version ${{ steps.version.outputs.version }} for build"
-          cat cli-ts/package.json | grep '"version"'
-
-      - name: Clean previous builds
-        if: steps.check_commits.outputs.skip != 'true'
-        run: rm -rf dist-standalone
+          cat cli/package.json | grep '"version"'
 
       - name: Build and package CLI
         if: steps.check_commits.outputs.skip != 'true'
@@ -119,7 +104,6 @@ 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: node scripts/package-npm.mjs
 
       - name: Verify build output
@@ -128,16 +112,14 @@ jobs:
           echo "Checking dist-standalone directory..."
           ls -la dist-standalone/
 
-          echo "Checking dist-standalone/dist..."
-          ls -la dist-standalone/dist/
+          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
+          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,28 @@ 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: |
+                  for FILE in webview-ui/src/assets/cline_kanban_demo.mp4 webview-ui/src/assets/cline_kanban_demo.webm; do
+                    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
+                  done
+
             - 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,24 @@ 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: |
+                  for FILE in webview-ui/src/assets/cline_kanban_demo.mp4 webview-ui/src/assets/cline_kanban_demo.webm; do
+                    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
+                  done
 
             - name: Package and Publish Extension
               env:
@@ -121,7 +172,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 +188,34 @@ 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 }}
+
+            - name: Post release to Slack
+              uses: slackapi/slack-github-action@v3.0.1
+              with:
+                  method: chat.postMessage
+                  token: ${{ secrets.SLACK_RELEASE_BOT_TOKEN }}
+                  payload: |
+                    channel: "C0APVKGGZFC"
+                    text: "Cline ${{ steps.resolve_tag.outputs.tag }}"
+                    blocks:
+                      - type: "section"
+                        text:
+                          type: "mrkdwn"
+                          text: "*Cline ${{ steps.resolve_tag.outputs.tag }}*"
+                      - type: "section"
+                        text:
+                          type: "mrkdwn"
+                          text: ${{ toJSON(steps.changelog.outputs.content) }}
+                      - type: "context"
+                        elements:
+                          - type: "mrkdwn"
+                            text: "Full Changelog: https://github.com/${{ github.repository }}/compare/${{ steps.prev_tag.outputs.prev_tag }}...${{ steps.resolve_tag.outputs.tag }}"

.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,35 +141,18 @@ 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: Download ripgrep binaries
@@ -194,17 +162,11 @@ jobs:
               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
+              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
@@ -47,3 +48,11 @@ test-results
 .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

.mocharc.json

@@ -3,7 +3,11 @@
 		"ts"
 	],
 	"spec": [
-		"src/**/__tests__/*.ts"
+		"src/**/__tests__/*.ts",
+		"src/test/services/**/*.test.ts"
+	],
+	"ignore": [
+		"src/sdk/**"
 	],
 	"require": [
 		"ts-node/register",

.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)

ARCHITECTURE.md

@@ -0,0 +1,940 @@
+# SDK Migration — Architecture & Design
+
+Evergreen reference for the Cline SDK migration project. For the
+living implementation plan, see `migration.md`.
+
+## References
+
+### Code References
+
+Cline SDK is at ~/clients/cline/sdk-wip
+Cline (core, classic VSCode extension, CLI) is at ~/clients/cline/cline
+JetBrains Plugin is at ~/clients/cline/intellij-plugin
+IntelliJ open source reference is at ~/clients/cline/intellij-community
+JCEF (Java-Chromium embedded framework reference) is at ~/clients/cline/jcef
+
+You can use kb_search with these identifiers to understand the
+existing code and the SDK code:
+
+cline - Cline core, classic VSCode extension, CLI
+sdk - Cline SDK
+plugin - JetBrains plugin
+vscode - Visual Studio Code opens source
+ij - IntelliJ open source
+jcef - JCEF IntelliJ's embedded Chromium layer
+
+Prototype VSCode extension on SDK is at ~/clients/cline/sdk-vscode-sample
+Prototype JetBrains plugin on SDK is at ~/clients/cline/sdk-intellij-plugin-sample
+
+These are prototypes with features missing and added, so refer to them
+as examples, but don't overindex on them.
+
+### Documentation references
+
+See the ~/clients/cline/cline/docs for extension product documentation
+and ~/clients/cline/sdk-wip/*.md for SDK documentation.
+
+### Background on the products & architecture
+
+There's a VSCode extension in cline/src. A large part of its UI is a
+React-based webview in cline/webview-ui.
+
+There's a JetBrains plugin in the intellij-plugin repo. It packages
+the core of the VSCode extension, including the webview, and
+communicates with it with protobufs. There's a bunch of stuff in the
+cline repo called "standalone" which is what JetBrains communicates
+with.
+
+In cline/cli there's a CLI and Kanban tool. Those use the SDK/are
+being ported separately to the SDK, so you don't need to worry about
+them. It is OK if you have to break them. Just ignore them.
+
+Note, there was an earlier, failed attempt at a cli in go. The go cli
+used to use "standalone" like JetBrains. If there's any old go support
+cluttering up the repo, it is fine to delete it and clean it up.
+
+The source code and docs mentioned above are the best reference to the
+product architecture, behavior, etc. Feel free to ask clarifying
+questions when necessary.
+
+---
+
+## Features
+
+### Features to remove
+
+Terminal integration: There is legacy code in the VSCode extension,
+and stubs in the RPC system for JetBrains, which used the IDE's
+integrated terminals. We have decided we don't need these old modes
+and they should be removed. Instead we will rely on "background
+terminal". This literally means the node code forks and execs a shell
+and uses pipes to communicate with it.
+
+Browser automation: Remove the system that uses Playwright to automate
+browsers. These use cases are now well served by third-party MCP
+tools.
+
+"Shadow git" checkpointing system. This is too slow, especially on
+Windows. The way the Kanban project uses the existing git repo to
+store references, and only after each user message, is better. So we
+will drop the "shadow copy" git checkpointing system.
+
+Memory bank, structured context: multi-file documentation
+(projectbrief, productContext, activeContext, systemPatterns,
+techContext, progress.)
+
+Memory bank, persistence: cross-session context preservation.
+
+Focus chain, task tracking: Auto-generated to-do list with real-time
+progress indicators.
+
+Focus chain, integration: Editable focus chain integration with deep
+planning and reminders.
+
+Deep planning exploration, output and the /deep-planning command.
+
+Workflows (definition, natural language + XML tool syntax, MCP tools
+and user input prompts) ... these have been superceded by SKILLS
+moving forward.
+
+Slash commands no longer necessary:
+
+/deep-planning (codebase investigation + plan... we have plan/act mode)
+/reportbug (bug reporting with diagnostics)
+Custom workflows (/workflow.md for user-defined workflows... we have "skills" now.)
+
+### Core features
+
+These must work:
+
+File operations: read, write, search, replace, list files, inspect
+code definitions (functions, classes, methods)
+
+Terminal integration: "Background terminal" must work. The agent
+relies on this to run npm, git, docker, etc.
+
+Multi-provider AI models: 30+ providers with seamless
+switching. There's one provider of note: VSCode has a provider which
+hooks up to Copilot using the VSCode LM Provider API. It would be good
+to support this *if possible.*
+
+Auto-approve & YOLO mode
+- Granular per-tool permission controls
+- YOLO mode for maximum automation
+- Monitoring, notifications for long-running commands
+
+Auto-compaction
+- Summarization automatically compresses conversations when context fills
+- Model support for Claude, Gemini, GPT-5, Grok, etc.
+
+Subagents
+- Parallel execution of independent research agents
+- Isolation with separate context windows
+- Cost tracking for task usage per subagent
+
+Web search and web fetch
+
+Worktrees
+- git worktrees for parallel sessions
+- branch management and .worktreeinclude support
+- conflict resolution and merging
+
+Workspaces
+- "multi-root" workspaces/projects with multiple root folders
+- @workspace:path scoped references
+
+Jupyter Notebooks
+- Generate, explain, and improve notebook cells
+
+Cline Rules
+- project-specific .cline/rules and global instructions.
+- Conditional logic: Path-based activation of rules.
+- Compatibility: Works with Cursor Rules, Windsurf rules, AGENTS.md
+
+Skills
+- SKILL.md format with YAML frontmatter
+- Loading levels: Metadata, instructions and resources
+- Scope: Global and project-specific; toggleable
+
+Hooks
+- Events: Task lifecycle + tool events (TaskStart, PreToolUse, etc.)
+- Runtimes: bash, powershell for Windows
+- IO: JSON
+- Context injection: Be able to modify or inject context dynamically
+
+.clineignore
+- Exclusion rules, gitignore-style file/directory exclusion
+- Exceptions: ! prefix for overrides
+- Override behavior: Explicit @ mentions bypass ignore rules
+
+MCP (Model Context Protocol)
+- Server management: Discovery, enable/disable, restart, config editing
+- Transport: stdio (local) and SSE (remote)
+- ...all the typical use cases for MCP: APIs, browser automation, db queries, etc.
+
+### Core workflows
+
+These must work:
+
+Task Management
+
+Task lifecycle - create and resume tasks; view task history
+Cost tracking - token using and cost monitoring per task
+
+Plan & Act Mode
+Plan mode - Explore and investigate without modifying files
+Act mode - Implementation with approval gates
+Model config - Separate model configuration for plan and act mode if
+               the user desires
+State persistence - Mode switching, task switching preserves history
+
+File context (@-mentions)
+Context referencing - Reference files, folders, terminal output, git
+changes, URLs, commits via @
+
+Slash commands
+/newtask (new task)
+/smol (compress history)
+/newrule (create rules)
+
+### Model Configuration
+
+We want to continue supporting our 30+ providers (Anthropic, OpenAI,
+OpenAI Codex, OpenRouter, Google Gemini, AWS Bedrock, DeepSeek,
+Cerebras, Qwen, Mistral, Groq, Fireworks, Together, xAI Grok,
+Moonshot, Nebius, HuggingFace, LiteLLM, Ollama, LM Studio, and more.)
+
+THE MOST IMPORTANT REQUIREMENT HERE, after continuing to support them,
+is to USE THE CREDENTIALS, MODEL NAMES, CONFIGS, etc. WE HAVE
+SAVED. Logging people out of their providers is really annoying to
+users; regenerating API keys is painful for them.
+
+VSCode LM API provider may be an interesting/unusual provider out of
+this set; it only works in VSCode by calling a specific API.
+
+We must continue supporting local models like Ollama and LM Studio.
+
+We must support the Cline provider with unified auth (open a
+webbrowser, handle the SSO redirect), built-in billing and credit
+display, banners advertising new or free models, stealth/early access
+models, organization switching.
+
+### Enterprise Features
+
+Security and governance
+- Client-side execution only (no data transmission outside of limited
+  Telemetry and inference; no remote codebase indexing)
+- SSO role-based access control (member, admin, owner)
+- Model and tool controls per team
+- Remote configuration downloaded and applied by the extension
+
+Observability
+- OpenTelemetry, Datadog, Grafana, Splunk integrations
+- Real-time analytics, cost breakdown by team, selective audit logging
+
+Infrastructure
+- AWS Bedrock, Google Vertex AI, Azure OpenAI integration
+- Bring-your-own-inference with custom endpoints
+
+### Priority "P1" (mid priority) items
+
+Checkpoints - automatic file snapshots after each change. Note, the
+snapshot system in the VSCode extension and JetBrains plugin which
+copies the whole repository is slow, *especially on Windows*, so we
+should replace it with one that writes refs directly into the local
+git repo. Look at the way the kanban project does it; this is
+preferred (and maybe we should extract and share this code.)
+
+Diffing - compare changes between checkpoints
+
+Restore - restore files, task to a point, or both
+
+MCP Marketplace - we could get rid of this, but ultimately we do want
+this feature with major improvements like allowing remote install. For
+now, consider removing it, but if it is easier to keep it around let's
+do that to lay the groundwork for improvements.
+
+### Priority "P2" (lower priority) items
+
+Task organization - favorites for task grouping and management
+
+File context - Drag and drop files to add to context
+File context - actions - context menus to add to Cline, fix, explain, improve
+
+Slash commands
+/explain-changes (git diff explanation)
+
+---
+
+## Detailed Design
+
+### Naming: "Sdk..." considered harmful
+
+Do not name types "SdkFoo" or folders "sdk". If you need to use SdkFoo
+as a way to keep two classes around in parallel while you're porting,
+that's OK, but when this project is done we want to have one clean,
+simple codebase; the SDK backing is an implementation detail so just
+use simple noun phrases for classes, etc. and don't litter "Sdk" all
+over identifiers and folders.
+
+### Proto deprecation and removal
+
+We don't need proto files to describe webview messages. The webview
+and extension backend are both in TypeScript and are versioned and
+shipped together. We just need to use shared TypeScript interfaces
+between them.
+
+We *also* don't need proto to describe JetBrains <--> node
+exchanges. We just need something typed and in sync between Kotlin and
+TypeScript that we can serialize. JSON probably makes sense. Protos
+are OK but we have had problems with that setup creating a ton of GC
+pressure on the Kotlin side, hit maximum message size limits, etc.
+
+There are proto build steps which we can remove, as we use proto less.
+
+protos are useful for state which is serialized. If there are files
+that are persisted described by protos, it is ok/good to keep
+them. Don't expand the use of protos to places protos are not already
+used.
+
+### Web View UI
+
+The Webview UI is very dependent on state arising from implementation
+details of the pre-SDK implementation. At the same time, we don't want
+to build a new UI from scratch right now because it may be forcing too
+many changes upon our users at once. So we aim to reuse the existing
+webview, but with radical simplificiation in its state management now
+that we will have a cleaner architecture in the extension "backend"
+with the layering enforced by the SDK.
+
+The webview UI had defects like showing the wrong keybindings for
+JetBrains, or using tons of memory or CPU cycles by spamming state
+updates really rapidly or sending n^2 state updates as they streamed
+in. The first principle of this migration to the SDK is not get worse,
+but at the same time, we expect the state clean-up necessary in the
+webview will lead to radical simplifications which make some
+low-hanging fruit available in performance. It's great to go make
+those improvements where they are available.
+
+We don't need this UI to be pixel perfect identical. We need it to be
+FAMILIAR, NOT WORSE and preferably BETTER than the status quo.
+
+### Data formats, settings
+
+We MUST pick up existing on-disk state for settings, etc. We don't
+want to log users out of their inference providers as we make this
+change to the SDK.
+
+The CLI, VSCode extension and JetBrains extension largely share state
+on disk. We should continue that situation. If data migrations are
+necessary, that's fine, but design them with care. In particular, we
+want the long term to be fast, so we should write breadcrumbs
+indicating when migration is done. In addition, users can upgrade and
+downgrade their extension versions, etc. and we want to be robust to
+that in addition to all kinds of failures. For example, in the past we
+had problems where we overwrote a JSON settings file, perhaps racily,
+and left trailing }s in the file and this caused the product to
+totally fail. That's a very serious issue for our users so pay extra
+effort and attention to what is happening on disk. (We want PRACTICAL
+solutions and robustness and not performative solutions that just add
+tons of code and complexity with no real benefit.)
+
+Invalidating old checkpoints is acceptable, unless it is particularly
+cheap to support the classic checkpoints. We won't be authoring those
+checkpoints any more, and it would be heavy to migrate them.
+
+We want to move from .clinerules (old style) to .cline/rules (new style.)
+
+### Telemetry
+
+We generally want to continue sending the same Telemetry events. If
+that is hard, make a detailed report and we can follow up with our
+backend team. Note some enterprise features depend on OTEL
+observability.
+
+### Code Sharing
+
+In general we should share code between IDEs where there are benefits
+to do so. However trivial tools, or tools specific to a given IDE, can
+be wired up directly from the extension through to the SDK. (This is
+something that was hard to do in the old architecture and we would
+like to make easier.)
+
+---
+
+## Research Findings
+
+### SDK Session Backend Extensibility
+
+**Question**: Does the SDK's `SessionBackend` interface support
+storing arbitrary per-task data (e.g., tool settings, hook
+configuration, auto-approve preferences per task)?
+
+**Answer**: Partially. The `SessionRow` has a `metadata:
+Record<string, unknown> | null` field that can store arbitrary
+key-value data per session. This is sufficient for per-task settings
+like auto-approve preferences, tool configuration, etc.
+
+The SDK supports three backend implementations:
+1. `SqliteSessionStore` — SQLite-backed (default, preferred)
+2. `FileSessionService` — JSON file-backed (fallback when SQLite
+   unavailable)
+3. `RpcCoreSessionService` — delegates to an RPC server
+
+For our migration, we'll use either `FileSessionService` or provide a
+custom `SessionPersistenceAdapter` that reads/writes our existing task
+history format. The `ClineCoreOptions.sessionService` field accepts
+any backend implementing `CoreSessionService | RpcCoreSessionService |
+FileSessionService`.
+
+**Key finding**: The `SessionPersistenceAdapter` interface is the
+cleanest extension point. It requires implementing: `ensureSessionsDir`,
+`upsertSession`, `getSession`, `listSessions`, `updateSession`,
+`deleteSession`, `enqueueSpawnRequest`, `claimSpawnRequest`. Our
+`LegacySessionBackend` adapter wraps the existing
+`~/.cline/data/tasks/` directory and `taskHistory` JSON array in
+`globalState.json`, mapping between `SessionRow` fields and our
+`HistoryItem` type:
+
+```
+HistoryItem.id          → SessionRow.sessionId
+HistoryItem.ts          → SessionRow.startedAt (ISO string)
+HistoryItem.task        → SessionRow.prompt
+HistoryItem.tokensIn    → metadata.tokensIn
+HistoryItem.tokensOut   → metadata.tokensOut
+HistoryItem.totalCost   → metadata.totalCost
+HistoryItem.modelId     → SessionRow.model
+HistoryItem.isFavorited → metadata.isFavorited
+```
+
+Per-task files (`api_conversation_history.json`, `ui_messages.json`)
+map to `SessionRow.messagesPath` and `SessionRow.transcriptPath`.
+
+**Decision**: We will provide a custom `SessionPersistenceAdapter`
+that translates between our existing format and the SDK's interface.
+No need for a separate sidecar storage layer. The `metadata` field
+handles all per-task extensions.
+
+### Telemetry Event Mapping
+
+The extension currently emits telemetry events via a PostHog-based
+`TelemetryService`. The SDK has its own `TelemetryService` with
+pluggable adapters (`OpenTelemetryAdapter`, `LoggerTelemetryAdapter`).
+
+**Mapping of current extension events → SDK events:**
+
+| Extension Event | SDK CORE_TELEMETRY_EVENTS | Notes |
+|---|---|---|
+| `user.extension_activated` | `CLIENT.STARTED` ("extension.activated") | ✅ Same event name |
+| `user.auth_started` | `USER.AUTH_STARTED` | ✅ Direct match |
+| `user.auth_succeeded` | `USER.AUTH_SUCCEEDED` | ✅ Direct match |
+| `user.auth_failed` | `USER.AUTH_FAILED` | ✅ Direct match |
+| `user.auth_logged_out` | `USER.AUTH_LOGGED_OUT` | ✅ Direct match |
+| `task.created` | `TASK.CREATED` | ✅ Direct match |
+| `task.restarted` | `TASK.RESTARTED` | ✅ Direct match |
+| `task.completed` | `TASK.COMPLETED` | ✅ Direct match |
+| `task.conversation_turn` | `TASK.CONVERSATION_TURN` | ✅ Direct match |
+| `task.tokens` | `TASK.TOKEN_USAGE` | ✅ Direct match |
+| `task.mode` | `TASK.MODE_SWITCH` | ✅ Direct match |
+| `task.tool_used` | `TASK.TOOL_USED` | ✅ Direct match |
+| `task.skill_used` | `TASK.SKILL_USED` | ✅ Direct match |
+| `task.diff_edit_failed` | `TASK.DIFF_EDIT_FAILED` | ✅ Direct match |
+| `task.provider_api_error` | `TASK.PROVIDER_API_ERROR` | ✅ Direct match |
+| `task.mention_used` | `TASK.MENTION_USED` | ✅ Direct match |
+| `task.mention_failed` | `TASK.MENTION_FAILED` | ✅ Direct match |
+| `task.mention_search_results` | `TASK.MENTION_SEARCH_RESULTS` | ✅ Direct match |
+| `task.subagent_started` | `TASK.SUBAGENT_STARTED` | ✅ Direct match |
+| `task.subagent_completed` | `TASK.SUBAGENT_COMPLETED` | ✅ Direct match |
+| `hooks.discovery_completed` | `HOOKS.DISCOVERY_COMPLETED` | ✅ Direct match |
+| `session.started` | `SESSION.STARTED` | ✅ Direct match |
+| `session.ended` | `SESSION.ENDED` | ✅ Direct match |
+
+**Extension events with NO SDK equivalent (need adapter-layer emit):**
+
+| Extension Event | Action |
+|---|---|
+| `user.opt_out` / `user.opt_in` | Emit via SDK's `captureRequired()` |
+| `user.telemetry_enabled` | Emit via SDK's `capture()` |
+| `user.extension_storage_error` | Emit via SDK's `capture()` |
+| `user.onboarding_progress` | Emit via SDK's `capture()` |
+| `workspace.*` (initialized, vcs_detected, etc.) | Emit via SDK's `capture()` |
+| `task.feedback` | Emit via SDK's `capture()` |
+| `task.option_selected` / `task.options_ignored` | Emit via SDK's `capture()` |
+| `task.checkpoint_used` | Emit via SDK's `capture()` |
+| `task.mcp_tool_called` | Emit via SDK's `capture()` |
+| `task.historical_loaded` | Emit via SDK's `capture()` |
+| `task.retry_clicked` | Emit via SDK's `capture()` |
+| `task.slash_command_used` | Emit via SDK's `capture()` |
+| `task.feature_toggled` | Emit via SDK's `capture()` |
+| `task.rule_toggled` | Emit via SDK's `capture()` |
+| `task.auto_condense_toggled` | Emit via SDK's `capture()` |
+| `task.yolo_mode_toggled` | Emit via SDK's `capture()` |
+| `task.terminal_*` (execution, output_failure, hang) | Emit via SDK's `capture()` |
+| `task.initialization` | Emit via SDK's `capture()` |
+| `task.summarize_task` | Emit via SDK's `capture()` |
+| `ui.*` (model_selected, button_clicked, etc.) | Emit via SDK's `capture()` |
+| `hooks.enabled` / `hooks.disabled` | Emit via SDK's `capture()` |
+| `hooks.cancel_requested` | Emit via SDK's `capture()` |
+| `hooks.context_modified` | Emit via SDK's `capture()` |
+| `worktree.*` | Emit via SDK's `capture()` |
+| `host.detected` | Emit via SDK's `capture()` |
+
+**Extension events being REMOVED (features deleted):**
+
+| Extension Event | Reason |
+|---|---|
+| `task.browser_tool_start/end/error` | Browser automation removed |
+| `task.focus_chain_*` (6 events) | Focus chain removed |
+| `task.workspace_search_pattern` | Folded into SDK search |
+| `task.subagent_enabled/disabled` | Toggle events; SDK manages directly |
+| `task.cline_web_tools_toggled` | Feature simplified |
+| `cline.grpc.response.size_bytes` | gRPC being removed |
+
+**Metrics (OTEL counters/histograms):**
+
+The extension has ~30 OTEL metrics (`cline.turns.total`,
+`cline.tokens.input.total`, `cline.api.ttft.seconds`, etc.). The SDK
+telemetry service supports `recordCounter`, `recordHistogram`, and
+`recordGauge`. We will emit these same metrics from the adapter layer
+using `telemetry.recordCounter()` / `telemetry.recordHistogram()`.
+The metric names can stay the same.
+
+**Decision**: The SDK's `ITelemetryService.capture()` is a generic
+event emitter — we can emit ALL extension events through it. The
+adapter layer will create a thin telemetry wrapper that provides
+the same `captureTaskCreated()`, `captureToolUsage()`, etc. methods
+but delegates to the SDK's telemetry service. Events where the SDK
+already has a helper function (listed in the first table) use those
+directly. Others use `capture({ event, properties })`. No backend
+team coordination needed for the initial migration.
+
+### JetBrains IPC Design
+
+#### Current Architecture
+
+```
+┌── Kotlin Plugin ──────────────────────────────┐
+│                                                │
+│  CoreProcessManager                            │
+│    └─ launches Node.js process (cline-core)    │
+│    └─ communicates via gRPC ProtoBus           │
+│       (port 26040-26340)                       │
+│                                                │
+│  HostBridgeService (gRPC server, port 26041)   │
+│    ├─ DiffService                              │
+│    ├─ WindowService (show file, open dialog)   │
+│    ├─ WorkspaceService (paths, diagnostics)    │
+│    ├─ EnvService                               │
+│    └─ TestingService (get webview HTML)         │
+│                                                │
+│  ProtoBusProxyService                          │
+│    └─ proxies webview ↔ cline-core gRPC        │
+│                                                │
+│  JsPostMessageHandler                          │
+│    └─ injects JS bridge into JCEF webview      │
+│    └─ converts postMessage → gRPC request      │
+│                                                │
+│  WebViewManager                                │
+│    └─ loads webview HTML in JCEF                │
+│    └─ receives gRPC responses → postMessage    │
+└────────────────────────────────────────────────┘
+```
+
+Problems with this architecture:
+- **Proto size limits**: gRPC messages hit 256MB limits with large
+  conversations. The `ProtoBusProxyService` logs warnings at 10MB+.
+- **Java heap pressure**: Serializing/deserializing large proto
+  messages stresses the JVM heap.
+- **Build complexity**: Proto compilation required for both
+  TypeScript and Java/Kotlin.
+- **Stateless-in-theory**: The design is somewhat stateless but we
+  haven't leveraged restart-for-reliability because state
+  reconstruction is expensive.
+
+#### Target Architecture
+
+```
+┌── Kotlin Plugin ──────────────────────────────┐
+│                                                │
+│  CoreProcessManager                            │
+│    └─ launches SDK sidecar (Node.js)           │
+│    └─ communicates via JSON-RPC over stdio     │
+│                                                │
+│  HostCallbackService (JSON-RPC server)         │
+│    ├─ showTextDocument, openDialog             │
+│    ├─ getWorkspacePaths, getDiagnostics        │
+│    ├─ getEnvVars, clipboard                    │
+│    └─ (extensible for PSI, run configs, etc.)  │
+│                                                │
+│  WebviewBridge                                 │
+│    └─ receives JSON messages from sidecar      │
+│    └─ forwards to JCEF via executeJavaScript   │
+│    └─ receives postMessage from JCEF           │
+│    └─ forwards to sidecar via stdio            │
+│                                                │
+│  WebViewManager                                │
+│    └─ loads adapted webview in JCEF            │
+└────────────────────────────────────────────────┘
+
+┌── SDK Sidecar (Node.js) ──────────────────────┐
+│                                                │
+│  SidecarMain                                   │
+│    └─ JSON-RPC over stdio (bidirectional)      │
+│    └─ imports @clinebot/core                   │
+│    └─ shares SDK adapter layer with VSCode     │
+│                                                │
+│  ClineCore instance                            │
+│    └─ session management                       │
+│    └─ tool execution                           │
+│    └─ provider handling                        │
+│                                                │
+│  HostCallbackClient                            │
+│    └─ calls back to Kotlin for IDE ops         │
+│    └─ registered as tool executors in SDK      │
+│                                                │
+│  WebviewBridge                                 │
+│    └─ translates SDK events → webview messages │
+│    └─ same code as VSCode adapter              │
+└────────────────────────────────────────────────┘
+```
+
+#### IPC Mechanism: JSON-RPC over stdio
+
+**Why JSON-RPC over stdio instead of gRPC:**
+- **No message size limits**: JSON over stdio has no inherent size
+  cap. Conversations with 100K+ tokens serialize to ~5-20MB JSON
+  which flows fine over pipes.
+- **No heap pressure**: No proto serialization on the Java side.
+  Kotlin reads/writes JSON strings directly. JCEF already works
+  with JSON.
+- **No proto compilation**: Eliminates the Java protobuf dependency
+  and the dual TypeScript/Java proto generation step.
+- **Simple**: Well-understood protocol. Easy to debug (just read
+  the pipe).
+
+**Protocol**: JSON-RPC 2.0 over stdin/stdout with newline-delimited
+JSON messages. The sidecar reads from stdin and writes to stdout.
+Stderr is reserved for logging.
+
+```
+→ {"jsonrpc":"2.0","method":"session/start","params":{...},"id":1}
+← {"jsonrpc":"2.0","result":{"sessionId":"..."},"id":1}
+← {"jsonrpc":"2.0","method":"webview/message","params":{"type":"assistant_delta","text":"..."}}
+```
+
+**Notifications** (no `id`) are used for streaming events
+(assistant deltas, tool events, state updates). The Kotlin plugin
+processes these and forwards them to the JCEF webview.
+
+**Callbacks** from sidecar → Kotlin (host operations) use
+JSON-RPC requests in the reverse direction:
+
+```
+← {"jsonrpc":"2.0","method":"host/showTextDocument","params":{"path":"..."},"id":100}
+→ {"jsonrpc":"2.0","result":{"success":true},"id":100}
+```
+
+#### Code Sharing Between VSCode, JetBrains, and CLI
+
+The shared SDK adapter layer contains:
+
+```
+src/sdk-adapter/
+  index.ts              — ClineSdkHost (creates ClineCore instance)
+  session-backend.ts    — LegacySessionBackend adapter
+  webview-bridge.ts     — SDK events → webview message translation
+  provider-migration.ts — Legacy provider settings migration
+  approval-adapter.ts   — Auto-approve settings → SDK tool policies
+  telemetry-adapter.ts  — Extension telemetry → SDK telemetry
+  types.ts              — WebviewInbound, WebviewOutbound types
+```
+
+Each host then has a thin integration layer:
+
+- **VSCode** (`src/hosts/vscode/sdk-extension.ts`): In-process.
+  Creates `ClineSdkHost`, registers VSCode LM handler, manages
+  webview lifecycle. Uses `postMessage` for webview communication.
+
+- **JetBrains** (`src/sidecar/main.ts`): Separate process. Creates
+  `ClineSdkHost`, reads/writes JSON-RPC on stdio. Registers
+  `HostCallbackClient` for IDE operations. The webview bridge code
+  is identical — it just sends messages over stdio instead of
+  `postMessage`.
+
+#### Statefulness and Reliability
+
+The sidecar is **stateful** — it holds the `ClineCore` instance with
+active sessions in memory. However, it is designed for **graceful
+restart**:
+
+- **Session persistence**: All session state is written to disk
+  after each turn (messages, manifest, transcript). On restart, the
+  sidecar re-reads the session index and can resume.
+- **Crash detection**: The Kotlin plugin monitors the sidecar
+  process. If it exits unexpectedly, the plugin restarts it after a
+  brief delay (same as current `CoreProcessManager.RESTART_DELAY`).
+- **Smaller messages**: Because the protocol is JSON-RPC with
+  incremental streaming (notifications for each delta), the
+  messages are much smaller than the current gRPC approach which
+  sends full state snapshots. This eliminates the heap pressure
+  that made the current system unreliable.
+- **Interrupted operations**: If the sidecar crashes mid-turn, the
+  next startup detects the unfinished session (status = "running"
+  but no live process) and marks it as interrupted, just like the
+  current task resumption flow.
+
+#### JetBrains-Specific Tools
+
+The HostCallback pattern makes it easy to add JetBrains-specific
+capabilities without changing shared code:
+
+1. **Registration**: The sidecar's `HostCallbackClient` declares
+   what capabilities the host supports (e.g., `"psi"`, `"runConfigs"`).
+2. **Tool Executors**: JetBrains-specific tool executors are
+   registered in `ClineCoreOptions.defaultToolExecutors` when the
+   sidecar starts. For example, a `getDiagnostics` executor that
+   calls `host/getDiagnostics` via JSON-RPC to get IntelliJ's PSI
+   analysis results.
+3. **No shared code changes**: Adding a new JetBrains capability
+   requires:
+   - Implementing the handler in Kotlin (`HostCallbackService`)
+   - Adding a JSON-RPC method in the sidecar's `HostCallbackClient`
+   - Optionally registering a custom tool executor
+
+Example for exposing JetBrains PSI:
+```kotlin
+// Kotlin side
+"host/getPsiStructure" -> {
+    val file = PsiManager.getInstance(project).findFile(virtualFile)
+    // ... extract structure
+    respondWithJson(result)
+}
+```
+```typescript
+// Sidecar side - registered as a custom tool executor
+defaultToolExecutors: {
+  list_code_definition_names: async (args) => {
+    // Call back to JetBrains for richer PSI-based results
+    const result = await hostCallback.call("host/getPsiStructure", { path: args.path });
+    return result;
+  }
+}
+```
+
+---
+
+## Architecture Overview
+
+### Current Architecture
+```
+┌─── VSCode Extension ──┐  ┌── JetBrains Plugin ──┐  ┌──── CLI ────┐
+│  WebviewProvider       │  │  Kotlin Plugin       │  │  React Ink  │
+│  Controller            │  │  CoreProcessManager  │  │  ClineAgent │
+│  Task                  │  │  ProtoBusProxy       │  │             │
+│  API providers (30+)   │  │  JCEF WebView        │  │             │
+│  McpHub                │  │                      │  │             │
+│  Webview (React)       │  │  ↓ gRPC              │  │             │
+│                        │  │  cline-core           │  │             │
+│  proto/cline/*.proto   │  │  (standalone Node)    │  │             │
+└────────────────────────┘  └──────────────────────┘  └─────────────┘
+```
+
+### Target Architecture
+```
+┌─── VSCode Extension ──┐  ┌── JetBrains Plugin ──┐  ┌──── CLI ────┐
+│  SDK Adapter Layer     │  │  Kotlin Plugin       │  │  React Ink  │
+│  @clinebot/core        │  │                      │  │  TUI        │
+│  (in-process)          │  │  ↓ JSON-RPC/stdio    │  │             │
+│  Webview (adapted)     │  │  SDK sidecar (Node)  │  │             │
+│                        │  │  @clinebot/core      │  │             │
+│  registerHandler       │  │                      │  │             │
+│  ("vscode-lm", ...)   │  │  Webview (adapted)    │  │             │
+└────────────────────────┘  └──────────────────────┘  └─────────────┘
+
+All clients backed by:
+  @clinebot/core → @clinebot/agents → @clinebot/llms
+       ↓                  ↓                   ↓
+    Sessions          Tools/Hooks        Providers
+    Storage           MCP Bridge         Model Catalog
+    Telemetry         Teams/Spawn        Handler Registry
+```
+
+---
+
+## What the SDK Already Provides
+
+These capabilities exist in the SDK and do not need to be rebuilt:
+
+1. **Legacy provider settings migration** —
+   `migrateLegacyProviderSettings()` reads `globalState.json` +
+   `secrets.json`, writes to `providers.json`. Handles Anthropic,
+   OpenAI, OpenAI Codex OAuth, OpenRouter, Bedrock, custom
+   OpenAI-compatible endpoints, etc. Existing providers are never
+   overwritten. Migrated entries are tagged `tokenSource: "migration"`.
+
+2. **30+ provider handlers** — Anthropic, OpenAI (chat + responses
+   API), Google Gemini, AWS Bedrock, Vertex AI, DeepSeek, Ollama,
+   LM Studio, Mistral, Groq, Fireworks, Together, xAI, Cerebras,
+   LiteLLM, Nebius, HuggingFace, and more.
+
+3. **Custom handler registry** — `registerHandler(id, factory)` and
+   `registerAsyncHandler(id, factory)` for providers that need
+   host-specific dependencies (e.g., VSCode LM API).
+
+4. **MCP management** — `InMemoryMcpManager` with stdio, SSE, and
+   streamableHttp transports. Config loader reads from
+   `~/.cline/data/settings/mcp.json` with Zod validation. Supports
+   legacy format migration.
+
+5. **Tool framework** — 8 built-in tools: `read_files`,
+   `search_codebase`, `run_commands`, `editor`, `apply_patch`,
+   `fetch_web_content`, `skills`, `ask_question`. Preset system with
+   `development` (act mode) and `readonly` (plan mode) presets.
+   Per-tool enable/disable. Policy-based approval (auto-approve,
+   require-approval, per-tool overrides). Model-aware tool routing
+   (e.g., OpenAI models use `apply_patch` instead of `editor`).
+
+6. **Session lifecycle** — `ClineCore.create()` → `host.start()` /
+   `host.send()` / `host.abort()` / `host.stop()` / `host.subscribe()`
+   Interactive mode with prompt queueing (`queue`/`steer` delivery).
+   Event subscription for streaming.
+
+7. **Telemetry** — `TelemetryService` with pluggable adapters:
+   `OpenTelemetryAdapter` (for enterprise OTEL), `LoggerTelemetryAdapter`.
+   Standard events: `session.started`, `session.ended`,
+   `task.created`, `task.conversation_turn`, `task.tool_used`, etc.
+   See "Telemetry Event Mapping" above for full mapping.
+
+8. **Rules & Skills** — Discovery from `.clinerules/`,
+   `~/Documents/Cline/Rules`, `~/.cline/data/settings/rules/`.
+   SKILL.md format with YAML frontmatter. Global and project scopes.
+
+9. **Hooks** — `HookEngine` with lifecycle events. Node subprocess
+   hook helpers for bash/powershell execution.
+
+10. **Subagents/Teams** — `AgentTeamsRuntime`, spawn tools, team
+    coordination with concurrent teammate agents.
+
+11. **System prompt generation** — `getClineDefaultSystemPrompt()`
+    with platform-aware customization.
+
+12. **OAuth token management** — `RuntimeOAuthTokenManager` handles
+    automatic token refresh during sessions for OAuth providers
+    (Cline, OpenAI Codex).
+
+13. **Storage isolation** — `CLINE_DIR`, `CLINE_DATA_DIR`,
+    `CLINE_SESSION_DATA_DIR` environment variables plus
+    `setClineDir()` / `setHomeDir()` APIs for test isolation.
+
+---
+
+## Test Strategy
+
+See `migration.md` for the phase-by-phase test plan. This section
+covers the evergreen test infrastructure and classification.
+
+### Test Infrastructure
+
+**Extension unit tests** use Mocha with a custom `requires.ts` that
+mocks `vscode` and `@integrations/checkpoints` modules. Config in
+`.mocharc.json`. These tests run without VSCode.
+
+**Webview tests** use Vitest with React Testing Library. Independent
+from the extension — they test React components in isolation.
+
+**E2E tests** use Playwright to drive a real VSCode instance with
+the extension loaded. They test chat, auth, diff editing, and editor
+integration against a mock API server on localhost:7777.
+
+**SDK adapter tests** use Vitest (simpler setup, better TypeScript
+support, no need for vscode-mock since adapter layer is
+VSCode-independent). Config in `vitest.config.sdk.ts`.
+
+### SDK Storage Isolation for Tests
+
+The SDK fully supports isolated test environments via environment
+variables and API calls:
+
+```typescript
+import { setClineDir, setHomeDir } from "@clinebot/shared/storage";
+const tempHome = mkdtempSync(join(tmpdir(), "test-home-"));
+process.env.HOME = tempHome;
+process.env.CLINE_DIR = join(tempHome, ".cline");
+process.env.CLINE_DATA_DIR = join(tempHome, ".cline", "data");
+setHomeDir(tempHome);
+setClineDir(process.env.CLINE_DIR);
+```
+
+### Test Framework Decisions
+
+- **Keep Mocha** for extension unit tests (existing infrastructure)
+- **Keep Vitest** for webview and CLI tests
+- **Keep Playwright** for VSCode E2E tests
+- **Add Vitest** for new SDK adapter tests
+- **Isolated home directories** for all new tests touching storage
+
+---
+
+## Manual QA Guide
+
+This section is for the QA team. It describes what has been removed
+(so you don't file bugs for missing features) and what areas carry
+the most regression risk after the SDK migration.
+
+### Removed Features — Do Not File Bugs
+
+- **Browser automation** — The built-in Playwright browser tool is
+  gone. Users should use third-party MCP browser tools instead.
+- **IDE terminal integration** — Commands now run exclusively in a
+  "background terminal" (headless shell). No terminal tab opens.
+- **Shadow-git checkpoints** — Existing checkpoints are invalidated.
+- **Memory bank / structured context** — All memory bank files and
+  UI removed.
+- **Focus chain** — No focus chain panel or inline indicators.
+- **Deep planning / `/deep-planning`** — Plan/Act mode remains as
+  the replacement.
+- **`/reportbug`** — Removed.
+- **Workflows** — Skills (SKILL.md format) are the replacement.
+- **Custom workflow slash commands** — Skills replace this.
+
+### Risk Areas — VSCode Extension
+
+1. **Provider credentials & model selection** — Verify existing API
+   keys survive the upgrade and downgrade.
+2. **Cline provider OAuth / SSO** — Test sign-in, sign-out, token
+   refresh, org switching.
+3. **Chat streaming & message display** — Watch for missing/duplicated
+   messages, broken streaming, performance regressions.
+4. **Tool approval flow** — Verify auto-approve, YOLO mode, per-tool
+   permissions.
+5. **Plan/Act mode** — Verify toggling, separate model configs,
+   state persistence.
+6. **Task history & resume** — Old tasks appear, can be resumed; new
+   tasks are saved.
+7. **MCP servers** — Existing configs picked up, tools work.
+8. **VSCode LM provider (Copilot)** — Verify it still works.
+9. **Settings UI** — All toggles and inputs persist correctly.
+10. **Webview performance** — Long conversations should not cause
+    sluggishness.
+
+### Risk Areas — JetBrains Extension
+
+1. **Sidecar process lifecycle** — Starts reliably, auto-restarts,
+   shuts down cleanly.
+2. **Webview communication** — Messages arrive, state is fresh.
+3. **Large conversations** — 100K+ tokens without OOM.
+4. **Host operations** — Open file, diagnostics, clipboard all work.
+5. **Keybindings** — Correct for the JetBrains platform.
+
+### Risk Areas — CLI
+
+1. **Agent backend replacement** — Core loop works in TUI and
+   headless modes.
+2. **Provider & model picker** — All providers appear, defaults
+   correct.
+3. **Shared state with IDE clients** — Credentials and history
+   visible across clients.
+4. **Slash commands** — Removed commands don't appear; remaining
+   ones work.
+5. **Worktrees & `--cwd`** — Function correctly.
+6. **ACP (Agent Communication Protocol)** — Programmatic usage works.

CAVEATS.md

@@ -0,0 +1,188 @@
+# SDK Migration Caveats & Known Issues
+
+Tracking issues found during the migration from the legacy inference system to the ClineCore SDK.
+
+## Status Legend
+- 🔴 **Blocker** — prevents core functionality
+- 🟡 **Minor** — cosmetic or UX annoyance
+- 🟢 **Fixed** — resolved
+
+---
+
+## Fixed
+
+### 1. 🟢 Remote inference fails with ECONNREFUSED (localhost:4000)
+**File:** `src/sdk/cline-session-factory.ts`  
+**Symptom:** Sending any message with the Cline provider fails after 6 retries with "Cannot connect to API" / ECONNREFUSED to `http://localhost:4000/v1/chat/completions`.  
+**Root cause:** Base URL overrides (`openAiBaseUrl`, `openRouterBaseUrl`, `liteLlmBaseUrl`) were applied unconditionally to ALL providers, clobbering the Cline API URL. A stale `openAiBaseUrl: "http://localhost:4000/v1"` in `~/.cline/data/globalState.json` overwrote `https://api.cline.bot/api/v1`.  
+**Fix:** Guard each base URL override with a provider check so it only applies to its respective provider.
+
+---
+
+### 2. 🟢 Task history not persisted after completion
+**File:** `src/sdk/SdkController.ts`  
+**Symptom:** After a task completes successfully, the task did NOT appear in the RECENT section when returning to the home screen.  
+**Root cause:** `newTask()` created a `currentTaskItem` but never pushed it to `this.taskHistory[]`. `clearTask()` discarded it without saving. No disk persistence implementation existed.  
+**Fix:** `SdkController` now persists tasks on three paths: (1) `done` event updates `currentTaskItem` with final usage and calls `persistCurrentTask()`, (2) `clearTask()` calls `persistCurrentTask()` before resetting, (3) `cancelTask()` persists the in-progress task. `LegacyStateReader` gained `saveTaskHistory()`, `saveUiMessages()`, and `deleteTaskDirectory()` methods for disk I/O.
+
+### 3. 🟢 Task resumption not implemented
+**File:** `src/sdk/SdkController.ts`  
+**Symptom:** Cannot resume a previous task from history.  
+**Fix:** `showTaskWithId()` now finds the task in history, loads saved UI messages via `legacyState.readUiMessages()`, restores them into the translator, and sets `currentTaskItem`. The task view renders with full message history.
+
+### 6. 🟢 Settings persistence is best-effort / incomplete
+**File:** `src/sdk/SdkController.ts`  
+**Symptom:** `updateSettings()` was a no-op stub with a TODO comment.  
+**Fix:** `updateSettings()` now persists settings to `globalState.json` via `legacyState.saveApiConfiguration()`. `updateAutoApprovalSettings()` also persists via the same mechanism.
+
+### 7. 🟢 Completed task not appearing in RECENT section
+**Where:** Home screen → RECENT section  
+**Symptom:** After completing a task and clicking "New Task", the completed task did not appear in the RECENT history list.  
+**Fix:** Resolved by issue #2 fix — tasks are now persisted to `taskHistory` on completion, so they appear in RECENT.
+
+### 8. 🟢 Top bar buttons are non-functional
+**Where:** Header bar — accounts, settings, new chat, history buttons  
+**Symptom:** Clicking any of the top bar buttons (accounts icon, settings gear, new chat +, task history) does nothing. No navigation occurs, no panels open.  
+**Root cause:** gRPC stub. The webview subscribes to `subscribeToSettingsButtonClicked`, etc. — these are event streams pushed from the extension host when VSCode title bar buttons are clicked.  
+**Fix:** Extension.ts button commands now send typed `navigate` messages via `WebviewGrpcBridge.navigate()`, bypassing gRPC streaming subscriptions. Plus button also calls `clearSdkTask()` to reset the SDK session.
+
+### 9. 🟢 @ mentions / autocomplete not working
+**Where:** Chat input textarea  
+**Symptom:** Typing `@` in the chat input does not trigger any autocomplete dropdown. No filename suggestions, no context items offered.  
+**Root cause:** gRPC stub. The `@` autocomplete calls `FileServiceClient.searchFiles()` to get matching file paths.  
+**Fix:** Implemented `searchFiles` handler in grpc-handler.ts that delegates to `SdkController.searchFiles()`, which does a real filesystem walk of the workspace directory (max depth 8, skips node_modules/.git/etc). Returns results with `mentionsRequestId` for proper request correlation.
+
+### 10. 🟢 Add files/images button (+) does nothing
+**Where:** Bottom bar, "+" button next to chat input  
+**Symptom:** Clicking the "+" button to add files and images produces no response — no file picker, no dropdown, no action.  
+**Root cause:** gRPC stub. The button calls `FileServiceClient.selectFiles()` which opens a native file picker dialog.  
+**Fix:** Implemented `selectFiles` handler that returns `StringArrays` format (`values1` = image data URLs, `values2` = file paths). VscodeWebviewProvider callback reads image files as base64 data URLs and returns relative paths for non-images.
+
+### 11. 🟢 Cannot switch from Plan mode back to Act mode
+**Where:** Bottom bar Plan/Act toggle  
+**Symptom:** Clicking "Plan" successfully switches to Plan mode. However, clicking "Act" after that does NOT switch back to Act mode.  
+**Root cause:** Proto enum conversion bug — the webview sends numeric enum values (0=PLAN, 1=ACT) but the handler expected string values.  
+**Fix:** `handleTogglePlanActMode` now converts proto enum values: `0/"PLAN" → "plan"`, `1/"ACT" → "act"`, with fallback for already-converted string values.
+
+### 12. 🟢 "Manage cline rules and workflows" still mentions workflows
+**Where:** ClineRulesToggleModal tooltip and aria-label  
+**Symptom:** The tooltip and aria-label still said "Manage Cline Rules & Workflows".  
+**Fix:** Updated tooltip to "Manage Cline Rules" and aria-label to "Show/Hide Cline Rules". Also simplified chat placeholder text to remove "workflows" mention.
+
+### 4. 🟢 Input text not cleared immediately on send
+**Where:** Webview chat input  
+**Symptom:** After typing a message and pressing send/enter, the text remains visible in the input field briefly before clearing. Creates a feeling of lag.  
+**Root cause:** In `useMessageHandlers.ts`, `setInputValue("")` was called AFTER `await TaskServiceClient.newTask(...)` or `await TaskServiceClient.askResponse(...)` completed. The network round-trip caused visible delay before the input cleared.  
+**Fix:** Moved `setInputValue("")`, `setActiveQuote(null)`, `setSelectedImages([])`, `setSelectedFiles([])` to execute immediately when `hasContent` is true, before any async gRPC calls. React schedules a re-render synchronously, clearing the input before the network round-trip.
+
+### 5. 🟢 api_req_started fires with zeroed token counts
+**Where:** Message stream / ChatRow rendering  
+**Symptom:** An `api_req_started` partial message fires with `{"tokensIn":0,"tokensOut":0,"cost":0}` before real counts arrive, causing a brief flash of "0 / 200.0k" in the token usage bar.  
+**Root cause:** `ContextWindow.tsx` rendered the token bar whenever `tokenData` existed (i.e., when `contextWindow > 0`), regardless of whether `lastApiReqTotalTokens` was 0.  
+**Fix:** Added `tokenData.used === 0` guard to the null-return check in `ContextWindow.tsx`. The token bar now only renders when real (non-zero) token data is available.
+
+### 14. 🟢 "Delete chat" button shows placeholder size
+**Where:** Task history → delete button tooltip / label  
+**Symptom:** The "Delete chat" button tooltip displays `Delete Task (size: --)` when task size data is unavailable.  
+**Root cause:** `DeleteTaskButton.tsx` unconditionally rendered `(size: ${taskSize ? formatSize(taskSize) : "--"})`, showing "--" when `taskSize` is undefined.  
+**Fix:** Changed to conditionally include size: `taskSize ? \`Delete Task (${formatSize(taskSize)})\` : "Delete Task"`. The tooltip now shows just "Delete Task" when size is unavailable, or "Delete Task (12.4 KB)" when it is.
+
+### 13. 🟢 Terminal settings navigates to blank/stuck webview
+**Where:** Settings → Terminal tab  
+**Symptom:** Opening terminal settings causes React to crash, leaving a blank webview.  
+**Root cause:** `getAvailableTerminalProfiles` was a gRPC stub returning `{data:{}}`. The webview called `setAvailableTerminalProfiles(response.profiles)` where `response.profiles` was `undefined`, overwriting the default `[]`. Then `TerminalSettingsSection` called `profilesToShow.map()` on `undefined`, crashing React.  
+**Fix:** Implemented real `handleGetAvailableTerminalProfiles()` handler in grpc-handler.ts that calls `getAvailableTerminalProfiles()` from `utils/shell.ts`, returning platform-specific profiles (Default, zsh, bash on macOS). Also added `availableTerminalProfiles: []` to state-builder.ts as a safety net, and wired `scrollToSettings` to fire `navigate("settings", { targetSection })` via the bridge.  
+**Verified:** Debug harness confirmed handler returns `{data:{profiles:[{id:"default",...},{id:"zsh",...},{id:"bash",...}]}}`, Settings → Terminal tab renders "Default Terminal Profile" dropdown with all 3 options, shell integration timeout, and terminal reuse settings.
+
+### 16. 🟢 Cline Rules popup still has a "Workflows" tab
+**Where:** Scales-of-justice icon → Cline Rules modal  
+**Symptom:** The "Manage Cline Rules" popup contains a "Workflows" tab. Issue #12 fixed the tooltip text, but the tab itself still exists inside the modal.  
+**Root cause:** The `ClineRulesToggleModal` component had a full "Workflows" tab with toggle lists for global, local, and remote workflows, plus a description section. Workflows are no longer a feature.  
+**Fix:** Removed the Workflows tab button, workflows description text, workflows content section (remote/global/local workflow toggle lists), and the remote workflows banner condition from `ClineRulesToggleModal.tsx`. The `currentView` state type was narrowed from `"rules" | "workflows" | "hooks" | "skills"` to `"rules" | "hooks" | "skills"`.
+
+### 17. 🟢 Account pane shows "Sign up with Cline" despite being logged in
+**Where:** Account panel / pane  
+**Symptom:** Even when the user is already authenticated and logged in, the account pane still displays "Sign up with Cline" and other sign-up prompts as if the user were not authenticated.  
+**Root cause:** `subscribeToAuthStatusUpdate` is a streaming subscription. The bridge's `handleStreamingRequest()` fell into the `default` no-op case, so auth state was never pushed to the webview.  
+**Fix:** Added explicit `subscribeToAuthStatusUpdate` case in `handleStreamingRequest()` that reads auth credentials from disk and pushes them. Added `roles` to org data and null safety in `isAdminOrOwner()`.
+
+### 18. 🟢 "Sign up with Cline" button does nothing (moot)
+**Where:** Account pane → Sign up button  
+**Fix:** Resolved by #17 — the sign-up button is no longer shown when the user is already authenticated.
+
+### 19. 🟢 Terminal settings still shows "Terminal Execution Mode" option
+**Where:** Settings → Terminal  
+**Fix:** Removed the Terminal Execution Mode dropdown, its handler, and unused imports from `TerminalSettingsSection.tsx`.
+
+### 20. 🟢 Cline provider model type-ahead search does not work
+**Where:** Settings → Model selector (Cline provider)  
+**Root cause:** `refreshClineModelsRpc` was a gRPC stub returning `{}`. The webview never received any model data.  
+**Fix:** Implemented `handleRefreshClineModels()` in grpc-handler.ts that reads from disk cache first, then falls back to fetching from the Cline API using `globalThis.fetch`. Converts API response to `ModelInfo` records and returns in protobuf format.
+
+### 21. 🟢 Cline provider recommends possibly outdated model
+**Where:** Settings → Model selector (Cline provider)  
+**Fix:** Updated fallback recommendation text in `ClineModelPicker.tsx` from `anthropic/claude-sonnet-4.5` to `anthropic/claude-sonnet-4.6`.
+
+### 22. 🟢 "Use different models for Plan and Act" checkbox immediately unchecks
+**Where:** Settings → Model configuration  
+**Root cause:** `updateSettings()` was writing raw settings instead of merging individual known keys.  
+**Fix:** `updateSettings()` now iterates known settings keys and writes each one individually. `buildExtensionState()` reads `planActSeparateModels` from `globalState`.
+
+### 23. 🟢 MCP settings Configure tab crashes React
+**Where:** MCP Servers → Configure tab  
+**Root cause:** `refreshMcpMarketplace` stub returns `{}`, replacing the default `{ items: [] }` state, causing `items.find()` to crash.  
+**Fix:** Added optional chaining (`?.items?.find`) in `getMcpServerDisplayName()`.
+
+### 24. 🟢 History tab is empty and search does nothing
+**Where:** History tab (task history list)  
+**Root cause:** `handleGetTaskHistory()` returned `{ data: { history } }` but webview reads `response.tasks`.  
+**Fix:** Changed return to `{ data: { tasks, totalCount } }`. Implemented server-side filtering/sorting.
+
+### 25. 🟢 Auto-approve options immediately uncheck when toggled
+**Where:** Auto-approve options flyout  
+**Root cause:** Same as #22 — `updateAutoApprovalSettings()` was not persisting properly.  
+**Fix:** Fixed alongside #22.
+
+---
+
+## Open Issues
+
+### 15. 🔴 MCP tools are missing / not visible to the agent
+**Where:** Agent tool execution  
+**Symptom:** MCP tools that should be available to the agent are not discovered or listed. The agent cannot see or use any MCP-provided tools during task execution.  
+**Expected:** Connected MCP servers should expose their tools to the agent, and the agent should be able to invoke them.  
+**Investigation:** `@clinebot/core` has full MCP support (`InMemoryMcpManager`, `registerMcpServersFromSettingsFile`, `resolveMcpServerRegistrations`). The issue is that `ClineCoreSession` in `cline-session-factory.ts` doesn't pass MCP configuration through `coreConfig` when calling `host.start()`. The MCP settings file exists at `~/.cline/data/settings/cline_mcp_settings.json` and `SdkController.getMcpServers()` already reads it for the UI, but the session factory never wires MCP servers into the ClineCore session. The fix requires: (1) reading MCP server registrations via `resolveMcpServerRegistrations()` or passing the settings file path in `coreConfig`, (2) creating/passing an `InMemoryMcpManager` to ClineCore, or (3) ensuring ClineCore auto-discovers MCP settings from the default path. This is a deep architectural change that can't be verified via the debug harness (requires actual agent task execution).
+
+
+---
+
+## Observations (not bugs, just notes)
+
+### UI Rendering — Task Completion View
+The completed task view renders correctly:
+- Task header with cost badge (e.g. "$0.0072")
+- Token usage bar (e.g. "1.4k / 200.0k")
+- Response text displayed properly
+- "Task Completed" card with green checkmark and the result
+- "Start New Task" button appears below the chat
+- Input area changes to "Type a message..." (follow-up mode)
+
+### Feature Card Carousel
+The home screen shows a rotating feature card carousel (1/4 through 4/4) promoting:
+- Claude Sonnet 4.6
+- MiniMax M2.5
+- ChatGPT integration
+- Jupyter Notebooks
+Each with a dismiss (X) button per-card.
+
+### Model Selector
+Bottom bar correctly shows `cline:anthropic/claud...` (truncated) with Plan/Act toggle. Act mode is the default.
+
+### Debug Harness Limitations (Fixed)
+All three limitations below have been addressed:
+
+- ~~Programmatic textarea input doesn't reliably trigger React state updates after the first task.~~ **Fixed**: Two new commands added:
+  - `ui.react_input` — Uses `document.execCommand('insertText')` which fires real InputEvents that React's onChange handler processes correctly, even after multiple tasks.
+  - `ui.send_message` — Bypasses the textarea entirely by sending gRPC requests via `postMessage` directly to the extension host.
+- ~~The `web.evaluate` context can't access the VS Code API.~~ **Fixed**: The webview now exposes the VS Code API as `window.__clineVsCodeApi`, and a new `web.post_message` command lets the harness send arbitrary messages to the extension host through it.
+- ~~The `ui.locator` Playwright actions don't reliably target elements inside the webview iframe.~~ **Fixed**: `findSidebar()` now validates cached frame references (checking for both detached and stale frames), `getTarget()` accepts a `forceRefresh` flag, and `ui.locator` automatically retries with frame re-discovery when targeting sidebar elements.

CHANGELOG.md

@@ -1,14 +1,385 @@
 # Changelog
 
+## [3.77.0]
+
+### Added
+
+- Add "Lazy Teammate Mode" experimental toggle
+- `read_file` tool now supports chunked reading for targeted file access
+
+### Fixed
+
+- Exclude `new_task` tool from system prompt in yolo/headless mode
+- Fix Kanban demo video formatting
+
+### Changed
+
+- Polish `Notification` hook functionality
+
+## [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
+
+- Bug in responses API
 
 ## [3.53.0]
 
 ### Fixed
- - Removed grok model from free tier
+
+- Removed grok model from free tier
 
 ## [3.52.0]
 

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**
 

DEBUG-HARNESS.md

@@ -0,0 +1,84 @@
+# E2E Debugging Visibility
+
+This is a sub-project of the project described in migration.md. We are
+engaging in a big change to the VSCode extension. You gain visibility
+into the extension through tests, but sometimes that is not enough.
+
+Your goal is to create way where you can launch the VSCode extension
+and have access to the node debugger and webview debugger so that you
+can set break points, evaluate expressions, inject input (consider
+Microsoft's work with Playwright in VSCode, but anything that works is
+fine) step, etc. so that you can observe execution and find and fix
+problems without the tedious cycle off adding print statements,
+running a test which may hang, fixing something, removing the print
+statements, etc.
+
+For this step to be complete, you need to demonstrate you have the
+ability to:
+
+1. Build and run the VSCode extension in an unminified form, including
+   the webview unminified.
+
+2. Add and remove breakpoints, including conditional breakpoints, on
+   the extension side.
+
+3. Add and remove breakpoints, including conditional breakpoints, on
+   the webview side.
+
+4. Evaluate expressions at breakpoints. You should be able to refer to
+   local variables, that is, the extension code should be
+   unminified. (Concatenated is fine as long as you can find your way
+   around.)
+
+5. Run, step at breakpoints.
+
+6. Generate UI actions like opening the Cline sidebar, focusing
+   elements, typing, etc.
+
+7. Take screenshots that you can view.
+
+You need to use this tool inside your agentic loop, that is, you will
+need to drive both of these debugees simultaneously from one loop, so
+you may need to write yourself a tool which blocks until one of the
+debugees hits a breakpoint; can use a timeout and let you break and
+examine isolates and stacks; things of that nature.
+
+We are working on macOS, it is fine if this tool just works on macOS
+for now.
+
+## Caveats
+
+- **"Introducing Cline Kanban" promotion**: On fresh launches, a
+  full-screen promotional overlay ("Introducing Cline Kanban") may
+  appear in the sidebar webview. It obscures all other UI elements, so
+  screenshots will show only the promo and interactions with the chat
+  input, settings buttons, etc. will fail. You must dismiss it before
+  doing anything else. Use the debug harness to click the dismiss/close
+  button:
+  ```bash
+  curl localhost:19229/api -d '{
+    "method": "ui.locator",
+    "params": {"text": "Dismiss", "frame": "sidebar", "action": "click"}
+  }'
+  ```
+  Or close it via `web.evaluate`:
+  ```bash
+  curl localhost:19229/api -d '{
+    "method": "web.evaluate",
+    "params": {"expression": "document.querySelector('[data-testid=\"dismiss-announcement\"]')?.click() || document.querySelector(\"button\")?.click()"}
+  }'
+  ```
+  If the exact selector changes, take a screenshot first
+  (`ui.sidebar_screenshot`) to identify the current dismiss control.
+
+- **CDP disconnects after window reload**: If you use
+  `workbench.action.reloadWindow` (e.g., to pick up a rebuilt
+  webview), the extension host CDP connection drops. You must do a full
+  `shutdown` + relaunch of the debug harness to reconnect.
+
+## References
+
+You can see the vscode source code in ~/clients/cline/vscode and
+search it with kb_search vscode
+
+You can search the cline source code (snapshot) with kb_search cline.

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

@@ -129,9 +129,9 @@ Thanks to the [Model Context Protocol](https://github.com/modelcontextprotocol),
 
 ### Checkpoints: Compare and Restore
 
-As Cline works through a task, the extension takes a snapshot of your workspace at each step. You can use the 'Compare' button to see a diff between the snapshot and your current workspace, and the 'Restore' button to roll back to that point.
+As Cline works through a task, the extension can take an internal snapshot of your workspace at each step. You can use the 'Compare' button to see a diff between the snapshot and your current workspace, and the 'Restore' button to roll back to that point.
 
-For example, when working with a local web server, you can use 'Restore Workspace Only' to quickly test different versions of your app, then use 'Restore Task and Workspace' when you find the version you want to continue building from. This lets you safely explore different approaches without losing progress.
+For example, when working with a local web server, you can use 'Restore Workspace Only' to quickly test different versions of your app, then use 'Restore Task and Workspace' when you find the version you want to continue building from. This lets you safely explore different approaches without losing progress while the current checkpoint system is available.
 
 <!-- Transparent pixel to create line break after floating image -->
 
@@ -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/sleepy-cline.svg

@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg id="Layer_1" xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 512 535">
+  <!-- Generator: Adobe Illustrator 29.8.5, SVG Export Plug-In . SVG Version: 2.1.1 Build 2)  -->
+  <defs>
+    <style>
+      .st0 {
+        fill: #fff;
+      }
+    </style>
+  </defs>
+  <path class="st0" d="M500.6,300.5c-9-20.7-17.9-41.4-26.9-62.1-.7-2-.3-4.4-.3-6.4.4-9,1.1-18,1.4-27,2.8-28.4-6.5-58-25.2-79.6-15.1-18.1-36.6-30.7-59.6-35.5-8.1-1.8-16.6-1.6-25-2.1-10-.7-20-1-30-1.7,2-11.9,1-24.1-3.7-35.3-5.8-14.1-16.8-25.9-30.6-32.5-14.4-7-31.5-8.2-46.7-3.1-16,5.2-29.5,17-36.8,32.1-4.9,10-6.8,21.2-6.1,32.2-19.7-1-39.4-2.2-59.1-3.1-26.8.5-53,11.7-72,30.6-20.2,19.5-31.7,47-32.3,75-.5,9.3-1,18.7-1.5,28-.2,2.1,0,4.1-1.2,6-9.8,16.8-19.5,33.7-29.4,50.6-2.2,4.1-4.9,8-6.6,12.3-2,5.7-1.2,12.2,1.3,17.6,8.9,19.5,17.6,39.2,26.5,58.7.8,1.9,1.5,3.7,1.3,5.8-.6,10.3-1.1,20.7-1.7,31-1.5,21.2,3,42.6,13.5,61.1,8.8,15.8,21.6,29.4,37.1,38.9,13.9,8.7,29.7,13.9,46,15.4,72,3.9,144,7.7,216,11.5,20.1,1.8,40.8-2.8,58.5-12.5,18.8-10.1,34.2-26,44.1-44.9,6.5-12.6,10.5-26.4,11.7-40.5.7-12.4,1.2-24.7,2-37.1,0-3.3,1.9-5.5,3.3-8.2,6.6-11.8,13.5-23.4,20.1-35.2,3.7-6.9,8.1-13.4,11.6-20.4,3.2-6.1,3.2-13.5.3-19.7ZM218.5,316.5c-9.7,7.1-21.3,12.3-33.5,12.5-17.6,1-35.1-5.3-49-16-4.6-3.2-8.1-7.5-9.6-13,0-1.8-.7-3.6,1.7-3.8,4,1,7.9,2.6,12,3.5,22.8,5.6,47.6,5.9,71,4.8,6.5-.2,13-1.3,19.5-.9-2.7,5.6-7.1,9.2-12,12.9ZM276,449.7c-14,.5-28,.1-42-.2-2.1,0-4.3,0-6.4-.4-.9-2.1.6-3.2,1.7-4.8,4.8-5.9,11-11,18.7-12.4,8.4-1.6,16.5,1.2,23.5,5.5,4.7,3,9.2,6.3,12.6,10.8-2.6,1.1-5.3,1.4-8.1,1.4ZM390.4,319.4c-16.4,14.2-38.8,21.8-60.4,18.4-13.2-1.6-24.7-8.6-34.1-17.7-3-3-6.2-6.5-8.1-10.4.5-1,1.2-1.6,2.2-1.6,2.8-.2,5.7.7,8.5,1.1,16,2.9,32.3,4.9,48.5,5.5,14.3.4,28.2-.2,42.2-3.6,2.2-.6,3.7-.3,5.8.5-1.1,2.9-2.2,5.7-4.6,7.8Z"/>
+</svg>

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,19 +28,19 @@
 		"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",
@@ -51,35 +51,36 @@
 				"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,14 +142,15 @@
 		{
 			"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"
@@ -154,35 +163,37 @@
 			],
 			"includes": [
 				"**",
-				"!**/esbuild.*",
-				"!**/*.mts",
-				"!**/webview-ui/**",
-				"!**/evals/**",
-				"!**/standalone/**",
-				"!**/e2e/**",
-				"!**/test/**",
-				"!**/__tests__/**",
-				"!**/*.test.ts",
-				"!**/*.stories.ts",
-				"!src/dev/**",
-				"!**/*.mjs",
-				"!**/*.js",
-				"!**/scripts/**",
-				"!**/*.tsx",
-				"!**/testing-platform/**",
-				"!**/cli-ts/src/acp/**"
+				"!!**/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"
+				"!!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/esbuild.mts

@@ -1,272 +0,0 @@
-import fs from "node:fs"
-import path from "node:path"
-import { fileURLToPath } from "node:url"
-import dotenv from "dotenv"
-import * as esbuild from "esbuild"
-
-const __filename = fileURLToPath(import.meta.url)
-const __dirname = path.dirname(__filename)
-const rootDir = path.resolve(__dirname, "..")
-
-// Load .env from repo root
-dotenv.config({ path: path.join(rootDir, ".env") })
-
-const production = process.argv.includes("--production")
-const watch = process.argv.includes("--watch")
-
-/**
- * Plugin to resolve path aliases from the parent project
- */
-const aliasResolverPlugin: esbuild.Plugin = {
-	name: "alias-resolver",
-	setup(build) {
-		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"),
-		}
-
-        // 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 }
-                    }
-                }
-
-                // Handle .js -> .ts extension mapping (common in ESM TypeScript projects)
-                if (importPath.endsWith(".js")) {
-                    const tsPath = importPath.replace(/\.js$/, ".ts")
-                    if (fs.existsSync(tsPath)) {
-                        return { path: tsPath }
-                    }
-                    const tsxPath = importPath.replace(/\.js$/, ".tsx")
-                    if (fs.existsSync(tsxPath)) {
-                        return { path: tsxPath }
-                    }
-                }
-
-                // If nothing worked, return the original path and let esbuild handle the error
-                return { path: importPath }
-            })
-        })
-    },
-}
-
-/**
- * Plugin to redirect vscode imports to our shim
- */
-const vscodeStubPlugin: esbuild.Plugin = {
-	name: "vscode-stub",
-	setup(build) {
-		// Redirect 'vscode' imports to our shim
-		build.onResolve({ filter: /^vscode$/ }, () => {
-			return { path: path.join(__dirname, "src", "vscode-shim.ts") }
-		})
-	},
-}
-
-const esbuildProblemMatcherPlugin: esbuild.Plugin = {
-	name: "esbuild-problem-matcher",
-	setup(build) {
-		build.onStart(() => {
-			console.log("[cli-ts esbuild] 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("[cli-ts esbuild] Build finished")
-		})
-	},
-}
-
-// Plugin to stub out optional devtools module
-const stubOptionalModulesPlugin: esbuild.Plugin = {
-	name: "stub-optional-modules",
-	setup(build) {
-		build.onResolve({ filter: /^react-devtools-core$/ }, () => {
-			return { path: path.join(__dirname, "src", "stub-devtools.js"), external: false }
-		})
-	},
-}
-
-const copyWasmFiles: esbuild.Plugin = {
-	name: "copy-wasm-files",
-	setup(build) {
-		build.onEnd(() => {
-			const destDir = path.join(__dirname, "dist")
-
-            // Ensure dist directory exists
-            if (!fs.existsSync(destDir)) {
-                fs.mkdirSync(destDir, { recursive: true })
-            }
-
-            // tree sitter
-            const sourceDir = path.join(rootDir, "node_modules", "web-tree-sitter")
-
-            // Copy tree-sitter.wasm
-            const treeSitterWasm = path.join(sourceDir, "tree-sitter.wasm")
-            if (fs.existsSync(treeSitterWasm)) {
-                fs.copyFileSync(treeSitterWasm, path.join(destDir, "tree-sitter.wasm"))
-            }
-
-            // Copy language-specific WASM files
-            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(destDir, filename))
-                    }
-                })
-            }
-        })
-    },
-}
-
-const buildEnvVars: Record<string, string> = {
-	"process.env.IS_STANDALONE": JSON.stringify("true"),
-	"process.env.IS_CLI": JSON.stringify("true"),
-}
-
-const buildTimeEnvs = [
-    "TELEMETRY_SERVICE_API_KEY",
-    "ERROR_SERVICE_API_KEY",
-    "POSTHOG_TELEMETRY_ENABLED",
-    "OTEL_TELEMETRY_ENABLED",
-    "OTEL_LOGS_EXPORTER",
-    "OTEL_METRICS_EXPORTER",
-    "OTEL_EXPORTER_OTLP_PROTOCOL",
-    "OTEL_EXPORTER_OTLP_ENDPOINT",
-    "OTEL_EXPORTER_OTLP_HEADERS",
-    "OTEL_METRIC_EXPORT_INTERVAL",
-    "CLINE_ENVIRONMENT",
-]
-
-buildTimeEnvs.forEach((envVar) => {
-    if (process.env[envVar]) {
-        console.log(`[cli-ts esbuild] ${envVar} env var is set`)
-        buildEnvVars[`process.env.${envVar}`] = JSON.stringify(process.env[envVar])
-    }
-})
-
-if (production) {
-    buildEnvVars["process.env.IS_DEV"] = "false"
-}
-
-const config: esbuild.BuildOptions = {
-	entryPoints: [path.join(__dirname, "src", "index.ts")],
-	bundle: true,
-	minify: production,
-	sourcemap: !production,
-	logLevel: "silent",
-	define: buildEnvVars,
-	tsconfig: path.join(__dirname, "tsconfig.json"),
-	plugins: [copyWasmFiles, aliasResolverPlugin, vscodeStubPlugin, stubOptionalModulesPlugin, esbuildProblemMatcherPlugin],
-	format: "esm",
-	sourcesContent: false,
-	platform: "node",
-	target: "node20",
-	outfile: path.join(__dirname, "dist", "cli.mjs"),
-	// These modules need to load files from the module directory at runtime
-	external: [
-		"@grpc/reflection",
-		"grpc-health-check",
-		"better-sqlite3",
-		"ink",
-		"ink-spinner",
-		"ink-picture",
-		"react",
-		"aws4fetch",
-		"pino",
-		"pino-roll",
-	],
-	supported: { "top-level-await": true },
-	banner: {
-		js: `#!/usr/bin/env node
-// Suppress all Node.js warnings (deprecation, experimental, etc.)
-process.emitWarning = () => {};
-import { createRequire as _createRequire } from 'module';
-import { fileURLToPath as _fileURLToPath } from 'url';
-import { dirname as _dirname } from 'path';
-const require = _createRequire(import.meta.url);
-const __filename = _fileURLToPath(import.meta.url);
-const __dirname = _dirname(__filename);`,
-    },
-}
-
-async function main() {
-    const ctx = await esbuild.context(config)
-    if (watch) {
-        await ctx.watch()
-        console.log("[cli-ts] Watching for changes...")
-    } else {
-        await ctx.rebuild()
-        await ctx.dispose()
-
-        // Make the output executable
-        const outfile = path.join(__dirname, "dist", "cli.mjs")
-        if (fs.existsSync(outfile)) {
-            fs.chmodSync(outfile, "755")
-        }
-    }
-}
-
-main().catch((e) => {
-    console.error(e)
-    process.exit(1)
-})

cli-ts/package.json

@@ -1,81 +0,0 @@
-{
-	"name": "@cline/cli",
-	"version": "2.0.0",
-	"description": "Autonomous coding agent CLI - capable of creating/editing files, running commands, using the browser, and more",
-	"main": "dist/cli.mjs",
-	"bin": {
-		"cline": "./dist/cli.mjs"
-	},
-	"type": "module",
-	"engines": {
-		"node": ">=20.0.0"
-	},
-	"scripts": {
-		"prepublishOnly": "npm run build:production",
-		"package:brew": "node ./scripts/update-brew-formula.mts",
-		"package": "npm pack --pack-destination ./dist",
-		"build": "node esbuild.mts",
-		"build:production": "node esbuild.mts --production",
-		"watch": "node esbuild.mts --watch",
-		"dev": "IS_DEV=true && npm run link && npm run watch ; npm run unlink",
-		"clean": "rimraf dist",
-		"typecheck": "tsc --noEmit",
-		"link": "npm run build && npm link",
-		"unlink": "npm unlink -g @cline/cli && npm unlink -g cline",
-		"test": "vitest",
-		"test:run": "vitest run"
-	},
-	"keywords": [
-		"cline",
-		"claude",
-		"dev",
-		"mcp",
-		"openrouter",
-		"coding",
-		"agent",
-		"autonomous",
-		"chatgpt",
-		"sonnet",
-		"ai",
-		"llama",
-		"cli"
-	],
-	"author": {
-		"name": "Cline Bot Inc."
-	},
-	"license": "Apache-2.0",
-	"repository": {
-		"type": "git",
-		"url": "https://github.com/cline/cline"
-	},
-	"homepage": "https://cline.bot",
-	"bugs": {
-		"url": "https://github.com/cline/cline/issues"
-	},
-	"devDependencies": {
-		"@types/node": "20.x",
-		"@types/prompts": "^2.4.9",
-		"@types/react": "^19.2.9",
-		"dotenv": "^16.4.5",
-		"esbuild": "^0.25.0",
-		"ink-testing-library": "^4.0.0",
-		"rimraf": "^6.0.1",
-		"typescript": "^5.4.5",
-		"vitest": "^4.0.17"
-	},
-	"dependencies": {
-		"@agentclientprotocol/sdk": "^0.13.1",
-		"aws4fetch": "^1.0.20",
-		"chalk": "^5.3.0",
-		"commander": "^12.1.0",
-		"ink": "npm:@jrichman/ink@6.4.7",
-		"ink-picture": "^1.3.3",
-		"ink-spinner": "^5.0.0",
-		"ora": "^8.0.1",
-		"nanoid": "^5.1.6",
-		"pino": "^10.0.0",
-		"pino-roll": "^4.0.0",
-		"prompts": "^2.4.2",
-		"react": "^19.2.3"
-	}
-}

cli-ts/src/acp/types.ts

@@ -1,184 +0,0 @@
-/**
- * Custom types and extensions for ACP integration with Cline CLI.
- *
- * This file extends the base ACP types with Cline-specific functionality.
- */
-
-import type * as acp from "@agentclientprotocol/sdk"
-import type { Controller } from "@/core/controller"
-
-// Re-export common ACP types for convenience
-export type {
-	Agent,
-	AgentSideConnection,
-	AudioContent,
-	CancelNotification,
-	ContentBlock,
-	ImageContent,
-	InitializeRequest,
-	InitializeResponse,
-	LoadSessionRequest,
-	LoadSessionResponse,
-	McpServer,
-	ModelInfo,
-	NewSessionRequest,
-	NewSessionResponse,
-	PermissionOption,
-	PermissionOptionKind,
-	PromptRequest,
-	PromptResponse,
-	ReadTextFileRequest,
-	ReadTextFileResponse,
-	RequestPermissionRequest,
-	RequestPermissionResponse,
-	SessionConfigOption,
-	SessionModelState,
-	SessionNotification,
-	SessionUpdate,
-	SetSessionConfigOptionRequest,
-	SetSessionConfigOptionResponse,
-	SetSessionModelRequest,
-	SetSessionModelResponse,
-	SetSessionModeRequest,
-	SetSessionModeResponse,
-	StopReason,
-	TextContent,
-	ToolCall,
-	ToolCallStatus,
-	ToolCallUpdate,
-	ToolKind,
-	WriteTextFileRequest,
-	WriteTextFileResponse,
-} from "@agentclientprotocol/sdk"
-
-/**
- * Cline-specific agent capabilities extending the ACP base capabilities.
- */
-export interface ClineAgentCapabilities {
-	/** Support for loading sessions from disk */
-	loadSession: boolean
-	/** Prompt capabilities for the agent */
-	promptCapabilities: {
-		/** Support for image inputs */
-		image: boolean
-		/** Support for audio inputs */
-		audio: boolean
-		/** Support for embedded context (file resources) */
-		embeddedContext: boolean
-	}
-	/** MCP server passthrough capabilities */
-	mcpCapabilities: {
-		/** Support for HTTP MCP servers */
-		http: boolean
-		/** Support for SSE MCP servers */
-		sse: boolean
-	}
-}
-
-/**
- * Cline agent info for ACP initialization response.
- */
-export interface ClineAgentInfo {
-	name: "cline"
-	title: "Cline"
-	version: string
-}
-
-/**
- * Extended session data stored by Cline for ACP sessions.
- * Maps to Cline's task history structure.
- */
-export interface ClineAcpSession {
-	/** Unique session/task ID */
-	sessionId: string
-	/** Working directory for the session */
-	cwd: string
-	/** Current mode (plan/act) */
-	mode: "plan" | "act"
-	/** MCP servers passed from the client */
-	mcpServers: acp.McpServer[]
-	/** Timestamp when session was created */
-	createdAt: number
-	/** Timestamp of last activity */
-	lastActivityAt: number
-	/** Whether this session was loaded from history (needs resume on first prompt) */
-	isLoadedFromHistory?: boolean
-	/** Controller instance for this session (manages task execution) */
-	controller?: Controller
-	/** Model ID override for plan mode (format: "provider/modelId") */
-	planModeModelId?: string
-	/** Model ID override for act mode (format: "provider/modelId") */
-	actModeModelId?: string
-}
-
-/**
- * Permission option as presented to the ACP client.
- */
-export interface ClinePermissionOption {
-	kind: acp.PermissionOptionKind
-	name: string
-	optionId: string
-}
-
-/**
- * Mapping of Cline message types to their ACP session update equivalents.
- */
-export type ClineToAcpUpdateMapping = {
-	/** Text messages from the agent */
-	text: "agent_message_chunk"
-	/** Reasoning/thinking from the agent */
-	reasoning: "agent_thought_chunk"
-	/** Markdown content from the agent */
-	markdown: "agent_message_chunk"
-	/** Tool execution */
-	tool: "tool_call"
-	/** Command execution */
-	command: "tool_call"
-	/** Command output */
-	command_output: "tool_call_update"
-	/** Task completion */
-	completion_result: "end_turn"
-	/** Error messages */
-	error: "tool_call_update" | "error"
-}
-
-/**
- * Options for creating an ACP agent instance.
- */
-export interface AcpAgentOptions {
-	/** CLI version string */
-	version: string
-	/** Whether debug logging is enabled */
-	debug?: boolean
-}
-
-/**
- * Result of translating a Cline message to ACP session update(s).
- * A single Cline message may produce multiple ACP updates.
- */
-export interface TranslatedMessage {
-	/** The session updates to send */
-	updates: acp.SessionUpdate[]
-	/** Whether this message requires a permission request */
-	requiresPermission?: boolean
-	/** Permission request details if required */
-	permissionRequest?: Omit<acp.RequestPermissionRequest, "sessionId">
-	/** The toolCallId that was created/used (for tracking across streaming updates) */
-	toolCallId?: string
-}
-
-/**
- * State tracking for an active ACP session within Cline.
- */
-export interface AcpSessionState {
-	/** Session ID */
-	sessionId: string
-	/** Whether the session is currently processing a prompt */
-	isProcessing: boolean
-	/** Current tool call ID being executed (if any) */
-	currentToolCallId?: string
-	/** Whether the session has been cancelled */
-	cancelled: boolean
-	/** Accumulated tool calls for permission batching */
-	pendingToolCalls: Map<string, acp.ToolCall>
-}

cli-ts/src/components/DiffView.tsx

@@ -1,216 +0,0 @@
-/**
- * DiffView component for displaying file diffs in Ink
- * Shows unified diff output with colored lines for additions/deletions
- * Supports SEARCH/REPLACE format and ApplyPatch format
- */
-
-import { Box, Text } from "ink"
-import React from "react"
-
-interface DiffViewProps {
-	/** Diff content (SEARCH/REPLACE format, ApplyPatch format, or raw content for new files) */
-	content?: string
-}
-
-interface DiffLine {
-	type: "add" | "remove" | "context" | "separator"
-	content: string
-}
-
-interface ParsedPatch {
-	additions: number
-	deletions: number
-	lines: DiffLine[]
-}
-
-// Constants for format markers
-const MARKERS = {
-	SEARCH_BLOCK: "------- SEARCH",
-	SEARCH_SEPARATOR: "=======",
-	REPLACE_BLOCK: "+++++++ REPLACE",
-	NEW_BEGIN: "*** Begin Patch",
-	NEW_END: "*** End Patch",
-} as const
-
-/**
- * Parse SEARCH/REPLACE format into diff lines
- * Format: ------- SEARCH\n...\n=======\n...\n+++++++ REPLACE
- */
-function parseSearchReplaceFormat(content: string): ParsedPatch {
-	const result: ParsedPatch = { additions: 0, deletions: 0, lines: [] }
-
-	// Find all SEARCH blocks
-	const searchRegex = /-{7,} SEARCH/g
-	const searchPositions: number[] = []
-	let match: RegExpExecArray | null
-	while ((match = searchRegex.exec(content)) !== null) {
-		searchPositions.push(match.index)
-	}
-
-	for (let i = 0; i < searchPositions.length; i++) {
-		// Add separator between blocks
-		if (i > 0) {
-			result.lines.push({ type: "separator", content: "" })
-		}
-
-		const start = searchPositions[i]
-		const end = i < searchPositions.length - 1 ? searchPositions[i + 1] : content.length
-		const blockContent = content.substring(start, end)
-
-		// Extract content after SEARCH marker
-		const afterSearch = blockContent.substring(MARKERS.SEARCH_BLOCK.length).replace(/^\r?\n/, "")
-		const separatorIndex = afterSearch.indexOf(MARKERS.SEARCH_SEPARATOR)
-
-		if (separatorIndex === -1) {
-			// Still streaming - only SEARCH block available
-			const searchContent = afterSearch.trimEnd()
-			for (const line of searchContent.split("\n")) {
-				result.lines.push({ type: "remove", content: line })
-				result.deletions++
-			}
-		} else {
-			// Extract SEARCH block (deletions)
-			const searchContent = afterSearch.substring(0, separatorIndex).replace(/\r?\n$/, "")
-			for (const line of searchContent.split("\n")) {
-				result.lines.push({ type: "remove", content: line })
-				result.deletions++
-			}
-
-			// Extract REPLACE block (additions)
-			const afterSeparator = afterSearch.substring(separatorIndex + MARKERS.SEARCH_SEPARATOR.length).replace(/^\r?\n/, "")
-			const replaceEndIndex = afterSeparator.indexOf(MARKERS.REPLACE_BLOCK)
-			const replaceContent =
-				replaceEndIndex !== -1
-					? afterSeparator.substring(0, replaceEndIndex).replace(/\r?\n$/, "")
-					: afterSeparator.trimEnd()
-
-			for (const line of replaceContent.split("\n")) {
-				result.lines.push({ type: "add", content: line })
-				result.additions++
-			}
-		}
-	}
-
-	return result
-}
-
-/**
- * Parse ApplyPatch format into diff lines
- * Format: *** Begin Patch\n*** Update File: path\n+line\n-line\n*** End Patch
- */
-function parseApplyPatchFormat(content: string): ParsedPatch {
-	const result: ParsedPatch = { additions: 0, deletions: 0, lines: [] }
-
-	const beginIndex = content.indexOf(MARKERS.NEW_BEGIN)
-	if (beginIndex === -1) return result
-
-	const endIndex = content.indexOf(MARKERS.NEW_END)
-	const contentStart = beginIndex + MARKERS.NEW_BEGIN.length
-	const contentEnd = endIndex !== -1 ? endIndex : content.length
-	const patchContent = content.substring(contentStart, contentEnd).trim()
-
-	for (const line of patchContent.split("\n")) {
-		// Skip file header lines
-		if (line.match(/^\*\*\* (Add|Update|Delete) File:/)) continue
-		if (line.trim() === "@@") continue
-
-		if (line.startsWith("+")) {
-			const hasSpace = line.startsWith("+ ")
-			result.lines.push({ type: "add", content: hasSpace ? line.slice(2) : line.slice(1) })
-			result.additions++
-		} else if (line.startsWith("-")) {
-			const hasSpace = line.startsWith("- ")
-			result.lines.push({ type: "remove", content: hasSpace ? line.slice(2) : line.slice(1) })
-			result.deletions++
-		} else if (line.trim()) {
-			// Context line
-			result.lines.push({ type: "context", content: line })
-		}
-	}
-
-	return result
-}
-
-/**
- * Parse tool content into diff lines
- * Detects format and delegates to appropriate parser
- */
-function parseToolContent(content: string): ParsedPatch {
-	// Try SEARCH/REPLACE format first
-	if (content.includes(MARKERS.SEARCH_BLOCK)) {
-		return parseSearchReplaceFormat(content)
-	}
-
-	// Try ApplyPatch format
-	if (content.includes(MARKERS.NEW_BEGIN)) {
-		return parseApplyPatchFormat(content)
-	}
-
-	// Fallback: treat as new file (all additions)
-	const lines = content.split("\n")
-	return {
-		additions: lines.length,
-		deletions: 0,
-		lines: lines.map((line) => ({ type: "add", content: line })),
-	}
-}
-
-// Dim diff colors similar to IDE diff views
-const DIFF_COLORS = {
-	addBg: "rgb(35, 61, 41)", // dark muted green
-	addFg: "rgb(156, 204, 122)", // light green text
-	removeBg: "rgb(62, 36, 36)", // dark muted red
-	removeFg: "rgb(224, 139, 139)", // light red/pink text
-} as const
-
-/**
- * Render a diff line with full-width background color highlighting
- * Uses Box with backgroundColor to handle wrapping properly
- */
-const DiffLineRow: React.FC<{ line: DiffLine }> = ({ line }) => {
-	if (line.type === "separator") {
-		return <Text> </Text>
-	}
-
-	const prefix = line.type === "add" ? "+" : line.type === "remove" ? "-" : " "
-	const content = prefix + line.content
-
-	switch (line.type) {
-		case "add":
-			return (
-				<Box backgroundColor={DIFF_COLORS.addBg} width="100%">
-					<Text color={DIFF_COLORS.addFg}>{content}</Text>
-				</Box>
-			)
-		case "remove":
-			return (
-				<Box backgroundColor={DIFF_COLORS.removeBg} width="100%">
-					<Text color={DIFF_COLORS.removeFg}>{content}</Text>
-				</Box>
-			)
-		case "context":
-			return <Text dimColor>{content}</Text>
-		default:
-			return null
-	}
-}
-
-/**
- * DiffView component that renders file edits as a diff
- * Supports SEARCH/REPLACE format and ApplyPatch format
- */
-export const DiffView: React.FC<DiffViewProps> = ({ content }) => {
-	if (!content) {
-		return null
-	}
-
-	const parsed = parseToolContent(content)
-
-	return (
-		<Box flexDirection="column" width="100%">
-			{parsed.lines.map((line, idx) => (
-				<DiffLineRow key={idx} line={line} />
-			))}
-		</Box>
-	)
-}

cli-ts/src/components/ProviderPicker.tsx

@@ -1,44 +0,0 @@
-/**
- * Provider picker component for API provider selection
- */
-
-import React, { useMemo } from "react"
-import { API_PROVIDERS_LIST } from "@/shared/api"
-import providersData from "@/shared/providers/providers.json"
-import { SearchableList, SearchableListItem } from "./SearchableList"
-
-// Create a lookup map from provider value to display label
-const providerLabels: Record<string, string> = Object.fromEntries(
-	providersData.list.map((p: { value: string; label: string }) => [p.value, p.label]),
-)
-
-// Get provider order from providers.json (same order as webview)
-const providerOrder: string[] = providersData.list.map((p: { value: string }) => p.value)
-
-export function getProviderLabel(providerId: string): string {
-	return providerLabels[providerId] || providerId
-}
-
-export function getProviderOrder(): string[] {
-	return providerOrder
-}
-
-interface ProviderPickerProps {
-	onSelect: (providerId: string) => void
-	isActive?: boolean
-}
-
-export const ProviderPicker: React.FC<ProviderPickerProps> = ({ onSelect, isActive = true }) => {
-	// Use providers.json order, filtered to only available providers
-	const items: SearchableListItem[] = useMemo(() => {
-		const availableProviders = new Set(API_PROVIDERS_LIST)
-		const sorted = providerOrder.filter((p) => availableProviders.has(p))
-
-		return sorted.map((providerId) => ({
-			id: providerId,
-			label: getProviderLabel(providerId),
-		}))
-	}, [])
-
-	return <SearchableList isActive={isActive} items={items} onSelect={(item) => onSelect(item.id)} />
-}

cli-ts/src/components/WelcomeView.tsx

@@ -1,328 +0,0 @@
-/**
- * Welcome view component
- * Shows an interactive prompt when user starts cline without a command
- * Supports file mentions with @
- */
-
-import { Box, Text, useInput } from "ink"
-import React, { useCallback, useEffect, useMemo, useRef, useState } from "react"
-import { StateManager } from "@/core/storage/StateManager"
-import { getProviderDefaultModelId, Mode } from "@/shared/storage"
-import { useStdinContext } from "../context/StdinContext"
-import {
-	checkAndWarnRipgrepMissing,
-	extractMentionQuery,
-	type FileSearchResult,
-	getRipgrepInstallInstructions,
-	insertMention,
-	searchWorkspaceFiles,
-} from "../utils/file-search"
-import { isMouseEscapeSequence } from "../utils/input"
-import { parseImagesFromInput } from "../utils/parser"
-import { AccountInfoView } from "./AccountInfoView"
-import { FileMentionMenu } from "./FileMentionMenu"
-
-interface WelcomeViewProps {
-	onSubmit: (prompt: string, imagePaths: string[]) => void
-	onExit?: () => void
-	controller?: any
-}
-
-// ASCII art Cline logo
-const CLINE_LOGO = [
-	"            :::::::            ",
-	"           :::::::::           ",
-	"       :::::::::::::::::       ",
-	"    :::::::::::::::::::::::    ",
-	"   :::::::::::::::::::::::::   ",
-	"  :::::::::::::::::::::::::::  ",
-	"  :::::::   :::::::   :::::::  ",
-	" :::::::     :::::     ::::::: ",
-	"::::::::     :::::     ::::::::",
-	"::::::::     :::::     ::::::::",
-	" :::::::     :::::     ::::::: ",
-	"  :::::::   :::::::   :::::::  ",
-	"  :::::::::::::::::::::::::::  ",
-	"   :::::::::::::::::::::::::   ",
-	"    :::::::::::::::::::::::    ",
-	"       ::::::::::::::::       ",
-]
-
-const SEARCH_DEBOUNCE_MS = 150
-const RIPGREP_WARNING_DURATION_MS = 5000
-const MAX_SEARCH_RESULTS = 15
-
-export const WelcomeView: React.FC<WelcomeViewProps> = ({ onSubmit, onExit, controller }) => {
-	const { isRawModeSupported } = useStdinContext()
-	const [textInput, setTextInput] = useState("")
-	const [fileResults, setFileResults] = useState<FileSearchResult[]>([])
-	const [selectedIndex, setSelectedIndex] = useState(0)
-	const [isSearching, setIsSearching] = useState(false)
-	const [showRipgrepWarning, setShowRipgrepWarning] = useState(false)
-	const [escPressedOnce, setEscPressedOnce] = useState(false)
-	const [mode, setMode] = useState<Mode>(() => {
-		const stateManager = StateManager.get()
-		return stateManager.getGlobalSettingsKey("mode") || "act"
-	})
-
-	const provider = useMemo(() => {
-		const stateManager = StateManager.get()
-		const mode = stateManager.getGlobalSettingsKey("mode") as string
-		const providerKey = mode === "act" ? "actModeApiProvider" : "planModeApiProvider"
-		const currentProvider = stateManager.getGlobalSettingsKey(providerKey) as string
-		return currentProvider || "cline"
-	}, [controller])
-
-	// Get model ID based on current mode
-	const modelId = useMemo(() => {
-		const stateManager = StateManager.get()
-		const modelKey = mode === "act" ? "actModeApiModelId" : "planModeApiModelId"
-		return (stateManager.getGlobalSettingsKey(modelKey) as string) || getProviderDefaultModelId(provider)
-	}, [mode, provider])
-
-	const toggleMode = useCallback(() => {
-		const newMode: Mode = mode === "act" ? "plan" : "act"
-		setMode(newMode)
-		const stateManager = StateManager.get()
-		stateManager.setGlobalState("mode", newMode)
-	}, [mode])
-
-	const refs = useRef({
-		searchTimeout: null as NodeJS.Timeout | null,
-		lastQuery: "",
-		hasCheckedRipgrep: false,
-	})
-
-	const { prompt, imagePaths } = parseImagesFromInput(textInput)
-
-	const mentionInfo = useMemo(() => extractMentionQuery(textInput), [textInput])
-
-	const workspacePath = useMemo(() => {
-		try {
-			const root = controller?.getWorkspaceManagerSync?.()?.getPrimaryRoot?.()
-			if (root?.path) {
-				return root.path
-			}
-		} catch {
-			// Fallback to cwd
-		}
-		return process.cwd()
-	}, [controller])
-
-	// Search for files when in mention mode
-	useEffect(() => {
-		const { current: r } = refs
-
-		if (!mentionInfo.inMentionMode) {
-			setFileResults([])
-			setSelectedIndex(0)
-			if (r.searchTimeout) {
-				clearTimeout(r.searchTimeout)
-				r.searchTimeout = null
-			}
-			return
-		}
-
-		// Check for ripgrep on first mention trigger
-		if (!r.hasCheckedRipgrep) {
-			r.hasCheckedRipgrep = true
-			if (checkAndWarnRipgrepMissing()) {
-				setShowRipgrepWarning(true)
-				setTimeout(() => setShowRipgrepWarning(false), RIPGREP_WARNING_DURATION_MS)
-			}
-		}
-
-		const { query } = mentionInfo
-		if (query === r.lastQuery) {
-			return
-		}
-		r.lastQuery = query
-
-		if (r.searchTimeout) {
-			clearTimeout(r.searchTimeout)
-		}
-		setIsSearching(true)
-
-		r.searchTimeout = setTimeout(async () => {
-			try {
-				const results = await searchWorkspaceFiles(query, workspacePath, MAX_SEARCH_RESULTS)
-				setFileResults(results)
-				setSelectedIndex(0)
-			} catch {
-				setFileResults([])
-			} finally {
-				setIsSearching(false)
-			}
-		}, SEARCH_DEBOUNCE_MS)
-
-		return () => {
-			if (r.searchTimeout) {
-				clearTimeout(r.searchTimeout)
-			}
-		}
-	}, [mentionInfo.inMentionMode, mentionInfo.query, workspacePath])
-
-	useInput(
-		(input, key) => {
-			// Filter out mouse escape sequences
-			if (isMouseEscapeSequence(input)) {
-				return
-			}
-
-			const inMenu = mentionInfo.inMentionMode && fileResults.length > 0
-
-			// Menu navigation
-			if (inMenu) {
-				if (key.upArrow) {
-					setSelectedIndex((i) => (i > 0 ? i - 1 : fileResults.length - 1))
-					return
-				}
-				if (key.downArrow) {
-					setSelectedIndex((i) => (i < fileResults.length - 1 ? i + 1 : 0))
-					return
-				}
-				if (key.tab || key.return) {
-					const file = fileResults[selectedIndex]
-					if (file) {
-						setTextInput(insertMention(textInput, mentionInfo.atIndex, file.path))
-						setFileResults([])
-						setSelectedIndex(0)
-					}
-					return
-				}
-				if (key.escape) {
-					setFileResults([])
-					setSelectedIndex(0)
-					return
-				}
-			}
-
-			// Normal input handling
-			if (key.tab && !mentionInfo.inMentionMode) {
-				toggleMode()
-				return
-			}
-			if (key.return && !mentionInfo.inMentionMode) {
-				if (prompt.trim() || imagePaths.length > 0) {
-					onSubmit(prompt.trim(), imagePaths)
-				}
-				return
-			}
-			if (key.escape && !mentionInfo.inMentionMode) {
-				if (escPressedOnce) {
-					onExit?.()
-				} else {
-					setEscPressedOnce(true)
-				}
-				return
-			}
-			if (key.backspace || key.delete) {
-				setTextInput((prev) => prev.slice(0, -1))
-				setEscPressedOnce(false)
-				return
-			}
-			if (input && !key.ctrl && !key.meta && !key.upArrow && !key.downArrow && !key.tab) {
-				setTextInput((prev) => prev + input)
-				setEscPressedOnce(false)
-			}
-		},
-		{ isActive: isRawModeSupported },
-	)
-
-	const borderColor = mode === "act" ? "blue" : "yellow"
-
-	return (
-		<Box flexDirection="column" width="100%">
-			{/* Account/Provider info at top */}
-			{controller && (
-				<Box marginBottom={1}>
-					<AccountInfoView controller={controller} />
-				</Box>
-			)}
-
-			{/* Cline logo - centered */}
-			<Box alignItems="center" flexDirection="column">
-				{CLINE_LOGO.map((line, idx) => (
-					// biome-ignore lint/suspicious/noArrayIndexKey: static array that never changes
-					<Text color="white" key={idx}>
-						{line}
-					</Text>
-				))}
-			</Box>
-
-			{/* Main prompt - centered, bold */}
-			<Box justifyContent="center" marginTop={1}>
-				<Text bold color="white">
-					What can I do for you?
-				</Text>
-			</Box>
-
-			{/* Ripgrep warning if needed */}
-			{showRipgrepWarning && (
-				<Box marginTop={1}>
-					<Text color="yellow">⚠ ripgrep not found - file search will be slower. </Text>
-					<Text color="gray">Install: {getRipgrepInstallInstructions()}</Text>
-				</Box>
-			)}
-
-			{/* Input field with border */}
-			<Box
-				borderColor={borderColor}
-				borderStyle="round"
-				flexDirection="row"
-				marginTop={1}
-				paddingLeft={1}
-				paddingRight={1}
-				width="100%">
-				<Text>{textInput}</Text>
-				<Text inverse> </Text>
-			</Box>
-
-			{/* Model ID and Mode toggle row */}
-			<Box justifyContent="space-between" width="100%">
-				{/* Model ID on left */}
-				<Text color="gray">{modelId}</Text>
-
-				{/* Mode toggle on right */}
-				<Box gap={1}>
-					<Box>
-						<Text bold={mode === "plan"} color={mode === "plan" ? "yellow" : "gray"}>
-							{mode === "plan" ? "●" : "○"} Plan
-						</Text>
-					</Box>
-					<Box>
-						<Text bold={mode === "act"} color={mode === "act" ? "blue" : "gray"}>
-							{mode === "act" ? "●" : "○"} Act
-						</Text>
-					</Box>
-					<Text color="gray">(Tab)</Text>
-				</Box>
-			</Box>
-
-			{/* File mention menu - below input */}
-			{mentionInfo.inMentionMode && (
-				<FileMentionMenu
-					isLoading={isSearching}
-					query={mentionInfo.query}
-					results={fileResults}
-					selectedIndex={selectedIndex}
-				/>
-			)}
-
-			{/* Attached images */}
-			{imagePaths.length > 0 && (
-				<Text color="magenta">
-					📎 {imagePaths.length} image{imagePaths.length > 1 ? "s" : ""} attached
-				</Text>
-			)}
-
-			{/* Help text */}
-			<Box>
-				<Text color="gray">Enter to submit · @ to mention files · </Text>
-				<Text bold={escPressedOnce} color={escPressedOnce ? "white" : "gray"}>
-					{escPressedOnce ? "Press Esc again to exit" : "Esc to exit"}
-				</Text>
-			</Box>
-		</Box>
-	)
-}

cli-ts/src/constants/featured-models.ts

@@ -1,52 +0,0 @@
-/**
- * Featured models shown in the Cline model picker during onboarding
- * These are curated models that work well with Cline
- */
-
-export interface FeaturedModel {
-	id: string
-	name: string
-	description: string
-	label: string
-}
-
-export const FEATURED_MODELS = {
-	recommended: [
-		{
-			id: "anthropic/claude-opus-4.5",
-			name: "Claude Opus 4.5",
-			description: "State-of-the-art for complex coding",
-			label: "Best",
-		},
-		{
-			id: "openai/gpt-5.2-codex",
-			name: "GPT 5.2 Codex",
-			description: "OpenAI's latest with strong coding abilities",
-			label: "New",
-		},
-		{
-			id: "google/gemini-3-pro-preview",
-			name: "Gemini 3 Pro",
-			description: "1M context window for large codebases",
-			label: "Trending",
-		},
-	] as FeaturedModel[],
-	free: [
-		{
-			id: "kwaipilot/kat-coder-pro",
-			name: "KAT Coder Pro",
-			description: "Advanced agentic coding model",
-			label: "FREE",
-		},
-		{
-			id: "mistralai/devstral-2512:free",
-			name: "Devstral",
-			description: "Mistral's coding model",
-			label: "FREE",
-		},
-	] as FeaturedModel[],
-}
-
-export function getAllFeaturedModels(): FeaturedModel[] {
-	return [...FEATURED_MODELS.recommended, ...FEATURED_MODELS.free]
-}

cli-ts/src/index.ts

@@ -1,705 +0,0 @@
-/**
- * Cline CLI - TypeScript implementation with React Ink
- */
-
-import path from "node:path"
-import { exit } from "node:process"
-import type { ApiProvider } from "@shared/api"
-import { Command } from "commander"
-import { render } from "ink"
-import React from "react"
-import { ClineEndpoint } from "@/config"
-import { Controller } from "@/core/controller"
-import { StateManager } from "@/core/storage/StateManager"
-import { AuthHandler } from "@/hosts/external/AuthHandler"
-import { HostProvider } from "@/hosts/host-provider"
-import { FileEditProvider } from "@/integrations/editor/FileEditProvider"
-import { openAiCodexOAuthManager } from "@/integrations/openai-codex/oauth"
-import { StandaloneTerminalManager } from "@/integrations/terminal/standalone/StandaloneTerminalManager"
-import { BannerService } from "@/services/banner/BannerService"
-import { ErrorService } from "@/services/error/ErrorService"
-import { initializeDistinctId } from "@/services/logging/distinctId"
-import { telemetryService } from "@/services/telemetry"
-import { Logger } from "@/shared/services/Logger"
-import { Session } from "@/shared/services/Session"
-import { getProviderModelIdKey, ProviderToApiKeyMap } from "@/shared/storage"
-import { secretStorage } from "@/shared/storage/ClineSecretStorage"
-import { version as CLI_VERSION } from "../package.json"
-import { runAcpMode } from "./acp/index.js"
-import { App } from "./components/App"
-import { checkRawModeSupport } from "./context/StdinContext"
-import { createCliHostBridgeProvider } from "./controllers"
-import { CliCommentReviewController } from "./controllers/CliCommentReviewController"
-import { CliWebviewProvider } from "./controllers/CliWebviewProvider"
-import { restoreConsole } from "./utils/console"
-import { calculateRobotTopRow, queryCursorPos } from "./utils/cursor-position"
-import { printInfo, printWarning } from "./utils/display"
-import { parseImagesFromInput, processImagePaths } from "./utils/parser"
-import { CLINE_CLI_DIR } from "./utils/path"
-import { readStdinIfPiped } from "./utils/piped"
-import { runPlainTextTask } from "./utils/plain-text-task"
-import { printSessionSummary } from "./utils/session-summary"
-import { checkForUpdates } from "./utils/update"
-import { initializeCliContext } from "./vscode-context"
-import { CLI_LOG_FILE, shutdownEvent, window } from "./vscode-shim"
-
-// Track active context for graceful shutdown
-let activeContext: CliContext | null = null
-let isShuttingDown = false
-
-function setupSignalHandlers() {
-	const shutdown = async (signal: string) => {
-		if (isShuttingDown) {
-			// Force exit on second signal
-			process.exit(1)
-		}
-		isShuttingDown = true
-
-		// Notify components to hide UI before shutdown
-		shutdownEvent.fire()
-
-		// Clear several lines to remove the input field and footer from display
-		// Move cursor up and clear lines (input box + footer rows)
-		const linesToClear = 8 // Input box (3 lines with border) + footer (4-5 lines)
-		process.stdout.write(`\x1b[${linesToClear}A\x1b[J`)
-
-		printWarning(`${signal} received, shutting down...`)
-
-		try {
-			if (activeContext) {
-				const task = activeContext.controller.task
-				if (task) {
-					task.abortTask()
-				}
-				await activeContext.controller.stateManager.flushPendingState()
-				await activeContext.controller.dispose()
-			}
-			await ErrorService.get().dispose()
-		} catch {
-			// Best effort cleanup
-		}
-
-		// Print session summary before exit
-		printSessionSummary()
-
-		process.exit(0)
-	}
-
-	process.on("SIGINT", () => shutdown("SIGINT"))
-	process.on("SIGTERM", () => shutdown("SIGTERM"))
-
-	// Suppress known abort errors from unhandled rejections
-	// These occur when task is cancelled and async operations throw "Cline instance aborted"
-	process.on("unhandledRejection", (reason: unknown) => {
-		const message = reason instanceof Error ? reason.message : String(reason)
-		// Silently ignore abort-related errors - they're expected during task cancellation
-		if (message.includes("aborted") || message.includes("abort")) {
-			Logger.info("Suppressed unhandled rejection due to abort:", message)
-			return
-		}
-		// For other unhandled rejections, log to file via Logger (if available)
-		// This won't show in terminal but will be in log files for debugging
-		Logger.error("Unhandled rejection:", reason)
-	})
-}
-
-setupSignalHandlers()
-
-interface CliContext {
-	extensionContext: any
-	dataDir: string
-	extensionDir: string
-	workspacePath: string
-	controller: Controller
-}
-
-interface InitOptions {
-	config?: string
-	cwd?: string
-	verbose?: boolean
-	enableAuth?: boolean
-}
-
-/**
- * Initialize all CLI infrastructure and return context needed for commands
- */
-async function initializeCli(options: InitOptions): Promise<CliContext> {
-	const workspacePath = options.cwd || process.cwd()
-	const { extensionContext, DATA_DIR, EXTENSION_DIR } = initializeCliContext({
-		clineDir: options.config,
-		workspaceDir: workspacePath,
-	})
-
-	await ClineEndpoint.initialize()
-	await initializeDistinctId(extensionContext)
-
-	// Initialize/reset session tracking for this CLI run
-	Session.reset()
-
-	if (options.enableAuth) {
-		AuthHandler.getInstance().setEnabled(true)
-	}
-
-	const outputChannel = window.createOutputChannel("Cline CLI")
-	outputChannel.appendLine(
-		`Cline CLI initialized. Data dir: ${DATA_DIR}, Extension dir: ${EXTENSION_DIR}, Log dir: ${CLINE_CLI_DIR.log}`,
-	)
-	const logToChannel = (message: string) => outputChannel.appendLine(message)
-
-	HostProvider.initialize(
-		() => new CliWebviewProvider(extensionContext as any),
-		() => new FileEditProvider(),
-		() => new CliCommentReviewController(),
-		() => new StandaloneTerminalManager(),
-		createCliHostBridgeProvider(workspacePath),
-		logToChannel,
-		async () => (options.enableAuth ? AuthHandler.getInstance().getCallbackUrl() : ""),
-		async (name: string) => path.join(process.cwd(), name),
-		EXTENSION_DIR,
-		DATA_DIR,
-	)
-
-	await ErrorService.initialize()
-	await StateManager.initialize(extensionContext as any)
-
-	// Initialize OpenAI Codex OAuth manager with extension context for secrets storage
-	openAiCodexOAuthManager.initialize(extensionContext)
-
-	// Configure the shared Logging class to use HostProvider's output channel
-	Logger.subscribe((msg: string) => HostProvider.get().logToChannel(msg))
-
-	const webview = HostProvider.get().createWebviewProvider() as CliWebviewProvider
-	const controller = webview.controller
-
-	BannerService.initialize(webview.controller)
-
-	telemetryService.captureHostEvent("cline_cli", "initialized")
-
-	const ctx = { extensionContext, dataDir: DATA_DIR, extensionDir: EXTENSION_DIR, workspacePath, controller }
-	activeContext = ctx
-	return ctx
-}
-
-/**
- * Run an Ink app with proper cleanup handling
- */
-async function runInkApp(element: React.ReactElement, cleanup: () => Promise<void>): Promise<void> {
-	// Note: incrementalRendering is disabled because it causes UI glitches on terminal resize.
-	// Ink's incremental rendering tries to erase N lines based on previous output height,
-	// but when the terminal shrinks, this leaves artifacts. Gemini CLI only enables
-	// incrementalRendering when alternateBuffer is also enabled (which we don't use).
-	//
-	// exitOnCtrlC: false - We handle Ctrl+C ourselves so we can clean up UI before exiting.
-	// The app components listen for Ctrl+C via useInput and call their exit handlers.
-	const { waitUntilExit, unmount } = render(element, { exitOnCtrlC: false })
-
-	try {
-		await waitUntilExit()
-	} finally {
-		try {
-			unmount()
-		} catch {
-			// Already unmounted
-		}
-		restoreConsole()
-		await cleanup()
-	}
-}
-
-/**
- * Run a task with the given prompt - uses welcome view for consistent behavior
- */
-async function runTask(
-	prompt: string,
-	options: {
-		act?: boolean
-		plan?: boolean
-		model?: string
-		verbose?: boolean
-		cwd?: string
-		config?: string
-		thinking?: boolean
-		yolo?: boolean
-		images?: string[]
-		json?: boolean
-		stdinWasPiped?: boolean
-	},
-	existingContext?: CliContext,
-) {
-	const ctx = existingContext || (await initializeCli({ ...options, enableAuth: true }))
-
-	// Parse images from the prompt text (e.g., @/path/to/image.png)
-	const { prompt: cleanPrompt, imagePaths: parsedImagePaths } = parseImagesFromInput(prompt)
-
-	// Combine parsed image paths with explicit --images option
-	const allImagePaths = [...(options.images || []), ...parsedImagePaths]
-	// Convert image file paths to base64 data URLs
-	const imageDataUrls = await processImagePaths(allImagePaths)
-
-	// Use clean prompt (with image refs removed)
-	const taskPrompt = cleanPrompt || prompt
-
-	// Task without prompt starts in interactive mode
-	telemetryService.captureHostEvent("task_command", prompt ? "task" : "interactive")
-
-	if (options.plan) {
-		StateManager.get().setGlobalState("mode", "plan")
-		telemetryService.captureHostEvent("mode_flag", "plan")
-	} else if (options.act) {
-		StateManager.get().setGlobalState("mode", "act")
-		telemetryService.captureHostEvent("mode_flag", "act")
-	}
-
-	if (options.model) {
-		const selectedMode = (StateManager.get().getGlobalSettingsKey("mode") || "act") as "act" | "plan"
-
-		// Get the current provider for the selected mode
-		const providerKey = selectedMode === "act" ? "actModeApiProvider" : "planModeApiProvider"
-		const currentProvider = StateManager.get().getGlobalSettingsKey(providerKey) as ApiProvider
-
-		// Update the generic model ID for the current mode
-		const modelKey = selectedMode === "act" ? "actModeApiModelId" : "planModeApiModelId"
-		StateManager.get().setGlobalState(modelKey, options.model)
-
-		// Also update the provider-specific model ID key if applicable
-		const providerModelKey = getProviderModelIdKey(currentProvider, selectedMode)
-		if (providerModelKey) {
-			StateManager.get().setGlobalState(providerModelKey, options.model)
-		}
-		telemetryService.captureHostEvent("model_flag", options.model)
-	}
-
-	// Set thinking budget based on --thinking flag
-	const thinkingBudget = options.thinking ? 1024 : 0
-	const currentMode = StateManager.get().getGlobalSettingsKey("mode") || "act"
-	const thinkingKey = currentMode === "act" ? "actModeThinkingBudgetTokens" : "planModeThinkingBudgetTokens"
-	StateManager.get().setGlobalState(thinkingKey, thinkingBudget)
-	if (options.thinking) {
-		telemetryService.captureHostEvent("thinking_flag", "true")
-	}
-
-	// Set yolo mode based on --yolo flag
-	if (options.yolo) {
-		StateManager.get().setGlobalState("yoloModeToggled", true)
-		telemetryService.captureHostEvent("yolo_flag", "true")
-	}
-
-	await StateManager.get().flushPendingState()
-
-	// Detect if output is a TTY (interactive terminal) or redirected to a file/pipe
-	const isTTY = process.stdout.isTTY === true
-
-	// Use plain text mode when output is redirected, stdin was piped, or JSON mode is enabled
-	// Ink requires raw mode on stdin which isn't available when stdin is piped
-	// Note: we use the stdinWasPiped flag passed from the caller because process.stdin.isTTY
-	// may not be reliable after stdin has been consumed by readStdinIfPiped()
-	if (!isTTY || options.stdinWasPiped || options.json) {
-		// Check if auth is configured before attempting to run the task
-		// In plain text mode we can't show the interactive auth flow
-		const hasAuth = await isAuthConfigured()
-		if (!hasAuth) {
-			printWarning("Not authenticated. Please run 'cline auth' first to configure your API credentials.")
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			exit(1)
-		}
-
-		const reason = options.json ? "json" : options.stdinWasPiped ? "piped_stdin" : "redirected_output"
-		telemetryService.captureHostEvent("plain_text_mode", reason)
-		// Plain text mode: no Ink rendering, just clean text output
-		const success = await runPlainTextTask({
-			controller: ctx.controller,
-			prompt: taskPrompt,
-			imageDataUrls: imageDataUrls.length > 0 ? imageDataUrls : undefined,
-			verbose: options.verbose,
-			jsonOutput: options.json,
-		})
-
-		// Cleanup
-		await ctx.controller.stateManager.flushPendingState()
-		await ctx.controller.dispose()
-		await ErrorService.get().dispose()
-		exit(success ? 0 : 1)
-	}
-
-	// Use welcome view for consistent rendering (same as interactive mode)
-	// Query cursor position BEFORE Ink mounts to know where robot will render
-	const cursorPos = await queryCursorPos(process.stdin, process.stdout)
-	const terminalRows = process.stdout.rows ?? 24
-	const robotTopRow = calculateRobotTopRow(cursorPos, terminalRows)
-
-	let taskError = false
-
-	// Render the welcome view with optional initial prompt/images
-	// If prompt provided (cline task "prompt"), ChatView will auto-submit
-	// If no prompt (cline interactive), user will type it in
-	await runInkApp(
-		React.createElement(App, {
-			view: "welcome",
-			verbose: options.verbose,
-			controller: ctx.controller,
-			isRawModeSupported: checkRawModeSupport(),
-			robotTopRow,
-			initialPrompt: taskPrompt || undefined,
-			initialImages: imageDataUrls.length > 0 ? imageDataUrls : undefined,
-			onError: () => {
-				taskError = true
-			},
-			onWelcomeExit: () => {
-				// User pressed Esc
-				exit(0)
-			},
-		}),
-		async () => {
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			if (taskError) {
-				printWarning("Task ended with errors.")
-				exit(1)
-			}
-			exit(0)
-		},
-	)
-}
-
-/**
- * List task history
- */
-async function listHistory(options: { config?: string; limit?: number; page?: number }) {
-	const ctx = await initializeCli(options)
-
-	const taskHistory = StateManager.get().getGlobalStateKey("taskHistory") || []
-	// Sort by timestamp (newest first) before pagination
-	const sortedHistory = [...taskHistory].sort((a: any, b: any) => (b.ts || 0) - (a.ts || 0))
-	const limit = typeof options.limit === "string" ? parseInt(options.limit, 10) : options.limit || 10
-	const initialPage = typeof options.page === "string" ? parseInt(options.page, 10) : options.page || 1
-	const totalCount = sortedHistory.length
-	const totalPages = Math.ceil(totalCount / limit)
-
-	telemetryService.captureHostEvent("history_command", "executed")
-
-	if (sortedHistory.length === 0) {
-		printInfo("No task history found.")
-		await ctx.controller.stateManager.flushPendingState()
-		await ctx.controller.dispose()
-		await ErrorService.get().dispose()
-		exit(0)
-	}
-
-	await runInkApp(
-		React.createElement(App, {
-			view: "history",
-			historyItems: [],
-			historyAllItems: sortedHistory,
-			controller: ctx.controller,
-			historyPagination: { page: initialPage, totalPages, totalCount, limit },
-			isRawModeSupported: checkRawModeSupport(),
-		}),
-		async () => {
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			exit(0)
-		},
-	)
-}
-
-/**
- * Show current configuration
- */
-async function showConfig(options: { config?: string }) {
-	const ctx = await initializeCli(options)
-	const stateManager = StateManager.get()
-
-	// Dynamically import the wrapper to avoid circular dependencies
-	const { ConfigViewWrapper } = await import("./components/ConfigViewWrapper")
-
-	// Check feature flags
-	const skillsEnabled = stateManager.getGlobalSettingsKey("skillsEnabled") ?? false
-
-	telemetryService.captureHostEvent("config_command", "executed")
-
-	await runInkApp(
-		React.createElement(ConfigViewWrapper, {
-			controller: ctx.controller,
-			dataDir: ctx.dataDir,
-			globalState: stateManager.getAllGlobalStateEntries(),
-			workspaceState: stateManager.getAllWorkspaceStateEntries(),
-			hooksEnabled: true,
-			skillsEnabled,
-			isRawModeSupported: checkRawModeSupport(),
-		}),
-		async () => {
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			exit(0)
-		},
-	)
-}
-
-/**
- * Run authentication flow
- */
-async function runAuth(options: {
-	provider?: string
-	apikey?: string
-	modelid?: string
-	baseurl?: string
-	verbose?: boolean
-	cwd?: string
-	config?: string
-}) {
-	const ctx = await initializeCli({ ...options, enableAuth: true })
-
-	const hasQuickSetupFlags = options.provider || options.apikey || options.modelid || options.baseurl
-	const quickSetup = hasQuickSetupFlags
-		? { provider: options.provider, apikey: options.apikey, modelid: options.modelid, baseurl: options.baseurl }
-		: undefined
-
-	telemetryService.captureHostEvent("auth_command", hasQuickSetupFlags ? "quick_setup" : "interactive")
-
-	let authError = false
-
-	await runInkApp(
-		React.createElement(App, {
-			view: "auth",
-			controller: ctx.controller,
-			isRawModeSupported: checkRawModeSupport(),
-			onComplete: () => {
-				telemetryService.captureHostEvent("auth", "completed")
-				exit(0)
-			},
-			onError: () => {
-				telemetryService.captureHostEvent("auth", "error")
-				authError = true
-			},
-			authQuickSetup: quickSetup,
-		}),
-		async () => {
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			exit(0)
-		},
-	)
-
-	if (authError) {
-		process.exit(1)
-	}
-}
-
-// Setup CLI commands
-const program = new Command()
-
-program.name("cline").description("Cline CLI - AI coding assistant in your terminal").version(CLI_VERSION)
-
-// Enable positional options to avoid conflicts between root and subcommand options with the same name
-program.enablePositionalOptions()
-
-program
-	.command("task")
-	.alias("t")
-	.description("Run a new task")
-	.argument("<prompt>", "The task prompt")
-	.option("-a, --act", "Run in act mode")
-	.option("-p, --plan", "Run in plan mode")
-	.option("-y, --yolo", "Enable yolo mode (auto-approve actions)")
-	.option("-m, --model <model>", "Model to use for the task")
-	.option("-v, --verbose", "Show verbose output")
-	.option("-c, --cwd <path>", "Working directory for the task")
-	.option("--config <path>", "Path to Cline configuration directory")
-	.option("--thinking", "Enable extended thinking (1024 token budget)")
-	.option("--json", "Output messages as JSON instead of styled text")
-	.action((prompt, options) => runTask(prompt, options))
-
-program
-	.command("history")
-	.alias("h")
-	.description("List task history")
-	.option("-n, --limit <number>", "Number of tasks to show", "10")
-	.option("-p, --page <number>", "Page number (1-based)", "1")
-	.option("--config <path>", "Path to Cline configuration directory")
-	.action(listHistory)
-
-program
-	.command("config")
-	.description("Show current configuration")
-	.option("--config <path>", "Path to Cline configuration directory")
-	.action(showConfig)
-
-program
-	.command("auth")
-	.description("Authenticate a provider and configure what model is used")
-	.option("-p, --provider <id>", "Provider ID for quick setup (e.g., openai-native, anthropic)")
-	.option("-k, --apikey <key>", "API key for the provider")
-	.option("-m, --modelid <id>", "Model ID to configure (e.g., gpt-4o, claude-sonnet-4-5-20250929)")
-	.option("-b, --baseurl <url>", "Base URL (optional, only for openai provider)")
-	.option("-v, --verbose", "Show verbose output")
-	.option("-c, --cwd <path>", "Working directory for the task")
-	.option("--config <path>", "Path to Cline configuration directory")
-	.action(runAuth)
-
-program
-	.command("version")
-	.description("Show Cline CLI version number")
-	.action(() => printInfo(`Cline CLI version: ${CLI_VERSION}`))
-
-program
-	.command("update")
-	.description("Check for updates and install if available")
-	.option("-v, --verbose", "Show verbose output")
-	.action(() => checkForUpdates(CLI_VERSION))
-
-// Dev command with subcommands
-const devCommand = program.command("dev").description("Developer tools and utilities")
-
-devCommand
-	.command("log")
-	.description("Open the log file")
-	.action(async () => {
-		const { openExternal } = await import("@/utils/env")
-		await openExternal(CLI_LOG_FILE)
-	})
-
-/**
- * Check if the user has authentication configured.
- * Returns true if they have either:
- * - Cline provider with stored auth data
- * - OpenAI Codex provider with OAuth credentials
- * - BYO provider with an API key configured
- */
-async function isAuthConfigured(): Promise<boolean> {
-	const stateManager = StateManager.get()
-	const mode = stateManager.getGlobalSettingsKey("mode") as string
-	const providerKey = mode === "act" ? "actModeApiProvider" : "planModeApiProvider"
-	const currentProvider = (stateManager.getGlobalSettingsKey(providerKey) as string) || "cline"
-
-	if (currentProvider === "cline") {
-		// For Cline provider, check if we have stored auth data
-		const authData = await secretStorage.get("cline:clineAccountId")
-		return !!authData
-	}
-
-	if (currentProvider === "openai-codex") {
-		// For OpenAI Codex, check if OAuth credentials are stored
-		const isAuthenticated = await openAiCodexOAuthManager.isAuthenticated()
-		return isAuthenticated
-	}
-
-	// For BYO providers, check if the API key is configured
-	const keyField = ProviderToApiKeyMap[currentProvider as keyof typeof ProviderToApiKeyMap]
-	if (!keyField) {
-		return false
-	}
-
-	const fields = Array.isArray(keyField) ? keyField : [keyField]
-	for (const field of fields) {
-		const value = await secretStorage.get(field)
-		if (value) {
-			return true
-		}
-	}
-
-	return false
-}
-
-/**
- * Show welcome prompt and wait for user input
- * If auth is not configured, show auth flow first
- */
-async function showWelcome(options: { verbose?: boolean; cwd?: string; config?: string; thinking?: boolean }) {
-	const ctx = await initializeCli({ ...options, enableAuth: true })
-
-	// Check if auth is configured
-	const hasAuth = await isAuthConfigured()
-
-	// Query cursor position BEFORE Ink mounts
-	const cursorPos = await queryCursorPos(process.stdin, process.stdout)
-	const terminalRows = process.stdout.rows ?? 24
-	const robotTopRow = calculateRobotTopRow(cursorPos, terminalRows)
-
-	let hadError = false
-
-	await runInkApp(
-		React.createElement(App, {
-			// Start with auth view if not configured, otherwise welcome
-			view: hasAuth ? "welcome" : "auth",
-			verbose: options.verbose,
-			controller: ctx.controller,
-			isRawModeSupported: checkRawModeSupport(),
-			robotTopRow,
-			onWelcomeExit: () => {
-				exit(0)
-			},
-			onError: () => {
-				hadError = true
-			},
-		}),
-		async () => {
-			await ctx.controller.stateManager.flushPendingState()
-			await ctx.controller.dispose()
-			await ErrorService.get().dispose()
-			exit(hadError ? 1 : 0)
-		},
-	)
-}
-
-// Interactive mode (default when no command given)
-program
-	.argument("[prompt]", "Task prompt (starts task immediately)")
-	.option("-a, --act", "Run in act mode")
-	.option("-p, --plan", "Run in plan mode")
-	.option("-y, --yolo", "Enable yolo mode (auto-approve actions)")
-	.option("-m, --model <model>", "Model to use for the task")
-	.option("-v, --verbose", "Show verbose output")
-	.option("-c, --cwd <path>", "Working directory")
-	.option("--config <path>", "Configuration directory")
-	.option("--thinking", "Enable extended thinking (1024 token budget)")
-	.option("--json", "Output messages as JSON instead of styled text")
-	.option("--acp", "Run in ACP (Agent Client Protocol) mode for editor integration")
-	.action(async (prompt, options) => {
-		// Check for ACP mode first - this takes precedence over everything else
-		if (options.acp) {
-			await runAcpMode({
-				config: options.config,
-				cwd: options.cwd,
-				verbose: options.verbose,
-			})
-			return
-		}
-
-		// Always check for piped stdin content
-		const stdinInput = await readStdinIfPiped()
-
-		// If no prompt argument, check if input is piped via stdin
-		let effectivePrompt = prompt
-		if (stdinInput) {
-			if (effectivePrompt) {
-				// Prepend stdin content to the prompt
-				effectivePrompt = `${stdinInput}\n\n${effectivePrompt}`
-			} else {
-				effectivePrompt = stdinInput
-			}
-
-			telemetryService.captureHostEvent("piped", "detached")
-
-			// Debug: show that we received piped input
-			if (options.verbose) {
-				process.stderr.write(`[debug] Received ${stdinInput.length} bytes from stdin\n`)
-			}
-		}
-
-		if (effectivePrompt) {
-			// Pass stdinWasPiped flag so runTask knows to use plain text mode
-			await runTask(effectivePrompt, { ...options, stdinWasPiped: !!stdinInput })
-		} else {
-			// Show welcome prompt if no prompt given
-			await showWelcome(options)
-		}
-	})
-
-// Parse and run
-program.parse()

cli-ts/src/utils/cursor-position.ts

@@ -1,57 +0,0 @@
-/**
- * Query terminal cursor position before Ink mounts
- * Must be called BEFORE render() to avoid escape sequence leaking into Ink's input handling
- */
-
-export async function queryCursorPos(
-	stdin: NodeJS.ReadStream,
-	stdout: NodeJS.WriteStream,
-	{ timeoutMs = 75 } = {},
-): Promise<{ row: number; col: number } | null> {
-	if (!stdin.isTTY || !stdout.isTTY || typeof (stdin as any).setRawMode !== "function") return null
-
-	const ttyIn = stdin as any as { isRaw?: boolean; setRawMode: (b: boolean) => void; on: any; off: any }
-	const wasRaw = !!ttyIn.isRaw
-
-	ttyIn.setRawMode(true)
-	stdin.resume()
-
-	return await new Promise((resolve) => {
-		let buf = ""
-		const onData = (chunk: Buffer) => {
-			buf += chunk.toString("utf8")
-			const m = buf.match(/\x1b\[(\d+);(\d+)R/)
-			if (!m) return
-			cleanup()
-			resolve({ row: Number(m[1]), col: Number(m[2]) })
-		}
-
-		const cleanup = () => {
-			clearTimeout(timer)
-			stdin.off("data", onData)
-			try {
-				ttyIn.setRawMode(wasRaw)
-			} catch {}
-		}
-
-		const timer = setTimeout(() => {
-			cleanup()
-			resolve(null)
-		}, timeoutMs)
-
-		stdin.on("data", onData)
-		stdout.write("\x1b[6n") // DSR: cursor position
-	})
-}
-
-/**
- * Calculate where the robot will be rendered on screen
- */
-export function calculateRobotTopRow(cursorPos: { row: number } | null, terminalRows: number): number {
-	const robotHeight = 12
-	const firstFrameHeight = robotHeight + 8 // robot + welcome text + margins + input + footer
-
-	const startRow = cursorPos?.row ?? 1
-	// If content doesn't fit below cursor, terminal scrolls
-	return Math.max(1, Math.min(startRow, terminalRows - firstFrameHeight + 1))
-}

cli-ts/src/utils/input.ts

@@ -1,13 +0,0 @@
-/**
- * Input filtering utilities for CLI components
- */
-
-/**
- * Check if input contains mouse escape sequences from terminal mouse tracking.
- * AsciiMotionCli enables mouse tracking which generates sequences like [<35;46;17M
- * These should be filtered out of text input handlers.
- */
-export function isMouseEscapeSequence(input: string): boolean {
-	// Mouse events look like: [<35;46;17M or contain escape characters
-	return input.includes("\x1b") || input.includes("[<") || /\d+;\d+[Mm]/.test(input)
-}

cli-ts/src/utils/path.ts

@@ -1,11 +0,0 @@
-import os from "node:os"
-import path from "node:path"
-
-const data = process.env.CLINE_DATA_DIR ?? path.join(os.homedir(), ".cline", "data")
-
-const log = process.env.CLINE_LOG_DIR ?? path.join(data, "logs")
-
-export const CLINE_CLI_DIR = {
-	data,
-	log,
-}

cli-ts/src/utils/piped.test.ts

@@ -1,392 +0,0 @@
-import { Readable } from "node:stream"
-import { afterEach, beforeEach, describe, expect, it, vi } from "vitest"
-import { readStdinIfPiped } from "./piped"
-
-describe("readStdinIfPiped", () => {
-	let mockStdin: Readable & { isTTY?: boolean }
-
-	beforeEach(() => {
-		// Create a mock readable stream
-		mockStdin = new Readable({
-			read() {},
-		}) as Readable & { isTTY?: boolean }
-
-		// Mock process.stdin by stubbing its properties
-		vi.spyOn(process, "stdin", "get").mockReturnValue(mockStdin as any)
-	})
-
-	afterEach(() => {
-		vi.restoreAllMocks()
-	})
-
-	describe("TTY detection", () => {
-		it("should return null when stdin is a TTY (interactive terminal)", async () => {
-			mockStdin.isTTY = true
-			const result = await readStdinIfPiped()
-			expect(result).toBeNull()
-		})
-
-		it("should attempt to read when stdin is not a TTY (piped input)", async () => {
-			mockStdin.isTTY = false
-
-			// Simulate immediate end event (no data)
-			setImmediate(() => {
-				mockStdin.emit("end")
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toBeNull()
-		})
-	})
-
-	describe("piped input scenarios", () => {
-		interface TestCase {
-			name: string
-			input: string | string[]
-			expected: string | null
-			description?: string
-		}
-
-		const testCases: TestCase[] = [
-			{
-				name: "single line input",
-				input: "echo hello",
-				expected: "echo hello",
-				description: "should read and return single line",
-			},
-			{
-				name: "multi-line input",
-				input: ["line 1", "line 2", "line 3"],
-				expected: "line 1\nline 2\nline 3",
-				description: "should read and join multiple lines",
-			},
-			{
-				name: "empty string",
-				input: "",
-				expected: null,
-				description: "should return null for empty input",
-			},
-			{
-				name: "whitespace only",
-				input: "   \n  \t  \n   ",
-				expected: null,
-				description: "should return null for whitespace-only input",
-			},
-			{
-				name: "leading and trailing whitespace",
-				input: "  hello world  \n",
-				expected: "hello world",
-				description: "should trim leading and trailing whitespace",
-			},
-			{
-				name: "large input",
-				input: "a".repeat(10000),
-				expected: "a".repeat(10000),
-				description: "should handle large input",
-			},
-			{
-				name: "special characters",
-				input: "!@#$%^&*(){}[]|\\:;\"'<>?,./",
-				expected: "!@#$%^&*(){}[]|\\:;\"'<>?,./",
-				description: "should preserve special characters",
-			},
-			{
-				name: "unicode characters",
-				input: "Hello 世界 🌍 مرحبا",
-				expected: "Hello 世界 🌍 مرحبا",
-				description: "should handle unicode characters correctly",
-			},
-			{
-				name: "JSON input",
-				input: '{"key": "value", "nested": {"data": 123}}',
-				expected: '{"key": "value", "nested": {"data": 123}}',
-				description: "should preserve JSON structure",
-			},
-			{
-				name: "code snippet",
-				input: ["function test() {", '  console.log("hello")', "}"],
-				expected: 'function test() {\n  console.log("hello")\n}',
-				description: "should preserve code structure with indentation",
-			},
-		]
-
-		testCases.forEach(({ name, input, expected, description }) => {
-			it(`${name}${description ? ` - ${description}` : ""}`, async () => {
-				mockStdin.isTTY = false
-
-				// Simulate piped data
-				setImmediate(() => {
-					const data = Array.isArray(input) ? input.join("\n") : input
-					mockStdin.push(data)
-					mockStdin.push(null) // Signal end of stream
-				})
-
-				const result = await readStdinIfPiped()
-				expect(result).toBe(expected)
-			})
-		})
-	})
-
-	describe("chunked data", () => {
-		it("should accumulate data from multiple chunks", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				mockStdin.emit("data", "chunk1 ")
-				mockStdin.emit("data", "chunk2 ")
-				mockStdin.emit("data", "chunk3")
-				mockStdin.emit("end")
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toBe("chunk1 chunk2 chunk3")
-		})
-
-		it("should handle rapid successive chunks", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				for (let i = 0; i < 100; i++) {
-					mockStdin.emit("data", `${i} `)
-				}
-				mockStdin.emit("end")
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toContain("0 ")
-			expect(result).toContain("99")
-		})
-	})
-
-	describe("timeout behavior", () => {
-		it("should timeout after 100ms if no data received", async () => {
-			mockStdin.isTTY = false
-
-			// Don't emit any events - let it timeout
-
-			const startTime = Date.now()
-			const result = await readStdinIfPiped()
-			const elapsed = Date.now() - startTime
-
-			expect(result).toBeNull()
-			expect(elapsed).toBeGreaterThanOrEqual(95) // Allow small margin
-			expect(elapsed).toBeLessThan(150)
-		})
-
-		it("should return data received before timeout", async () => {
-			mockStdin.isTTY = false
-
-			setTimeout(() => {
-				mockStdin.emit("data", "quick data")
-				// Don't emit end - let it timeout
-			}, 50)
-
-			const result = await readStdinIfPiped()
-			expect(result).toBe("quick data")
-		})
-
-		it("should not timeout if end event is received", async () => {
-			mockStdin.isTTY = false
-
-			// Delay end event but emit it before timeout
-			setTimeout(() => {
-				mockStdin.emit("data", "delayed data")
-				mockStdin.emit("end")
-			}, 50)
-
-			const result = await readStdinIfPiped()
-			expect(result).toBe("delayed data")
-		})
-	})
-
-	describe("error handling", () => {
-		it("should return null on stdin error", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				mockStdin.emit("error", new Error("stdin read error"))
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toBeNull()
-		})
-
-		it("should handle error after partial data received", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				mockStdin.emit("data", "partial data")
-				mockStdin.emit("error", new Error("read error"))
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toBeNull()
-		})
-
-		it("should clean up listeners on error", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				mockStdin.emit("error", new Error("test error"))
-			})
-
-			await readStdinIfPiped()
-
-			// Note: Implementation uses removeAllListeners() without event names
-			// which should remove all listeners, but in practice there may be one remaining
-			// This is acceptable behavior for error handling
-			expect(mockStdin.listenerCount("data")).toBeLessThanOrEqual(1)
-			expect(mockStdin.listenerCount("end")).toBeLessThanOrEqual(1)
-			expect(mockStdin.listenerCount("error")).toBeLessThanOrEqual(1)
-		})
-	})
-
-	describe("listener cleanup", () => {
-		it("should remove all listeners on successful completion", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				mockStdin.emit("data", "test data")
-				mockStdin.emit("end")
-			})
-
-			await readStdinIfPiped()
-
-			// Note: Implementation doesn't explicitly clean up listeners on normal end,
-			// so some listeners may remain attached. This is acceptable for one-time use.
-			expect(mockStdin.listenerCount("data")).toBeLessThanOrEqual(1)
-			expect(mockStdin.listenerCount("end")).toBeLessThanOrEqual(1)
-			expect(mockStdin.listenerCount("error")).toBeLessThanOrEqual(1)
-		})
-
-		it("should remove all listeners on timeout", async () => {
-			mockStdin.isTTY = false
-
-			// Let it timeout
-			await readStdinIfPiped()
-
-			// Verify listeners are cleaned up
-			expect(mockStdin.listenerCount("data")).toBe(0)
-			expect(mockStdin.listenerCount("end")).toBe(0)
-			expect(mockStdin.listenerCount("error")).toBe(0)
-		})
-
-		it("should clear timeout when data ends normally", async () => {
-			mockStdin.isTTY = false
-			const clearTimeoutSpy = vi.spyOn(global, "clearTimeout")
-
-			setImmediate(() => {
-				mockStdin.emit("data", "test")
-				mockStdin.emit("end")
-			})
-
-			await readStdinIfPiped()
-
-			expect(clearTimeoutSpy).toHaveBeenCalled()
-		})
-
-		it("should clear timeout when error occurs", async () => {
-			mockStdin.isTTY = false
-			const clearTimeoutSpy = vi.spyOn(global, "clearTimeout")
-
-			setImmediate(() => {
-				mockStdin.emit("error", new Error("test"))
-			})
-
-			await readStdinIfPiped()
-
-			expect(clearTimeoutSpy).toHaveBeenCalled()
-		})
-	})
-
-	describe("encoding", () => {
-		it("should handle UTF-8 encoded data", async () => {
-			mockStdin.isTTY = false
-
-			setImmediate(() => {
-				// The function sets utf8 encoding
-				mockStdin.setEncoding("utf8")
-				mockStdin.emit("data", "UTF-8: café ☕")
-				mockStdin.emit("end")
-			})
-
-			const result = await readStdinIfPiped()
-			expect(result).toBe("UTF-8: café ☕")
-		})
-	})
-
-	describe("stdin resume", () => {
-		it("should call resume on stdin when not TTY", async () => {
-			mockStdin.isTTY = false
-			const resumeSpy = vi.spyOn(mockStdin, "resume")
-
-			setImmediate(() => {
-				mockStdin.emit("end")
-			})
-
-			await readStdinIfPiped()
-
-			expect(resumeSpy).toHaveBeenCalled()
-		})
-
-		it("should not call resume when TTY", async () => {
-			mockStdin.isTTY = true
-			const resumeSpy = vi.spyOn(mockStdin, "resume")
-
-			const result = await readStdinIfPiped()
-
-			expect(result).toBeNull()
-			expect(resumeSpy).not.toHaveBeenCalled()
-		})
-	})
-
-	describe("real-world use cases", () => {
-		interface UseCaseTest {
-			name: string
-			input: string
-			expected: string | null
-		}
-
-		const useCases: UseCaseTest[] = [
-			{
-				name: "git diff output",
-				input: "diff --git a/file.ts b/file.ts\nindex 123..456\n--- a/file.ts\n+++ b/file.ts",
-				expected: "diff --git a/file.ts b/file.ts\nindex 123..456\n--- a/file.ts\n+++ b/file.ts",
-			},
-			{
-				name: "curl JSON response",
-				input: '{"status": "ok", "data": [1, 2, 3]}',
-				expected: '{"status": "ok", "data": [1, 2, 3]}',
-			},
-			{
-				name: "cat file contents",
-				input: "export function test() {\n  return true\n}",
-				expected: "export function test() {\n  return true\n}",
-			},
-			{
-				name: "echo command with newline",
-				input: "Hello World\n",
-				expected: "Hello World",
-			},
-			{
-				name: "command output with ANSI codes",
-				input: "\x1b[32mSUCCESS\x1b[0m",
-				expected: "\x1b[32mSUCCESS\x1b[0m",
-			},
-		]
-
-		useCases.forEach(({ name, input, expected }) => {
-			it(`should handle ${name}`, async () => {
-				mockStdin.isTTY = false
-
-				setImmediate(() => {
-					mockStdin.push(input)
-					mockStdin.push(null)
-				})
-
-				const result = await readStdinIfPiped()
-				expect(result).toBe(expected)
-			})
-		})
-	})
-})

cli-ts/src/utils/piped.ts

@@ -1,47 +0,0 @@
-import * as fs from "node:fs"
-
-/**
- * Read piped input from stdin (non-blocking)
- */
-export async function readStdinIfPiped(): Promise<string | null> {
-	// Check if stdin is a TTY (interactive) or piped
-	if (process.stdin.isTTY) {
-		return null
-	}
-
-	try {
-		// Use synchronous read for reliability with piped input
-		// fd 0 is stdin
-		const data = fs.readFileSync(0, "utf8")
-		return data.trim() || null
-	} catch {
-		// Fallback to async approach if sync read fails
-		return new Promise((resolve) => {
-			let data = ""
-			process.stdin.setEncoding("utf8")
-
-			// Set a timeout in case stdin is not actually providing data
-			const timeout = setTimeout(() => {
-				process.stdin.removeAllListeners()
-				resolve(data.trim() || null)
-			}, 1000)
-
-			process.stdin.on("data", (chunk) => {
-				data += chunk
-			})
-
-			process.stdin.on("end", () => {
-				clearTimeout(timeout)
-				resolve(data.trim() || null)
-			})
-
-			process.stdin.on("error", () => {
-				clearTimeout(timeout)
-				resolve(null)
-			})
-
-			// Resume stdin in case it's paused
-			process.stdin.resume()
-		})
-	}
-}

cli-ts/src/utils/plain-text-task.ts

@@ -1,225 +0,0 @@
-/**
- * Plain-text task runner for non-TTY environments (piped output, file redirection)
- * Outputs clean text without ANSI codes or Ink rendering
- */
-
-/* eslint-disable no-console */
-// Console output is intentional here for plain text mode
-
-import { registerPartialMessageCallback } from "@core/controller/ui/subscribeToPartialMessage"
-import type { ClineMessage } from "@shared/ExtensionMessage"
-import type { Controller } from "@/core/controller"
-import { setTerminalTitle } from "./display"
-
-export interface PlainTextTaskOptions {
-	controller: Controller
-	prompt: string
-	imageDataUrls?: string[]
-	verbose?: boolean
-	jsonOutput?: boolean
-}
-
-/**
- * Run a task with plain text output (no Ink, no ANSI codes)
- * Returns true if task completed successfully, false if error
- */
-export async function runPlainTextTask(options: PlainTextTaskOptions): Promise<boolean> {
-	const { controller, prompt, imageDataUrls, verbose, jsonOutput } = options
-
-	// Track completion state
-	let isComplete = false
-	let hasError = false
-	const processedMessages = new Map<number, number>() // index -> last output text length
-	let lastStreamingMessageIndex = -1 // track open streaming line that needs closing
-
-	// Subscribe to state updates
-	const originalPostState = controller.postStateToWebview.bind(controller)
-
-	const handleStateUpdate = async () => {
-		try {
-			const state = await controller.getStateToPostToWebview()
-			const messages = state.clineMessages || []
-
-			// Process new messages
-			for (let i = 0; i < messages.length; i++) {
-				const message = messages[i]
-				const currentTextLength = message.text?.length ?? 0
-				const lastOutputLength = processedMessages.get(i) ?? 0
-
-				// Skip if no new content to output
-				if (currentTextLength <= lastOutputLength) continue
-
-				// Close previous streaming line if we're moving to a different message
-				if (lastStreamingMessageIndex >= 0 && lastStreamingMessageIndex !== i && !jsonOutput) {
-					process.stdout.write("\n")
-					lastStreamingMessageIndex = -1
-				}
-
-				processedMessages.set(i, currentTextLength)
-
-				// Output the message
-				if (jsonOutput) {
-					process.stdout.write(JSON.stringify(message) + "\n")
-				} else {
-					const isStreaming = outputMessageAsText(message, verbose || false, lastOutputLength)
-					// Track streaming state for text messages
-					if (isStreaming) {
-						lastStreamingMessageIndex = i
-					} else {
-						lastStreamingMessageIndex = -1
-					}
-				}
-
-				// Check for completion
-				if (
-					message.say === "completion_result" ||
-					message.ask === "completion_result" ||
-					message.say === "error" ||
-					message.ask === "api_req_failed"
-				) {
-					isComplete = true
-					if (message.say === "error" || message.ask === "api_req_failed") {
-						hasError = true
-					}
-				}
-			}
-
-			// Close streaming line on completion
-			if (isComplete && lastStreamingMessageIndex >= 0 && !jsonOutput) {
-				process.stdout.write("\n")
-				lastStreamingMessageIndex = -1
-			}
-		} catch (error) {
-			if (jsonOutput) {
-				process.stdout.write(
-					JSON.stringify({ type: "error", message: error instanceof Error ? error.message : String(error) }) + "\n",
-				)
-			} else {
-				process.stderr.write(`Error: ${error instanceof Error ? error.message : String(error)}` + "\n")
-			}
-			hasError = true
-			isComplete = true
-		}
-	}
-
-	// Override postStateToWebview to capture state updates
-	controller.postStateToWebview = async () => {
-		await originalPostState()
-		await handleStateUpdate()
-	}
-
-	// Subscribe to partial message updates (for streaming)
-	const unsubscribePartial = registerPartialMessageCallback(() => {
-		// Partial updates are handled via postStateToWebview
-	})
-
-	try {
-		// Get initial state
-		await handleStateUpdate()
-
-		// Set terminal title to the task prompt
-		setTerminalTitle(prompt)
-
-		// Start the task
-		await controller.initTask(prompt, imageDataUrls)
-
-		// Wait for completion with timeout
-		const timeout = 10 * 60 * 1000 // 10 minutes
-		const startTime = Date.now()
-
-		while (!isComplete && Date.now() - startTime < timeout) {
-			await new Promise((resolve) => setTimeout(resolve, 100))
-		}
-
-		if (!isComplete) {
-			// Close any open streaming line before error message
-			if (lastStreamingMessageIndex >= 0 && !jsonOutput) {
-				process.stdout.write("\n")
-				lastStreamingMessageIndex = -1
-			}
-			if (jsonOutput) {
-				process.stdout.write(JSON.stringify({ type: "error", message: "Task timeout" }) + "\n")
-			} else {
-				process.stderr.write("Error: Task timeout" + "\n")
-			}
-			hasError = true
-		}
-	} catch (error) {
-		if (jsonOutput) {
-			process.stdout.write(
-				JSON.stringify({ type: "error", message: error instanceof Error ? error.message : String(error) }) + "\n",
-			)
-		} else {
-			process.stderr.write(`Error: ${error instanceof Error ? error.message : String(error)}` + "\n")
-		}
-		hasError = true
-	} finally {
-		// Close any open streaming line
-		if (lastStreamingMessageIndex >= 0 && !jsonOutput) {
-			process.stdout.write("\n")
-		}
-		// Restore original postStateToWebview
-		controller.postStateToWebview = originalPostState
-		unsubscribePartial()
-	}
-
-	return !hasError
-}
-
-/**
- * Format a Cline message as plain text
- * @param previousLength - Length of text already output for this message (for streaming)
- * @returns true if this is a streaming message (caller should track for newline), false otherwise
- */
-function outputMessageAsText(message: ClineMessage, verbose: boolean, previousLength: number = 0): boolean {
-	const timestamp = new Date(message.ts || Date.now()).toLocaleTimeString()
-	const fullText = message.text ?? ""
-
-	if (!fullText) {
-		// Skip partial messages without text
-		return false
-	}
-
-	// For streaming text continuations, output only new content
-	if (previousLength > 0 && message.type === "say" && message.say === "text") {
-		process.stdout.write(fullText.slice(previousLength))
-		return true // Still streaming
-	}
-
-	if (message.type === "say") {
-		if (message.say === "task") {
-			process.stdout.write(`[${timestamp}] Task: ${fullText}\n`)
-		} else if (message.say === "text") {
-			// First output of text message - write prefix but no newline (streaming)
-			process.stdout.write(`[${timestamp}] ${fullText}`)
-			return true // Streaming - newline will be added when stream ends
-		} else if (message.say === "completion_result" && fullText) {
-			process.stdout.write(`[${timestamp}] Completed: ${fullText}\n`)
-		} else if (message.say === "error") {
-			process.stderr.write(`[${timestamp}] Error: ${fullText}\n`)
-		} else if (message.say === "api_req_started") {
-			if (verbose) {
-				process.stdout.write(`[${timestamp}] API request started\n`)
-			}
-		} else if (message.say === "api_req_finished") {
-			if (verbose) {
-				process.stdout.write(`[${timestamp}] API request finished\n`)
-			}
-		} else if (verbose) {
-			process.stdout.write(`[${timestamp}] ${message.say}: ${fullText}\n`)
-		}
-	} else if (message.type === "ask") {
-		if (message.ask === "completion_result") {
-			process.stdout.write(`[${timestamp}] Task completed\n`)
-		} else if (message.ask === "api_req_failed") {
-			process.stderr.write(`[${timestamp}] API request failed: ${fullText}\n`)
-		} else if (message.ask === "tool" || message.ask === "command" || message.ask === "browser_action_launch") {
-			// These require approval - in non-interactive mode, warn the user
-			process.stderr.write(`[${timestamp}] Waiting for approval (use --yolo for auto-approve): ${message.ask}\n`)
-		} else if (verbose) {
-			process.stdout.write(`[${timestamp}] Question: ${fullText}\n`)
-		}
-	}
-
-	return false
-}

cli-ts/src/utils/provider-config.ts

@@ -1,63 +0,0 @@
-/**
- * Shared utility for applying provider configuration
- * Used by both AuthView (onboarding) and SettingsPanelContent (settings)
- */
-
-import { ProviderToApiKeyMap } from "@shared/storage"
-import { buildApiHandler } from "@/core/api"
-import type { Controller } from "@/core/controller"
-import { StateManager } from "@/core/storage/StateManager"
-import { getDefaultModelId } from "../components/ModelPicker"
-
-export interface ApplyProviderConfigOptions {
-	providerId: string
-	apiKey?: string
-	modelId?: string // Override default model
-	baseUrl?: string // For OpenAI-compatible providers
-	controller?: Controller
-}
-
-/**
- * Apply provider configuration to state and rebuild API handler if needed
- */
-export async function applyProviderConfig(options: ApplyProviderConfigOptions): Promise<void> {
-	const { providerId, apiKey, modelId, baseUrl, controller } = options
-	const stateManager = StateManager.get()
-
-	const config: Record<string, string> = {
-		actModeApiProvider: providerId,
-		planModeApiProvider: providerId,
-	}
-
-	// Add model ID (use provided or fall back to default)
-	const finalModelId = modelId || getDefaultModelId(providerId)
-	if (finalModelId) {
-		config.actModeApiModelId = finalModelId
-		config.planModeApiModelId = finalModelId
-	}
-
-	// Add API key if provided (maps to provider-specific field like anthropicApiKey, openAiApiKey, etc.)
-	if (apiKey) {
-		const keyField = ProviderToApiKeyMap[providerId as keyof typeof ProviderToApiKeyMap]
-		if (keyField) {
-			const fields = Array.isArray(keyField) ? keyField : [keyField]
-			config[fields[0]] = apiKey
-		}
-	}
-
-	// Add base URL if provided (for OpenAI-compatible providers)
-	if (baseUrl) {
-		config.openAiBaseUrl = baseUrl
-	}
-
-	// Save via StateManager
-	stateManager.setApiConfiguration(config)
-	await stateManager.flushPendingState()
-
-	// Rebuild API handler on active task if one exists
-	if (controller?.task) {
-		const currentMode = stateManager.getGlobalSettingsKey("mode")
-		const apiConfig = stateManager.getApiConfiguration()
-		controller.task.api = buildApiHandler({ ...apiConfig, ulid: controller.task.ulid }, currentMode)
-	}
-}

cli-ts/src/utils/update.ts

@@ -1,106 +0,0 @@
-import { spawn } from "node:child_process"
-import { exit } from "node:process"
-import { fetch } from "@/shared/net"
-import { printInfo, printWarning } from "./display"
-
-/**
- * Check for updates and install if available
- */
-export async function checkForUpdates(currentVersion: string, options?: { verbose?: boolean }) {
-	printInfo("Checking for updates...")
-
-	try {
-		// Fetch latest version from npm registry
-		const response = await fetch("https://registry.npmjs.org/cline/latest")
-		if (!response.ok && response.statusText !== "OK") {
-			printWarning(`Failed to check for updates: ${response.statusText}`)
-			exit(1)
-		}
-
-		const data = (await response.json()) as { version: string }
-		const latestVersion = data.version
-
-		if (options?.verbose) {
-			printInfo(`Current version: ${currentVersion}`)
-			printInfo(`Latest version: ${latestVersion}`)
-		}
-
-		// Compare versions
-		if (latestVersion === currentVersion) {
-			printInfo(`You are already on the latest version (${currentVersion})`)
-			exit(0)
-		}
-
-		// Check if current is newer (dev version)
-		if (compareVersions(currentVersion, latestVersion) > 0) {
-			printInfo(`You are already on a newer version ${currentVersion} (latest: ${latestVersion})`)
-			exit(0)
-		}
-
-		printInfo(`New version available: ${latestVersion} (current: ${currentVersion})`)
-		// Ask user to confirm update
-		const userConfirmed = new Promise<boolean>((resolve) => {
-			process.stdout.write("Do you want to update now? (y/N): ")
-			process.stdin.setEncoding("utf-8")
-			process.stdin.once("data", (dataBuff) => {
-				const input = dataBuff.toString().trim().toLowerCase()
-				resolve(input === "y" || input === "yes")
-			})
-		})
-
-		if (!(await userConfirmed)) {
-			exit(0)
-		}
-
-		printInfo("Installing update...")
-
-		// Run npm install -g cline@latest
-		const npmProcess = spawn("npm", ["install", "-g", "cline@latest"], {
-			stdio: "inherit",
-			shell: true,
-			// Ensures the process uses the same environment
-			env: process.env,
-			detached: false,
-			windowsHide: true,
-		})
-
-		npmProcess.on("close", (code) => {
-			if (code === 0) {
-				printInfo(`Successfully updated to version ${latestVersion}`)
-				exit(0)
-			} else {
-				printWarning("Update failed. Please try running: npm install -g cline@latest")
-				exit(1)
-			}
-		})
-
-		npmProcess.on("error", (err) => {
-			printWarning(`Failed to run npm install: ${err.message}`)
-			printInfo("Please try running manually: npm install -g cline@latest")
-			exit(1)
-		})
-	} catch (error) {
-		const message = error instanceof Error ? error.message : String(error)
-		printWarning(`Error checking for updates: ${message}`)
-		exit(1)
-	}
-}
-
-/**
- * Compare two semantic version strings
- * Returns: 1 if v1 > v2, -1 if v1 < v2, 0 if equal
- */
-function compareVersions(v1: string, v2: string): number {
-	const parts1 = v1.split(".").map(Number)
-	const parts2 = v2.split(".").map(Number)
-
-	for (let i = 0; i < Math.max(parts1.length, parts2.length); i++) {
-		const part1 = parts1[i] || 0
-		const part2 = parts2[i] || 0
-
-		if (part1 > part2) return 1
-		if (part1 < part2) return -1
-	}
-
-	return 0
-}

cli-ts/src/vscode-context.ts

@@ -1,194 +0,0 @@
-/**
- * VSCode context stub for CLI mode
- * Provides mock implementations of VSCode extension context
- */
-
-import { mkdirSync } from "node:fs"
-import os from "os"
-import path from "path"
-import { ExtensionRegistryInfo } from "@/registry"
-import { ClineExtensionContext } from "@/shared/cline"
-import { ClineFileStorage } from "@/shared/storage"
-import { EnvironmentVariableCollection, ExtensionKind, ExtensionMode, readJson, URI } from "./vscode-shim"
-
-const SETTINGS_SUBFOLDER = "data"
-
-/**
- * CLI-specific state overrides.
- * These values are always returned regardless of what's stored,
- * and writes to these keys are silently ignored.
- */
-const CLI_STATE_OVERRIDES: Record<string, any> = {
-	// CLI always uses background execution, not VSCode terminal
-	vscodeTerminalExecutionMode: "backgroundExec",
-	backgroundEditEnabled: true,
-	multiRootEnabled: false,
-	enableCheckpointsSetting: false,
-	browserSettings: {
-		disableToolUse: true,
-	},
-}
-
-/**
- * File-based Memento store with optional key overrides.
- * Implements VSCode's Memento interface using SyncJsonFileStorage.
- */
-class MementoStore extends ClineFileStorage {
-	private overrides: Record<string, any>
-
-	constructor(filePath: string, overrides: Record<string, any> = {}) {
-		super(filePath, "MementoStore")
-		this.overrides = overrides
-	}
-
-	// VSCode Memento interface - override base class get() with overload support
-	override get<T>(key: string): T | undefined
-	override get<T>(key: string, defaultValue: T): T
-	override get<T>(key: string, defaultValue?: T): T | undefined {
-		if (key in this.overrides) {
-			return this.overrides[key] as T
-		}
-		const value = super.get<T>(key)
-		return value !== undefined ? value : defaultValue
-	}
-
-	override async update(key: string, value: any): Promise<void> {
-		if (key in this.overrides) {
-			return
-		}
-		this.set(key, value)
-	}
-
-	setKeysForSync(_keys: readonly string[]): void {
-		// No-op for CLI
-	}
-}
-
-/**
- * File-based secret storage implementing VSCode's SecretStorage interface.
- * Uses sync storage internally but exposes async API for VSCode compatibility.
- */
-class SecretStore {
-	private storage: ClineFileStorage<string>
-	private onDidChangeEmitter = {
-		event: () => ({ dispose: () => {} }),
-		fire: (_e: any) => {},
-		dispose: () => {},
-	}
-
-	onDidChange = this.onDidChangeEmitter.event
-
-	constructor(filePath: string) {
-		this.storage = new ClineFileStorage<string>(filePath, "SecretStore")
-	}
-
-	get(key: string): Promise<string | undefined> {
-		return Promise.resolve(this.storage.get(key))
-	}
-
-	store(key: string, value: string): Promise<void> {
-		this.storage.set(key, value)
-		return Promise.resolve()
-	}
-
-	delete(key: string): Promise<void> {
-		this.storage.delete(key)
-		return Promise.resolve()
-	}
-}
-
-export interface CliContextConfig {
-	clineDir?: string
-	/** The workspace directory being worked in (for hashing into storage path) */
-	workspaceDir?: string
-}
-
-/**
- * Create a short hash of a string for use in directory names
- */
-function hashString(str: string): string {
-	let hash = 0
-	for (let i = 0; i < str.length; i++) {
-		const char = str.charCodeAt(i)
-		hash = (hash << 5) - hash + char
-		hash = hash & hash // Convert to 32bit integer
-	}
-	return Math.abs(hash).toString(16).substring(0, 8)
-}
-
-export interface CliContextResult {
-	extensionContext: ClineExtensionContext
-	DATA_DIR: string
-	EXTENSION_DIR: string
-	WORKSPACE_STORAGE_DIR: string
-}
-
-/**
- * Initialize the VSCode-like context for CLI mode
- */
-export function initializeCliContext(config: CliContextConfig = {}): CliContextResult {
-	const CLINE_DIR = config.clineDir || process.env.CLINE_DIR || path.join(os.homedir(), ".cline")
-	const DATA_DIR = path.join(CLINE_DIR, SETTINGS_SUBFOLDER)
-
-	// Workspace storage should always be under ~/.cline/data/workspaces/<hash>/
-	// where hash is derived from the workspace path to keep workspaces isolated
-	const workspacePath = config.workspaceDir || process.cwd()
-	const workspaceHash = hashString(workspacePath)
-	const WORKSPACE_STORAGE_DIR = process.env.WORKSPACE_STORAGE_DIR || path.join(DATA_DIR, "workspaces", workspaceHash)
-
-	// Ensure directories exist
-	mkdirSync(DATA_DIR, { recursive: true })
-	mkdirSync(WORKSPACE_STORAGE_DIR, { recursive: true })
-
-	// For CLI, extension dir is the root of the project (parent of cli-ts)
-	const EXTENSION_DIR = path.resolve(__dirname, "..", "..")
-	const EXTENSION_MODE = process.env.IS_DEV === "true" ? ExtensionMode.Development : ExtensionMode.Production
-
-	const extension: ClineExtensionContext["extension"] = {
-		id: ExtensionRegistryInfo.id,
-		isActive: true,
-		extensionPath: EXTENSION_DIR,
-		extensionUri: URI.file(EXTENSION_DIR),
-		packageJSON: readJson(path.join(EXTENSION_DIR, "package.json")),
-		exports: undefined,
-		activate: async () => {},
-		extensionKind: ExtensionKind.UI,
-	}
-
-	const extensionContext: ClineExtensionContext = {
-		extension: extension,
-		extensionMode: EXTENSION_MODE,
-
-		// Set up KV stores (globalState has CLI-specific overrides)
-		globalState: new MementoStore(path.join(DATA_DIR, "globalState.json"), CLI_STATE_OVERRIDES),
-		secrets: new SecretStore(path.join(DATA_DIR, "secrets.json")),
-
-		// Set up URIs
-		storageUri: URI.file(WORKSPACE_STORAGE_DIR),
-		storagePath: WORKSPACE_STORAGE_DIR,
-		globalStorageUri: URI.file(DATA_DIR),
-		globalStoragePath: DATA_DIR,
-
-		// Logs
-		logUri: URI.file(DATA_DIR),
-		logPath: DATA_DIR,
-
-		extensionUri: URI.file(EXTENSION_DIR),
-		extensionPath: EXTENSION_DIR,
-		asAbsolutePath: (relPath: string) => path.join(EXTENSION_DIR, relPath),
-
-		subscriptions: [],
-
-		environmentVariableCollection: new EnvironmentVariableCollection() as any,
-
-		// Workspace state
-		workspaceState: new MementoStore(path.join(WORKSPACE_STORAGE_DIR, "workspaceState.json")),
-	}
-
-	return {
-		extensionContext,
-		DATA_DIR,
-		EXTENSION_DIR,
-		WORKSPACE_STORAGE_DIR,
-	}
-}

cli/.gitignore

@@ -1,2 +0,0 @@
-cline-core-debug.log
-bin/*

cli/CHANGELOG.md

@@ -0,0 +1,256 @@
+# cline
+
+## [2.12.0]
+
+### Added
+
+- `read_file` tool now supports chunked reading for targeted file access
+
+### Fixed
+
+- Exclude `new_task` tool from system prompt in yolo/headless mode
+
+### Changed
+
+- Polish `Notification` hook functionality
+
+## [2.9.0]
+
+### Added
+
+- Latency improvements for remote workspaces
+
+## [2.8.2]
+
+### Fixed
+- Use `kanban@latest` in `cline kanban` to always fetch the newest version
+
+## [2.8.1]
+
+### 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
+- Fix flaky CLI Enter-key handling across Windows/test environments
+- 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
+
+## [2.8.0]
+
+### Added
+
+- Added W&B Inference by CoreWeave as a new API provider with 17 models including DeepSeek-V3.1, Llama 4, and Qwen3-Coder
+- Added CLI TUI end-to-end test suite
+
+### Fixed
+
+- Claude Code: handle rate limit events, empty content arrays, error results, and unknown content types without crashing
+- CLI: `/q` and `/exit` slash commands now execute immediately on Enter without requiring the slash menu to be visible
+- CLI: slash command filtering now prioritizes exact and prefix matches over fuzzy matches
+
+## [2.7.0]
+
+### Added
+
+- Added MCP add shortcuts for stdio and HTTP servers
+- Added `--continue` for the current directory
+- Added `--auto-condense` flag for AI-powered context compaction
+- Added `--hooks-dir` flag for runtime hook injection
+- Enabled error autocapture
+- Prompt rules now include test verification guidance and make `CLI_RULES` language-agnostic
+
+### Fixed
+
+- Fixed remount behavior so TUI remounts only on width resize
+- Fixed startup prompt replay on resize remount
+- Fixed task flags so they are applied before the welcome TUI mounts
+
+### Changed
+
+- Hooks: reintroduced feature toggle
+
+## [2.6.1]
+
+### Added
+
+- Added GPT-5.4 models for ChatGPT subscription users
+- Hooks: Added a `Notification` hook for attention and completion boundaries
+- Added `--hooks-dir` CLI flag for runtime hook injection
+- Added `--auto-approve-all` CLI flag for interactive mode
+
+### Fixed
+
+- Handle streamable HTTP MCP reconnects more reliably
+
+## [2.6.0]
+
+### Added
+
+- 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
+
+## [2.5.2]
+
+### Added
+
+- Added Windows PowerShell support for hooks (execution, resolution, and management), improving hook behavior on Windows for CLI and shared core workflows.
+
+### Fixed
+
+- Restored GPT-OSS native file editing for OpenAI-compatible models used through shared core tooling.
+- Improved OpenRouter context overflow error handling so auto-compaction triggers correctly for wrapped 400 errors.
+- Hardened checkpoint recovery by retrying nested git restore and preventing silent `.git_disabled` leftovers.
+- Added a User-Agent header for requests to the Cline back-end to improve request handling consistency.
+
+## [2.5.1]
+
+### Added
+
+- Expanded CLI markdown rendering support (headings, lists, blockquotes, fenced code blocks, links, and nested lists).
+
+### Fixed
+
+- Fixed CLI headless auth provider model metadata loading for Cline and Vercel AI Gateway by fetching model info from API with cache fallback.
+- Increased flaky CLI import test timeout on Windows CI to reduce intermittent test failures.
+
+## [2.5.0]
+
+### 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
+
+## [2.4.3]
+
+### Added
+
+- Add /q command to quit CLI
+- Fetch featured models from backend with local fallback
+
+### Fixed
+
+- Fix auth check for ACP mode
+- Fix Cline auth with ACP flag
+- Fix yolo mode to not persist yolo setting to disk
+
+## [2.4.2]
+
+### Added
+
+- Gemini-3.1 Pro Preview
+
+### Patch Changes
+
+- VSCode uses shared files for global, workspace and secret state.
+
+## [2.4.1]
+
+### Fixed
+
+- Fix infinite retry loop when write_to_file fails with missing content parameter. Provides progressive guidance to the model, escalating from suggestions to hard stops, with context window awareness to break the loop.
+
+## [2.4.0]
+
+### Added
+
+- Adding Anthropic Sonnet 4.6
+- Allows users to enter custom aws region when selecting bedrock as a provider in CLI
+- Keep reasoning rows visible when low-stakes tool groups start immediately after reasoning.
+- Restore reasoning trace visibility in chat and improve the thinking row UX so streamed reasoning is visible, then collapsible after completion.
+
+### 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)
+
+## [2.2.2]
+
+- Allows users to enter custom aws region when selecting bedrock as a provider
+- Prevent Parent Container Scrolling In Dropdowns
+
+## [2.2.1]
+
+- Added Minimax 2.5 Free Promo
+- Fixed Response chaining for OpenAI's Responses API
+
+## [2.2.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
+
+## [2.1.0]
+
+### Minor Changes
+
+- 42ce100: Add Generate API Key on Hicap Provider selection
+
+### Patch Changes
+
+- 195294f: Add support for bundled endpoints.json in enterprise distributions. Extensions can now include a pre-configured endpoints.json file that automatically switches Cline to self-hosted mode. Includes packaging scripts for VSIX, NPM, and JetBrains plugins.
+- a1f2601: Replace the LiteLLM model list with a selector
+- 739d75a: Add Claude Code provider support for Claude Opus 4.6 and Sonnet 4.5 1M variants via both full model names and aliases (`opus[1m]`, `sonnet[1m]`), and align the `opus` alias with Opus 4.6.
+- 8440380: Add GitHub Actions workflow to build CLI from any commit for testing
+- b1a8db2: fix(cli): prevent hang when spawned without TTY
+- 7c87017: Add Claude Opus 4.6 model support
+- d116ac5: Supports rendering markdown table in chat view.
+- 6d8fb85: Fix CLI crashing in CI environments and with stdin redirection (e.g., `cline "prompt" < /dev/null`). Now checks both stdin and stdout TTY status before using Ink, and only errors on empty stdin when no prompt is provided.
+- 70a9904: Fix JetBrains sign-in regression by adding fallback for openExternal RPC
+- f440f3a: fix: use vscode.env.openExternal for auth in remote environments
+
+  Fixes OAuth authentication in VS Code Server and remote environments by routing browser URL opening through VS Code's native openExternal API instead of the npm 'open' package.
+
+- 70a9904: fix: use vscode.env.asExternalUri for auth callback URLs only in VS Code Web
+
+  Fixes OAuth callback redirect in VS Code Web (`code serve-web`, Codespaces) by using `vscode.env.asExternalUri()` to resolve the callback URI. This is gated behind a `vscode.env.uiKind === UIKind.Web` check so regular desktop VS Code continues to use the `vscode://` URI directly. The `getCallbackUrl` API now accepts a `path` parameter so the full callback URI (including route) is resolved correctly, and callers pass their path directly instead of appending after.
+
+- 5308ded: Updating script documentation and removing unnecessary continue on error
+- b514f18: Prevent duplicate streamed text rows when a partial text update arrives after the same text was already finalized.
+- 26391c9: Fix Bedrock model id
+- d19a877: Unify ViewHeader Styles Across All Views
+- 5dcaa8c: Add Vertex Claude Opus 4.6 1M model option and global endpoint support, and pass the 1M beta header for Vertex Claude requests.

cli/DEVELOPMENT.md

@@ -1,6 +1,6 @@
-# Cline CLI (TypeScript)
+# Cline CLI
 
-A TypeScript CLI implementation of Cline that reuses the core TypeScript codebase. This allows you to run Cline tasks directly from the terminal while sharing the same underlying functionality as the VS Code extension.
+The official CLI for Cline. Run Cline tasks directly from the terminal with the same underlying functionality as the VS Code extension.
 
 ## Features
 
@@ -27,23 +27,8 @@ npm run install:all
 # Ensure protos are generated
 npm run protos
 
-# Build the CLI
-npm run build:cli
-```
-
-Or install the CLI globally:
-
-```bash
-# Install all dependencies first
-npm run install:all
-
-# Ensure protos are generated
-npm run protos
-
 # Build and link the CLI globally
-cd cli-ts
-npm install
-npm run link
+npm run cli:link
 ```
 
 ## Usage
@@ -203,54 +188,51 @@ These options are available for the default command (running a task directly):
 
 ## Development
 
-For active development, at the root of this repo:
-
-1. **Initial setup:**
-   ```bash
-   npm run install:all
-   npm run protos
-   ```
-
-2. **Make changes to cli-ts:**
-   ```bash
-   npm run cli:dev 
-   # or
-   cd cli-ts && npm run dev
-   ```
-
-3. **Test your changes:**
-   ```bash
-   cline [your-command] # In a new Terminal
-   ```
-
-4. **When done:**
-   ```bash
-   npm run cli:unlink
-   ```
-
-### Build
+### Quick Start
 
 ```bash
-cd cli-ts
+# 1. Install all dependencies (root, webview-ui, cli)
+npm run install:all
 
-# Development build with source maps
-npm run build
+# 2. Build and link globally so you can run `cline` from anywhere
+npm run cli:link
 
-# Production build (minified)
-npm run build:production
+# 3. Test it
+cline --help
 ```
 
-### Watch Mode
+### Scripts
+
+Run these from the repository root:
+
+| Script | Description |
+|--------|-------------|
+| `npm run install:all` | Install deps for root, webview-ui, and cli |
+| `npm run cli:build` | Generate protos and build CLI |
+| `npm run cli:build:production` | Production build (minified) |
+| `npm run cli:link` | Build and `npm link` so you can run `cline` from anywhere |
+| `npm run cli:unlink` | Remove the global `cline` symlink |
+| `npm run cli:dev` | Link + watch mode for development |
+| `npm run cli:watch` | Watch mode only (no initial build) |
+| `npm run cli:test` | Run CLI tests |
+
+### Development Workflow
+
+1. Run `npm run cli:dev` - this links the CLI globally and starts watch mode
+2. Make changes to files in `cli/src/`
+3. The build automatically rebuilds on save
+4. Test your changes by running `cline` in another terminal
+5. When done, run `npm run cli:unlink` to clean up
+
+### Proto Generation
+
+The CLI uses proto-generated types for message passing (same as the VS Code extension). If you modify any `.proto` files, run:
 
 ```bash
-npm run watch
+npm run protos
 ```
 
-### Type Checking
-
-```bash
-npm run typecheck
-```
+This generates TypeScript types in `src/generated/` that both the CLI and extension use.
 
 ## Publish
 
@@ -268,7 +250,7 @@ npm run update-brew-formula
 ```bash
 # Create a local tap
 brew tap-new cline/local
-cp ./cli-ts/cline.rb "$(brew --repository)/Library/Taps/cline/homebrew-local/Formula/cline.rb"
+cp ./cli/cline.rb "$(brew --repository)/Library/Taps/cline/homebrew-local/Formula/cline.rb"
 
 # Build from Source
 brew install --build-from-source cline/local/cline
@@ -289,19 +271,50 @@ git push
 
 ## Architecture
 
-The CLI reuses the core Cline TypeScript codebase:
+### How It Works
 
-- **Controller** (`@core/controller`): Manages task lifecycle and state
-- **Task** (`@core/task`): Executes Cline tasks using the AI API
-- **StateManager** (`@core/storage`): Handles persistent state storage
+The CLI directly imports and reuses the core Cline TypeScript codebase (the same code that powers the VS Code extension). This means feature parity is easy to maintain - when core gets updated, the CLI automatically benefits.
 
-CLI-specific implementations:
+```
+┌─────────────────────────────────────────────────────────┐
+│                     CLI (cli/)                          │
+│  - React Ink terminal UI                                │
+│  - Command parsing (commander)                          │
+│  - Terminal-specific adapters                           │
+└─────────────────────────────────────────────────────────┘
+                          │
+                          │ direct imports
+                          ▼
+┌─────────────────────────────────────────────────────────┐
+│                  Core (src/core/)                       │
+│  - Controller: task lifecycle, state management         │
+│  - Task: AI API calls, tool execution                   │
+│  - StateManager: persistent storage                     │
+│  - Proto types: message definitions                     │
+└─────────────────────────────────────────────────────────┘
+```
 
-- `cli-host-bridge.ts`: CLI implementations of host bridge services
-- `cli-webview-provider.ts`: WebviewProvider that outputs to terminal
-- `cli-comment-review.ts`: Comment review controller for terminal
-- `vscode-context.ts`: Mock VSCode extension context
-- `display.ts`: Terminal output formatting utilities
+Unlike a client-server architecture, the CLI runs everything in a single Node.js process. The "host bridge" pattern provides terminal-appropriate implementations for things the VS Code extension would handle differently (clipboard, file dialogs, etc.).
+
+### Key Files
+
+| File | Purpose |
+|------|---------|
+| `src/index.ts` | Entry point, command definitions |
+| `src/components/App.tsx` | Main React Ink app |
+| `src/components/ChatView.tsx` | Task conversation UI |
+| `src/controllers/CliWebviewProvider.ts` | Bridges core messages to terminal output |
+| `src/vscode-context.ts` | Mock VS Code extension context for core compatibility |
+| `src/vscode-shim.ts` | Shims for VS Code APIs that core depends on |
+| `src/constants/colors.ts` | Terminal color definitions |
+
+### React Ink
+
+The CLI uses [React Ink](https://github.com/vadimdemedes/ink) for its terminal UI. This lets us build the interface with React components that render to the terminal. Key patterns:
+
+- Components in `src/components/` render terminal UI
+- Hooks in `src/hooks/` manage terminal-specific state (size, scrolling)
+- The `useStateSubscriber` hook subscribes to core state changes
 
 ## Configuration
 
@@ -314,41 +327,39 @@ The CLI stores its data in `~/.cline/data/` by default:
 
 Override with the `--config` option or `CLINE_DIR` environment variable.
 
-## Comparison with Go CLI
-
-This TypeScript CLI differs from the Go CLI (`cli/` directory):
-
-| Feature | Go CLI | TypeScript CLI |
-|---------|--------|----------------|
-| Language | Go | TypeScript |
-| Core sharing | Uses gRPC to communicate | Direct imports |
-| Startup time | Fast | Moderate |
-| Dependencies | Standalone binary | Requires Node.js |
-| Best for | Production deployment | Development, debugging |
-
-Choose the TypeScript CLI when you need to debug or modify the core Cline logic. Choose the Go CLI for production deployment with faster startup.
-
 ## Troubleshooting
 
 ### Build Errors
 
-If you encounter build errors, ensure you've:
-1. Run `npm install` in the repository root
-2. Run `npm run protos` to generate proto files
-3. Have all peer dependencies installed
+If you encounter build errors:
 
-### Missing Dependencies
-
-The CLI imports from the parent project. If you see import errors:
 ```bash
-cd ..  # Go to repository root
-npm install
+# Make sure all deps are installed
+npm run install:all
+
+# Regenerate proto types
 npm run protos
+
+# Then rebuild
+npm run cli:build
 ```
 
-### Permission Denied
+### "command not found: cline"
+
+The CLI isn't linked globally. Run:
 
-Make the CLI executable:
 ```bash
-chmod +x dist/cli.js
-```
+npm run cli:link
+```
+
+### Changes Not Reflected
+
+If your code changes aren't showing up:
+
+1. Make sure watch mode is running (`npm run cli:dev`)
+2. Check for TypeScript errors in the watch output
+3. Try unlinking and relinking: `npm run cli:unlink && npm run cli:link`
+
+### Import Errors from Core
+
+The CLI imports from `@core/`, `@shared/`, etc. These paths are defined in the root `tsconfig.json`. If you see import errors, make sure you're building from the repo root, not from inside `cli/`.

cli/README.md

@@ -1,73 +1,81 @@
-# Cline CLI
+# Cline
 
-```
-/_____/\ /_/\      /_______/\/__/\ /__/\ /_____/\
-\:::__\/ \:\ \     \__.::._\/\::\_\\  \ \\::::_\/_
- \:\ \  __\:\ \       \::\ \  \:. `-\  \ \\:\/___/\
-  \:\ \/_/\\:\ \____  _\::\ \__\:. _    \ \\::___\/_
-   \:\_\ \ \\:\/___/\/__\::\__/\\. \`-\  \ \\:\____/\
-    \_____\/ \_____\/\________\/ \__\/ \__\/ \_____\/
-```
+<p align="center">
+  <img src="https://github.com/user-attachments/assets/7123f9d1-afeb-48d5-93fa-e750dec0ebba" width="70%" />
+</p>
 
-Autonomous coding agent CLI - capable of creating/editing files, running commands, using the browser, and more.
+<div align="center">
+<table>
+<tbody>
+<td align="center">
+<a href="https://www.npmjs.com/package/cline" target="_blank"><strong>NPM</strong></a>
+</td>
+<td align="center">
+<a href="https://discord.gg/cline" target="_blank"><strong>Discord</strong></a>
+</td>
+<td align="center">
+<a href="https://www.reddit.com/r/cline/" target="_blank"><strong>r/cline</strong></a>
+</td>
+<td align="center">
+<a href="https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop" target="_blank"><strong>Feature Requests</strong></a>
+</td>
+<td align="center">
+<a href="https://docs.cline.bot/getting-started/for-new-coders" target="_blank"><strong>Getting Started</strong></a>
+</td>
+</tbody>
+</table>
+</div>
 
-## Installation
+Meet Cline, an AI assistant that lives in your terminal.
 
-Install Cline globally using npm:
+Cline can handle complex software development tasks step-by-step. With tools that let him create & edit files, explore large projects, use the browser, and execute terminal commands (after you grant permission), he can assist you in ways that go beyond code completion or tech support.
 
 ```bash
-npm install -g cline
-```
+npm i -g cline
 
-## Usage
-
-```bash
+# cd into your project and run:
 cline
 ```
 
-This will start the Cline CLI interface where you can interact with the autonomous coding agent.
+> Move your mouse around under the Cline icon for a surprise!
 
-## Features
+---
 
--   **Autonomous Coding**: AI-powered code generation, editing, and refactoring
--   **File Operations**: Create, read, update, and delete files and directories
--   **Command Execution**: Run shell commands and scripts
--   **Browser Automation**: Interact with web pages and applications
--   **Multi-Model Support**: Works with Anthropic Claude, OpenAI GPT, and other AI models
--   **MCP Integration**: Extensible through Model Context Protocol servers
--   **Project Understanding**: Analyzes codebases to provide context-aware assistance
+<img align="right" width="340" src="https://github.com/user-attachments/assets/ceb74224-08aa-4b8b-a3e7-b438ac3d160a">
 
-## Requirements
+### Use any API and Model
 
--   Node.js 18.0.0 or higher
--   Supported platforms: macOS, Linux. Windows soon
--   Supported architectures: x64, arm64
+Cline supports API providers like ChatGPT, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure, GCP Vertex, Cerebras, Groq, and Moonshot. You can also configure any OpenAI compatible API, or use a local model through LM Studio/Ollama. If you're using a Cline Account, you'll always have access to the newest models as soon as they're available.
 
-## Configuration
+<!-- Transparent pixel to create line break after floating image -->
 
-Cline can be configured through:
+<img width="2000" height="0" src="https://github.com/user-attachments/assets/ee14e6f7-20b8-4391-9091-8e8e25561929"><br>
 
--   Environment variables
--   Configuration files
--   Command-line arguments
+<img align="left" width="370" src="https://github.com/user-attachments/assets/cad091f6-6c0f-4e4b-97ea-a1ff67e39b9b">
 
-See the [main documentation](https://cline.bot) for detailed configuration options.
+### Stay in Control with Human-in-the-Loop
 
-## Links
+Cline asks for your approval before running commands, editing files, or taking any action. Review each step and approve or reject as you go—or enable auto-approve to let Cline work autonomously to completion.
 
--   **Website**: [https://cline.bot](https://cline.bot)
--   **Documentation**: [https://docs.cline.bot](https://docs.cline.bot)
--   **GitHub**: [https://github.com/cline/cline](https://github.com/cline/cline)
--   **VSCode Extension**: Available in the VSCode Marketplace
--   **JetBrains Extension**: Available in the JetBrains Marketplace
+<!-- Transparent pixel to create line break after floating image -->
+
+<img width="2000" height="0" src="https://github.com/user-attachments/assets/cad091f6-6c0f-4e4b-97ea-a1ff67e39b9b"><br>
+
+<img align="right" width="400" src="https://github.com/user-attachments/assets/4f264a0c-3802-49a7-8e5e-13d97beb659e">
+
+### Plan & Act Modes
+
+Toggle to Plan Mode to discuss implementation and architecture with Cline. He'll ask clarifying questions, explore your codebase, and present a plan for you to align on. Once you're satisfied, switch to Act Mode and let Cline execute the plan.
+
+<!-- Transparent pixel to create line break after floating image -->
+
+<img width="2000" height="0" src="https://github.com/user-attachments/assets/4f264a0c-3802-49a7-8e5e-13d97beb659e"><br>
+
+
+## Enterprise
+
+Get the same Cline experience with enterprise-grade controls: SSO (SAML/OIDC), global policies and configuration, observability with audit trails, private networking (VPC/private link), and self-hosted or on-prem deployments, and enterprise support. Learn more at our [enterprise page](https://cline.bot/enterprise) or [talk to us](https://cline.bot/contact-sales).
 
 ## License
 
-Apache-2.0 - see [LICENSE](https://github.com/cline/cline/blob/main/LICENSE) for details.
-
-## Support
-
--   Report issues: [GitHub Issues](https://github.com/cline/cline/issues)
--   Community: [GitHub Discussions](https://github.com/cline/cline/discussions)
--   Documentation: [docs.cline.bot](https://docs.cline.bot)
--   Cline CLI Architecture: [architecture.md](./architecture.md)
+[Apache 2.0 © 2026 Cline Bot Inc.](./LICENSE)

cli/architecture.md

@@ -1,292 +0,0 @@
-# Cline CLI Architecture
-
-The CLI is a **standalone terminal interface** for the Cline AI coding assistant, written in Go. It provides the same autonomous coding capabilities as the VS Code extension but runs entirely in the terminal.
-
-## High-Level Architecture
-
-```
-┌─────────────────────────────────────────────────────────────────────────┐
-│                           User Terminal                                 │
-└─────────────────────────────────────────────────────────────────────────┘
-                                    │
-                                    ▼
-┌─────────────────────────────────────────────────────────────────────────┐
-│                         cline (Go binary)                               │
-│                         cmd/cline/main.go                               │
-│   • Cobra CLI commands (task, auth, config, instance, etc.)             │
-│   • Interactive input via Bubble Tea                                    │
-│   • Streaming output with markdown rendering                            │
-└─────────────────────────────────────────────────────────────────────────┘
-          │ gRPC (50052)                                │ starts subprocess
-          ▼                                             ▼
-┌─────────────────────────┐                  ┌─────────────────────────┐
-│      cline-core         │◄────────────────►│      cline-host         │
-│      (Node.js)          │   gRPC (51052)   │      (Go binary)        │
-│                         │                  │   cmd/cline-host/main.go│
-│  • AI/LLM orchestration │                  │                         │
-│  • Tool execution       │                  │  • Workspace paths      │
-│  • Task state mgmt      │                  │  • File diff editing    │
-│  • Message handling     │                  │  • Clipboard access     │
-└─────────────────────────┘                  │  • Environment info     │
-          │                                  └─────────────────────────┘
-          │ SQLite (self-registration)
-          ▼
-┌─────────────────────────────────────────────────────────────────────────┐
-│                   ~/.cline/data/locks/locks.db                          │
-│            (Instance registry - core self-registers on startup)         │
-└─────────────────────────────────────────────────────────────────────────┘
-```
-
-## Entry Points (`cmd/`)
-
-### `cmd/cline/main.go` - Main CLI
-
-Cobra-based CLI with commands:
-
-- **Root**: `cline [prompt]` - Start a task directly
-- **task**: Create, send, view, list, pause, restore tasks
-- **auth**: Authentication setup and provider configuration
-- **config**: Read/write settings
-- **instance**: Manage running Cline instances
-- **logs**: View and clean log files
-- **doctor**: System health check
-
-### `cmd/cline-host/main.go` - Host Bridge Service
-
-Separate gRPC server providing host environment operations to cline-core:
-
-- Workspace paths
-- File diff editing
-- Clipboard access
-- Shutdown coordination
-
----
-
-## `pkg/cli/` Subsystems
-
-### 1. `auth/` - Authentication System
-
-Handles authentication with Cline service and BYO (Bring Your Own) API providers.
-
-| File                      | Purpose                                                                  |
-| ------------------------- | ------------------------------------------------------------------------ |
-| `auth_cline_provider.go`  | OAuth login flow - opens browser, subscribes to auth callback stream     |
-| `auth_menu.go`            | Interactive menu showing auth options based on current state             |
-| `auth_subscription.go`    | gRPC stream subscription for auth status updates                         |
-| `wizard_byo.go`           | Interactive wizard for configuring BYO providers                         |
-| `wizard_byo_bedrock.go`   | AWS Bedrock-specific credential setup                                    |
-| `wizard_byo_oca.go`       | Oracle Code Assist setup                                                 |
-| `providers_list.go`       | Retrieves configured providers from core state                           |
-| `providers_byo.go`        | Provider selection UI and field configuration                            |
-| `models_*.go`             | Model listing (static lists + dynamic fetch from OpenRouter/OpenAI/Ollama) |
-
-**Flow**: User runs `cline auth` → Menu shows options → For BYO: wizard guides through provider/key/model selection → Config saved via gRPC to core.
-
----
-
-### 2. `clerror/` - Error Handling
-
-Parses and classifies API errors from the Cline service.
-
-**Error Types:**
-
-- `ErrorTypeAuth` - 401, bad API key
-- `ErrorTypeBalance` - Insufficient credits
-- `ErrorTypeRateLimit` - 429, quota exceeded
-- `ErrorTypeNetwork` - Connection issues
-- `ErrorTypeUnknown` - Catch-all
-
-Extracts billing details (balance, spent, buy credits URL) from error responses.
-
----
-
-### 3. `config/` - Configuration Management
-
-| File                  | Purpose                                                                    |
-| --------------------- | -------------------------------------------------------------------------- |
-| `manager.go`          | gRPC interface for reading/writing settings via `UpdateSettingsCli` RPC    |
-| `settings_renderer.go`| Pretty-prints config values, censors sensitive fields (keys, secrets)      |
-
-Supports dot-notation paths: `cline config get auto-approval-settings.actions.read-files`
-
----
-
-### 4. `display/` - Terminal Display System
-
-The most complex subsystem - handles all visual output.
-
-| File                    | Purpose                                                              |
-| ----------------------- | -------------------------------------------------------------------- |
-| `renderer.go`           | Central coordinator with lipgloss styles, color methods, markdown delegation |
-| `streaming.go`          | Real-time streaming display with deduplication                       |
-| `segment_streamer.go`   | Streaming segments (header + body) with context-aware headers        |
-| `typewriter.go`         | Character-by-character animation with variable delays                |
-| `markdown_renderer.go`  | Glamour wrapper for terminal markdown rendering                      |
-| `tool_renderer.go`      | Tool operation formatting ("Cline is editing `file.ts`")             |
-| `tool_result_parser.go` | Parses structured tool results (file lists, search results)          |
-| `banner.go`             | Session startup banner with version/model/workspace                  |
-| `deduplicator.go`       | MD5-based deduplication with 2-second window                         |
-| `system_renderer.go`    | Rich error/warning boxes for balance errors, auth failures           |
-| `ansi.go`               | TTY detection, line clearing with escape codes                       |
-
----
-
-### 5. `global/` - Global State Management
-
-| File               | Purpose                                                                    |
-| ------------------ | -------------------------------------------------------------------------- |
-| `global.go`        | Global config (paths, verbosity, output format), initialization            |
-| `registry.go`      | Instance discovery via SQLite, health checking, default instance management|
-| `cline-clients.go` | Starts cline-core + cline-host processes, port allocation, cleanup         |
-
-**Instance lifecycle:**
-
-1. Find available port pair
-2. Start `cline-host` on port+1000
-3. Start `cline-core` on port
-4. Wait for core to self-register in SQLite
-5. Set as default if first instance
-
----
-
-### 6. `handlers/` - Message Handlers
-
-Routes incoming messages from cline-core to appropriate renderers.
-
-| File               | Purpose                                                               |
-| ------------------ | --------------------------------------------------------------------- |
-| `handler.go`       | Handler registry with priority-based routing                          |
-| `ask_handlers.go`  | Approval requests: tool, command, followup, api_req_failed, etc.      |
-| `say_handlers.go`  | Status messages: text, reasoning, command_output, tool, checkpoint, etc. |
-
-Uses `DisplayContext` providing renderer access, state, and context flags (isLast, isPartial, isStreamingMode).
-
----
-
-### 7. `output/` - Output Coordination
-
-| File                  | Purpose                                                                 |
-| --------------------- | ----------------------------------------------------------------------- |
-| `coordinator.go`      | Coordinates streaming output with interactive input (saves/restores input state) |
-| `input_model.go`      | Bubble Tea model for rich input (message, approval, feedback types)     |
-| `slash_completion.go` | Autocomplete dropdown for slash commands                                |
-
-**Key pattern:** When output needs to print while input is visible, the coordinator saves input state, clears the form, prints, then restores input.
-
----
-
-### 8. `slash/` - Slash Command Registry
-
-Central registry for commands like `/plan`, `/act`, `/cancel`:
-
-- **CLI-local commands**: Handled directly by CLI
-- **Backend commands**: Fetched from core via gRPC, filtered by `CliCompatible` flag
-
----
-
-### 9. `sqlite/` - Instance Locking
-
-Manages the distributed locking system:
-
-- **Instance locks**: Track running Cline instances by address
-- **File locks**: Coordinate file access across instances
-- SQLite database created by cline-core, CLI reads/writes for discovery
-
----
-
-### 10. `task/` - Task Management
-
-| File                    | Purpose                                                              |
-| ----------------------- | -------------------------------------------------------------------- |
-| `manager.go`            | Core orchestrator: create, cancel, resume, restore tasks; stream handling |
-| `stream_coordinator.go` | Deduplication and turn management for dual streams                   |
-| `input_handler.go`      | Interactive input during follow mode (polling, approval detection)   |
-| `history_handler.go`    | Direct disk access to `taskHistory.json`                             |
-| `settings_parser.go`    | Parse settings from CLI flags                                        |
-| `follow_options.go`     | Configuration for follow behavior                                    |
-
-**Streaming:** Task manager subscribes to two gRPC streams:
-
-1. `SubscribeToState` - Full state updates
-2. `SubscribeToPartialMessage` - Streaming AI responses
-
----
-
-### 11. `terminal/` - Terminal Handling
-
-Enhanced keyboard protocol support and terminal configuration:
-
-- Enables modifyOtherKeys and Kitty keyboard protocol
-- Detects terminal type (VS Code, iTerm, Ghostty, Kitty, etc.)
-- Auto-configures shift+enter keybindings for various terminals
-
----
-
-### 12. `types/` - Type Definitions
-
-| File           | Purpose                                                           |
-| -------------- | ----------------------------------------------------------------- |
-| `messages.go`  | `ClineMessage`, `AskType`, `SayType`, `ToolType` enums, proto conversion |
-| `state.go`     | `ConversationState` with thread-safe message access               |
-| `history.go`   | `HistoryItem` matching taskHistory.json format                    |
-
----
-
-### 13. `updater/` - Auto-Update
-
-Background auto-update checking:
-
-- 24-hour check interval (cached)
-- Queries npm registry for newer versions
-- Supports `latest` and `nightly` channels
-- Runs `npm install -g cline` to update
-
----
-
-## `pkg/common/` - Shared Types
-
-| File            | Purpose                                                      |
-| --------------- | ------------------------------------------------------------ |
-| `constants.go`  | `SETTINGS_SUBFOLDER`, `DEFAULT_CLINE_CORE_PORT`              |
-| `schema.go`     | SQL queries for instance/file locks                          |
-| `types.go`      | `CoreInstanceInfo`, `LockRow`, `DefaultCoreInstance`         |
-| `utils.go`      | Port checking, health checks, address normalization, retry logic |
-
----
-
-## `pkg/generated/` - Auto-Generated
-
-| File                  | Purpose                                                                                                              |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| `providers.go`        | Provider definitions (Anthropic, OpenAI, Bedrock, etc.) with field metadata and model specs - generated from TypeScript sources |
-| `field_overrides.go`  | Manual overrides for field filtering                                                                                 |
-
----
-
-## `pkg/hostbridge/` - CLI-to-Core Bridge
-
-This is the **reverse bridge** allowing cline-core to request host environment operations:
-
-| File                    | Purpose                                              |
-| ----------------------- | ---------------------------------------------------- |
-| `grpc_server.go`        | Main server registering all services                 |
-| `simple_workspace.go`   | Workspace service: returns CWD as workspace path     |
-| `diff.go`               | In-memory file diff editing with line-based operations |
-| `env.go`                | Clipboard access, version info, shutdown coordination |
-| `window.go`             | UI stubs (no-ops or console output)                  |
-
-**Why this exists:** The same cline-core logic runs in VS Code and CLI. In VS Code, the "host" is the extension with editor APIs. In CLI, hostbridge emulates these capabilities with terminal-appropriate implementations.
-
----
-
-## Key Design Decisions
-
-1. **Two-process model:** `cline` CLI manages instances; `cline-core` is the actual AI engine (Node.js). This allows reusing the same core as the VS Code extension.
-
-2. **Self-registration via SQLite:** `cline-core` registers itself in a SQLite database on startup. The CLI discovers instances by reading this database, enabling multi-instance support.
-
-3. **Host bridge abstraction:** The `cline-host` process provides platform-specific operations (clipboard, workspace paths) via gRPC, allowing `cline-core` to remain host-agnostic.
-
-4. **Streaming-first UI:** The CLI uses gRPC streaming to display AI responses in real-time with typewriter-style rendering.
-
-5. **Dual stream handling:** Task manager subscribes to both state updates and partial messages, using deduplication to prevent duplicate rendering.

cli/cline.rb

@@ -7,6 +7,7 @@ class Cline < Formula
   license "Apache-2.0"
 
   depends_on "node@20"
+  depends_on "ripgrep"
 
   def install
     system "npm", "install", *std_npm_args(prefix: false)