Whatever selected agent supports: subscription login, API key, local model, etc. | Best when ACP se…
انتشار: 2026/07/14 22:07 UTC
Whatever selected agent supports: subscription login, API key, local model, etc. | Best when ACP server/agent runs where repo lives | Whatever backend supports: AGENTS.md, CLAUDE.md, skills, etc. | Backend-dependent | ACP may not expose every slash command, rich TUI feature, hook, auth flow, skill, or subagent visualization; adapter quality varies || ECA / eca-emacs | Full | Yes, contextual ghost text; not clearly equivalent to Copilot NES | Automatic, including repo map/workspace context | Emacs client → external ECA server → provider API | Yes | Usually provider API keys or local/OpenAI-compatible models | Server can run near project, but remote setup must be planned | ECA project config, prompts, tools, MCP | Supported depending on version/config | Does not inherit Claude Code, Codex, or Copilot CLI-specific features, subscription integrations, commands, or skills || claude-code-ide.el | Full | No | Automatic | Runs real Claude Code and augments it through MCP/WebSocket integration | No; Claude only | Claude Code-supported login/subscription or Anthropic API config | Best when Claude Code runs where repository resides | CLAUDE.md, skills, hooks, MCP, custom agents | Yes, through Claude Code | Claude-only; no autocomplete; TUI-only features may not map directly into Emacs || claude-code.el | Backend; full | No | Automatic | Runs real Claude Code in terminal/comint/eat/vterm | No; Claude only | Claude Code authentication | Strong when launched on remote host | Full Claude Code config ecosystem | Yes, if exposed by CLI | Less structured native review/navigation than IDE-oriented clients || emacs-gravity | Backend; full | No | Automatic | Structured Emacs frontend over Claude Code sessions | No; Claude only | Claude Code authentication | Depends on where Claude Code runs | Full Claude Code config ecosystem | Yes; explicitly visualizes agent trees | Newer integration; Claude-only; must keep pace with Claude session structures || emacs-claude-agent | Backend; full | No | Automatic | Direct frontend around Claude Code process | No; Claude only | Claude Code authentication | Backend placement determines remote behavior | Claude Code instructions/config | Backend-dependent | Smaller ecosystem; overlaps with other Claude integrations || claudemacs | Backend; full | No | Automatic | Manages multiple external agent CLI sessions | Multiple CLIs | Selected CLI authentication | Generally strong when CLI runs on remote host | Whatever selected CLI supports | Backend-dependent; multiple sessions | Primarily a session/process manager rather than one deeply structured integration || emacs-codex-ide | Full | No | Automatic | Native Emacs client communicating with codex app-server | No; Codex only | Codex/ChatGPT login or OpenAI API, depending on config | App-server must run with correct project/filesystem access | AGENTS.md, Codex config, exposed skills/features | Codex-dependent | Newer project; app-server features still need explicit Emacs-side rendering || codex.el | Full | No | Automatic | Codex app-server mode or terminal backend | No; Codex only | Codex authentication | Terminal mode often easiest remotely; app-server placement matters | Codex project instructions/config | Codex-dependent; multiple sessions | App-server and terminal backends may differ in behavior and available UI || codex-cli.el | Backend; full | No | Automatic | Runs real Codex CLI in project terminal | No; Codex only | Codex authentication | Strong if installed on remote server | Full CLI-visible Codex config | Codex-dependent | Minimal native integration; fewer structured/clickable objects || copilot.el | Partial chat/editing; not full CLI Agent Mode | Yes; inline completion and genuine NES | Completion is contextual; agent autonomy limited | Emacs client → official Copilot language server → GitHub service | Multiple Copilot-hosted models, not arbitrary providers | GitHub Copilot subscription or enterprise seat | Node/language server needs project access | Copilot instructions/skills where exposed | No full
پستهای تلگرام — /r/emacs
Vague theme for emacs built on top of Modus themesHi all,I recently made the emacs port for the excellent vague theme. It is built on top of Modus themes and I've been daily driving it since then.Happy to hear feedback/suggestions. It would be great if people could try it and report issues on the issue tracker.Main repository: github.com/paniash/modus-vaguehttps://red…
Update Reddigg is now a fullblown reddit clientJust an update for one or two users of my reddigg package (github.com/thanhvg/emacs-reddigg). It has become a flullblown client. Beside reading, you should be able to submit a post, make a comment, upvote, downvote, edit your post, your comment... There is a dedicated minor mode which some of the users have been asking for but I was too lazy. Key bindings are not complete yet though.If you can see this post it means it works because I did it through reddigg.Okay here is the fine print:- you must have browsel github.com/dmgerman/browsel, btw many thanks to the creator of this awesome package.- you must have a reddit account, have your browser open old reddit and allow browsel to run on that tab.- reddigg will use browsel to drive the interaction with reddit through your browser.- llm code but lgtm :P- Don't think so but reddit might ban me and you. they closed the free access to old reddit recenly which led me to make this changeredd.it/1vqy5pn@r_emacs
What is emacs canvas and how does it work?Emacs Canvas (patch) on redditFrom my understanding of how programs draw to screens, it seems that Emacs canvas provides a video buffer to external graphics programs or libraries so that instead of drawing to the regular screen, they draw inside a video buffer created and displayed within Emacs.The equivalent I can think of is the case of VNC or Xpra where a program uses a $DISPLAY which is rendered remotely on the client.Would that mean that getting a program to run in a canvas would be along the lines:(emacs-create-canvas height width buffer-name "/usr/bin/random-gui-program -param 1 -param -2")?I suppose there would be some additional parameters relating to passing key strokes, controlling window movement and size etc.redd.it/1vqtjmi@r_emacs
emado: manage 100k+ markdown entries from Emacs at native speedredd.it/1vqtodk@r_emacs
Emacs AI assistants (results)Disclaimer: I'm not a heavy AI user, I'm just trying to understand the differences between AI harnesses specifically for Emacs and if using the real harness claude-code would even make a difference.I like agent-shell more than anything else I've tried in Emacs including ECA which I recently configured but never used for anything.Today I decided to give them both a try to a relatively complicated task (reviewing code) and oh boy, ECA was not only better but thousands of times better.They both are using the same model and configs so I feel I'm missing something here, agent-shell failed to trigger simple things as bufffer overflows while ECA correctly pointed out the issue and fix. I'm I missing something here? Anybody had experience with this kind of things?redd.it/1vqr0f9@r_emacs
Tempted to try Meow over Evil, but worried about IntelliJ / cross-editor muscle memoryI'm coming back to Emacs and I'm playing with Doom and vanilla configurations. I'm really tempted to ditch Evil and give Meow a proper shot. The selection-first model and native Emacs integration make a lot of sense to me, but I have one major hesitation: portability.At work, we use IntelliJ (I enabled IdeaVim). Sticking with Evil on Emacs means my muscle memory stays aligned between Doom/Emacs and my IDE. If I switch to Meow, I'm worried about the context-switching friction during the workday.Has anyone managed to port Meow-style bindings/selection mechanics to IntelliJ or found a solid way to bridge that gap? Would love to hear how others handle using Meow alongside non-Emacs tools at work.Thanks!redd.it/1vqkogz@r_emacs