[cedws]

Could you briefly explain your workflow? I use Zed’s agent mode and I don’t really understand how people are doing it purely through the CLI. How do you get a decent workflow where you can approve individual hunks? Aren’t you missing out on LSP help doing it in the CLI?

[mindwok]

Claude code has a VS Code plugin now that lets you view and approve diffs in the editor. Before it did that, I really don't understand how people got anything of substance done because it simply isn't reliable enough over large codebases.

[phillipcarter]

I managed this (and still do) just fine by using source control. Commits are checkpoints and it's trivial (esp. with AI-assisted CLI) to roll things back if needed. Workflow is all about small diffs, with sessions being fine-grained, not about implementing entire features wholesale. Serialize overall plans for feature work as files in the codebase in the interim.

[gaut]

How is viewing and approving diffs in an editor any less reliable than viewing and approving them through the CLI? It won't make any changes without approval (unless you explicitly grant it auto-approval).

[insane_dreamer]

Before that it showed you diffs in the console, which worked ok.

Claude Code now also has a PyCharm plugin (and probably other JetBrains IDEs) that also shows you diffs in the pycharm editor.

[bananapub]

claude code churns away in a terminal, I have the git repository open in emacs with auto-revert-mode enabled so it reloads files if they're changed under it.

I view the files, and then review the changes in magit, and either approve some or all of them and commit them, or tell claude to do some thing else.

it works astonishingly well.