GitHub Copilot vs Kilo Code: what developers actually say
Based on 690 opinions on Hacker News from developers who discussed these two, most of them first-hand users.
Kilo Code comes out ahead on approval, 63% from 31 opinions against 42% from 659 for Copilot, and on cost sentiment, 4 positive to 1 negative against 60 to 80. Copilot's weak spots are code quality, 38 positive to 93 negative, and reliability, 14 to 54, while its UX is nearly even at 48 to 50. The Kilo lead rests on thin evidence: 21 authors, no 90-day approval figure, and no month above 6 opinions. Copilot wins the only explicit head-to-head and is the safer pick when work already licenses it or you want many models in one harness; Kilo fits if you want an open, low-cost, customizable tool and can accept the small sample.
When developers explicitly said they prefer one or switched: 1 picked GitHub Copilot, 0 picked Kilo Code.
Choose GitHub Copilot if
- Your workplace already provides Copilot
- You want several model providers in one tool
- You prefer the option with far more user reports
Choose Kilo Code if
- You want lower cost and more model options
- You want to switch providers mid-task
- You want an open, customizable harness
Where each one wins and loses
Why developers switched
Picked GitHub Copilot
Picked Kilo Code
No explicit switches recorded.
Summaries are paraphrased. Each links to the original comment.