Side-by-side comparison · apps and saas
GPT Engineer vs Kimi
What we have checked about each, line by line. Every value shows where it came from and when we last confirmed it.
Apps and SaaS
GPT Engineer
CLI platform to experiment with codegen.
Apps and SaaS
Kimi
Try Kimi K2.6 to build stunning, full-stack websites, use Agent Swarm for massive tasks, turn documents into reusable skills, and explore Claw Groups preview for agent teamwork.
Checked facts
Line by line
| Measure | GPT Engineer | Kimi |
|---|---|---|
| Days since the last commit | 530 | Not checked yet |
| GitHub forks | 7,273 | Not checked yet |
| GitHub stars | 55,003 | Not checked yet |
| Days to a first reply on issues | 466.9 | Not checked yet |
| Open issues | 32 | Not checked yet |
| Releases in the last 90 days | 0 | Not checked yet |
A line appears only when at least one record has a value we confirmed from a source. Values we have not confirmed are left out, never guessed. Records of different types share fewer lines.
Add a third
Compare with one more record
How this works
Share it, or build your own
This page works for any two or three records in the directory, of any type. The link stays the same whichever order you name them in, so you can share it as it is. Change the records in the address, for example /directories/vs/claude-code-vs-cursor, or start from our editorial comparisons.