paperclipai/paperclip-docs

0 Fork 0

mirror of https://github.com/paperclipai/paperclip-docs.git synced 2026-11-07 06:16:07 -10:00

Files

T

d627632874 Release docs for paperclip v2026.1106.0 (#172 )

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]>

2026-11-07 13:02:42 +01:00

4.2 KiB

Raw Blame History

paperclip_version, seo_title, seo_description

paperclip_version	seo_title	seo_description
v2026.1106.0	Windsor.ai Marketing Data Connector	Let agents query marketing, analytics, CRM, and warehouse data through Windsor.ai, and hold back any action that changes campaigns, budgets, or posts.

Windsor.ai

Agents can query the data you connected in Windsor.ai — advertising, analytics, CRM, and warehouse sources — through one connection. It is a fast way to answer "how did last week's campaigns do?" without a connector for each ad platform.

Windsor.ai appears in the catalog on every instance; no experimental setting is needed.

Warning: Windsor.ai's server also exposes write actions on some connected ad and commerce platforms: campaigns, budgets, posts, and listings. Connecting a data source in Windsor.ai does not mean an agent should change it. Keep those actions Off or Ask first.

Before you connect

A Windsor.ai account with the data sources you need already linked. Link only the source accounts the task needs.
For browser sign-in, Paperclip must be reachable on a public HTTPS address. Windsor.ai rejects local HTTP callbacks; on a local instance, use an API key instead.

Connect Windsor.ai

Open Connectors and select Windsor.ai.
Read the access line above the main button. It says who the connection belongs to and which agents can use it. To pick a different identity, narrow the agents, or switch method, select Change.
Choose a method:
- Sign in with Windsor.ai — select Continue to sign in and complete browser sign-in. Paperclip registers its client automatically.
- Use a Windsor.ai API key — create a key for the intended Windsor.ai organization and paste it into the Your Windsor.ai key field.

Choose access

Browser sign-in asks for the create, delete, and offline_access scopes. Windsor.ai requires the delete scope to open a session at all, even when you only want to read, so approving sign-in grants provider-level delete permission. If that is not acceptable for your account, do not approve it. Paperclip cannot raise or narrow an API key's permissions either.

Paperclip's action list is where you narrow things down:

Action type	Suggested setting
Reading source fields and report data	Allowed
Changing campaigns, budgets, posts, or listings	Off, or Ask first if a person reviews each one

Set these on the Permissions tab right after you connect. See Set action permissions.

When agents report results, ask them to name the source account and metric definitions, since the same metric can mean different things on different platforms.

Try it

Using Windsor.ai, list the connected data sources, then pull clicks and impressions from our Search Console source for the last five days. Name the source account in your answer. Do not change anything.

Check the figures against the source platform. A bounded read like this confirms the credential and which sources are linked.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem	Likely cause	Fix
Browser sign-in fails on a local instance	Windsor.ai rejects local HTTP callbacks	Use a public HTTPS address, or connect with an API key
A data source is missing	It is not linked in Windsor.ai	Link the source account in Windsor.ai
An agent changed a campaign or budget	A write action was set to Allowed	Set it to Off, and review the change on the ad platform
Needs attention	The grant or key was revoked	Select Reconnect

Limitations: one Windsor.ai organization per connection. Sign-in always includes the provider's delete scope. The available actions are whatever Windsor.ai's hosted server exposes.

GSC Wizard — search performance from Search Console and Bing Webmaster.
Set action permissions
Windsor.ai MCP

Sources

Windsor.ai definition — methods, scopes, callback requirement, key field, and warnings.

4.2 KiB Raw Blame History