d627632874
Docs for parent release `v2026.1106.0` (`d69631b0`), up from `v2026.1023.0` (`1b4c8038`): 515 parent commits. ## How this branch was built The tag is 914 commits behind what `nightly` has drafted, so this branch isn't cut from `nightly` HEAD. It starts at nightly commit `1952052` (parent `043f2514`), 19 commits before the tag, then adds: - the `main` hotfix (#160) - the sync tooling from `nightly` - docs for those 19 commits Later nightly drafts stay on `nightly`, so no pages had to be removed. No `nightly-draft/*` PRs are open. ## What changed - **Runner by default:** new Claude, Codex, OpenCode and Pi agents start on Paperclip Runner on supported hosts, with **Legacy runner** and **Upgrade runner**. - **Workspaces:** cleanup of finished workspaces, optional Git expiration, and restore points for unsaved work. Restore points are off by default. - **New pages:** Prompt injection prevention, Google Workspace, GitHub Copilot, Speko, Braintrust, Daytona, Ditto and Unikraft. - **Breaking and upgrade notes:** the run history limit, Sentry run failures off by default and the DSN variables, the Docker start command for custom images, `--yes` on `instructions-file:delete`, and slower migrations on large instances. - **Also covered:** project repositories as skill sources, roster bulk edit, Artifacts V1 (experimental, off by default), composer dismissal, `expectedStatusVersion`, `unexecuted_review_stage`, and plugin workspace providers. - **Changelog:** a v2026.1106.0 entry in `reference/changelog.md`. ## Older text corrected These were wrong at the tag, and most are also wrong on the live site: - which permissions let an agent read a peer's configuration or change instructions (`api/agents.md`) - `decideNowCount`, which doesn't exist; the field is `deskBadgeCount` - `file-resources` routes, which are board-only - the **Create project** dialog fields, a CEO rule the code doesn't enforce, and where a terminated agent's reports appear - `instructions-file:put` and `:delete` examples that always failed (`cli/agent.md`) - a curl example that returned `422` (`api/cases.md`) - Google Workspace **Reconnect** instructions, which claimed it reopens the service picker - the `permissionKey` table, which listed 8 of 21 keys - drafting text at the end of `api/agents.md` ## ⚠ Please check these - **Product behaviour that may be a parent bug.** The docs now describe the tag's code, which you may prefer to fix upstream: - The project **Environment** dropdown saves a choice, but runs ignore it (`experimental/environments.md`). - `environments:manage` is granted by roles but no environment route checks it. - `suggest-changes` is documented as agent-only, because only agents have a consent path. Company skill policy decides skill edits. - **Reader-visible mismatches in the parent UI.** The docs follow the code. Upstream copy still mentions a "Built-in agents tab", says Copilot "awaits qualification", and tells people to "Reconnect Google Workspace to change access". ## ⚠ Post-tag leaks removed Nothing to remove from an already-drafted page: post-tag surfaces such as 1Password, Vercel, Supabase deploy, custom gateway onboarding and Artifacts V1 as default never came onto this branch. Authors left out post-tag hunks of the next nightly draft, and the reasons are in the run notes. ## ⚠ Drift None. Zero findings at the tag, from a full parent snapshot. ## ⚠ Verification Failures The tag-accuracy gate reports one leak and nine review entries. None is a real failure: - **Leak:** `reference/cli/service.md`, `paperclipai payload and`. This is a false positive; it's prose from a real message at `cli/src/commands/service.ts:184`. - **Review, 8 new connector pages:** the gate can't confirm new pages. Reviewers confirmed each surface exists at the tag. - **Review, `local_tools`:** an example value from the tag's Runner README. Not provable from code, and kept deliberately: - `sandbox-providers.md` uses `sandbox.yaml`. The tag's README says `install.yaml`, which returned 404 when checked. The upstream fix is post-tag. - The Google Workspace row about older OAuth brokers rests on release notes and a design doc. The broker isn't in this repo. - External claims about provider behaviour (for example Braintrust, Daytona, Unikraft and Google scopes). ## ↻ Renames detected None. The rename helper wasn't run: the 19-commit delta adds no new adapter, skill, or plugin directories that it would check. ## Verification All checks read a checkout pinned to the tag. - **First round:** authors, a release-notes audit, an audit of corrections stranded on `nightly`, an audit of 321 lines the last realign dropped from `main` (about 130 checked directly in code), and six fresh verifiers. - **Second round:** seven new verifiers re-checked every changed area, tracing behaviour rather than matching labels, and fixed about 50 more defects. That volume means more may remain. - **Limits of that second round:** - Each verifier reported what it only string-matched. That includes parts of Artifacts V1, the **Upgrade runner** notice, Copilot run behaviour, and some Plugin SDK contract text. - The second-round fixes themselves weren't reviewed by a third round. - **Gates:** `docs:build`, `docs:test` and `sync:check` pass. - **Nothing was run against a live instance.** All of this comes from reading code. ## Screenshots **196 of 278 screenshots are stale and none were recaptured.** The list is in `SCREENSHOTS_PENDING.md`. Some visibly differ from the text, such as the removed **Run with provider trace** button and the old roster tabs. ## After merge 1. Keep the PR title as is: `tag-docs-release.yml` reads the version from it. 2. Confirm the `docs/v2026.1106.0` tag exists. 3. Run `node scripts/sync/realign-nightly.mjs release/v2026.1106.0 --push`, then audit for dropped lines and duplicated paragraphs, and set `nightly` state back to `branch_mode: nightly`. 4. Check that `docs.paperclip.ing` serves the release: a new page, a new claim, and the changelog's top entry. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]> Co-authored-by: DevRel Gemini <[email protected]> Co-authored-by: Paperclip <[email protected]> Co-authored-by: Dotta <[email protected]> Co-authored-by: ClaudeCoder <[email protected]>
12 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1106.0 | Google Workspace Connector | Connect Gmail, Drive, and Calendar with one Google account, choose read-only or read and write per service, and see what agents can do with each. |
Google Workspace
Warning: Google verification pending. Paperclip has not yet completed Google app verification. You may see an unverified-app warning during authorization. If Google offers an Advanced option to continue to Paperclip, you can choose to proceed after reviewing the requested access. This option is not available for every account; Workspace administrator restrictions and other Google access requirements still apply. Contact [email protected] if you cannot connect.
One Google account, one connection, and you choose which services it covers. Before you sign in, you pick Gmail, Drive (which includes Docs, Sheets, and Slides), and Calendar, and decide for each one whether agents can only read or can also make changes. Agents then get only the actions for the services you picked and Google actually granted.
Warning: Google Workspace needs Google Workspace Developer Preview registration before tools can run. Google must register the Workspace email that signs in, and the Cloud project that owns the OAuth client if you bring your own. Apply first at Google Workspace Developer Preview.
When to pick this over the single-service connectors
Google Workspace is the connector the Connectors page offers for new Google accounts. The nine single-service connectors (Gmail, Google Calendar, Google Chat, Google Docs, Google Drive, Google People, Google Sheets, Google Slides, and Google Workspace Search) are no longer listed for new setup. They still appear on the page if you already have a saved connection to one of them, and those connections keep working as before.
Pick Google Workspace when you want:
- One account for several services. One sign-in covers mail, files, and calendar, instead of a separate connection for each.
- Access set per service. You choose read-only or read and write for each service in one place, and your choices are saved with the connection, so a reconnect asks Google for the same access again.
Some things are only on the older connectors. Google Workspace does not offer Google Chat, contacts and directory lookups, cross-service search, or archiving in Gmail. If you already rely on Google Chat, Google People, Google Workspace Search, or a Gmail archive connection, keep that connection.
Before you connect
- A Google Workspace account that can already open the mail, files, and calendars you want agents to use.
- Developer Preview registration for that account, confirmed by Google.
- If your instance is not enrolled with Paperclip Cloud, your own Google OAuth client. Set up your own Google OAuth app is the complete procedure; enable the APIs listed there for each service you plan to select.
Choose services and access
When you start the connection, Paperclip opens a Connect Google Workspace picker before it sends you to Google. Each service has a switch and an access menu:
| Service | What it covers | Access choices |
|---|---|---|
| Gmail | Your mailbox | Read only or Read & write |
| Drive | Drive files, plus Docs, Sheets, and Slides | Read only or Read & write |
| Calendar | Your calendars and events | Read only or Read & write |
All three start switched on with Read & write. Switch a service off to leave it out entirely, or set it to Read only. You need at least one service on to continue. If you select Cancel, Paperclip creates nothing and remembers your choices for the next try.
Your picks decide what Paperclip asks Google for:
| Service | Read only requests | Read & write requests |
|---|---|---|
| Gmail | gmail.readonly |
gmail.readonly, gmail.compose |
| Drive | drive.readonly, documents.readonly, spreadsheets.readonly, presentations.readonly |
drive.readonly, drive.file, documents, spreadsheets, presentations |
| Calendar | calendar.calendarlist.readonly, calendar.events.freebusy, calendar.events.readonly |
calendar.calendarlist.readonly, calendar.events |
A service you switch off is not requested at all, and nothing it would have unlocked becomes available later.
Connect Google Workspace
- Open Connectors and select Google Workspace.
- Read the access line above the main button. It says who the connection signs in as and which agents can use it. Google Workspace connects as you or as an organization identity. To change the identity, narrow the agents, or pick another sign-in method, select Change.
- Choose how to sign in. Paperclip uses the Paperclip-managed sign-in when your instance offers it, and you have nothing to set up in Google Cloud. To use your own Google OAuth app instead, pick it under Change and supply the client ID and secret from Set up your own Google OAuth app.
- Start the connection. The service picker opens; choose services and access, then select Continue.
- Complete Google's consent screen with the registered Workspace account.
Then open the Permissions tab and set the actions. Leave reads Allowed, and keep writes on Ask first until you have watched the agent work. Set action permissions is the how-to, and How connector access works covers identity and agent selection.
What agents can do
Each service has a fixed, reviewed list of actions. Read actions need the service on; write actions need it on Read & write. Because one connection holds several services, each action's full name starts with its service, such as gmail__create_draft or calendar__delete_event; look for that prefix when you set actions on the Permissions tab. The table drops the prefix.
| Service | Read actions | Write actions |
|---|---|---|
| Gmail | search_threads, list_threads, get_thread, search_messages, get_message, list_drafts, get_draft, list_labels |
create_draft |
| Drive | search_files, list_recent_files, get_file_metadata, read_file_content, download_file_content, get_file_permissions |
create_file, copy_file |
| Docs | read_doc |
update_doc |
| Sheets | get_spreadsheet, get_values |
update_spreadsheet, update_values, update_formulas, insert_dimension |
| Slides | read_presentation |
update_presentation |
| Calendar | list_calendars, list_events, get_event, search_events, suggest_time |
create_event, update_event, delete_event, respond_to_event |
A few things worth knowing:
- Gmail never sends. Google's
gmail.composescope would allow sending, but sending is not on the reviewed list, so agents can only leave drafts for a person to send. Archiving, trashing, and other label changes are not available here either. - Drive creates and copies, but does not edit arbitrary files. The
drive.filescope only reaches files the app created or opened. To change content inside a document, spreadsheet, or deck, agents use the Docs, Sheets, and Slides actions. Deleting, moving, and re-sharing files are not available. - Calendar writes include deleting.
delete_eventcomes with Read & write access, so give it Ask first or switch it Off if you do not want agents removing events. - Anything new stays off. If Google adds a tool to its servers, it is not enabled until Paperclip reviews it.
When you decline part of Google's consent
Google's consent screen can let you untick individual permissions. Paperclip only enables actions backed by permissions Google reports as granted, and never more than you chose in the picker. If you decline one, only the actions that need it are disabled; everything else keeps working.
For example, if you leave Drive and Calendar on but decline Docs editing on Google's screen, Drive and Calendar work as chosen while the Docs actions stay unavailable. Under Read & write, one permission covers both reading and editing for Docs, Sheets, Slides, and Calendar events, so declining it removes that service's reads as well as its writes. If you want an agent to read but not change something, choose Read only in the picker rather than declining at Google.
An agent that calls an action you have not granted gets "This Google action needs a permission you have not granted. Reconnect Google Workspace to change access."
The same limit applies the other way. If your Google account already granted Paperclip broader access in the past, the connection still stops at what you picked this time.
Reconnect signs you in again with the access you saved. It does not open the picker, so you cannot widen or narrow access there. If Paperclip cannot find your saved choices, it stops rather than falling back to the defaults, so a reconnect never quietly asks for more than you had.
To change access, select Add account on the Google Workspace row in Connectors, make your choices in the picker, and complete Google's consent. That creates a new connection, so set its actions on the Permissions tab, then remove the old connection.
Try it
List my Google calendars and tell me the title and start time of my next event. Do not create or change anything.
Expect your next event, which you can confirm in Google Calendar. This checks the credential, the account, and the agent's permission without writing anything. If you left Calendar out, try a Drive or Gmail search instead.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Google refuses before the consent screen | Developer Preview registration is incomplete for the account or Cloud project | Finish registration and retry |
| The Paperclip-managed sign-in is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not offering the Google Workspace profile | Use your own Google OAuth app, or ask an administrator about enrollment |
| A new Paperclip-managed Google Workspace sign-in is rejected | New Google Workspace requests rely on an updated Paperclip-hosted OAuth broker, and an older broker may reject them | Try again later, or use your own Google OAuth app. Existing single-service Google connections keep working |
| Continue is greyed out in the picker | Every service is switched off | Switch on at least one service |
| A whole service's actions are missing | The service was switched off in the picker, or you declined its permissions at Google | Select Add account on the Google Workspace row, switch the service on, approve it at Google, then remove the old connection |
| Read actions work but write actions are missing | The service is on Read only | Select Add account on the Google Workspace row, choose Read & write, approve the new permissions at Google, then remove the old connection |
| You need Google Chat, contacts, or cross-service search | Not offered by Google Workspace | Use an existing Google Chat, Google People, or Google Workspace Search connection |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: one connection covers one Google account. No sending mail, no deleting or re-sharing Drive files, and no editing of arbitrary existing Drive files outside Docs, Sheets, and Slides. Google's Workspace MCP servers remain in Developer Preview, so treat the surface as subject to change.
Related guides
- Set up your own Google OAuth app
- Gmail, Google Drive, Google Calendar — the single-service connectors, for connections you already have.
- How connector access works
- Set action permissions
- Configure MCP servers — Google's own guide.