Comparison

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

What each file covers, counted
Dimension	Only in A	Only in B	Overlap
Sections	19	9	0%
Commands	3	0	0%
Section tags	5	4	0%

What each file covers

Sections

0 shared · 19 only in A · 9 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
+ Storage Architecture
+ Key Abstractions
+ `StorageContext` (src/shared/storage/storage-context.ts)
+ `ClineFileStorage` (src/shared/storage/ClineFileStorage.ts)
+ `StateManager` (src/core/storage/StateManager.ts)
+ ⚠️ Do NOT Use VSCode's ExtensionContext for Storage
+ VSCode Migration (src/hosts/vscode/vscode-to-file-migration.ts)
+ Adding New Storage Keys
+ File Layout

Commands

0 shared · 3 only in A · 0 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

Section tags

0 shared · 5 only in A · 4 only in B

− build
− test
− testing-strategy
− security
− api
+ code-style
+ architecture
+ database
+ do-not

Line diff

+45 added−110 removed20 unchanged15.4% 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/storage.md

@@ +1 @@

1# Storage Architecture

3Global 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.

5## Key Abstractions

7### `StorageContext` (src/shared/storage/storage-context.ts)

8The entry point. Created via `createStorageContext()` and passed to `StateManager.initialize()`. Contains three `ClineFileStorage` instances:

9- `globalState` → `~/.cline/data/globalState.json`

10- `secrets` → `~/.cline/data/secrets.json` (mode 0o600)

11- `workspaceState` → `~/.cline/data/workspaces/<hash>/workspaceState.json`

13### `ClineFileStorage` (src/shared/storage/ClineFileStorage.ts)

14Synchronous JSON key-value store backed by a single file. Supports `get()`, `set()`, `setBatch()`, `delete()`. Writes are atomic (write-then-rename).

16### `StateManager` (src/core/storage/StateManager.ts)

17In-memory cache on top of `StorageContext`. All runtime reads hit the cache; writes update cache immediately and debounce-flush to disk.

19## ⚠️ Do NOT Use VSCode's ExtensionContext for Storage

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

23Instead, use:

24```typescript

25// Reading state

26StateManager.get().getGlobalStateKey("myKey")

27StateManager.get().getSecretKey("mySecretKey")

28StateManager.get().getWorkspaceStateKey("myWsKey")

30// Writing state

31StateManager.get().setGlobalState("myKey", value)

32StateManager.get().setSecret("mySecretKey", value)

33StateManager.get().setWorkspaceState("myWsKey", value)

34```

36Remember 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.

38## VSCode Migration (src/hosts/vscode/vscode-to-file-migration.ts)

40On 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()`.

42- **Sentinel**: `__vscodeMigrationVersion` key in global state and workspace state — prevents re-migration.

43- **Merge strategy**: File store wins. Existing values are never overwritten.

44- **Safe downgrade**: VSCode storage is NOT cleared, so older extension versions still work.

46## Adding New Storage Keys

481. Add to `src/shared/storage/state-keys.ts` (see existing patterns)

492. Read/write via `StateManager` (NOT via `context.globalState`)

503. If adding a secret, add to `SecretKeys` array in `state-keys.ts`

52## File Layout

54```

55~/.cline/

56 data/

57 globalState.json # Global settings & state

58 secrets.json # API keys (mode 0o600)

59 tasks/

60 taskHistory.json # Task history (separate file)

61 workspaces/

62 <hash>/

63 workspaceState.json # Per-workspace toggles

64```

@@ −1 +1 @@

1−# Debug Harness

1+# Storage Architecture

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

3+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.

5−## Quick start

5+## Key Abstractions

7−```bash

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

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

7+### `StorageContext` (src/shared/storage/storage-context.ts)

8+The entry point. Created via `createStorageContext()` and passed to `StateManager.initialize()`. Contains three `ClineFileStorage` instances:

9+- `globalState` → `~/.cline/data/globalState.json`

10+- `secrets` → `~/.cline/data/secrets.json` (mode 0o600)

11+- `workspaceState` → `~/.cline/data/workspaces/<hash>/workspaceState.json`

1012

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

13+### `ClineFileStorage` (src/shared/storage/ClineFileStorage.ts)

14+Synchronous JSON key-value store backed by a single file. Supports `get()`, `set()`, `setBatch()`, `delete()`. Writes are atomic (write-then-rename).

1415

15−# In another terminal:

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

17−```

16+### `StateManager` (src/core/storage/StateManager.ts)

17+In-memory cache on top of `StorageContext`. All runtime reads hit the cache; writes update cache immediately and debounce-flush to disk.

1818

19−## Data Isolation

19+## ⚠️ Do NOT Use VSCode's ExtensionContext for Storage

2020

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

21+**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.

2422

25−## Browser Capture & OAuth

23+Instead, use:

24+```typescript

25+// Reading state

26+StateManager.get().getGlobalStateKey("myKey")

27+StateManager.get().getSecretKey("mySecretKey")

28+StateManager.get().getWorkspaceStateKey("myWsKey")

2629

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:

29−

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`

33−

34−### OAuth API

35−

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

40−

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−

71−```bash

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

30+// Writing state

31+StateManager.get().setGlobalState("myKey", value)

32+StateManager.get().setSecret("mySecretKey", value)

33+StateManager.get().setWorkspaceState("myWsKey", value)

7334 ```

7435

75−## Key commands

36+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.

7637

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

38+## VSCode Migration (src/hosts/vscode/vscode-to-file-migration.ts)

7839

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

40+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()`.

9341

94−## Typical Session

42+- **Sentinel**: `__vscodeMigrationVersion` key in global state and workspace state — prevents re-migration.

43+- **Merge strategy**: File store wins. Existing values are never overwritten.

44+- **Safe downgrade**: VSCode storage is NOT cleared, so older extension versions still work.

9545

96−```bash

97−# 1. Launch

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

46+## Adding New Storage Keys

9947

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())"}}'

48+1. Add to `src/shared/storage/state-keys.ts` (see existing patterns)

49+2. Read/write via `StateManager` (NOT via `context.globalState`)

50+3. If adding a secret, add to `SecretKeys` array in `state-keys.ts`

10351

104−# 3. Navigate to view

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

52+## File Layout

10653

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"}'

11254 ```

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.

55+~/.cline/

56+ data/

57+ globalState.json # Global settings & state

58+ secrets.json # API keys (mode 0o600)

59+ tasks/

60+ taskHistory.json # Task history (separate file)

61+ workspaces/

62+ <hash>/

63+ workspaceState.json # Per-workspace toggles

64+```

13065