Files
3679b7e739 Release docs for paperclip v2026.1005.0 (#147)
## Summary

Release docs for Paperclip **v2026.1005.0** (parent tag commit
`467125fa`).
- **Window:** `v2026.1001.0` → `v2026.1005.0`, 179 commits, 1,645 files,
compare truncation 0.
- **Branch:** cut from `nightly` (`c42305a`). Nightly had drafted
against parent master up to `a6306ba6`, which is 159 commits past the
tag.
- **Review:** every changed page was checked by hand against a checkout
of the tag.

**Headline doc changes:**
- **New pages:**
  - [Browser Use Cloud](docs/connectors/browser-use-cloud.md)
- [Memory connectors](docs/connectors/memory-connectors.md), plus
Cognee, Honcho, Supermemory and Zep
  - [Agent Chat](docs/experimental/agent-chat.md)
  - [Paperclip Runner](docs/reference/adapters/paperclip-runner.md)
- **Breaking changes applied:**
- @-mentions no longer start a run (#14577). Ten pages that still said
they did are fixed.
- Keyboard shortcuts are always on, and `/api/auth/preferences` is gone.
  - Connector setup is one screen (#14811).
- Agent files that persist across tasks, a GitHub skill **Sources** tab,
aggregators on by default, two-way Slack, Grok Build on the Runner,
refreshed model catalogs, and the new env vars, including
`PAPERCLIP_RUNNER_API_TOOLS_ENABLED` / `_COMPANY_IDS`.
- A changelog entry, and 113 pages stamped `paperclip_version:
v2026.1005.0`.

### ⚠ Post-tag leaks removed

These document parent `master` features that are **not in
v2026.1005.0**. They stay on `nightly` for the next release.

- **Pages removed entirely (9):**
  - `connectors/ai-usage.md` (7d59de61)
  - `connectors/custom-model-providers.md` (9f7057e1)
  - `connectors/connection-instructions.md` (4857799a)
  - `administration/agent-commentary.md` (b508a05c)
- `experimental/assistant-connections.md`,
`reference/api/assistant-mcp.md` and `reference/cli/mcp.md` (e34abee6,
22a3ea34, 2d0c1381)
  - `guides/org/agent-identity.md` (a590ab76)
  - `reference/cli/runtime.md` (a6306ba6)
- **Reverted to `main`:**
  - `agentmail.md` (6c1a75da)
  - `openrouter.md`; only the released access-line change was re-applied
- `asana.md` (4ac37410); only the released access-line change was
re-applied
  - `delegation.md` and `team-catalog.md` (862a5758, b17019e1)
  - `adapters/overview.md` (a6306ba6)
  - `api/tool-gateway.md`, the GET → 405 change
- **Sections trimmed (~50 pages):**
  - AgentMail as a default connection
  - **Check usage**
  - aggregator account sync and grouping (b43073d1)
  - MCP `offline_access` (839cac13) and readable test results (6d654f63)
  - saved connection guidance
- the **Update skill** tool (eb049aeb) and managed-checkout import roots
(427e0484)
  - low-trust scoped work and owner-chat edits (0829d94a, 4039d4f0)
  - reduced default instructions (b17019e1)
  - Chat leading the nav and the combined inbox (1c07b590)
  - steer/interrupt recovery (cc67d4e1)
  - branch artifacts without a remote (db72ad4c)
  - Cursor on the Runner (a6306ba6)
  - Claude/Codex model ordering (92ad158c, d9b64ee2)
  - Daytona stalled-log polling (4e524632)
  - the agent identity env vars
  - the shared task composer for new tasks (2c43b391)

### ⚠ Drift

Checked against the tag. **No real drift remains:**
- **Env vars that exist at the tag but are read through helpers the
checker doesn't scan (false positives):**
  - `PAPERCLIP_WORKSPACE_GIT_SCAN_*`
  - `PAPERCLIP_WORKSPACE_GIT_SNAPSHOT_TIMEOUT_MS`
  - `PAPERCLIP_RUNNER_API_COMPANY_CAPTURE_MAX_BYTES`
  - `PAPERCLIP_CLOUD_CONNECTOR_*`
- `PAPERCLIP_ID_CONNECTOR_*` are documented as **retired**, which is
correct.
- Verify: `/api/companies/{companyId}/chats/{agentRef}` is registered
dynamically (`router[method]`, `issues.ts:17185`). False positive.
- Verify: `/api/agent-avatars/...png` and
`/api/companies/import/transfers*` are known false positives from
constant or param registration.

### ⚠ Verification Failures / review notes

- **Asana:** `asana.md` keeps "register your own Asana OAuth app". The
tag's `asana.json` advertises "Sign in with Asana" (DCR), but Asana's v2
MCP server needs a registered app, and sign-in only works after post-tag
#14756. Confirm you're happy with that wording.
- **Google Docs/Sheets/Slides/Calendar:** the "Reconnect after the scope
change" paragraph isn't confirmed in code.
- **`grok-local.md`:** "Intel Mac rejected" and "subscription sign-in,
no automatic fallback" are only partly confirmed.
- **`paperclip-runner.md`:** "Grok cannot automatically approve
Paperclip tool calls under narrower ACP modes" isn't confirmed directly.
- **`cognee.md`:** the tag's setup text says `uv` is required, which
contradicts `tool-access.ts:3560`. The page follows the code.
- **`work-modes.md`:** the per-reply mode chip was removed because it
couldn't be found at the tag.
- **`browser-use-cloud.md`:** the `frame-src` CSP advice is general
advice, not code-backed.

### Screenshots

**180 of 350 screenshots are stale**, across 41 routes (see
`SCREENSHOTS_PENDING.md`). None were recaptured in this PR; refresh
separately with `npm run screenshots:refresh`.

### Other open PRs

- **#143** (Browser Use Cloud + Neon, targets `main`): Browser Use Cloud
is covered here, and Neon is post-tag (5b8b2b38). Suggest closing it or
retargeting it to `nightly`.

## Checks

- `docs:build` passes.
- `sync:check` passes, with no broken internal links.
- `docs:test` passes in full: SEO metadata, crawlable links (275
routes), doc link resolution (2,198 checks), static routes, asset
fingerprints, skills nav, and skill source blocks.

## After merge (Phase 9)

- [ ] `docs/v2026.1005.0` tag is created by the workflow (keep the PR
title as is).
- [ ] `node scripts/sync/realign-nightly.mjs release/v2026.1005.0
--push`. The nine removed pages stay on `nightly`.
- [ ] Flip `nightly`'s `.sync-state.json` back to `branch_mode:
nightly`.
- [ ] docs.paperclip.ing serves the release: the changelog's top entry
reads v2026.1005.0, and `/connectors/browser-use-cloud/` returns 200.

🤖 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-10-07 09:19:28 +02:00

5.8 KiB


paperclip_version: v2026.1005.0 seo_title: Postman Connector seo_description: Connect Postman's hosted MCP server. Choose your region first, then a capability group: Minimal, Code, or Full. Setup, access, and a read test.

Postman

Agents can work with your Postman workspaces, collections, and environments — reading API definitions, and on the fuller capability groups generating code and making changes.

Two decisions come before credentials, and getting either wrong means starting over.

Decide region and capability group first

Region determines both the endpoint and how you authenticate:

Region Authentication
US Browser sign-in
EU API key — browser sign-in is not available on EU endpoints

Capability group determines how many tools the connection exposes:

Group What it covers
Minimal The smallest tool catalog — core workspace, collection, environment, mock and spec tools
Code A toolset focused on generating code from API definitions
Full The complete Postman API tool catalog

Warning: Minimal is a smaller catalog, not a read-only one. Postman's own documentation describes it that way, and its published minimal list includes createCollection, createWorkspace, putCollection, updateWorkspace, publishMock, duplicateCollection and runCollection. Choosing Minimal does not stop an agent creating, changing, publishing or running things. If you want a read-only posture, that comes from Paperclip's action settings, not from the group.

Start with Minimal anyway — a smaller catalog is easier for both you and the agent to reason about — but set the write actions it does contain to Ask first or Off when you finish setup.

The region and group are fixed on the connection. To change either, make a new connection.

Before you connect

  • A Postman account with access to the workspaces you want agents to use.
  • For the EU region, a Postman API key.

Connect Postman

  1. Open Connectors and select Postman.
  2. 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.
  3. Check that the selected option matches your region and capability group. To pick another, select Change.
  4. For US, complete Postman's browser sign-in. For EU, paste your Postman API key.

Choose access

Workspace, collection, and environment reach comes from Postman: the connection sees what the authenticating account or key can see. Paperclip has no workspace picker, so narrow access by authenticating with an account that has access to fewer workspaces.

Warning: Postman environments commonly hold API keys, tokens, and passwords as variables. An agent that can read an environment can read those values. The controls that actually help here are authenticating with a limited account and keeping secrets out of shared Postman environments — alongside the discovered tool list and Paperclip's action permissions.

Toolsets differ by purpose; do not assume they form progressively broader permission tiers. Inspect the discovered actions for your selected endpoint. Review generated code before using it, and set permissions for each available action separately.

One tool deserves separate attention: runCollection is present in the Minimal list, and running a collection means issuing its requests against whatever the collection targets. Decide explicitly whether an agent should be able to do that, and set it to Off if not.

Set write and destructive actions to Ask first or Off on the Permissions tab. On this connector that is the read-only control. See Set action permissions.

Try it

List the Postman collections you can see and tell me how many requests are in the first one. Do not change anything.

Compare the collection list against what you see in Postman. This confirms the credential, the region endpoint, and the agent's permission at once.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem Likely cause Fix
Browser sign-in is not offered You selected an EU option; EU endpoints require an API key Use the EU key option, or the US region if the account is hosted there
Authentication succeeds but nothing is visible The account is in the other region Connect with the option matching where the Postman account is hosted
A tool you expected is missing The connection uses a narrower capability group Make a new connection with Code or Full
Writes are refused The action is set to Ask first or Off Check the Permissions tab. Do not expect the capability group to be the cause — Minimal contains write tools too
An agent changed or published something on Minimal Minimal is a smaller catalog, not a read-only one Set the write actions to Off on the Permissions tab
A workspace is missing The authenticating account cannot see it Grant access in Postman; no reconnect needed
Needs attention The API key was revoked, or the sign-in expired Select Reconnect

Limitations: one region and one capability group per connection. No workspace selection in Paperclip. Do not infer read-only access from a capability group's name. Postman's own plan limits apply.