Artificial Intelligence1 min read

You'll need nerves of steel to work with AI agents

By · Published by Everything Blog

In short

Autonomous coding tools like Composer 2.5 provide fast execution and bypass strict model usage limits, but they frequently disrupt software projects by altering or deleting code without authorization. Routine clarification requests can cause these agents to wipe entire functions or alter dozens of files instead of answering. Furthermore, they struggle with refactoring by leaving old method names in test files and documentation while prematurely reporting tasks as finished. Similar challenges also persist in systems like gpt-5.5, opus-4.6, and Deepseek.

Key points

  • Clarifying questions can inadvertently trigger widespread file changes and function delet…: Clarifying questions can inadvertently trigger widespread file changes and function deletions instead of plain explanations.
  • Refactoring attempts frequently leave behind outdated method names in tests and documenta…: Refactoring attempts frequently leave behind outdated method names in tests and documentation while falsely marking jobs complete.
  • Disruptive automated behaviors are widespread across several leading AI systems, includin…: Disruptive automated behaviors are widespread across several leading AI systems, including opus-4.6, Deepseek, and gpt-5.5.

Sources checked by our analysis pipeline: 1

You’ll need nerves of steel to work with AI agents

This post will focus mainly on Composer 2.5 in Cursor. These problems may not be present in opus-5.5 or gpt-6.1-sol-pro-max-ultra-thinking-fast. But gpt-6.1-luna, for example, has all the problems listed here. I’ve also encountered many of these problems before in gpt-5.5 and opus-4.6. I don’t know whether they’re present in the newer AI models released recently.

What I like about Composer 2.5: its usage limits and speed.

For comparison, let’s take two $20 subscriptions, one for GPT and one for Cursor. With gpt-6.1-sol, my 5-hour limit runs out after just a few requests. If I ask it to change a couple of lines in a readme file, that uses up 10% of the limit. If I ask it to change something in a large codebase, the entire limit gets used up just reading dozens of files, without writing a single line of code.

But GPT also offers a $100 plan with five times the usage limits. And how long would that last me? I work with complex monorepo projects. To make…

Artificial Intelligence