paperclipai/paperclip

Prefer upstream unless you specifically need a pinned snapshot. This fork shows no unique feature work and is far behind an active upstream, so it is better as a starting point for custom development than as an adoption target.

Prefer this fork if you want Paperclip with CLI-centric agent administration and customized onboarding/auth workflows. Prefer upstream if you want the newest fixes, UI work, and the lowest maintenance burden, because this fork is materially behind upstream.

Choose this fork if you care most about RBAC, superadmin bootstrap, and project-local/plugin workflows. Choose upstream instead if you want the newest Paperclip runtime and UX work with less maintenance overhead.

Choose this fork if your main workflow is conversation-centric and you want custom wake routing plus stronger thread-management UX. Choose upstream if you want the broadest, freshest Paperclip release with lower maintenance burden.

Choose this fork only if you want a clean, low-drift starting point. If you want the latest Paperclip features or an actively differentiated fork, upstream is the better choice.

Prefer upstream unless you specifically need this older 83-commit-lag snapshot. This fork adds no visible capabilities and is best viewed as stale relative to the active project.

Prefer upstream unless you specifically need this older snapshot. This fork adds no visible capability, is 294 commits behind, and looks more like a stale mirror than a differentiated distribution.

Prefer upstream unless you explicitly need this pinned snapshot. The fork adds no clear product value and is materially stale, so it is only attractive as a short-term maintenance fork.

Prefer this fork if you want a more opinionated agent-operations layer with added skills, workflow automation, and lower-cost defaults. Prefer upstream if you want the newest Paperclip changes and less maintenance overhead.