A
gemini-cli
96.3
108,897 stars · Apache-2.0
AI Agents
langchain leads by 1.6 · narrow
A
96.3
108,897 stars · Apache-2.0
B · leads
97.9
149,766 stars · MIT
gemini-cli versus langchain is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gemini-cli is written mainly in TypeScript; langchain is written mainly in Python. The composite score is 96.3 for gemini-cli and 97.9 for langchain.
langchain has 149,766 GitHub stars to gemini-cli's 108,897, a gap of 40,869 (1.38×). Forks are 14,956 for gemini-cli and 25,149 for langchain. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 95 versus 100.
Push history: gemini-cli was last pushed on 17 November 2026 (0 days ago), and langchain was last pushed on 17 November 2026 (0 days ago). Open issues stand at 739 for gemini-cli (0.007 per star) and 759 for langchain (0.005 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. langchain is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for gemini-cli and 96 for langchain. This is a procurement signal, not legal advice.
In AI Agents, both gemini-cli (108,897 stars) and langchain (149,766 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: gemini-cli is open source, langchain is open source.
langchain is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 5 points (95 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
langchain finishes ahead at 97.9 against gemini-cli at 96.3, a 1.6 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | gemini-cli | langchain |
|---|---|---|
| GitHub stars | 108,897 | 149,766 |
| Forks | 14,956 | 25,149 |
| Open issues | 739 | 759 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.3 | 97.9 |
An open-source AI agent that brings the power of Gemini directly into your terminal.
The agent engineering platform.
langchain has more GitHub stars: 149,766 versus 108,897 for gemini-cli. The gap is 40,869 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both gemini-cli and langchain as self-hostable. Confirm each project's deploy docs before you plan a migration.
gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. langchain is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
langchain scores 97.9 and gemini-cli scores 96.3. This page calls that a narrow lead for langchain.