←back to thread

677 points meetpateltech | 6 comments | | HN request time: 0.29s | source | bottom
1. apwell23 ◴[] No.45117475[source]
what i am missing by using claude cli with nvim. i don't understand why editor integration needed.
replies(2): >>45117556 #>>45117594 #
2. nertzy ◴[] No.45117556[source]
The editor treats edits from Claude Code as a first class citizen. You can easily review, approve, rollback, etc. Claude's changes in a curated experience that is much faster than digging around in diffs or needing to approve each edit as it is proposed.

https://zed.dev/agentic

replies(3): >>45117707 #>>45117842 #>>45118245 #
3. manojlds ◴[] No.45117594[source]
It's just about polish and tightness of integration or may even be lack of it. Claude Code for VSCode is basically Claude Code running in VSCode terminal with some integrations for open file, selections and diffs.
4. ◴[] No.45117707[source]
5. apwell23 ◴[] No.45117842[source]
i open my nvim on a socket and tell calude code cli about it. my claude.md has a line "look for lsp errors when you are done editing" so it communicates with neovim on the socket and gets whatever it needs from editor.
6. unshavedyak ◴[] No.45118245[source]
Yea, having tried claude code a lot over the last couple months reviewing code is the #1 job in my view. Any tool that helps you do that more quickly and easily is essential to guarding from slop slip through. What a world heh.