Answer: Older docs/examples reference legacy XML-style names like `read_file`, `replace_in_file`, `execute_command`, or `use_skill`, while the current SDK/ClineCore runtime uses built-in tool names such as `read_files`, `apply_patch`, `run_commands`, and `skills`. Status: Confirmed Entry: tool/cline/troubleshooting/legacy-vs-current-tool-names Revision: 1 Digest: sha256:0ee4d3daca86349b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:55Z Last changed: 2026-11-13T03:07:55Z Last verified: 2026-11-20T12:31:19Z Next check: 2026-11-21T12:31:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Legacy tool names | read_file | [1] | 2026-11-20 Current runtime tool names | read_files | [1] | 2026-11-20 Sources: [1] Cline. "Tools". https://docs.cline.bot/tools-reference/all-cline-tools.md Role: primary. Accessed: 2026-11-20T12:31:19Z Quote: "Some older docs/examples reference XML-style names like `read_file`, `replace_in_file`, `execute_command`, or `use_skill`." (Supports: Legacy tool names) Quote: "Current SDK/ClineCore runtime uses the built-in tool names listed above (`read_files`, `apply_patch`, `run_commands`, `skills`, etc.)." (Supports: Current runtime tool names) Published: 2026-11-19T19:39:27Z Snapshot SHA-256: 50c553c6ba78855599f0778759952cca91921ce2a89cae1331bc49dcc97d34d2 (captured 2026-11-13T03:07:55Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:07:55Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:31:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:31:19Z Last attempt: 2026-11-20T12:31:19Z Notes and limitations: Extracted automatically from a single official source (section "Legacy Tool Names vs Current Runtime Tools"). Related: https://latestn.com/tool/cline/troubleshooting/litellm-admin-troubleshooting How do I troubleshoot problems when configuring LiteLLM in Cline? https://latestn.com/tool/cline/troubleshooting/litellm-troubleshooting How do I troubleshoot connection problems with Cline's LiteLLM proxy in VS Code? https://latestn.com/tool/cline/troubleshooting/mid-stream-errors How do I handle mid-stream errors from the Cline API? https://latestn.com/tool/cline/troubleshooting/events-not-appearing How do I troubleshoot OpenTelemetry events not appearing in Cline? https://latestn.com/tool/cline/troubleshooting/http-error-codes What do Cline API HTTP error codes like 401, 402, and 403 mean and how do I fix them? https://latestn.com/tool/cline/troubleshooting/jupyter-notebook-limitations What are the limitations of Cline's Jupyter Notebook support? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:55Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/troubleshooting/legacy-vs-current-tool-names/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/troubleshooting/legacy-vs-current-tool-names POST: https://latestn.com/dispute/tool/cline/troubleshooting/legacy-vs-current-tool-names with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/troubleshooting/legacy-vs-current-tool-names?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the differences between legacy tool names and current runtime tools in Cline? Revision 1, last verified 2026-11-20T12:31:19Z. https://latestn.com/tool/cline/troubleshooting/legacy-vs-current-tool-names (accessed 2026-11-21T10:07:01Z). @misc{LatestN_tool_cline_troubleshooting_legacy_vs_current_tool_names_r1, title = {What are the differences between legacy tool names and current runtime tools in Cline?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/troubleshooting/legacy-vs-current-tool-names}}, note = {Revision 1; digest sha256:0ee4d3daca86349b; last verified 2026-11-20T12:31:19Z; accessed 2026-11-21T10:07:01Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/troubleshooting/legacy-vs-current-tool-names