Comparison

A · Cline rules · cline/cline B · Cline rules · cline/cline

What each file covers, counted
Dimension	Shared	Only in A	Only in B	Overlap
Sections	0	19	8	0%
Commands	0	3	2	0%
Section tags	2	3	3	25%

What each file covers

Sections

0 shared · 19 only in A · 8 only in B

− Debug Harness
− Quick start
− Build extension first if needed (protos + esbuild):
− Launch (skip-build if already built). Run with node, NOT bun — Playwright's
− Electron launch times out under bun:
− In another terminal:
− Data Isolation
− Browser Capture & OAuth
− OAuth API
− OAuth testing flow
− Navigating Views — Use Commands, Not Clicks
− Key commands
− Typical Session
− 1. Launch
− 2. Open sidebar + dismiss overlays (ALWAYS do this first)
− 3. Navigate to view
− 4. Check captured OAuth URLs if testing auth
− 5. Verify
− Caveats
+ Cline Protobuf Development Guide
+ Overview
+ Key Concepts & Best Practices
+ 4-Step Development Workflow
+ 1. Define the RPC in a `.proto` File
+ 2. Compile Definitions
+ 3. Implement the Backend Handler
+ 4. Call the RPC from the Webview

Commands

0 shared · 3 only in A · 2 only in B

− bun run protos && IS_DEV=true bun esbuild.mjs
− node src/dev/debug-harness/server.ts --skip-build --auto-launch
− bun run dev:mcp-oauth-test-server
+ bun run protos
+ task.proto

Section tags

2 shared · 3 only in A · 3 only in B

− test
− testing-strategy
− security
+ code-style
+ architecture
+ agent-behaviour
build
api

Line diff

+65 added−105 removed25 unchanged19.2% identical

cline/cline · .clinerules/debug-harness.md

@@ −1 @@

1# Debug Harness

3HTTP-controlled debugger for the VSCode extension at `src/dev/debug-harness/server.ts`.

5## Quick start

7```bash

8# Build extension first if needed (protos + esbuild):

9bun run protos && IS_DEV=true bun esbuild.mjs

11# Launch (skip-build if already built). Run with node, NOT bun — Playwright's

12# Electron launch times out under bun:

13node src/dev/debug-harness/server.ts --skip-build --auto-launch

15# In another terminal:

16curl localhost:19229/api -d '{"method":"status"}'

17```

19## Data Isolation

21The debugee runs with `CLINE_DIR=~/.cline2` by default, separate from your real `~/.cline`.

22This prevents the debugee's logout from logging out the debugger, and vice versa.

23Override with `--cline-dir /tmp/test-dir`. Check with `status()` → `clineDir`.

25## Browser Capture & OAuth

27The debugee runs with `CLINE_CAPTURE_BROWSER=1`, which intercepts `openExternal()` in

28`src/utils/env.ts`. URLs are captured instead of opening a real browser:

30- Logged to `$CLINE_DIR/data/debug-captured-urls.jsonl`

31- POSTed in real-time to `/captured-url` on the harness server

32- Queryable via `oauth.captured_urls`

34### OAuth API

36- **`oauth.captured_urls`** `{clear?}` — URLs the debugee tried to open

37- **`oauth.read_stored_token`** — Check auth token presence in secrets.json

38- **`oauth.simulate_callback`** `{path, code?, state?, provider?, token?}` — Build vscode:// callback URI

39- **`oauth.read_captured_urls_file`** — Read on-disk JSONL of captured URLs

41### OAuth testing flow

43For **Cline OAuth** (SDK local callback): The SDK starts a local HTTP server, the auth URL

