Paperclip AI on GitHub: The paperclipai/paperclip Repo Explained (Stars, Structure, How to Read It)

The Paperclip AI GitHub repository, github.com/paperclipai/paperclip, is where the whole project lives: the server, the dashboard, the CLI, the adapters and the docs. It is MIT licensed, it went from zero to one of the fastest-growing repositories in GitHub history in the spring of 2026, and it is the only source of truth for what Paperclip does this week. This post explains what is in the repo, how to read it, and how to tell it apart from look-alikes. For the product itself, see our complete Paperclip AI guide.

What the repository is

paperclipai/paperclip is the source code for Paperclip, an open-source platform for running a "company" of AI agents with an org chart, tickets, budgets and approvals. The repository is maintained by Paperclip Labs, Inc. and was started by the pseudonymous developer known as @dotta. The README headline is "The open-source app everyone uses to manage agents at work."

Key facts as of September 2026:

Item	Value
URL	github.com/paperclipai/paperclip
License	MIT (copyright 2026 Paperclip Labs, Inc.)
Stars	Roughly 85,000
Forks	Roughly 15,000
Language	TypeScript (Node.js server, React UI)
Database	PostgreSQL (embedded locally by default)
Latest release	v2026.916.1 (September 21, 2026)
Website / docs	paperclip.ing / docs.paperclip.ing

Star growth timeline

Search interest in "paperclip github" is high partly because the star chart itself became a story. The rough sequence:

• Early March 2026: public launch. The launch post on X drew around 2.4 million views.
• Three weeks in: past 30,000 stars.
• First month: roughly 44,000 stars, putting it among the fastest month-one climbs on GitHub.
• June 2026: around 70,000 stars, 13,000 forks, 100-plus contributors.
• September 2026: roughly 85,000 stars and 15,000 forks.

Two caveats when you read those numbers. First, stars measure attention, not production use. Second, a large share of early stars came from the "zero-human company" framing in the launch, which is a much bigger claim than what most people actually run. The honest signal is the release cadence and the issue tracker, both of which are active.

How the monorepo is laid out

Paperclip is a pnpm monorepo. The exact folder names shift between releases, so treat this as a map of responsibilities rather than a directory listing:

• Server. The Node.js API. Owns companies, agents, tickets, goals, heartbeats, budgets, approvals and the audit log. Talks to Postgres. This is what listens on port 3100.
• UI. The React dashboard: org chart view, ticket board, cost reports, approvals inbox, activity log.
• CLI. The paperclipai command. Handles onboarding, install, test-drive, start and stop, updates and admin tasks.
• Adapters. One module per runtime: Claude Code, Codex, Cursor, OpenClaw, Hermes, OpenCode, Pi, Gemini, plus the generic process and HTTP adapters.
• Plugins. The plugin host and first-party plugins such as Linear sync and Slack or Telegram notifications. Plugins run out of process with capability-gated access to the server.
• Shared packages. Types, schema definitions and client libraries used by the server, UI and CLI.
• Docs. Source for docs.paperclip.ing.
• Tests. Vitest for unit and integration tests, Playwright for browser tests.

If you only read three things, read the README, the adapter for the runtime you use, and the database schema. The schema is the fastest way to understand what a "company," an "agent" and a "ticket" actually contain.

What to watch in the issue tracker

The issues tab is more useful than the star count for judging whether Paperclip fits you. Filter by the label for your adapter (for example OpenClaw or Claude Code) before you commit to a runtime, because adapter bugs are the most common category. Watch the pinned issues for known breaking changes in the current release. And search closed issues before filing: with thousands of tickets, most setup problems, especially around Postgres, ports and Node versions, have already been answered. Discussions is the right place for design questions and "how would I model this company" threads, and the maintainers respond there regularly.

Reading releases and version numbers

Paperclip uses calendar versioning. v2026.916.1 means 2026, day 916 in the project's own scheme, patch 1. In practice: newer number, newer build. Releases ship frequently, often several per week, and each release page lists breaking changes at the top. Before you update a production instance, read that section, because adapter configuration has changed shape more than once since launch.

The update path for a normal install is the CLI (the installer script or the paperclipai command), not a git pull. Git pull is only for people running from source. We cover updates and rollbacks in the hosting and self-hosting guide.

Is this the official repo? (forks and look-alikes)

Because the project got popular fast, there are thousands of forks and a handful of similarly named repositories. Three checks:

1. The owner is paperclipai. The canonical URL is github.com/paperclipai/paperclip. The website paperclip.ing links directly to it, and the npm package is paperclipai.
2. The install script is served from paperclip.ing. The README's install method downloads install.sh from paperclip.ing and verifies a SHA-256 checksum. Any repo telling you to curl a script from a different domain is not the official project.
3. Check the fork badge. GitHub labels forks with "forked from paperclipai/paperclip" under the repo name.

One repository people confuse with the main project is agencyenterprise/paperclip-ai, described as "open-source orchestration for zero-human companies." It shares the name and the concept but it is a separate codebase from a different organization, with a much smaller community. If you are evaluating "Paperclip AI" the way most people mean it, you want paperclipai/paperclip. Also unrelated: paperclip.inc, a different company with a paid product, and ClipMarts.com, a third-party marketplace.

Contributing and the community

The repo accepts pull requests, and with more than 100 contributors, a lot of adapter and plugin work has come from outside Paperclip Labs. Contributing guidelines live in the repo. The usual path is: open an issue or discussion first for anything larger than a bug fix, fork, branch, run the Vitest suite, and open a PR against main.

The community lives in three places:

• GitHub Discussions and Issues for bugs and feature requests. The issue count is in the low thousands, which is normal for a project this size and this young.
• Discord for real-time help.
• X at @papercliping for release announcements.

There is also a community index, gsxdsm/awesome-paperclip, that lists third-party plugins, company templates and adapters. It is the best starting point if you want to see what other people have built on top of the platform, and we go through the ecosystem in more detail in Paperclip use cases, templates, skills and ClipMart.

Running from source vs installing

Most users should not clone the repo. The supported paths are the one-line onboard command or the checksum-verified install script:

npx paperclipai onboard --yes

Clone the repo if you want to modify the code, write an adapter or plugin, or run the test suite. That path requires Node.js 24.11 or newer and pnpm 9.15 or newer:

git clone https://github.com/paperclipai/paperclip.git
cd paperclip
pnpm install
pnpm dev

The dev command starts the server, the UI and an embedded Postgres. Full install options, including Docker, are in How to install Paperclip AI.

FAQ

Is Paperclip AI really open source?

Yes. The code is MIT licensed, which allows commercial use, modification and redistribution. Paperclip Labs plans a hosted version, but the self-hosted software is free.

How many GitHub stars does Paperclip have?

Roughly 85,000 as of September 2026, up from about 70,000 in June and 44,000 after the first month.

Who created Paperclip AI?

A pseudonymous developer known as @dotta started it while running an automated trading operation with too many Claude Code sessions open. It is now maintained by Paperclip Labs, Inc. and a community of more than 100 contributors.

What is the difference between paperclipai/paperclip and agencyenterprise/paperclip-ai?

They are separate projects. paperclipai/paperclip is the widely used one with the large community and the paperclip.ing website. agencyenterprise/paperclip-ai is an unrelated codebase from a different organization that uses a similar name and pitch.

Do I need to clone the repo to use Paperclip?

No. Use the npx onboard command or the install script. Clone only if you plan to change the code.