superset

superset-sh/superset

Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 12, 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 14,485 → 14,907 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

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
15.1K
Forks
1.3K
Open issues
927
Watchers
37
Primary language
TypeScript
License
Other
Created
Oct 21, 2025
Owner
superset-sh · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 213 startups in the directory ship primarily in TypeScript.

Topics

#ade#agent#agent-orchestration#ai-agents#ai-coding#claude-code#cli#codex#coding-agents#cursor-agent#developer-tools#devtools#ide#macos#opencode#orchestration#parallel-agents#terminal#worktrees#yc-backed

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 40%, hosted offering 65%. 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.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.97. 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-12This is the badge for superset-sh/superset, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/superset-sh/superset.svg)](https://ossean.com/superset-sh/superset)

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.