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]>
7.3 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1106.0 | Google Calendar Connector | Let agents read calendars and availability, and optionally manage events. Capability groups, invitation side effects, and a safe read test. |
Google Calendar
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.
Note: This connector is no longer listed on the Connectors page for new setup; it appears there only when you have a saved connection to it, which keeps running unchanged. For a new Google account, use Google Workspace. An agent that needs this service can still ask you for it with a connection card on its task.
Agents can read the calendars on your Google account, look up events, and check availability. On a managing connection they can also create, update, delete, and respond to events.
Warning: Google Calendar needs Google Workspace Developer Preview registration before it will authorize. 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.
Before you connect
- A Google Workspace account that can already see the calendars you want agents to use.
- Developer Preview registration for that account, completed and confirmed by Google. Register every additional account before it connects; an unregistered account fails at authorization, not at connect time.
- If your instance is not enrolled with Paperclip Cloud, Connect with Paperclip is not offered and you will need your own Google OAuth client with the Calendar API and Calendar MCP API enabled. Set up your own Google OAuth app is the complete procedure — do it before you start here.
Pick a capability group
The group is fixed for the life of the connection. To change it, make a new connection.
| Group | What agents can do | Scopes requested |
|---|---|---|
| Read only | Read the calendar list, read and search events, check free/busy | calendar.calendarlist.readonly, calendar.events.freebusy, calendar.events.readonly |
| Read & manage | The above, plus create, update, delete, and respond to events | calendar.calendarlist.readonly, calendar.events |
Read & manage no longer asks for the separate free/busy scope; calendar.events already covers suggesting a time. Connections made with an earlier version asked for more. If a Connect with Paperclip connection from before this change stops working, select Reconnect to sign in with the smaller set. A connection using your own OAuth app keeps its earlier grant until you reconnect it.
Connect Google Calendar
- Open Connectors and select Google Calendar.
- Read the access line above the main button. It says who the connection signs in as and which agents can use it. To pick a different identity, narrow the agents, or use another sign-in method, select Change.
- Check the capability group. Setup starts on the group that can make changes; to connect read-only, select Change and pick it under What should Paperclip be able to do?. Paperclip uses Connect with Paperclip when your instance offers it. To use your own client instead, select Use your own Google OAuth app and supply the client ID and secret from Set up your own Google OAuth app.
- Complete Google's consent screen with the registered Workspace account.
Choose access
Which calendars an agent can reach is decided by Google, not Paperclip: it is whatever appears on the authorizing account's calendar list, including calendars shared with that account. There is no calendar picker in Paperclip. If an agent should not see a calendar, remove the sharing in Google Calendar or authorize with an account that does not have it.
Reviewed operations for this connector:
| Operation | Group |
|---|---|
list-calendars, list-events, search-events, get-event, suggest-time |
Both |
create-event, update-event, respond-to-event |
Read & manage only |
delete-event |
Read & manage only, classified destructive |
Warning: Event writes have side effects outside Paperclip. Creating or updating an event with attendees can send invitations and notifications from your account, and
respond-to-eventanswers an invitation as you. The connector's own guidance is that all event mutations should be approved — leave them on Ask first.
How connector access works covers identity and agent selection; Set action permissions is the how-to.
Try it
Read one event you can confirm by eye, and do not involve anyone else:
What is on my Google Calendar tomorrow? List event titles and times only. Do not create, change, or respond to anything.
Compare the result against Google Calendar. Times come back with the event's own timezone, so check against the calendar's display timezone rather than assuming your local one.
Do not verify with a test event on a shared calendar — attendees get notified. If you want to confirm writes, create the event on a private calendar with no attendees and delete it afterwards.
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 signing-in account | Finish registration and retry |
| Connect with Paperclip is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not advertising the Calendar profile | Use your own Google OAuth app, or ask an administrator |
| A calendar is missing | It is not on the authorizing account's calendar list | Subscribe to or share the calendar in Google Calendar; no reconnect needed |
| Event writes are absent | The connection was made with Read only | Make a connection with Read & manage |
| Times look wrong by a fixed offset | The event's timezone differs from the one you are reading in | Compare against the calendar's timezone |
| Needs attention | The Google token expired or the grant was revoked | Select Reconnect |
Limitations: one connection covers one Google account. Calendar sharing and access-control changes, and calendar creation or deletion, are not exposed — only events. Google's Workspace MCP servers are in Developer Preview, so treat the surface as subject to change.
Related guides
-
Google Workspace Search — one read-only search across Gmail, Drive, Calendar, and Chat.