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.7 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1106.0 | Google Chat Connector | Let agents search and read Google Chat conversations, and optionally send messages. This is a tool connector, not a way for people to chat with an agent. |
Google Chat
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. Google Workspace, the connector for new Google accounts, does not include Google Chat. An agent that needs this service can still ask you for it with a connection card on its task.
Agents can search Google Chat conversations and read messages, and on a sending connection post messages to spaces the authorizing account belongs to.
This is a tool connector: an agent reads and writes Chat using your Google account. It is not a channel for people to start work by messaging an agent — Google Chat is not one of Paperclip's conversation channels. If that is what you want, see Slack, Discord, Microsoft Teams, or Telegram.
Warning: Google Chat 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 already belongs to the spaces you want agents to read, with Developer Preview registration confirmed.
- Personal Google accounts do not have Google Chat spaces in the Workspace sense; this connector expects a Workspace account.
Decide your setup path now
This is the gate worth checking before anything else, because the two paths cost very different amounts of work:
| Path | What it takes | Offered when |
|---|---|---|
| Connect with Paperclip | Sign-in only, no Cloud console work | Only when the instance is enrolled with Paperclip Cloud and Cloud advertises the Chat profile. If it is not on the setup screen, it is unavailable to you |
| Use your own Google OAuth app | A Cloud project with the Chat API and Chat MCP API enabled, a registered callback URI, and a configured Chat app | Always |
Chat is the one Google connector that needs a configured Chat app, not merely an enabled API. In the Cloud console, open Chat API → Configuration and complete the app's identity — app name, avatar URL, and description — then set its functionality and visibility. Google will not authorize against a Chat API with no configured app, and the failure appears at the consent screen rather than earlier.
Set up your own Google OAuth app is the full procedure, including this step.
Pick a capability group
| Group | What agents can do | Scopes requested |
|---|---|---|
| Read only | Search conversations, list and search messages | chat.spaces.readonly, chat.memberships.readonly, chat.messages.readonly, chat.users.readstate.readonly |
| Read & send | The above, plus send a message | the read scopes, plus chat.messages.create |
The group is fixed for the life of the connection.
Connect Google Chat
- Open Connectors and select Google Chat.
- 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 conversations an agent can reach is decided by Google: the spaces and direct messages the authorizing account is a member of. Paperclip has no space picker. To narrow it, authorize with an account that belongs to fewer spaces.
Reviewed operations:
| Operation | Group |
|---|---|
search-conversations, list-messages, search-messages |
Both |
send-message |
Read & send only |
Warning: A sent message is visible to everyone in the space and arrives under the authorizing account's name, not an agent's. The connector's guidance is that sending should be approved — leave
send-messageon Ask first.
How connector access works covers identity and agent selection.
Try it
Pick a space the authorizing account belongs to and a recent message in it whose sender and wording you can see for yourself. Then:
In the Google Chat space "deploys", find the most recent message and tell me who
sent it and when. Do not send a message.
Expect the sender and timestamp you can already see in Chat. Matching a specific known message is the point — a plausible-sounding summary is not evidence the agent read anything.
If you must confirm sending, post to a space created for the purpose that contains only you. A direct message "with yourself" is ambiguous in Chat and a poor test target; a scratch space is unambiguous and equally harmless.
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 | Finish registration and retry |
| Authorization fails on a self-managed client | No Google Chat app is configured in the Cloud project | Configure the Chat app, then retry |
| Connect with Paperclip is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not advertising the Chat profile | Use your own Google OAuth app |
| A space is missing from results | The authorizing account is not a member of it | Join the space in Google Chat; no reconnect needed |
send-message is absent |
The connection was made with Read only | Make a connection with Read & send |
| People expect to message an agent and get no reply | Google Chat is not a Paperclip conversation channel | Use a supported channel instead |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: one connection covers one Google account. Creating, joining, or leaving spaces and changing memberships are not exposed. Reactions, message editing, and deletion are not available. Developer Preview applies.
Related guides
-
Slack, Discord, Microsoft Teams, Telegram — channels people can use to reach an agent.
-
Google Workspace Search — one read-only search across Gmail, Drive, Calendar, and Chat.