openinterpreter

openinterpreter/open-interpreter · now at openinterpreter/openinterpreter

A coding agent for open models like Kimi K3 and GLM 5.3

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 11, 2026
11 days ago
Ship score
78/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 68,265 → 68,608 (Sep 8 – Oct 20, 2026)
+208 stars in the 28 days to 2026-10-20

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
68.6K
Forks
5.9K
Open issues
21
Watchers
463
Primary language
Rust
Created
Jul 14, 2023
Owner
openinterpreter · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 45 startups in the directory ship primarily in Rust.

Topics

#acp#coding-agent#deepseek#kimi#python#qwen#rust

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 36% (self-hostable 56%, hosted offering 38%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-11This is the badge for openinterpreter/open-interpreter, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/openinterpreter/open-interpreter.svg)](https://ossean.com/openinterpreter/open-interpreter)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.