3.14 Part A

[hannesrudolph]

Important

This PR updates documentation for Roo Code version 3.14, introducing new tools, deprecations, and improvements, along with sidebar configuration updates.

• New Tools and Features:
  • Added insert_content and search_and_replace tools in tool-use-overview.md.
  • Deprecated append_to_file in favor of insert_content.
  • Improved apply_diff for better compatibility with Google Gemini 2.5.
  • Added Gemini prompt caching and context variable interpolation in system prompts.
• Documentation Updates:
  • Updated docs/features/tools to include new tools and deprecations.
  • Updated docs/update-notes with release notes for versions 3.14.0 and 3.14.1.
  • Updated sidebars.ts to include new documentation paths.
• Bug Fixes and Improvements:
  • Fixed issues with file handling and editor state preservation.
  • Improved performance and error handling in various tools.

^{This description was created by for 50f3ca0. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 25, 2025 0:16am

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 50f3ca0 in 1 minute and 43 seconds. Click for details.

• Reviewed 683 lines of code in 14 files
• Skipped 2 files when reviewing.
• Skipped posting 14 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. sidebars.ts:52

• Draft comment:
  New entry 'features/tools/insert-content' added in the Tool Use category. Please ensure this ordering is consistent with our modular design and documentation updates.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. sidebars.ts:57

• Draft comment:
  New entry 'features/tools/search-and-replace' added in the Tool Use category. Verify that its placement matches the intended grouping and ordering.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. docs/features/footgun-prompting.md:7

• Draft comment:
  The revised text is clearer and the addition of the warning indicator image is a good enhancement. Consider making the alt text even more descriptive (e.g. mention that the icon signals an active system prompt override) to aid accessibility.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. docs/features/tools/apply-diff.md:27

• Draft comment:
  The updated description clearly explains the fuzzy matching (using Levenshtein distance) and context window approach. The revisions improve clarity, and no further changes seem necessary.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. docs/features/tools/insert-content.md:1

• Draft comment:
  The new documentation for the insert_content tool is clear and well-structured, with detailed examples. The instructions properly explain the 1-based line parameter semantics.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

6. docs/features/tools/list-files.md:30

• Draft comment:
  The updates to list_files, including leveraging the ripgrep tool and detailing the 10-second timeout behavior, greatly enhance clarity. Verify that these timeout details align with the backend implementation.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

7. docs/features/tools/search-and-replace.md:1

• Draft comment:
  The search_and_replace documentation is comprehensive with clear parameter descriptions and usage examples. Ensure that regex examples (with proper escaping) are consistent with the implementation.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

8. docs/features/tools/tool-use-overview.md:11

• Draft comment:
  The Tool Use Overview now correctly includes the new edit tools (insert_content and search_and_replace) and omits the deprecated append_to_file. This improves completeness and consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

9. docs/features/tools/write-to-file.md:48

• Draft comment:
  The added note regarding reverting changes and suggesting alternatives when 'line_count' is missing or invalid adds valuable clarity to error handling. The explanation is consistent with our safety validations.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

10. docs/update-notes/index.md:5

• Draft comment:
  The update notes index has been refreshed to accurately group release notes for versions 3.14, 3.13, etc. The structure is clear and consistent with our documentation standards.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

11. docs/update-notes/v3.14.0.md:1

• Draft comment:
  The release notes for version 3.14.0 clearly document the new features, tool improvements, and bug fixes. The note on deprecating append_to_file in favor of insert_content is especially clear.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

12. sidebars.ts:52

• Draft comment:
  The sidebar configuration now properly includes the new tools (insert_content and search-and-replace) and removes the deprecated append_to_file entry. The ordering within the Tool Use category is consistent with our documentation.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

13. docs/features/footgun-prompting.md:13

• Draft comment:
  Typographical suggestion: The admonition block starts with '::::info' and ends with '::::'. Typically, these blocks use three colons (e.g., ':::info' and ':::') for consistency with common markdown syntax. Please adjust the number of colons for a uniform look.
• Reason this comment was not posted:
  Comment was on unchanged code.

14. docs/update-notes/v3.14.0.md:56

• Draft comment:
  Inconsistent quoting style for 'TASK RESUMPTION': line 15 uses straight quotes ('TASK RESUMPTION') while line 56 uses curly quotes (‘TASK RESUMPTION’). Please choose one style for consistency.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

Workflow ID: wflow_wSJErFddiMRTb4Jh

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}