←back to thread

677 points meetpateltech | 6 comments | | HN request time: 0.447s | source | bottom
1. Yhippa ◴[] No.45117702[source]
Naive question: is using Claude Code from the command line or in these tools like VSC or Zed different from using it in the native app on a desktop? Is that because it has access to your codebase?
replies(5): >>45117758 #>>45117765 #>>45117792 #>>45117917 #>>45119030 #
2. ascorbic ◴[] No.45117758[source]
Not tried with Zed yet, but in VS Code it's mostly the same except you can view the diffs in the editor, and can give context from the open file. I think it can also see errors from the editor.
3. dostick ◴[] No.45117765[source]
After having troubles with Claude desktop not properly updating canvas document, I found that apparently Claude Code is same as desktop one plus you can use it not just for code but documents in VS Code.
4. james_marks ◴[] No.45117792[source]
Not just your codebase, but also a wide range of *nix tooling. Night and day to working on the CLI vs an IDE.
5. ◴[] No.45117917[source]
6. josefrichter ◴[] No.45119030[source]
In Elixir/Rails (and newly React) world you can connect Clade Desktop to Tidewave, which gives you pretty close integration with codebase and CLI tools. That makes the experience somewhat similar to running Claude Code in editor's terminal, or now directly connected in Zed.

I think basically all these tools are trying to integrate all the stuff together and find the best way to do that, so that you don't need to be copy-pasting stuff around, jumping between tools, etc.