Paperclip merges governed Slack tools for tasks started in chat

Paperclip merged a Slack integration on September 22 that makes chat-origin tasks able to inspect their surrounding discussion and perform governed collaboration actions. The change is not an unrestricted Slack API proxy. It supplies typed tools to the originating task and its assigned agent, with the linked human requester resolved on the server. That distinction matters when an organization has several agents, several companies and private conversations on the same installation.

The new surface covers messages, reactions, pins, bookmarks, topics, files, canvases, lists and approved channel operations. It reuses Paperclip's action receipts, approvals, idempotency and reconciliation rather than inventing a parallel Slack task system. Membership and revocation are checked on each call and again before queued writes. Private-source publication is restricted, including automatic replies and uploaded deliverables. Other people's bot direct messages remain inaccessible.

The September 15 Connectors announcement supplies the product context: account sharing, agent access and permission to perform an action are separate choices. Its examples also warn that connector controls do not constrain shell Git or gh. The Slack merge extends that direction to work arriving from chat, not to every action an agent could take by another route.

The facts

- PR #13828 merged into Paperclip master on September 22, 2026, at 20:29 UTC. - The contribution adds 39 typed Slack tools and a bundled skill for chat-origin tasks. - Authority is bound to company, endpoint, task, run, assigned agent and admitted linked requester. - Current runtimes use bounded history search; native real-time search is deliberately disabled. - Inline file reads support text or canvas content up to 256 KiB; other file types return metadata. - The author reports live staging reads, uploads and approved channel creation, but incomplete optional OAuth and private multi-user qualification.

Why it matters

A chat connector becomes much more useful when it can recover the discussion behind a request. It also becomes more dangerous if the bot's access silently substitutes for the requester's. Paperclip is making that distinction part of tool execution and publication, with source-linked retrieval and durable approvals rather than a conversational promise to behave.

Current

Checked September 23, 2026. The inspected release baseline is v2026.916.1. The primary source is merged 2026-09-22T20:29:08Z. Tagged release availability and development-source state are separate: a release baseline does not establish that a proposed setting or newly merged feature is in an installed package.

Evidence

Primary: paperclipai/paperclip PR #13828 (https://github.com/paperclipai/paperclip/pull/13828). Context and implementation: Paperclip — Connectors product announcement (https://www.paperclip.app/blog/connectors-each-role/); paperclipai/paperclip — SLACK-TASK-TOOLS.md (source) (https://github.com/paperclipai/paperclip/blob/0eb21cba452d0dc411ba4df1fc20b9bff945d9e9/doc/connections/SLACK-TASK-TOOLS.md). The linked source text was inspected; reported experiments and test results remain attributed to their authors.

Operator take

Treat the merge as an integration to evaluate, not evidence that every deployed package already exposes these tools. Review requested Slack scopes and the originating task's permissions before enabling writes. An independent tool-action signing secret remains a provisioning prerequisite. When a write's outcome is uncertain, inspect the receipt and destination instead of retrying automatically; the source explicitly limits recovery for effects other than posts and uploads.

Caveat

Merged source is confirmed; packaged availability was not established. Test and staging outcomes are the contributor's reports, not this publication's experiments. Native real-time search, optional OAuth, private multi-user boundaries and CLI provider execution are not fully live-qualified.