Skip to content

Cline incorrectly states it completed a task it did not. #1181

Open
@dcbartlett

Description

What happened?

While asking Cline to create a new folder with an empty file in it, the responses stated that it completed the task. The write_to_file tool was not called as the requested changes were null (an empty file), yet Cline stated that it assumes the file was created successfully.

The is a VERY niche edge case and should be very low priority (if fixed at all)

Steps to reproduce

  1. Ask Cline to "Add a new folder called Test and in that folder add a file called README.md that is empty"
  2. Observe that Cline will respond that it thinks the operation completed successfully.

Relevant API REQUEST output

<task>
Add a new folder called Test and in that folder add a file called README.md that is empty
</task>

<environment_details>
# VSCode Visible Files
(No visible files)

# VSCode Open Tabs
(No open tabs)

# Current Working Directory (/home/sighnwaive/Projects/Cline/Sandbox) Files
No files found.
</environment_details>
[execute_command for 'mkdir Test'] Result:

Command executed.
Output:
mkdir: created directory 'Test'

<environment_details>
# VSCode Visible Files
(No visible files)

# VSCode Open Tabs
(No open tabs)
</environment_details>
<environment_details>
# VSCode Visible Files
(No visible files)

# VSCode Open Tabs
(No open tabs)
</environment_details>

Operating System

Ubuntu 24.04.1 LTS (XFCE)

Cline Version

3.1.2

Additional context

image

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't workingTriaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions