release-changelog-discord-message

发布 Discord 公告技能

为 稳定版 Paperclip 发布编写 Discord 公告。

这是 .agents/skills/release-changelog/SKILL.md 的配套技能。该技能用于编写变更日志——在 Beta 浸泡期，变更日志位于 release-notes/v{beta-version} 分支上的 releases/beta/v{beta-version}.md；稳定版发布后，规范化 PR 会将其重命名为 releases/vYYYY.MDD.P.md（参见该技能的 Channel Process 部分）。本技能会将该文件整理为一段可直接复制粘贴到 Discord 的内容，采用 dotta 的语气，并将其作为 discord_announcement 文档发布到发布 issue 上。

dotta 的原话

这是发到 Discord 上的——尽量遵循我的格式。如果我有一段是在思考未来，就结合我们最近正在处理的 issue 等内容来写。

Discord 公告不是变更日志。变更日志力求详尽；公告则有自己的观点、采用贴合本人语气的表达，并围绕同一批已发布的亮点展开，同时加入真实的“接下来要做什么”和“我在想什么”，内容取自 Paperclip 当前的工作，而非凭空编造。

何时使用

• 在 release-changelog 生成变更日志后使用（浸泡期内，变更日志按 Beta 版本号记录在 release-notes/v{beta-version} 分支上；稳定版发布后，则使用规范化后的 releases/vYYYY.MDD.P.md）。
• 当发布流程指定的发布 issue 要求编写 Discord 公告，或其中的 discord_announcement 文档需要针对新的日期或版本更新时使用。
• 切勿单独运行此技能。版本、日期、贡献者列表和重点内容必须与对应的变更日志文件一致——如果变更日志已更新，也要同步更新公告。

输出

一个可直接粘贴到 Discord 的 Markdown 围栏代码块。将其作为 discord_announcement 文档附加到发布 issue，并将原文粘贴到该 issue 的评论中，方便他人复制。 启用 Cases 时，还要创建或更新下面所述的社交子 case。

PUT /api/issues/{releaseIssueId}/documents/discord_announcement
{
  "title": "Discord announcement",
  "format": "markdown",
  "body": "<the announcement>",
  "baseRevisionId": "<latest if updating>"
}

如果文档已存在，先获取文档，并传入当前的 baseRevisionId。切勿悄无声息地覆盖——如果版本自上次写入文档后发生变化，请在 issue 评论中说明变更内容。

格式（遵循此模板）

使用 Discord 表情短代码（:paperclip:、:lock:、:brain: 等），不要使用 Unicode 表情符号。Discord 会渲染这些短代码；变更日志文件使用文字描述。

:paperclip: :paperclip: :paperclip: CLIPPERS!!! v{VERSION} IS OUT :paperclip: :paperclip: :paperclip:

OFFICIAL TWITTER: https://x.com/papercliping - follow it, report any others

## Highlights

:emoji: **Feature Name** - one-sentence description in dotta's voice.
:emoji: **Feature Name** - …
:emoji: **Feature Name** - …

... and a long tail of {flavor of the rest}. Read the [full release notes](<github link>).

## WHATS NEXT (:motorway:  Roadmap)

* **Theme A** - one-line forward-looking blurb
* **Theme B** - …
* **Theme C** - …

## What's on my mind

* **Topic** - what's bugging dotta / what's queued / open questions
* **Topic** - …

## PRESS                              (optional — only if there is real press)

* **Outlet / Person** - what happened ([link](<x.com link>))

## WHAT I NEED FROM YOU               (optional — only if there's a real ask)

FOLLOW THE TWITTER: https://x.com/papercliping - that's the only official one
TELL ME if you're using Paperclip in your business - I want to meet you

## Community

Thank you to everyone who contributed to this release!

@username1, @username2, @username3

## In Summary

PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK

Every single person will be managing a team of a dozen, or a hundred, or a
thousand agents and Paperclip will be the default tool to manage it all.

ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:

FULL RELEASE NOTES

https://github.com/paperclipai/paperclip/blob/master/releases/v{VERSION}.md

||@everyone||

模板说明：

• 开头和结尾的 :paperclip: :paperclip: :paperclip: 是品牌标识的一部分，务必保留。
• 在帖子中的某处注明安装渠道：稳定版使用 npx paperclipai@latest，抢先体验使用 @beta / @nightly / @canary；Docker :latest 仅在稳定版发布时更新。
• 完整版发布说明链接指向 master 上的 releases/v{VERSION}.md——该文件仅在稳定版发布后规范化 PR 合并后才会存在。发布公告前请先合并该 PR。
• 章节标题可以使用全大写或标题式大小写——dotta 两种都用过。选择一种风格，并在单条帖子中保持一致。
• 在最末尾使用 ||@everyone||（用 Discord 剧透格式包裹），这样发布者移除剧透遮挡时只会触发一次提醒。

语言风格提示

这些内容摘自 dotta 最近几次公告的写法。 请模仿这种语气；不要刻意营造“专业”腔调。

• 第一人称、对话式。“我想认识使用 Paperclip 的公司”， “我在想什么”，“如果说的就是你，告诉我”。不要写“Paperclip 很高兴 宣布”。
• 用全大写表达兴奋和诉求，尤其是在开场、章节 标题、“我需要你们做什么”章节和收尾标语中。功能描述不要 全大写。
• 每条亮点项目符号配一个 emoji 简码，选择能体现该功能的 简码（机密信息用 :lock:，规划用 :brain:，搜索用 :mag:， 云端／沙盒用 :cloud:，插件用 :jigsaw:，历史／恢复用 :rewind:，线程用 :thread: 等）。
• 亮点项目符号只写一句话，观点鲜明，从用户角度出发——“云端机密信息 的前置条件现在真能用了”，而不是“新增了对……的支持”。
• 亮点后面的收尾行用一个完整句子概括其余内容，并链接到完整发布说明 （“…还有一长串{类型}。阅读完整发布说明。”）。
• “接下来是什么”应着眼未来主题，而不是照搬冲刺任务列表。3–5 条 项目符号最合适。请从正在推进的目标、进行中的项目和团队最近正在 处理的问题中提炼，不要凭空编造主题。
• 亮点遵循 changelog 技能的增量规则：如果上一份公告已经介绍过某项功能， 本次只写本次发布中的变化，不要在后续工作中再次把它作为重点。
• **“我在想什么”**应体现 dotta 个人／战略层面的思考——文档缺口、 哲学定位（“我们是 AI 劳动力的人类控制平面”）、邀请（“如果你曾想 写写自己如何使用 Paperclip，来找我聊聊”）。请从最近的问题／评论中 提炼真实的矛盾，不要凭空编造。
• 媒体报道部分可选。只有在发布窗口内确实有媒体报道时才加入 （推文、播客、演讲、星标里程碑）。没有媒体报道 → 完全省略该部分。
• **“我需要你们做什么”**可选。只用于提出一个具体诉求（关注 Twitter、 引荐、报名参加 Beta）。没有实际诉求 → 省略该部分。
• 社区使用 changelog 文件中的同一份贡献者列表，放在三个反引号 fenced 代码块中，以逗号分隔，格式为 @username, @username。 排除机器人和 changelog 技能规范排除名单中的特定人员——使用相同规则。
• “总结”中的使命宣言变化缓慢。除非 dotta 另有说明，否则使用最近 的版本。最近的版本：
  • “PAPERCLIP 是帮助人类完成 100 倍工作量的 AI 编排器”
  • “PAPERCLIP 将成为每家公司的默认 Agent 管理工具”
  • “Paperclip 将成为每一家公司的 AI Agent 控制平面。”
• 收尾标语始终为 ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:。请保留。

工作流

1. 阅读 release-changelog 生成的对应变更日志——在观察期内使用以 beta 为键的文件，规范化后使用 releases/vYYYY.MDD.P.md。使用该文件中的版本和贡献者列表——绝不要重新推算。
2. 使用键 paperclip-release:vYYYY.MDD.P 查找父级 release case。如果不存在且已启用 Cases，请在创建子 case 之前，按照 .agents/skills/release-changelog/SKILL.md 中的架构创建它。
3. 阅读发布问题讨论串（分配给你、运行了发布流程的那条）——评论、关联问题以及公司中的近期问题是 WHATS NEXT 和 What's on my mind 的来源。beta 源提交之后已在 origin/master 上的提交，是绝佳的“接下来是什么”素材：它们就是下一次发布的内容。提炼真实主题，不要凭空捏造。
4. 重新阅读下面三个原样示例——它们是规范的语气范例。
5. 使用上面的模板起草公告。
6. 将公告作为 discord_announcement 文档 PUT 到发布问题上（见上面的“输出”）。如果是更新，请发送最新的 baseRevisionId。
7. 使用 parentCaseId 设置为发布 case ID，创建或更新 tweet_storm 子 case，然后将其 body 文档 PUT 为公告正文。
8. 在发布问题上发表评论，并将公告放在单个带围栏的 Markdown 代码块中，以便 dotta 无需打开文档即可复制粘贴到 Discord。

Tweet Storm Case 架构

使用此子 case 来存放 Discord／社交媒体公告串。键必须稳定，以便重试时更新同一个子 case：

POST /api/companies/:companyId/cases
{
  "caseType": "tweet_storm",
  "key": "paperclip-release:vYYYY.MDD.P:tweet-storm",
  "title": "Paperclip vYYYY.MDD.P tweet storm",
  "summary": "Social announcement thread for Paperclip vYYYY.MDD.P.",
  "status": "in_review",
  "parentCaseId": "<release-case-id>",
  "fields": {
    "schema_version": 1,
    "version": "vYYYY.MDD.P",
    "channel": "x",
    "discord_source": true,
    "post_count": 1,
    "target_audience": ["operators", "contributors", "agent-company builders"],
    "links": {
      "release_notes": "https://github.com/paperclipai/paperclip/blob/master/releases/vYYYY.MDD.P.md",
      "official_account": "https://x.com/papercliping"
    },
    "review": {
      "needs_human_copy_paste": true,
      "approved_by": null
    }
  }
}

然后编写 body 文档：

PUT /api/cases/:tweetStormCaseId/documents/body
{
  "title": "Paperclip vYYYY.MDD.P tweet storm body",
  "format": "markdown",
  "body": "<announcement body>",
  "changeSummary": "Draft social announcement"
}

如果要更新现有文档，请获取 case 并传入最新的 baseRevisionId。

不要发布到 Discord。此技能仅用于准备素材。

之前的原样示例

以下是 dotta 之前发布的三条 Discord 公告，原样保留，作为语气、结构和表情符号用法的权威示例。如有疑问，请参照这些示例。

示例 1 — v2026.403.0

CLIPPERS! v2026.403.0 has dropped!! :paperclip: :paperclip: :paperclip:

## Highlights

:inbox_tray:  **Inbox overhaul** - there is a new "mine" tab that has mail-client like keyboard shortcuts. It's my new default view for managing work
:thumbsup:  **Feedback and evals** - you can now vote :thumbsup: / :thumbsdown: on your agent's responses. If you choose to share your traces with me, I'll use it to make Paperclip better. In either case you can export locally for your own org's learning
:page_with_curl:  **Document revisions** - you can now restore old versions of your documents
:ping_pong:  **Telemetry** - this version has anonymized telemetry that helps me better understand the basic uses of Paperclip (adapters and so on) - if you hate that, just it disable with `DO_NOT_TRACK=1` or `PAPERCLIP_TELEMETRY_DISABLED=1` environment variables
:construction_worker: **Execution Workspaces (experimental)** - Paperclip is not a "code review" tool, but I have been finding worktrees are important for certain projects. Enable it in experimental settings
:loop:  **Routine variables** - sometimes you need to customize a routine and the new variables feature makes that easy

PLUS **tons** of improvements aound adapters, bugfixes, qol

## COMMUNITY

HUGE THANKS to the contributors with commits in this release:

@aronprins, @bittoby, @edimuj, @HenkDz, @kevmok, @mvanhorn, @radiusred, @remdev, @statxc, @vanductai

## WHATS NEXT (ROADMAP)

* **Multi-human users** -- you've been asking for it, we have a draft and will have this shortly
* **Sandbox execution** - the other half of cloud deployment: run your agents in a sandbox across any provider

