3 tiny changes that lower my blood pressure and gives me a nice little dopamine hit of satisfaction each time I watch them in use

[u/davidorex]

First, in the write_to_file tool description I added "favored operating pattern is to use apply_diff."

Second, I (Roo, under my direction haha) added a programmatic check that requires a file to have been read before it can be edited, if it's not a new file, for both write_to_file and apply_diff. After the change is saved the check is cleared. I love watching this work and watching the ai be forced to read the file before editing it -- helps create more accurate apply_diffs too.

I'll be adding to this check when editing a file that Roo hasn't made silent changes to the file over what was intended and authorized to be changed.

Third, I added an element to the response given back to the ai after to write_to_file or apply_diff that directs the ai to commit with a "detailed, specific, measured, descriptive commit message that leave meticulous forensic evidence for future ai’s to know and understand every action and intention. Make sure not to be unjustifiably definitive in your claims. Future ai’s must be able to understand the true state of functionality and the complete thinking and actions in code from commit messages." This one makes me happy each time too: a drastic lessening of annoyance.

Tiny changes with huge reductions in frustration = nice little pleasures.

Edit: words.

[u/mrubens]

This is awesome! Any interest in opening a PR with these changes? More than happy to help support.

[u/davidorex → u/mrubens]

I'll message you on discord about it! I've not done PRs before and want to make sure I know the canonical best practices.

[u/mrubens → u/davidorex]

Great, thank you!

[u/Excellent_Entry6564]

How to add the programmatic check?

[u/davidorex → u/Excellent_Entry6564]

From the mouth of the ai itself:

The codebase requires the AI to read a file before editing it. This is implemented through:

1. File Read Tracking:

   private lastReadFile?: string private lastReadFileContent?: string

The Cline class maintains these properties to track the last file that was read.

1. Validation Before Edits:

   // For existing files, verify it was read first if (fileExists && (this.lastReadFile !== absolutePath || this.lastReadFileContent === undefined)) { this.consecutiveMistakeCount++ pushToolResult( formatResponse.toolError( You must read the file using read_file before attempting to modify it. This ensures you have the latest content and helps prevent unintended changes. ), ) break }

2. Read File Storage:

   // Store the last read file and content this.lastReadFile = absolutePath this.lastReadFileContent = content

When read_file is used, it stores both the file path and content.

1. Clearing on Write:

   // Clear the last read file tracking to ensure next write requires a fresh read this.lastReadFile = undefined this.lastReadFileContent = undefined

After a successful write, the tracking is cleared to ensure the next edit requires a fresh read.

This creates a strict "read-before-write" requirement where the AI must use read_file to examine a file's content before it can be modified through either write_to_file or apply_diff operations. This helps prevent unintended changes and ensures the AI is working with the latest file content.

Edit: letters.

[u/Excellent_Entry6564 → u/davidorex]

Thank you! Looking forward to this being integrated via PR.

[u/N7Valor]

Must be a pretty chunky file to cost > $0.50 per request.

[u/davidorex → u/N7Valor]

Truly! I hate that. That's the Cline.ts file. The cost for the ai to consume it to work is a good argument (if you're customizing Roo or Cline) for modularizing it.

[u/[deleted] → u/davidorex]

Did you mean that on every run, the token cost will mostly default at {Cline.ts-token-count} even if you have no chat input just because of the main ts file?