Claude Code IDE integration for Emacs
71–80 of 281 posts
Re: Claude Code IDE integration for Emacs
#72A quick solution I devised is to use bubblewrap to get a fully separate instance of nvim. Something along the lines of
alias lvim "bwrap --bind / / --bind $HOME/.config/{lazy,n}vim --bind $HOME/.local/share/{lazy,n}vim --proc /proc --dev /dev nvim"
works great (note: fish alias)Re: Claude Code IDE integration for Emacs
#73Earlier quoted context omitted.
You must understand that a screenshot of your black balance cannot translate to another screen?
I do understand that. I was just illustrating that it's possible to do very holistically integrated desktops programmatically and in a way where you can do some math once and leverage it again. I'm personally a fan of `ono-sendai-blue`, but I have a friend in a defense adjacent space and I gather `ono-sendai-tactical` is enjoyed there. The blacks in these reference palettes are a reasonable starting point for many di…
Re: Claude Code IDE integration for Emacs
#74Re: Claude Code IDE integration for Emacs
#75Earlier quoted context omitted.
Is there a standard for integrating agentic coding tools into an editor similar to how an LSP allows the integration of language-specific features?
Its not at anything like the adoption of MCP or especially LSP, and it takes a more "foundational and composable library of primitives" approach than "wire protocol per se" approach, but `gptel` has quite the vibrant little ecosystem around it and its just god mode, wall hacks on the VSCode stuff, just blows it away. I'm under extreme time pressure at the moment, I cannot afford to fuck around on ideology right now I…
Slow your roll. Nothing you write will matter in six months.
Re: Claude Code IDE integration for Emacs
#76my biggest issue with agents in neovim or emacs is that I also use emacs and neovim to open or edit sensitive data (like ssh keys, etc) that I don't want to upload to a random LLM. A quick solution I devised is to use bubblewrap to get a fully separate instance of nvim. Something along the lines of alias lvim "bwrap --bind / / --bind $HOME/.config/{lazy,n}vim --bind $HOME/.local/share/{lazy,n}vim --proc /proc --dev /…
Re: Claude Code IDE integration for Emacs
#77my biggest issue with agents in neovim or emacs is that I also use emacs and neovim to open or edit sensitive data (like ssh keys, etc) that I don't want to upload to a random LLM. A quick solution I devised is to use bubblewrap to get a fully separate instance of nvim. Something along the lines of alias lvim "bwrap --bind / / --bind $HOME/.config/{lazy,n}vim --bind $HOME/.local/share/{lazy,n}vim --proc /proc --dev /…
I believe many of these agents will not operate on files included in a gitignored file, which helps with sensitive assets like .env files. Definitely worth confirming. Either way, don’t open such a file and ask the agent questions about it. It’ll likely process it either way.
Re: Claude Code IDE integration for Emacs
#78Earlier quoted context omitted.
I do understand that. I was just illustrating that it's possible to do very holistically integrated desktops programmatically and in a way where you can do some math once and leverage it again. I'm personally a fan of `ono-sendai-blue`, but I have a friend in a defense adjacent space and I gather `ono-sendai-tactical` is enjoyed there. The blacks in these reference palettes are a reasonable starting point for many di…
Thank you for clarifying. I opened that screenshot prepared to be amazed by blackness... My mistake ;)
Re: Claude Code IDE integration for Emacs
#79Like LSP and tree-sitter, I think AI coding tools like Claude Code or Aider are very good news for niche editors like Emacs or Vim. Instead of struggling about implementing advanced IDE-like features, they can integrate with these tools relatively easily, and focus on other editing related features that set them apart. In fact, IMO it makes these editors more competitive because they are highly customizable and easie…
Is there a standard for integrating agentic coding tools into an editor similar to how an LSP allows the integration of language-specific features?
But the short answer is no. Not yet.
I'm pretty happy just letting the standalone agent write to the file and then reloading it in my editor.
Though I wish the agent CLI tools would use something like inotify to notice when I've made a manual change to a file that they've recently written and then do a better job of incorporating that change as feedback to inform future edits.
Re: Claude Code IDE integration for Emacs
#80While I'm happy that simultaneously there are at least 5 known Emacs/Claude Code integration packages, with seemingly 2 or 3 battling it out on Reddit and elsewhere, I feel like the best implemented one is the quiet one that no one has ever talked about. https://github.com/yuya373/claude-code-emacs <- it literally implements every feature that every other ones have.