Paperclip merges AI account management into Connections without automatic agent adoption

Paperclip merged the two halves of AI Connections on September 12: a runtime credential foundation followed by an interface that reuses its existing sign-in components. The change turns provider accounts into managed, permissioned resources rather than a parallel set of agent settings. A fresh follow-up proposes letting a responsible user's chosen default determine whether a compatible provider uses a subscription or API key. That follow-up is still open. The landed foundation and the proposed refinement should not be treated as one already available behavior.

The facts

- The runtime foundation merged at 21:30 UTC on September 12, and the Connections interface followed at 21:51 UTC. - Credentials are stored on grants, with responsible-user defaults or explicit permitted grants selected independently of harness and model. - The foundation names Claude, OpenAI, OpenRouter and Grok account capabilities, while isolating managed credentials and provider sessions across accounts. - Missing managed credentials intentionally block execution rather than restoring an ambient or legacy fallback. - The interface reuses existing provider-connection and login controllers across Connections, agent configuration and task requests. - No agent automatically adopts managed Connections; a separate open follow-up addresses subscription-versus-API-key choice for responsible users.

Why it matters

For an app coordinating work across people and agents, the important account question is whose authority and budget a task uses. A convenient reconnect screen is only the visible part. Reusing the grants model can keep ownership and revocation consistent across tasks, but only if an unavailable account stops the task rather than quietly substituting a more privileged one. That is a governance change in product behavior, not merely another provider logo in a settings list.

Current

Inspected on 2026-09-13. The Paperclip release baseline is v2026.831.1 published 2026-09-02T04:56:26Z. The main source was merged 2026-09-12T21:30:11Z when captured. Proposals, merged mainline changes and packaged releases are different availability states; the linked release baseline does not imply that open proposals have shipped.

Evidence

Primary evidence: paperclipai/paperclip PR #13247 (https://github.com/paperclipai/paperclip/pull/13247). Supporting context: paperclipai/paperclip PR #13248 (https://github.com/paperclipai/paperclip/pull/13248); paperclipai/paperclip PR #13351 (https://github.com/paperclipai/paperclip/pull/13351). Sources were read directly through public pages or GitHub API bodies. Contributor test results are attributed claims, not independently reproduced results.

Operator take

Treat migration as deliberate adoption. Inventory which agents still use legacy authentication, which use responsible-user defaults and which explicitly select a shared grant. Then test revocation, a missing default and reconnect inside a waiting task. The authors report live local Claude detection and Codex API-key task repair; they explicitly did not repeat all subscription-refresh or independent-human isolation checks. Those limits should inform rollout tests rather than disappear behind a merged badge.

Caveat

Merged mainline is confirmed, but the inspected release feed does not establish a packaged release containing these changes. The new responsible-user method refinement remains open and reports synthetic-credential database tests, not a fresh live-provider acceptance pass. Existing legacy authentication remains in place until an agent deliberately adopts Connections.