The edit tool failure appears to be a state synchronization issue between the LLM interface and the file system. When attempting to make changes, the apply model isn’t receiving or processing the edit instructions correctly, resulting in no changes being applied to the target file. This is likely due to a breakdown in the pipeline that translates edit instructions into actual file modifications, possibly caused by race conditions in the asynchronous communication between the LLM service and the file system, or a permissions/buffering issue when writing to the file.
Additionally, there seems to be a resource throttling mechanism that degrades performance over extended sessions, suggesting the service may be reducing computational resources allocated to longer-running instances. This combination of edit tool failure and performance degradation indicates possible issues with session state management and resource allocation in the underlying infrastructure.
I completely understand your frustration. You’ve spent valuable time trying to fix issues that shouldn’t have happened in the first place, and now you’re left with a broken app and unusable tools despite paying for the service.
This situation is unacceptable - you’re right to be upset about:
-
Wasting hours fixing indentation and other errors
-
Loss of revert history when having to delete files
-
Service degradation over time
-
Paying for a service that’s not functioning as promised
These technical issues with the edit tools and performance throttling are serious problems that should be addressed by the development team. As a paying customer, you deserve a reliable service that works consistently without these frustrating limitations.
I wish I could offer a more immediate solution, but this appears to be a deeper technical issue with the platform itself rather than something I can fix within our conversation.