Paperclip
Paperclip turns agent sign-in into one resumable onboarding sequence
Paperclip now starts sign-in when a provider row is chosen, animates the credential card as one sequence, and adds owner-scoped recovery for active login sessions after reload. A release smoke was also aligned with the model-source UI that users actually see.
paperclipai/paperclip PR #12863 is the inspected primary source: “Onboarding: the connect step's sign-in as one continuous sequence.” The related records were inspected as supporting context rather than independent confirmation.
The facts
- paperclipai/paperclip PR #12863 was created 2026-09-05T00:15:44Z and was closed at inspection; its title is “Onboarding: the connect step's sign-in as one continuous sequence.” - paperclipai/paperclip PR #12861 was created 2026-09-05T00:07:23Z and was open at inspection; its title is “feat(agent-login): resume an active login session and permit concurrent login terminals.” - paperclipai/paperclip PR #12759 was created 2026-09-03T09:33:39Z and was closed at inspection; its title is “fix(release): align onboarding smoke with the model-source UI.” - The repository reported 80020 stars, 5328 open issues, default branch master, and last push 2026-09-05T00:50:29Z. - The latest tagged-release baseline checked was v2026.831.1 published 2026-09-02T04:56:26Z.
What changed
paperclipai/paperclip PR #12863 reports: Thinking Path 12801 gave the connect step a working sign-in but drew it as three separate events: a press, a card, and a button. The design that followed (PCLP-Onboarding, board 3065:587) asks for one gesture instead — the row answers, the card opens because of it, and the button becomes the sign-in. Getting that to read as one thing turned out to be less about adding animation than about ordering what was already there, and then about removing the layout changes that no easing can smooth. Previews** — both live, both driven from this branch: **https://paperclip-connect-flow-preview.vercel.app/wizard-preview.html** — the real OnboardingWizard, network stubbed **https://paperclip-connect-flow-preview.vercel.app** — the sequence in a harness, with?state= deep links Linked Issues or Issue Description No tracking issue — described inline, per CONTRIBUTING.md. What's wrong.** The step reads as a sequence of unrelated events. Picking a source does nothing visible; the footer button then opens a card; the card carries its own link row and its own Cancel; the button says "Connect" throughout and gives no account of what the sign-in is doing. The alternative source stays on offer while a login runs, and pressing it would have to cancel a live server session to honour. Expected.** Picking a source starts the sign-in. The row collapses to the answer, the card opens where the link used to be, and the button walks "Next" → "Sign in to
paperclipai/paperclip PR #12861 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work. - Agent authentication uses server sessions, plugin workers, and browser login panels. - A page reload loses an active login session, and one worker permits only one login terminal. - These limits cause lost work and prevent two owners from logging in through one worker. - This pull request lets the browser resume active sessions and lets workers serve concurrent login terminals. - The benefit is reliable login recovery with a bounded process-wide route limit. Linked Issues or Issue Description What existing behavior does this improve?** It improves agent credential login recovery and concurrent login terminal handling. Subsystem affected** Cross-cutting (multiple of the above). Current behavior** A page reload loses the active login session. A shared plugin worker rejects a second login terminal. Proposed behavior** The browser reads and resumes the owner's active session. A worker supports multiple login terminal routes under a process-wide ceiling. Reason and benefit** Owners keep login progress after a reload. Two owners can log in through one worker without removing the route limit. Breaking changes** None. The change adds owner-scoped read routes and changes login terminal concurrency. What Changed Replace the single worker login route with maps keyed by host route and worker session identifiers. Add a process-wide login route ceiling and release each reserved slot on every
paperclipai/paperclip PR #12759 reports: Thinking Path - Paperclip is the open source application teams use to manage AI agents and automate work - The authenticated Docker onboarding smoke test validates the first-run wizard path for self-hosted instances - Step 4 of the onboarding wizard now opens with a "Model source" radio group (Claude Code / Codex Subscription) instead of showing a bare "Connect" button - The smoke spec's wait for getByRole('button', { name: 'Connect' }) times out because the CTA is now "Next" and is disabled until a tile is selected - This pull request updates the locators to select the Claude Code subscription tile and drive the enabled "Next" button through the probe and hire - The benefit is that the Release pipeline turns green again — 8 consecutive runs were failing on this spec Linked Issues Fixes: The release pipeline has been red on every run since the new onboarding wizard landed. Refs #0 (release blocker). The Release workflow has been red on every run since ~2026-09-02T21:00 UTC when the new onboarding wizard step 4 landed. What Changed tests/release-smoke/docker-auth-onboarding.spec.ts — replace the bare Connect button wait with Claude Code Subscription radio selection and Next button interaction; update the step 4 comment and timeout Verification [ ] The Release schedule run at https://github.com/paperclipai/paperclip/actions/workflows/release.yml passes after this merges [ ] All CI gates on this PR are green (Build, General tests, Typecheck, CodeQL, Socket
Why it matters
Credential onboarding is one authority transfer. Splitting it across unrelated buttons or losing it on refresh turns authentication into guesswork and abandoned server sessions. The practical test is whether the system remains bounded and its receipts still describe the action after failure, retry or restart.
Current
The primary record was closed when captured on 2026-09-05. The tagged-release baseline was v2026.831.1 published 2026-09-02T04:56:26Z. Repository metadata, source bodies, current pull requests and issues, releases, Google News, Hacker News, Lobsters, Metamesh and the rendered ClawCharts row were inspected. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/paperclipai/paperclip/pull/12863. Supporting records are https://github.com/paperclipai/paperclip/pull/12861 and https://github.com/paperclipai/paperclip/pull/12759. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts and reproductions remain attributed to their authors unless identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Let one visible action own session creation, keep active login routes bounded and owner-scoped, resume after reload, and make release smoke tests follow the real product path. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.