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.4 KiB

Raw Permalink Blame History

paperclip_version, seo_title, seo_description

paperclip_version	seo_title	seo_description
v2026.1106.0	Make Automation Connector	Let agents run the Make scenarios you expose to MCP. Connect with browser sign-in or a scoped MCP token, choose a zone, and gate the actions that change data.

Make

Agents can work with your Make automations — looking up your organization and teams, and running the scenarios you have made available to MCP. If your team already wires apps together in Make, this lets an agent use that work instead of rebuilding it.

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

Before you connect

A Make account.
Access to the scenarios you want agents to use, with those scenarios exposed to MCP in Make.

If you plan to use a token instead of browser sign-in, you also need:

A Make API token with the mcp:use scope, plus any extra scopes your chosen scenarios require.
Your organization's zone host, such as eu2.make.com. Make shows it in its MCP client setup instructions.

Connect Make

Open Connectors and select Make.
Read the access line above the main button. It says who the connection belongs to and which agents can use it. Select Change to pick a different identity, narrow the agents, or choose the token method.
Connect with one of these methods:
- Sign in with Make — select Continue to sign in and complete browser sign-in. Paperclip registers its client automatically, so there is nothing to set up in a developer console.
- Use an MCP token — enter your Make zone host (for example eu2.make.com) and paste the token into Your Make key.

With a token, Paperclip builds the server address as https://<zone>/mcp. The zone must be a make.com host. The token is stored as a secret and sent as a Bearer header. Never put it in a URL.

Choose access

Reach depends on what Make allows the connected identity: which scenarios are exposed to MCP and, with a token, which scopes the token carries. Only give a token the scopes your scenarios actually need.

A scenario can do anything it was built to do — send messages, update records, move money between systems. When an agent runs one, those effects are real. Paperclip lists each action Make exposes and starts them as Allowed, so review the list on the Permissions tab:

Keep reads, such as organization and team lookups, Allowed.
Set anything that runs a scenario or changes data to Ask first, or Off until you need it.

See Set action permissions.

Try it

Start with a read:

Use Make to list the organization and teams this connection can see. Do not run any scenarios.

Compare the result with what you see in Make. That confirms the credential without triggering an automation.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem	Likely cause	Fix
The zone host is refused	It is not a `make.com` host, or it includes `https://` or a path	Enter just the host, such as `eu2.make.com`
The token is rejected	It is missing `mcp:use`, was revoked, or belongs to another zone	Create a token with `mcp:use` in the right organization and reconnect
A scenario does not appear	It is not exposed to MCP, or the token lacks a scope it needs	Expose the scenario in Make, or add the scope to the token
A scenario ran unexpectedly	Its action was Allowed	Set it to Ask first on the Permissions tab
Needs attention	The grant or token was revoked	Select Reconnect

Limitations: one Make identity per connection. Which scenarios are available is decided in Make, not in Paperclip.

Zapier — another automation service, where you pick actions on Zapier's side.
How connector access works
Set action permissions
Make MCP server documentation

Sources

Make definition — methods, labels, zone validation, and token placement.
Catalog visibility — Make is no longer hidden from the store; default action policy.

4.4 KiB Raw Permalink Blame History