Hey, you’re not doing anything wrong. Cloud agents just aren’t built for quick, simple tasks like hiding a menu link.
A few things to keep in mind:
-
Cloud agents always run in Max Mode, so every step like reading files, making edits, and running terminal commands counts as a separate iteration. There’s also startup overhead like spinning up the VM, cloning the repo, and setting up the environment. For something that takes seconds locally, that overhead ends up being most of the time.
-
For simple, one-shot changes, use a local agent. It’ll be faster and cheaper. Cloud agents are best for longer tasks you can parallelize, where you want to hand it off and come back later.
-
The team knows about cloud agent performance and is tracking it. I don’t have a timeline to share, but reports like yours help with prioritization.
Related threads if you want more context:
- Cloud agent runtime performance too slow for NextJS React app
- A Cloud Agent run a not-so-difficult task for 11 min, 2.2M tokens, counted as ~100 requests?
Let me know if you’ve got questions about when cloud vs local makes sense for your workflow.