Add a setAlwaysAllowBrowser checkbox to settings

[mrubens]

---

Important

Add alwaysAllowBrowser setting to allow browser actions without confirmation, updating core logic, UI, and messaging components.

• Behavior:
  • Adds cline.alwaysAllowBrowser setting in package.json to allow browser actions without confirmation.
  • Updates Cline class in Cline.ts to handle alwaysAllowBrowser for browser actions.
  • Modifies ClineProvider in ClineProvider.ts to initialize and update alwaysAllowBrowser state.
• UI:
  • Adds checkbox for alwaysAllowBrowser in SettingsView.tsx.
  • Updates ExtensionStateContext.tsx to manage alwaysAllowBrowser state.
• Messaging:
  • Updates WebviewMessage.ts and ExtensionMessage.ts to include alwaysAllowBrowser message type.
• Tests:
  • Updates Cline.test.ts to test alwaysAllowBrowser behavior.

^{This description was created by for 0346fde. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to cebcbfff889461c25c5d848a4ade35475f9f234f in 1 minute and 5 seconds

More details

• Looked at 345 lines of code in 7 files
• Skipped 1 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. src/core/webview/ClineProvider.ts:531

• Draft comment:
  The logic for updating global state and Cline instance for alwaysAllowBrowser is repeated for other settings like alwaysAllowReadOnly, alwaysAllowWrite, and alwaysAllowExecute. Consider refactoring to reduce redundancy.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The codebase has multiple instances where the same logic is repeated for different settings. This can be refactored to reduce redundancy.

2. src/core/webview/ClineProvider.ts:527

• Draft comment:
  Consider using async/await instead of .then() for promise handling to improve readability and maintainability. This is in line with our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Comment was not on a valid diff hunk.

3. src/core/webview/ClineProvider.ts:834

• Draft comment:
  Consider using async/await instead of .then() for promise handling to improve readability and maintainability. This is in line with our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_FAavBrKQa9uAnQUq

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 0346fde in 2 minutes and 41 seconds

More details

• Looked at 412 lines of code in 8 files
• Skipped 1 files when reviewing.
• Skipped posting 11 drafted comments based on config settings.

1. src/core/Cline.ts:875

• Draft comment:
  Remove the commented-out regex pattern if it's not needed to avoid confusion.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The regex pattern in the comment is incomplete and commented out, which might confuse future developers. It should be removed if not needed.

2. src/core/Cline.ts:1421

• Draft comment:
  Consider using serializeError for error serialization to handle potential circular references safely.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code uses JSON.stringify to serialize objects for logging or messaging. However, it doesn't handle potential circular references, which can cause runtime errors. Using serializeError from the serialize-error package can help safely serialize errors and objects with circular references.

3. src/core/Cline.ts:1464

• Draft comment:
  Consider using serializeError for error serialization to handle potential circular references safely.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code uses JSON.stringify to serialize objects for logging or messaging. However, it doesn't handle potential circular references, which can cause runtime errors. Using serializeError from the serialize-error package can help safely serialize errors and objects with circular references.

4. src/core/Cline.ts:1467

• Draft comment:
  Consider using serializeError for error serialization to handle potential circular references safely.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code uses JSON.stringify to serialize objects for logging or messaging. However, it doesn't handle potential circular references, which can cause runtime errors. Using serializeError from the serialize-error package can help safely serialize errors and objects with circular references.

5. src/core/Cline.ts:872

• Draft comment:
  Consider using serializeError for error serialization to handle potential circular references safely.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code uses JSON.stringify to serialize objects for logging or messaging. However, it doesn't handle potential circular references, which can cause runtime errors. Using serializeError from the serialize-error package can help safely serialize errors and objects with circular references.

6. src/core/Cline.ts:1440

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Comment was on unchanged code.

7. src/core/webview/ClineProvider.ts:527

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

8. src/core/webview/ClineProvider.ts:834

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

9. src/core/webview/ClineProvider.ts:945

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

10. src/core/webview/ClineProvider.ts:977

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

11. src/core/webview/ClineProvider.ts:1026

• Draft comment:
  Consider using async/await instead of .then() for handling promises. This makes the code more readable and maintainable. Refer to our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d581809f9af3fdba09412ef6
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_kXu0ThHcNoVAlhxS

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[lloydchang]

Merged changes from #14 to cline/cline#784

[lloydchang]

Regarding #14

https://discord.com/channels/1275535550845292637/1275535550845292640/1311045513864417330

The checkbox only applies when the model supports computer use. We only use Sonnet 3.5 at Roo, so things are simpler.