44is captured. To complete: open the captured URL in a real browser (it redirects back to the

45SDK's callback server), OR extract the callback port and `curl http://127.0.0.1:PORT/callback?code=...`.

47For **MCP/Provider OAuth** (vscode:// URI): The redirect goes to a vscode:// URI.

48`oauth.simulate_callback` only *builds* the URI — it does not deliver it, and the ESM

49extension host can't `require()` the handler. To actually deliver the callback, call the

50debug-only hook via `ext.evaluate` (with `awaitPromise: true`):

51`globalThis.__clineHandleUri("vscode://saoudrizwan.claude-dev/...?code=...&state=...")`.

52It runs the same `SharedUriHandler.handleUri` as VSCode's real URI handler and exists only

53when `CLINE_CAPTURE_BROWSER` is set (the harness always sets it; never ships in prod).

54For end-to-end MCP OAuth, get a real `code` from the local MCP OAuth test server

55(`bun run dev:mcp-oauth-test-server`).

57## Navigating Views — Use Commands, Not Clicks

59Don't try to find/click small sidebar icons. Use VSCode commands via command palette.

60Registered in `src/registry.ts`:

62| Command | View |

63|---------|------|

64| `cline.accountButtonClicked` | Account / sign-in |

65| `cline.historyButtonClicked` | Task history |

66| `cline.settingsButtonClicked` | Settings |

67| `cline.mcpButtonClicked` | MCP servers |

68| `cline.plusButtonClicked` | New task (chat) |

69| `cline.worktreesButtonClicked` | Worktrees |

71```bash

72curl localhost:19229/api -d '{"method":"ui.command_palette","params":{"command":"cline.accountButtonClicked"}}'

73```

75## Key commands

77All via `POST localhost:19229/api` with `{"method":"...", "params":{...}}`:

79- **`launch`** / **`shutdown`** — lifecycle

80- **`ui.screenshot`** — screenshot to `/tmp/cline-debug/`; returns `{path}` — **use `read_file` on the path to examine, do NOT `open` the file** (Preview.app covers the VSCode window)

81- **`ui.open_sidebar`** — open the Cline sidebar

82- **`ext.set_breakpoint`** `{file, line, condition?}` — breakpoint by source file (sourcemap-resolved)

83- **`ext.evaluate`** `{expression, callFrameId?}` — eval in extension host

84- **`ext.resume`** / **`ext.step_over`** / **`ext.step_into`** — stepping

85- **`ext.call_stack`** — inspect when paused

86- **`web.evaluate`** `{expression}` — eval in webview

87- **`web.post_message`** `{message}` — send postMessage to extension host via exposed vsCodeApi

88- **`wait_for_pause`** `{timeout?}` — block until breakpoint hit

89- **`ui.locator`** `{role?, testId?, text?, frame?}` — Playwright locator (auto-retries on stale sidebar frame)

90- **`ui.react_input`** `{text, selector?, clear?, submit?}` — set React textarea value via `execCommand('insertText')`; works reliably across multiple tasks

91- **`ui.send_message`** `{text, images?, files?, responseType?}` — send chat message bypassing the textarea entirely (via gRPC postMessage)

92- **`ui.command_palette`** `{command}` — run VSCode command

94## Typical Session

96```bash

97# 1. Launch

98curl localhost:19229/api -d '{"method":"launch","params":{"skipBuild":true}}'

100# 2. Open sidebar + dismiss overlays (ALWAYS do this first)

101curl localhost:19229/api -d '{"method":"ui.open_sidebar"}'

102curl localhost:19229/api -d '{"method":"web.evaluate","params":{"expression":"document.querySelectorAll(\".sr-only\").forEach(el => el.parentElement?.click())"}}'

103

104# 3. Navigate to view

105curl localhost:19229/api -d '{"method":"ui.command_palette","params":{"command":"cline.accountButtonClicked"}}'

106

107# 4. Check captured OAuth URLs if testing auth

108curl localhost:19229/api -d '{"method":"oauth.captured_urls"}'

109

110# 5. Verify

111curl localhost:19229/api -d '{"method":"ui.screenshot"}'

112```

113

114## Caveats

115

116- **⚠️ Dismiss promotional overlays FIRST**: On fresh launches, full-screen promo overlays block the sidebar. **Dismiss immediately after `ui.open_sidebar`**, before any other interaction or screenshot. May need to run twice:

117 ```bash

118 curl localhost:19229/api -d '{"method": "ui.open_sidebar"}'

119 curl localhost:19229/api -d '{"method": "web.evaluate", "params": {"expression": "document.querySelectorAll(\".sr-only\").forEach(el => el.parentElement?.click())"}}'

120 ```

121- **Screenshots — don't open the file**: `ui.screenshot` and `ui.sidebar_screenshot` save PNGs to `/tmp/cline-debug/` and return the `{path}`. Use `read_file` on that path to examine screenshots. Running `open <path>` launches Preview.app on macOS which covers the VSCode window.

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

123- **Port 9230**: Extension host inspector. If another VSCode instance uses this port, the harness will fail to connect. Kill other debug instances first.

124- **macOS only** for now (Playwright Electron launch behavior).

125- **Webview CDP**: `connect_webview` may fail depending on Electron version. `web.evaluate` still works via Playwright's `frame.evaluate()` fallback.

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

127- **OAuth with fake codes**: Browser capture intercepts the URL but doesn't provide a valid auth code. For real OAuth testing, open the captured URL in a browser. For unit testing, mock the token exchange.

128

129See `src/dev/debug-harness/README.md` for full API reference.

130

cline/cline · .clinerules/protobuf-development.md

@@ +1 @@

1# Cline Protobuf Development Guide

3This guide outlines how to add new gRPC endpoints for communication between the webview (frontend) and the extension host (backend).

5## Overview

7Cline uses [Protobuf](https://protobuf.dev/) to define a strongly-typed API, ensuring efficient and type-safe communication. All definitions are in the `/proto` directory. The compiler and plugins are included as project dependencies, so no manual installation is needed.

9## Key Concepts & Best Practices

11- **File Structure**: Each feature domain should have its own `.proto` file (e.g., `account.proto`, `task.proto`).

12- **Message Design**:

13 - For simple, single-value data, use the shared types in `proto/common.proto` (e.g., `StringRequest`, `Empty`, `Int64Request`). This promotes consistency.

14 - For complex data structures, define custom messages within the feature's `.proto` file (see `task.proto` for examples like `NewTaskRequest`).

15- **Naming Conventions**:

16 - Services: `PascalCaseService` (e.g., `AccountService`).

17 - RPCs: `camelCase` (e.g., `accountEmailIdentified`).

18 - Messages: `PascalCase` (e.g., `StringRequest`).

19- **Streaming**: For server-to-client streaming, use the `stream` keyword on the response type. See `subscribeToAuthCallback` in `account.proto` for an example.

21---

23## 4-Step Development Workflow

25Here’s how to add a new RPC, using `scrollToSettings` as an example.

27### 1. Define the RPC in a `.proto` File

29Add your service method to the appropriate file in the `proto/` directory.

31**File: `proto/ui.proto`**

32```proto

33service UiService {

34 // ... other RPCs

35 // Scrolls to a specific settings section in the settings view

36 rpc scrollToSettings(StringRequest) returns (KeyValuePair);

37}

38```

39Here, we use the common `StringRequest` and `KeyValuePair` types.

41### 2. Compile Definitions

43After editing a `.proto` file, regenerate the TypeScript code. From the project root, run:

44```bash

45bun run protos

46```

47This command compiles all `.proto` files and outputs the generated code to `src/generated/` and `src/shared/`. Do not edit these generated files manually.

49### 3. Implement the Backend Handler

51Create the RPC implementation in the backend. Handlers are located in `src/core/controller/[service-name]/`.

53**File: `src/core/controller/ui/scrollToSettings.ts`**

54```typescript

55import { Controller } from ".."

56import { StringRequest, KeyValuePair } from "../../../shared/proto/common"

58/**

59 * Executes a scroll to settings action

60 * @param controller The controller instance

61 * @param request The request containing the ID of the settings section to scroll to

62 * @returns KeyValuePair with action and value fields for the UI to process

63 */

64export async function scrollToSettings(controller: Controller, request: StringRequest): Promise<KeyValuePair> {

65 return KeyValuePair.create({

66 key: "scrollToSettings",

67 value: request.value || "",

68 })

69}

70```

72### 4. Call the RPC from the Webview

74Call the new RPC from a React component in `webview-ui/`. The generated client makes this simple.

76**File: `webview-ui/src/components/browser/BrowserSettingsMenu.tsx`** (Example)

77```tsx

78import { UiServiceClient } from "../../../services/grpc"

79import { StringRequest } from "../../../../shared/proto/common"

81// ... inside a React component

82const handleMenuClick = async () => {

83 try {

84 await UiServiceClient.scrollToSettings(StringRequest.create({ value: "browser" }))

85 } catch (error) {

86 console.error("Error scrolling to browser settings:", error)

87 }

88}

89```

@@ −1 +1 @@

1−# Debug Harness

1+# Cline Protobuf Development Guide

3−HTTP-controlled debugger for the VSCode extension at `src/dev/debug-harness/server.ts`.

3+This guide outlines how to add new gRPC endpoints for communication between the webview (frontend) and the extension host (backend).

5−## Quick start

5+## Overview

7−```bash

8−# Build extension first if needed (protos + esbuild):

9−bun run protos && IS_DEV=true bun esbuild.mjs

7+Cline uses [Protobuf](https://protobuf.dev/) to define a strongly-typed API, ensuring efficient and type-safe communication. All definitions are in the `/proto` directory. The compiler and plugins are included as project dependencies, so no manual installation is needed.

108

11−# Launch (skip-build if already built). Run with node, NOT bun — Playwright's

12−# Electron launch times out under bun:

13−node src/dev/debug-harness/server.ts --skip-build --auto-launch

9+## Key Concepts & Best Practices

1410

15−# In another terminal:

16−curl localhost:19229/api -d '{"method":"status"}'

17−```

11+- **File Structure**: Each feature domain should have its own `.proto` file (e.g., `account.proto`, `task.proto`).

12+- **Message Design**:

13+ - For simple, single-value data, use the shared types in `proto/common.proto` (e.g., `StringRequest`, `Empty`, `Int64Request`). This promotes consistency.

14+ - For complex data structures, define custom messages within the feature's `.proto` file (see `task.proto` for examples like `NewTaskRequest`).

15+- **Naming Conventions**:

16+ - Services: `PascalCaseService` (e.g., `AccountService`).

17+ - RPCs: `camelCase` (e.g., `accountEmailIdentified`).

18+ - Messages: `PascalCase` (e.g., `StringRequest`).

19+- **Streaming**: For server-to-client streaming, use the `stream` keyword on the response type. See `subscribeToAuthCallback` in `account.proto` for an example.

1820

19−## Data Isolation

21+---

2022

21−The debugee runs with `CLINE_DIR=~/.cline2` by default, separate from your real `~/.cline`.

22−This prevents the debugee's logout from logging out the debugger, and vice versa.

23−Override with `--cline-dir /tmp/test-dir`. Check with `status()` → `clineDir`.

23+## 4-Step Development Workflow

2424

25−## Browser Capture & OAuth

25+Here’s how to add a new RPC, using `scrollToSettings` as an example.

2626

27−The debugee runs with `CLINE_CAPTURE_BROWSER=1`, which intercepts `openExternal()` in

28−`src/utils/env.ts`. URLs are captured instead of opening a real browser:

27+### 1. Define the RPC in a `.proto` File

2928

30−- Logged to `$CLINE_DIR/data/debug-captured-urls.jsonl`

31−- POSTed in real-time to `/captured-url` on the harness server

32−- Queryable via `oauth.captured_urls`

29+Add your service method to the appropriate file in the `proto/` directory.

3330

34−### OAuth API

31+**File: `proto/ui.proto`**

32+```proto

33+service UiService {

34+ // ... other RPCs

35+ // Scrolls to a specific settings section in the settings view

36+ rpc scrollToSettings(StringRequest) returns (KeyValuePair);

37+}

38+```

39+Here, we use the common `StringRequest` and `KeyValuePair` types.

3540

36−- **`oauth.captured_urls`** `{clear?}` — URLs the debugee tried to open

37−- **`oauth.read_stored_token`** — Check auth token presence in secrets.json

38−- **`oauth.simulate_callback`** `{path, code?, state?, provider?, token?}` — Build vscode:// callback URI

39−- **`oauth.read_captured_urls_file`** — Read on-disk JSONL of captured URLs

41+### 2. Compile Definitions

4042

41−### OAuth testing flow

42−

43−For **Cline OAuth** (SDK local callback): The SDK starts a local HTTP server, the auth URL

44−is captured. To complete: open the captured URL in a real browser (it redirects back to the

45−SDK's callback server), OR extract the callback port and `curl http://127.0.0.1:PORT/callback?code=...`.

46−

47−For **MCP/Provider OAuth** (vscode:// URI): The redirect goes to a vscode:// URI.

48−`oauth.simulate_callback` only *builds* the URI — it does not deliver it, and the ESM

49−extension host can't `require()` the handler. To actually deliver the callback, call the

50−debug-only hook via `ext.evaluate` (with `awaitPromise: true`):

51−`globalThis.__clineHandleUri("vscode://saoudrizwan.claude-dev/...?code=...&state=...")`.

52−It runs the same `SharedUriHandler.handleUri` as VSCode's real URI handler and exists only

53−when `CLINE_CAPTURE_BROWSER` is set (the harness always sets it; never ships in prod).

54−For end-to-end MCP OAuth, get a real `code` from the local MCP OAuth test server

55−(`bun run dev:mcp-oauth-test-server`).

56−

57−## Navigating Views — Use Commands, Not Clicks

58−

59−Don't try to find/click small sidebar icons. Use VSCode commands via command palette.

60−Registered in `src/registry.ts`:

61−

62−| Command | View |

63−|---------|------|

64−| `cline.accountButtonClicked` | Account / sign-in |

65−| `cline.historyButtonClicked` | Task history |

66−| `cline.settingsButtonClicked` | Settings |

67−| `cline.mcpButtonClicked` | MCP servers |

68−| `cline.plusButtonClicked` | New task (chat) |

69−| `cline.worktreesButtonClicked` | Worktrees |

70−

43+After editing a `.proto` file, regenerate the TypeScript code. From the project root, run:

7144 ```bash

72−curl localhost:19229/api -d '{"method":"ui.command_palette","params":{"command":"cline.accountButtonClicked"}}'

45+bun run protos

7346 ```

47+This command compiles all `.proto` files and outputs the generated code to `src/generated/` and `src/shared/`. Do not edit these generated files manually.

7448

75−## Key commands

49+### 3. Implement the Backend Handler

7650

77−All via `POST localhost:19229/api` with `{"method":"...", "params":{...}}`:

51+Create the RPC implementation in the backend. Handlers are located in `src/core/controller/[service-name]/`.

7852

79−- **`launch`** / **`shutdown`** — lifecycle

80−- **`ui.screenshot`** — screenshot to `/tmp/cline-debug/`; returns `{path}` — **use `read_file` on the path to examine, do NOT `open` the file** (Preview.app covers the VSCode window)

81−- **`ui.open_sidebar`** — open the Cline sidebar

82−- **`ext.set_breakpoint`** `{file, line, condition?}` — breakpoint by source file (sourcemap-resolved)

83−- **`ext.evaluate`** `{expression, callFrameId?}` — eval in extension host

84−- **`ext.resume`** / **`ext.step_over`** / **`ext.step_into`** — stepping

85−- **`ext.call_stack`** — inspect when paused

86−- **`web.evaluate`** `{expression}` — eval in webview

87−- **`web.post_message`** `{message}` — send postMessage to extension host via exposed vsCodeApi

88−- **`wait_for_pause`** `{timeout?}` — block until breakpoint hit

89−- **`ui.locator`** `{role?, testId?, text?, frame?}` — Playwright locator (auto-retries on stale sidebar frame)

90−- **`ui.react_input`** `{text, selector?, clear?, submit?}` — set React textarea value via `execCommand('insertText')`; works reliably across multiple tasks

91−- **`ui.send_message`** `{text, images?, files?, responseType?}` — send chat message bypassing the textarea entirely (via gRPC postMessage)

92−- **`ui.command_palette`** `{command}` — run VSCode command

53+**File: `src/core/controller/ui/scrollToSettings.ts`**

54+```typescript

55+import { Controller } from ".."

56+import { StringRequest, KeyValuePair } from "../../../shared/proto/common"

9357

94−## Typical Session

58+/**

59+ * Executes a scroll to settings action

60+ * @param controller The controller instance

61+ * @param request The request containing the ID of the settings section to scroll to

62+ * @returns KeyValuePair with action and value fields for the UI to process

63+ */

64+export async function scrollToSettings(controller: Controller, request: StringRequest): Promise<KeyValuePair> {

65+ return KeyValuePair.create({

66+ key: "scrollToSettings",

67+ value: request.value || "",

68+ })

69+}

70+```

9571

96−```bash

97−# 1. Launch

98−curl localhost:19229/api -d '{"method":"launch","params":{"skipBuild":true}}'

72+### 4. Call the RPC from the Webview

9973

100−# 2. Open sidebar + dismiss overlays (ALWAYS do this first)

101−curl localhost:19229/api -d '{"method":"ui.open_sidebar"}'

102−curl localhost:19229/api -d '{"method":"web.evaluate","params":{"expression":"document.querySelectorAll(\".sr-only\").forEach(el => el.parentElement?.click())"}}'

74+Call the new RPC from a React component in `webview-ui/`. The generated client makes this simple.

10375

104−# 3. Navigate to view

105−curl localhost:19229/api -d '{"method":"ui.command_palette","params":{"command":"cline.accountButtonClicked"}}'

76+**File: `webview-ui/src/components/browser/BrowserSettingsMenu.tsx`** (Example)

77+```tsx

78+import { UiServiceClient } from "../../../services/grpc"

79+import { StringRequest } from "../../../../shared/proto/common"

10680

107−# 4. Check captured OAuth URLs if testing auth

108−curl localhost:19229/api -d '{"method":"oauth.captured_urls"}'

109−

110−# 5. Verify

111−curl localhost:19229/api -d '{"method":"ui.screenshot"}'

81+// ... inside a React component

82+const handleMenuClick = async () => {

83+ try {

84+ await UiServiceClient.scrollToSettings(StringRequest.create({ value: "browser" }))

85+ } catch (error) {

86+ console.error("Error scrolling to browser settings:", error)

87+ }

88+}

11289 ```

113−

114−## Caveats

115−

116−- **⚠️ Dismiss promotional overlays FIRST**: On fresh launches, full-screen promo overlays block the sidebar. **Dismiss immediately after `ui.open_sidebar`**, before any other interaction or screenshot. May need to run twice:

117− ```bash

118− curl localhost:19229/api -d '{"method": "ui.open_sidebar"}'

119− curl localhost:19229/api -d '{"method": "web.evaluate", "params": {"expression": "document.querySelectorAll(\".sr-only\").forEach(el => el.parentElement?.click())"}}'

120− ```

121−- **Screenshots — don't open the file**: `ui.screenshot` and `ui.sidebar_screenshot` save PNGs to `/tmp/cline-debug/` and return the `{path}`. Use `read_file` on that path to examine screenshots. Running `open <path>` launches Preview.app on macOS which covers the VSCode window.

122−- **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.

123−- **Port 9230**: Extension host inspector. If another VSCode instance uses this port, the harness will fail to connect. Kill other debug instances first.

124−- **macOS only** for now (Playwright Electron launch behavior).

125−- **Webview CDP**: `connect_webview` may fail depending on Electron version. `web.evaluate` still works via Playwright's `frame.evaluate()` fallback.

126−- **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.

127−- **OAuth with fake codes**: Browser capture intercepts the URL but doesn't provide a valid auth code. For real OAuth testing, open the captured URL in a browser. For unit testing, mock the token exchange.

128−

129−See `src/dev/debug-harness/README.md` for full API reference.

13090