How do you like to work with AI coding agents?

by•

There seems to have two types of developers:

  • Human in the loop: Those who like to control the behavior of their agents as it works, looking at the context usage, reading reasoning blocks, and approving individual file edits.

  • Agent first: Those who prefer to review the output of agents, rather than individual actions, and run one or more sessions in parallel.

What type of developer are you when working with AI coding agents?

For context, when launched their new extension , with parallel agents, inline diff reviewer, and multi-model comparisons, some users actually wanted more control back.

While the team is working on , like better diffs before you approve and permission flow fixes, I'm curious about your point of view.

How do you like to work with AI coding agents?

770 views

Add a comment

Replies

Best

I'd probably consider myself a "High-level Human-in-the-Loop." I don't approve every single edit, but I prefer to keep an eye on the overall direction.

Since I work a lot with a fast-evolving runtime like Bun, AI models can sometimes be a bit behind the latest updates, so some human oversight is still quite necessary for me. Plus, I notice agents often tend to over-complicate things - like adding too many CSS classes where clean cascading would do the job.

For me, a hybrid approach feels like the right balance: letting the agent do the heavy lifting, but stepping in manually when it's just faster (and cheaper on tokens) than writing yet another prompt.

agent can fast track concept testing. but i still prefer to most of the details to avoid biases and errors.

I'm a bit frustrating about the new version of Kilo Code. The agentic workflow make me completly blind of what's going on. Tokens running and at the end of the task I'm not sure that agent was handled the given mission in the right way. Still working with the previous "old school" version that I can interrupt / correct on each step that I desire.

appreciate the feedback!

The new extension launched pushed hard on capability - parallel agents, inline diff reviewer, multi-model comparisons. Some of that came at the cost of visibility and control. The team has worked on rebalancing it with , like expandable reasoning blocks, better diffs before you approve, and permission flow fixes.

This is a good time to check back. The experience is meaningfully different now. cc

Human in the loop 100%
But mostly for my benefits, as I'd like to learn as a PM how things are actually implemented :))

people said the same thing about AI writing copy and now half the internet runs on it without a second look. trust builds with consistency not permission screens

Both modes matter at different stages, HITL when exploring a new domain, agent-first once the patterns and guardrails are trusted. The teams that get stuck are the ones who stay in review-every-line mode indefinitely. Context richness usually determines when you can safely let go.

Coming into the convo a bit late, but I'm also one of the "it's got to have both parts". The Agent can type really fast, which is great...but having the human present and running the show is important - I'd say even vital - to getting a quality product.

I look at the agents like a hammer. You can build a house without a hammer, but it's going to take a lot longer. The agents - being a "tool" in the toolbox - make the project faster and (at least for me) better quality without the human-induced errors likely when we're tired, distracted, hungry, etc.

It gets you to around 60 percent profiencey. And its good as a tool.

I prefer a hands-on workflow because the projects I’m working on tend to be detailed and change as they develop. Staying involved in the steps lets me catch issues early, adjust direction on the fly, and make sure important context is incorporated before the work moves too far ahead. For me, that reduces the chance of agents completing a large amount of work that later has to be reworked because a detail, assumption, or workflow decision was missed.

I personally prefer Human in the loop since it helps control the quality output of my code. But AI still useful a lot in lots of basic and automation steps