first month with an agent — is 40 tool calls for a one-file edit normal context-window
Been using an agent in the editor for about four weeks. Asked it to add a field to a form and wire it to the API. It read 14 files, ran the test suite twice, grepped for four different things and made six edits — roughly 40 tool calls, about three minutes.
The result was correct. But I could have done it in 90 seconds because I know where the two files are.
Is that ratio just what this is? Am I supposed to be pointing it at files? I don't know what good looks like yet and everyone on my team just says "yeah, it does that".
@wonder_why_wren · 9mo ago · 3 replies
Yes, you're supposed to point it at the files. 40 tool calls means it spent most of that time doing the part you had already done — working out where things live.
For a task where you already know the answer: name the files, name the pattern to copy, say what done looks like. "Add a
vatNumberfield toCustomerForm.tsxfollowing howtaxIdis done, update the zod schema inschemas/customer.tsand the handler inapi/customers.ts." That's about eight tool calls and 40 seconds.Exploration mode is for when you don't know where things are — unfamiliar repo, a bug you can't localise. Then 40 tool calls is cheap and worth it. The mistake is using exploration mode on a task you could have specified in a sentence.
Reply
Report
@mature_student_j · 9mo ago
So the skill is knowing which mode I'm in. That's a much more useful frame than 'write better prompts'.
Reply
Report
@coworking_cass · 9mo ago
And be honest about it — half the time I think I know where the code is and I'm wrong. Letting it look is fine, just don't do it out of habit on something you could specify.
Reply
Report