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]>
5.6 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1106.0 | Recognized but Unlisted Providers | The provider definitions present in the Paperclip catalog but withheld from the Connectors list, and the providers that gate access behind their own approval. |
Providers Paperclip recognizes but does not list
Reference for the inventory behind the catalog. If you are looking for a connector to set up, start at Connectors. Apart from Composio, which is listed again, everything on this page is either withheld from the Connectors list or blocked by the provider, so it has no direct connector you can set up from the catalog today.
Two separate things get confused here, so they are listed separately. A withheld provider has a complete definition that Paperclip still recognizes, but it is deliberately kept out of the customer-facing list. A provider-gated one is not offered because the provider itself will not let an independently registered client connect.
Note: Checked against Paperclip v2026.1106.0. Catalog visibility can change between releases; recognition is not a promise of availability. Existing connections still need to be verified independently.
Withheld from the Connectors list
Paperclip keeps recognition and visibility as separate things: a definition can stay in the catalog while being hidden from the store. The comment on the hidden set in the App source gives the reason — separating the two means pulling a provider out of the list does not have to break connections somebody already saved.
What we can confirm at this release: the definitions below are present, Paperclip still resolves them, and they are filtered out of the list you browse. What we did not do is connect or run any of them, so whether a connection saved earlier still works is unverified here. If you have one, Verify a connector and fix a broken one is how to find out, and the answer is specific to your instance.
None of these have connector pages, and none can be added from the catalog.
As of Paperclip v2026.1023.0, Bitly, Context7, and Make have left this list and are back in the catalog — see Bitly, Context7, and Make. ClickUp, Klaviyo, and monday.com have joined it: their definitions exist, but sign-in has not yet been proven end to end, so they stay out of the list you browse.
| Provider | Slug |
|---|---|
| beehiiv | beehiiv |
| Brex | brex |
| Candid | candid |
| ClickUp | clickup |
| Coda | coda |
| Egnyte | egnyte |
| Embat | embat |
| Kernel | kernel |
| Klaviyo | klaviyo |
| Local Falcon | local-falcon |
| Manufact | manufact |
| monday.com | monday |
| O'Reilly | oreilly |
| PlanetScale | planetscale |
| Razorpay | razorpay |
| Sanity | sanity |
| Similarweb | similarweb |
| Ticket Tailor | ticket-tailor |
| TickTick | ticktick |
| Xero | xero |
Composio: listed again, old connections retired
Composio used to sit in the withheld list above. It is back in the Connectors list as a regular remote MCP connection through Composio Connect — see Connect apps through an MCP aggregator.
Connections made through the older Composio broker are a different matter. That broker is retired, so those connections no longer run: they show as unhealthy, their tools are not offered to agents, and calls to them are refused. Paperclip tells you what to do in the connection itself:
"This legacy Composio connection is no longer supported. Add a new Composio MCP connection from Connectors, then remove this connection. Existing credentials and permissions are not migrated."
In practice: connect Composio again from Connectors, set up access and action permissions on the new connection, then remove the old one. Nothing carries over automatically.
Gated by the provider
These are recorded as blocked because of a requirement on the provider's side. The requirement is theirs, not Paperclip's, and it has to be lifted or granted by them — there is no setting in Paperclip that works around it.
| Provider | What the provider requires |
|---|---|
G2 (g2) |
G2 has to enable cross-application token introspection before an independently registered client can connect at all. There is no customer-side application process for this. |
Vercel (vercel) |
Vercel reviews and approves MCP clients. Approval is between Vercel and the client's publisher, so an operator cannot request it for their own instance. The Connectors list can still show a Vercel row that connects through Composio or Arcade; that route goes through the aggregator, not a direct connection. |
monday.com (monday) |
monday.com rejects Paperclip's callback address during automatic client registration. monday.com has to allowlist the callback before sign-in can work; an account administrator may also need to approve. It is also withheld from the list above. |
Zomato (zomato) |
Zomato limits third-party clients and requires each redirect URI to be allowlisted. Both steps happen on Zomato's side. |
If you need one of these now, the routes that do not depend on the provider's client approval are in Can't find your app? — a custom server where the provider permits one, an MCP aggregator, or a workspace and a CLI.
Related
- Connectors — the catalog you can actually set up from.
- Connect a custom MCP server — the path for a service with no catalog entry.
- Verify a connector and fix a broken one — checking whether a connection you already have still works.