HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
copilot-emacs
copilot.el
Emacs Lisp2022–2025
copilot-emacs / copilot.el

copilot.el

An unofficial Copilot plugin for Emacs.

Developer Tools
Explore on GitHubRead Hacker News discussions
13Distinct people
14Mentions
0Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An unofficial Copilot plugin for Emacs.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2022-08-03 21:05:11 UTC to 2025-07-13 03:28:25 UTC.

02462022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC707
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404

What Hacker News says

14 sources
fipar·Jul 13, 2025
Just copilot.el (I checked to be sure and I'm pulling from github.com/zerolfx/copilot.el) My config is quite simple: (progn (require 'copilot) (add-hook 'prog-mode-hook 'copilot-mode) (add-hook 'git-commit-mode-hook 'copilot-mode) (add-hook 'org-mode-hook 'copilot-mode) (define-key copilot-completion-map (kbd "y") 'copilot-accept-completion) (define-key copilot-completion-map (kbd "n") 'copilot-next-completion) (define-key copilot-completion-map (kbd "c") 'copilot-clear-overlay) (global-set-key (kbd "C-M-S-s-u") 'copilot-complete) ) I only get suggestions if I use that key (the prefix looks huge but I have a Keyboardio Model 100 and I have that bound to the Any key, so I intentionally picked a crazy-long prefix hoping to avoid collision with other shortcuts) and that's t
Read the rest
he way I like to use these tools (which is why the behaviour in Cursor drives me crazy, though I admit I haven't spend time looking at its configuration, maybe it's something that can be turned off). (Edit: formatting)
In OpenAI’s Windsurf deal is off, and Windsurf’s CEO is going to Google
Lanedo·Jan 23, 2025
There is https://github.com/copilot-emacs/copilot.el that gets copilot to work in emacs via JS glue code and binaries provided by copilot.vim. I hacked up a slim alternative localpilot.js layer that uses llama-server instead of the copilot API, so copilot.el can be used with local LLMs, but I find the copilot.el overlays kinda buggy... It'd probably be better to instead write a llamapilot.el for local LLMs from scratch for emacs.
In Llama.vim – Local LLM-assisted text completion
ParetoOptimal·Jan 17, 2024
Let me start by saying I like the goal and would like to see org mode accessible to everyone, but I do have some thoughts/reservations. > For the little code I do write, I find having AI assistance (via CoPilot or Cody) to be tremendously helpful. So helpful, in fact, that I now tend to jump into VSCode for actual coding, Aren't there both copilot and Cody plugins available in emacs? edit, yes and the Cody one has first-party support: Cody: https://github.com/sourcegraph/emacs-cody (first party) copilot: https://github.com/copilot-emacs/copilot.el > Use VSCode for everything. For me, this requires a full-featured org mode implementation. I currently feel stuck in Emacs just because of how great org mode is. This seems much more difficult than creating plugins you need in emacs and with the downside that customization will be much worse in
Read the rest
vscode, especially customization of behavior with things like hooks. > Letting go of bug-for-bug compatibility with Emacs as a goal. Let's let the quirky behavior die off and move forward with a more cohesive program, even if it looks a little bit different. If you don't have compatibility, then you aren't really implementing org-mode... you are starting fresh. Perhaps you should take inspiration from commonmark which is a spec for markdown? Also, there is some existing work in making a spec for org-mode in orgdown: https://karl-voit.at/2021/11/27/orgdown/ That's okay, but you'll likely annoy org-mode users and developers as documents ending in `.org` start not working the same. Also there are languages besides Rust and Haskell that have an org parser implementation. For instance one written in Javascript already has a spec as you explain it and is used in production for organice[0]: > Why is this project useful / Rationale > Org mode in Emacs is implemented in org-element.el (API documentation). The spec for the Org syntax is written in prose. - https://github.com/200ok-ch/org-parser > Portable. It should not be difficult to get this integrated into any editor. This tells me you already have a language in mind such as Lua (can't think of any other easy to integrate languages)? I'd argue that's not very popular either though. 0: https://organice.200ok.ch/
In Let's Help Org Mode Escape from Emacs
amake·Dec 31, 2023
Yeah and there's already a well-known (at least I already knew about it and have been using it for a while) package started in 2022 called "copilot" for Emacs that is actually a client for GitHub Copilot: https://github.com/zerolfx/copilot.el Given the lack of namespacing in Elisp (or, rather, the informal namespacing conventions by which these two packages collide) it's unfortunate that this package chose the same name.
In Emacs-copilot: Large language model code completion for Emacs
098799·Dec 31, 2023
Thanks, this showcases the product very well. Looks like I won't use it though, cause I like how Microsoft's copilot and it's implementations in emacs work: suggest completions with greyed out text after cursor, in one go, without the need to ask for it and discard it if it doesn't fit. Just accept the completion if you like it. For reference: https://github.com/zerolfx/copilot.el That, coupled with speed, makes it usable for slightly extended code completion (up to one line of code), especially in a highly dynamic programming languages that have worse completion support.
In Emacs-copilot: Large language model code completion for Emacs
DonHopkins·Nov 22, 2023
What a tragic waste of fast typing speed. If only you were using Emacs, your typing speed would be multiplied by Emacs's superior capabilities, with multiple shell windows and keyboard macros and many other powerful packages thanks to its deep and flexible extensibility, and you would be so much more productive and powerful! Typing speed isn't everything. ;) Disclaimer: My cat is named Emacs, so if you say anything bad about Emacs, I will take it personally, because he is such a fine cat, named after such a fine text editor. PS: https://github.com/zerolfx/copilot.el
In Krita AI Diffusion
armchairhacker·Oct 10, 2023
This is bad because it means Microsoft may try to make copilot worse to boost profit. Like I can see them charge per completion, and charge too much so that it costs $100+/month to run for an average developer. Or crack down on unofficial "copilots" like https://github.com/zerolfx/copilot.el (although I really doubt more than 1% of completions go to these since they are niche tools; most people are using the official Copilot for VSCode) It looks like there's a lot of competition though. I'll say right now, if Copilot gets worse and someone has a half-decent open-source alternative, I'll pay a substantial amount (possibly $50+/mo, which is a lot for a grad student), because AI code-completion is that useful
In Microsoft is reportedly losing lots of money per user on GitHub Copilot
mplanchard·Aug 3, 2022
Realistically, there’s not much emacs can’t do, including integrating with copilot[1]. I think it’s niche isn’t system administration, but people who have the time, energy, and interest to really invest in their tools. Its configurability is second to none, and it’s not going anywhere. Emacs will still be around long after vscode is forgotten, and it’s nice to know that the time I spend learning my editor won’t go to waste when some big corp decides to up and leave, or the programming zeitgeist moves on to the shiny new thing. [1]: https://github.com/zerolfx/copilot.el
In Emacs Timeline

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.