PLUS: just dealing with the excellent PRs we have sitting in our inbox.

**What's also on my mind (coming soonish)**

* MAXIMIZER MODE - for when you've got a dream and tokens to burn
* Artifacts, work products, and deployments
* CEO Chat
* Stronger agent defaults

## PRESS

I've been doing my part to spread the word about Paperclip

* We talked to the incredible [Andrew Warner of Mixergy Fame](https://x.com/dotta/status/2039087507514507407)
* We gave a tutorial with the [inimitable Greg Isenberg](https://x.com/dotta/status/2037279902445994345)
* We met with the [Seed Club guys](https://x.com/dotta/status/2039020365926576377)
* We crossed [40k stars (46k now!)](https://x.com/dotta/status/2038638188227387613)
* ... and a couple others that will be released in a few days

## SUCCESS STORIES

* [Nevo made $76k in march](https://x.com/dotta/status/2039406772859920758) after using Paperclip to automate his marketing
* [Lewis Jackson](https://x.com/WhatSayLew/status/2039810227394978158) said 34 agents were already operating his trading firm through Paperclip and called it his "holy s***" AI moment.
* [Neal Kotak](https://x.com/nkotak1/status/2039582439459209638) said Paperclip already runs most of Roominary for him and praised how strong the product is.
* [Sam Woods](https://x.com/samwoods/status/2039039305960587755) said he knows several people who moved from OpenClaw to Paperclip, often with Hermes in the stack, and that they love it.
* [Josh Galt](https://x.com/JoshGalt/status/2039386307219095557) called Paperclip the coolest agent tooling he has used and said it is finally something that just works.

## IN SUMMARY

I know there are still some rough edges, but

Paperclip will be *the* control plane for AI agents in **every** company.

and I think we're moving at a pretty good clip :paperclip: :paperclip: :paperclip:

FULL RELEASE NOTES HERE

https://github.com/paperclipai/paperclip/releases/tag/v2026.403.0

||@everyone||

示例 2 — v2026.416.0

:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.416.0 IS OUT :paperclip: :paperclip: :paperclip:

## Highlights

This release has *tons* of quality of life improvements around speed, performance, and workflow. You should notice that comment threads feel faster and your agents stay on task longer

:thread: Issue chat threads now are a conversation more than comments
:police_officer: Execution policies like **Reviewer** and **Approver** are now first-class in the harness (e.g. enforce that QA *must* review a task)
:no_smoking: Blocker dependencies - first-class "wake on blocker resolved" which means now you can have "task graphs" that depend on one another and it's enforced by Paperclip
:woman_feeding_baby: Parent-child tasks - better support for sub-tasks all around, which makes it much easier to organize your work

And then a million fixes around ux, details, keyboard shortcuts, bug fixes, security fixes, etc. Really you should read the [full release notes here](https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0)

## COMMUNITY

INCREDIBLE INCREDIBLE WORK BY folks with commits and reports in this release:

@AllenHyang, @antonio-mello-ai, @aronprins, @chrisschwer, @cleanunicorn, @DanielSousa, @davison, @ergonaworks, @HearthCore, @HenkDz, @KhairulA, @kimnamu, @Lempkey, @marysomething99-prog, @mvanhorn, @officialasishkumar, @plind-dm, @shoaib050326, @sparkeros, @wbelt, @offset, @sagilayani, @mattdonnelly10, @peaktwilight, @YuvalElbar6

## WHATS NEXT (:motorway:  Roadmap)

* **Multi-human users** - in the last stages of testing, Paperclip is better with teams
* **Memory Infrastructure** - your agents will remember everything about yoru business
* **Sandbox execution** - run your agents anywhere

## What's on my mind

* I want to meet with companies who are using Paperclip in their business - if that's you let me know
* We need more Paperclip tutorials, defaults, and education - thanks to @aronprins for his work in this area already!
* We still need to get better at reviewing your PRs and we're improving our process every day
* "Zero-human company" language has to go - we're the human control plane for ai labor
* We're adding better support for *knowledge (wikis & files)*, *artifacts*, and *work product* in Paperclip soon.

## PRESS

* **AI Engineer Europe Tutorial** - I gave a tutorial for AIE. If someone is looking for a basics ABC of Paperclip [you can send them this](https://x.com/dotta/status/2044575580264316931)
* **AI Club Chicago** - JB gave a talk on Paperclip [at AI Tinkerers in Chicago](https://x.com/developwithJB/status/2044281068778316268) !

## IN SUMMARY

PAPERCLIP WILL BE THE DEFAULT AGENT-MANAGEMENT TOOL FOR EVERY COMPANY

If there's anything I can do to help you and your company use Paperclip, hit me up. Until then, enjoy the new release

ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:

FULL RELEASE NOTES

https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0

||@everyone||

示例 3 — v2026.427.0

:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.427.0 IS OUT :paperclip: :paperclip: :paperclip:

THIS IS THE OFFICIAL TWITTER FOLLOW IT: https://x.com/papercliping

## Highlights

:man_feeding_baby: **MULTI USER** - you can now invite multiple users to your instance
:factory_worker:  **HARDER WORKING** - robosut liveness continuations and lifecycle recovery means your instance tries harder before involving you
:white_check_mark:  **SUBISSUE CHECKLISTS** - subissues have better ordering which allows for long-run planning
:thread: **Rich Thread UX** - now your agents can ask you questions, ask for approvals, suggest tasks and you can approve or refine them right in your task threads
:cloud:  **BETA: Sandbox Providers** - Cloud sandboxing is in beta - the API ships in this release and we'll be adding more providers
... and *tons* of other improvements and bugfixes.

## Community

Thank you to everyone who contributed to this release!

@akhater, @aronprins, @GodsBoy, @LeonSGP43, @neerazz, @NoronhaH, @rbarinov, @rvanduiven, @SgtPooki, @superbiche

## WHATS NEXT (:motorway:  Roadmap)

* **Longer-range planning and execution** - Paperclip will support longer and longer tasks and work until it's done
* **Secrets Service v2** - an important prereq for Paperclip cloud
* **Artifacts, memory, and knowledge**
* **Conference Room** aka CEO/Agent Chat

## What's on my mind

* **Documentation & Blog posts** - I've fallen behind on the docs but aron has done a good job here - we'll be setting up Clips to help maintain these
* **Paperclip Cloud** - will be a critical unlock for us, but even the shared team story needs developed more - *where should the work be done* and *where are the outputs stored* and *how do we surface them to users*? Each of these questions are a core Paperclip service that needs developed
* **Paperclip Bench** - In the vein of SWE-Bench I've started an internal benchmark for Paperclip - we have to be able to measure that our changes are improving the system and not regressing
* **Paperclip Connections Store** - connecting to Github, Slack, Google Docs, and the hundreds of other services we use every day should be easy, secure, and configurable per agent and team

## Press

I met with the [Wisemen about Paperclip](https://x.com/dotta/status/2045146539534827998)

## WHAT I NEED FROM YOU

FOLLOW THIS TWITTER ACCOUNT: https://x.com/papercliping - that's the only official one, report any others

## In Summary

PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK

Every single person will be managing a team of a dozen, or a hundred, or a thousand agents and Paperclip will be the default tool to manage it all.

ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:

FULL RELEASE NOTES

https://github.com/paperclipai/paperclip/blob/master/releases/v2026.427.0.md

||@everyone||

审核清单

交接前：

1. 版本和日期必须与对应的 releases/vYYYY.MDD.P.md 完全一致。
2. 贡献者列表必须与变更日志一致（应用相同的排除项：机器人以及变更日志技能中规范的排除人员列表）。
3. 亮点必须是变更日志「亮点」部分内容的子集——必须是已发布的相同功能，不能杜撰或包含预 Alpha 阶段的工作。
4. WHATS NEXT 和 What's on my mind 必须取材于真实的近期问题／当前目标——不能凭空捏造主题。
5. 各部分的风格（全大写与标题式大小写）必须保持一致。
6. 结尾标语必须为 ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:，且 ||@everyone|| 必须是最后一行。
7. 发布问题上的 discord_announcement 文档必须已更新，且公告也必须以带围栏的代码块形式发布在评论中。

此技能不会发布到 Discord。它只用于准备公告素材。