[stpedgwdgfhgdd]

This is the dream, but we are not yet there. For any reasonable complex code base, CC needs guidance, like avoiding duplicate code/use library function. Write more tests. Sometimes there is a much more elegant solution for a problem. Claude will find it, but you need to hint and ask.

If people use Claude without a critical eye, our code bases will grow immensely.

[bapak]

> If people use Claude without a critical eye, our code bases will grow immensely.

Sounds like the baseline for programming in teams. People are more likely to write their own helpers or install dependencies than knowing what's already available in the repository.

[kasey_junk]

With most of the async Claude code systems I’ve tried you’d do iterations like this as part of code review.

And fwiw I use cc with a complex code base and an async workflow like the author describes daily.

[nojs]

The problem with working at the PR level is it massively sacrifices speed if you need to make small tweaks yourself interspersed with CC’s work, which seems to be the best workflow atm, at least for nontrivial changes.

Local git worktrees are way faster.

[kasey_junk]

Yeah. I don’t think it’s an all or nothing thing. Sometimes a change is best done all through async iterations, sometimes you want to be interactive and sometimes agent wrangling is just not worth it.

The painful thing for me right now is setting up the agent instructions, permissions and sandboxes varies for each of those use cases and the tooling around that is very rudimentary right now.

[barrenko]

It's a lot of work, but it's a different type of work.