Evidence record / paperclip
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-paperclip-v2026-1005-0-narrows-new-google-oauth-requests-without-narrowing-old-tokens
v2026.1005.0 narrows new Google OAuth requests without narrowing old tokens. Docs, Sheets and Slides request their service-specific scopes without additional Drive scopes; Calendar write drops a redundant scope. Existing consent is not retroactively reduced. Managed methods require a matching Cloud broker registry and exact scope evidence; mixed contracts fail closed. Customer-owned methods use reduced requests on new consent. The tagged document also describes independent app/tool profiles, not a single combined credential.
Channel: tagged-release. Half: both. Date: 2026-10-06.
Operator consequence: Reconnect affected grants for fresh reduced-scope consent and roll the broker scope registry with the application. Check provider-returned scopes rather than assuming the upgrade shrank existing tokens. Do not globally revoke the shared Google client to migrate one profile, because that can disrupt unrelated Workspace connections.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-paperclip-v2026-1005-0-narrows-new-google-oauth-requests-without-narrowing-old-tokens
Source links
Primary links, including exact changelog lines when available.
- tagged commit file2026-10-13-paperclip-v2026-1005-0-narrows-new-google-oauth-requests-without-narrowing-old-tokenspaperclipai/paperclip / doc/connections/GOOGLE-WORKSPACE.mdcommit2026-10-13-paperclip-v2026-1005-0-narrows-new-google-oauth-requests-without-narrowing-old-tokensgithub.com/paperclipai/paperclip/commit/25c422ba7e30f9e4bfb34ddeff88ce4bd6b2773e
Versioned source: run artifact