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]>
6.1 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1106.0 | Composio Connector | Connect Composio Connect or a configured session URL. Understand app authorization, aggregator permissions, and unverified setup steps. |
Composio
Composio lets agents discover and use apps through Composio Connect. App authorization happens in Composio as well as access selection in Paperclip.
Composio is available on every instance; no experimental setting is required.
Before you connect
- A Composio account and access to the apps you intend to authorize.
- For an externally configured session, its URL and required headers from its owner.
Connect Composio
Unverified setup: This procedure follows the pinned Paperclip definition and Composio's documentation. It has not been tested with a live Composio connection. Each step below is unverified.
- Unverified: Open Connectors and select Composio.
- Unverified: Read the access line above the main button. Select Change to choose the identity or narrow the agents that may use it.
- Unverified: Select Connect Composio to use the default
https://connect.composio.dev/mcpendpoint and complete browser sign-in. For an externally configured session, open Reuse an existing session and supply its URL and required headers under Change. - Unverified: Finish the connection check and inspect the exposed actions in Paperclip.
- Unverified: When Composio requests authorization for an upstream app, inspect the app and requested access before completing that separate browser flow.
Do not substitute a legacy server-creation recipe for Composio Connect. Composio now documents sessions for SDK-created endpoints; use the instructions for the endpoint you actually have.
Choose access
Tools come from your Composio account and appear in Paperclip when you connect. Composio Connect exposes discovery and execution actions that can reach upstream apps. Paperclip's setting for an execution action governs that exposed call; it does not provide a separate permission switch for every operation nested inside it.
Every tool starts as Allowed. Review broad execution and connection-management actions on Permissions and choose Ask first or Off as appropriate. Restrict upstream app authorizations in Composio too.
Connect an app through a saved account
For an app without native setup, select Connect on its catalog card and choose Composio if more than one provider is offered. Pick a saved Composio account and select Continue. To save another gateway, choose Connect a new account… and select Connect new account.
Paperclip checks whether that app is already active. If it needs authorization, use Connect {app} in Composio, finish the hosted sign-in, return, and select I’ve connected it. Paperclip checks the account again before reporting it connected. This flow creates no task and starts no agent run.
An expired or uncertain handoff is not retried silently. Get a new link lets you explicitly request another. Reusing a saved gateway keeps its access and action settings; it does not add new agent grants or create isolated permissions for this one app.
See and refresh app accounts
The gateway's Permissions page lists Connected apps and starts a check on first load. Refresh Composio refreshes that saved gateway. The same action is in its menu on Connectors; browsing also checks the supported public Composio catalog in the background.
Imported accounts appear under their app cards, labelled Managed by Composio with the saved gateway name. Failed checks preserve last-known accounts as Not verified; expired accounts show Needs sign-in. These are observations of Composio authorization, not new Paperclip connections or grants.
Use Open in Composio to manage an imported account. It opens Composio Connect's app area, which is separate from Platform developer projects. Removing the saved gateway from Paperclip does not delete its app accounts in Composio.
Try it
Ask an eligible agent to discover a read-only lookup in an app you have authorized. Approve only a lookup, compare its result with the app, and inspect the connector call.
Unverified check: Suggested test, not a recorded result. Discovery alone does not prove that app execution is authorized.
Troubleshooting and limitations
| Problem | Check |
|---|---|
| An app asks for sign-in | Complete its separate Composio authorization; Paperclip access does not authorize the app. |
| An authorization link expired | Request a new link through Composio. |
| A configured session refuses access | Verify its URL and required headers with the session owner. |
| An app action fails | Check the app connection in Composio and reauthorize it if needed. |
The connector's reach depends on upstream accounts and the selected endpoint. Removing an agent's Paperclip access does not delete those upstream authorizations.
Related guides
Sources
- Paperclip connector definition — method names, authentication, endpoints, and connector-specific limits at the pinned implementation. Provider setup documentation is linked above.
- Catalog and account grouping — filters, grouped account rows, and gateway menus.
- Connected app list — refresh controls and verification states.