> But where are the professional tools, meant to be used for people who don't want to do vibe-coding, but be heavily assisted by LLMs? Something that is meant to augment the human intellect, not replace it?

Claude Code not good enough for ya?

▲

embedding-shape 18 hours ago | parent [-]

Claude Code has absolutely zero features that help me review code or do anything else than vibe-coding and accept changes as they come in. We need diff-comparisons between different executions, tailored TUI for that kind of work and more. Claude Code is basically a MVP of that.

Still, I do use Claude Code and Codex daily as there is nothing better out there currently. But they still feel tailored towards vibe-coding instead of professional development.

▲

vidarh 17 hours ago | parent | next [-]

I really do not want those things in Claude COde - I much prefer choosing my own diff tools etc. and running them in a separate terminal. If they start stuffing too much into the TUI they'd ruin it - if you want all that stuff built in, they have the VS Code integration.

▲

Havoc 10 hours ago | parent | next [-]

Mind elaborating a bit on the diff tool / flow you’re using? Trying to follow along better with what CC is doing

	▲	jbs789 4 hours ago \| parent [-]
		Claude code run in a VS Code terminal window pops up a diff in VSCode before making changes. Not sure if that helps. I do have the Claude Code extension installed too. I find the flow works bc if it starts going off piste I just end it. Plus I then get my pre-commit hooks etc. I still like being relatively hands on though.

▲

embedding-shape 16 hours ago | parent | prev [-]

Me neither, hence the stated preference for something completely new and different, a stab in the different direction instead of the same boring iteration on yet another agentic TUI coder.

▲

pdntspa 6 hours ago | parent | prev | next [-]

IntelliJ's AI service as a PR summarizer that I have found very helpful

▲

johnfn 16 hours ago | parent | prev | next [-]

> Claude Code has absolutely zero features that help me review code

Err, doesn’t it have /review?

▲

victorbjorklund 16 hours ago | parent | prev [-]

What’s wrong with using GIT for reviewing the changes?

▲

embedding-shape 14 hours ago | parent [-]

Are any of them integrated with git? AFAIK, you'd have to instruct them to use git for you if you don't want to do it manually.

Imagine a GUI built around git branches + agents working in those branches + tooling to manage the orchestration and small review points, rather than "here's a chat and tool calling, glhf".

	▲	KronisLV an hour ago \| parent \| next [-]
		> Are any of them integrated with git? All of the models that can do tool calls are typically good enough to use Git. Just this week I used both Claude Code and Codex to look at unstaged/staged changes and to review them multiple times, even do comparison between a feature branch and the main branch to identify why a particular feature might have broken in the feature branch.
	▲	zer0tonin 16 minutes ago \| parent \| prev [-]
		Aider is integrated with git