Remove insert_content tool

[samhvw8]

Context

Remove insert_content tool

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Remove insert_content tool and related configurations, schemas, and tests from the codebase.

• Tool Removal:
  • Remove insert_content tool from Cline.ts, index.ts, and insert-groups.ts.
  • Delete insertContentTool.ts and insert-content.ts.
• Configuration Changes:
  • Remove insert_content from experimentIds in roo-code.ts and schemas/index.ts.
  • Update experiments in experiments.ts and experiments.test.ts.
• Schema and Type Updates:
  • Remove insert_content from GlobalSettings in roo-code.d.ts and types.ts.
  • Update experimentsSchema in schemas/index.ts.
• Test Updates:
  • Remove insert_content related tests in system.test.ts and modes.test.ts.
  • Update ExtensionStateContext.test.tsx to reflect changes in experiments.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: c175ef1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[samhvw8]

got this error when pushing

src/core/Cline.ts:1398:33 - error TS2366: Function lacks ending return statement and return type does not include 'undefined'.

1398 const toolDescription = (): string => {
~~~~~~

Found 1 error in src/core/Cline.ts:1398

[mrubens]

I feel torn on this one. I've heard some people say that insert_content is the only way to get models that can't do diffs to work, but on the other hand I don't really like the idea of experimental features that are rarely used. Is there a version of this that we'd feel comfortable turning on for everyone? Personally I lean toward one that looks more like append_to_file (a simple tool with a single block and a line number). Thoughts?

[samhvw8]

@mrubens or should we keep both insert_content and search_and_replace but we change it to xml, and remove multiple operation and move it from experimental tool ?

[mrubens]

@mrubens or should we keep both insert_content and search_and_replace but we change it to xml, and remove multiple operation and move it from experimental tool ?

Yeah I might be leaning in that direction. And maybe remove append_to_file in favor of insert_content?