mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-20 09:50:48 +01:00
docs(release): stable notes for the 2026.1120.0-beta.0 soak (v2026.1123.0) (#22372)
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - The release process promotes a soaked beta to stable. The stable GitHub Release body comes from `releases/beta/v<beta-version>.md` on `master` > - Beta `2026.1120.0-beta.0` published in workflow run 44647487455. Its `draft_stable_notes` job pushed a commit-log skeleton to this branch > - The skeleton is a raw commit list. It is not usable as release notes > - This pull request replaces the skeleton with curated stable notes. Each claim traces to a pull request in `v2026.1117.0..28043f8b` > - The benefit is that the stable promotion for this beta (v2026.1123.0) finds finished notes on `master` ## Linked Issues or Issue Description **Issue type** Missing content **Where is the issue?** `releases/beta/v2026.1120.0-beta.0.md` is the stable-notes file for the `2026.1120.0-beta.0` soak. At the branch head before this commit, it holds only the auto-generated commit-log skeleton. **What's wrong?** The stable promotion reads this file from `master` and publishes it as the GitHub Release body. A raw commit list is not suitable as a release body. **Suggested fix** Merge the curated notes. Correct the H1 and the `> Released:` line in a follow-up if the promotion date moves. ## What Changed - Replaced the skeleton in `releases/beta/v2026.1120.0-beta.0.md` with curated stable notes for v2026.1123.0, in the same layout as `releases/v2026.1117.0.md`: overview, Breaking Changes, Highlights, Improvements, Fixes, Upgrade Guide, Contributors - The notes are delta-framed against `releases/v2026.1117.0.md`. Features that the previous stable already describes are not repeated - The Upgrade Guide lists migrations `0452` through `0499` with one-phrase effects, the new environment variables with defaults, and the bundled harness pins - Release and CI internals, smoke specs, canary tooling, Paperclip Cloud work, dependency bumps, and test-only changes are left out ## Verification - Beta publish is complete: npm dist-tag `beta` is `2026.1120.0-beta.0`, tag `beta/v2026.1120.0-beta.0` points at `28043f8b93fa208ac83f96946953d05e7ba1dfd3`, and `publish_beta`, both `smoke_beta` jobs and `draft_stable_notes` in run 44647487455 succeeded. The beta Docker build (run 44679279012) succeeded - `git rev-list --count v2026.1117.0..28043f8b93fa208ac83f96946953d05e7ba1dfd3` returns 1222, which matches the overview and Contributors section - Contributors are the 16 unique GitHub logins of the commit authors in the range, read from the GitHub API with `[bot]` accounts excluded. External handles are thanked by name - Every `#NNNN` link in the file traces to a commit in the range (294 cited pull requests) - Migration numbers, setting keys, env var names, and defaults were checked in the code at the source commit, not in commit subjects - The file contains no internal ticket ids or instance-local links - The diff changes one file under `releases/` and no source files ## Risks - Low risk: a single markdown file, no source changes. If the promotion date moves past 2026-11-23, the H1 and `> Released:` line need a one-line update before the stable dispatch - The `draft_stable_notes` job force-pushes this branch name. A rerun of that job replaces this commit with the skeleton. Do not rerun it for this beta ## Model Used - Claude (Anthropic), model ID `claude-opus-5-5` (Claude Opus 5.5), tool use via Claude Code ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [ ] I have run tests locally and they pass - [ ] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: devinfoley <139239+devinfoley@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 file changed
+84
@@ -0,0 +1,84 @@
|
||||
# Paperclip v2026.1123.0
|
||||
|
||||
> Released: 2026-11-23
|
||||
|
||||
Paperclip v2026.1123.0 carries 1,222 commits, promoted from `2026.1120.0-beta.0`. The headline is reliability you can see: when a run is cut off and cannot resume exactly, the task now continues in a fresh run from its last saved work, restarts and deploys no longer spend the failure budget, and Retry, queue position, and a new **Move it forward now** action say what will actually happen. Around that: connected apps become first-class in task chat — interactive MCP App widgets, app questions answered in chat, live tool progress, and app-published skills — plus Tailscale networks for SSH environments, plugin-provided connectors, Fable 5.2 and GPT-6.2, a redesigned Routines page and Settings → Secrets, Inbox requests you can claim and transfer, per-agent interaction permissions, and Claude runs that wait for their own background commands. Underneath, the server does much less database and memory work per active agent, and remote sandbox follow-ups default to a warm sandbox.
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
- **Assistant connections (MCP) are always on.** The experimental `enablePublicMcp` setting is retired: its default is now `true`, a stored or patched `false` is ignored, and the Experimental toggle and enable prompts are gone. Any authenticated instance with a valid public URL now serves `/mcp/paperclip` discovery, OAuth, and tools without a setup step; a connection still exists only after a person approves OAuth consent for one company, and that person or an admin can revoke it. There is no instance-wide switch to turn the endpoint off, so if you had kept it off deliberately, restrict `/mcp/paperclip` at your reverse proxy. ([#22015](https://github.com/paperclipai/paperclip/pull/22015))
|
||||
- **Native tasks with pull request deliverables stay open until the PR is merged.** Before accepting Done, the server checks every non-archived `pull_request` work product and GitHub PR artifact against GitHub, and only a verified merge passes; open, draft, closed-unmerged, unavailable, or malformed PRs keep the task open with corrective feedback and the existing bounded continuation. Entering a configured review stage does not require a merge, PR links mentioned only in prose are not deliverables, no human approval step is added, and tasks already finished are not touched. ([#22244](https://github.com/paperclipai/paperclip/pull/22244))
|
||||
- **In `local_trusted` mode, agent processes no longer get implicit board access.** A credential-less local request is now checked against the process behind the connection; when it comes from an agent run's process tree it is treated as unauthenticated and must use the run's own credentials, including on the live-events WebSocket. Your browser, the CLI, and the server itself keep board access. Per `doc/DEPLOYMENT-MODES.md`, Windows and other platforms without process inspection — and Linux when `/proc/net/tcp` cannot be read — keep the old behavior and log a warning; authenticated deployments are unaffected. Custom scripts that agents run and that relied on unauthenticated local API calls must send the run's credentials. ([#21181](https://github.com/paperclipai/paperclip/pull/21181), [#21209](https://github.com/paperclipai/paperclip/pull/21209))
|
||||
- **Projects no longer choose where runs execute.** A project's workspace storage is fixed when it is created: `PATCH /projects/:id` rejects any storage change with `409 project_storage_locked`, the Environment and Workspace storage selectors are gone from Project Configuration, `Project.environmentId` is removed from the API contract, and a legacy `executionWorkspacePolicy.environmentId` is stripped on create and update. Runs use the agent's default environment, then the instance default, then local; where a project had pinned an environment, set it on the agent instead. ([#20835](https://github.com/paperclipai/paperclip/pull/20835), [#20860](https://github.com/paperclipai/paperclip/pull/20860))
|
||||
- **Agents no longer receive gateway token values.** When an agent with delegated authority creates a tool gateway token, the response carries metadata and `pendingReveal: true` but no token; the token's responsible person reveals it once with the new person-only `POST /api/tool-gateway/gateway-tokens/:tokenId/reveal` (a second reveal returns `409`, anyone else `403`). Tokens issued before the upgrade are unchanged; agent workflows that read the token from the create response must change. ([#20581](https://github.com/paperclipai/paperclip/pull/20581), [#20613](https://github.com/paperclipai/paperclip/pull/20613))
|
||||
- **The server refuses to start ACPX agents when an `ACPX_AUTH_*` variable is set on the host.** With the ACPX 0.22 upgrade those variables would authenticate every agent with the host's credential, so remove them from the Paperclip server environment. The same change limits ACPX model selection to models the agent advertises (Claude is exempt) and stops passing `XAI_API_KEY` through. ([#20770](https://github.com/paperclipai/paperclip/pull/20770))
|
||||
- **Agents can no longer change budgets through side routes.** A changed `budgetMonthlyCents` on `PATCH /api/agents/:id`, a configuration rollback that changes the budget, a positive budget on agent create or an immediate hire, and built-in agent provision overrides are now board-only; hires that need approval keep the proposed budget but activate it only on approval. ([#20213](https://github.com/paperclipai/paperclip/pull/20213))
|
||||
- **Native agents no longer receive `PAPERCLIP_NATIVE_MCP_NAME`, `_URL`, or `_TOKEN`.** Assigned MCP gateway tools reach every native harness through the Runner relay, so no provider process holds a gateway token; custom instructions or skills that read these variables stop working. ([#21274](https://github.com/paperclipai/paperclip/pull/21274))
|
||||
- **Claude agents started through ACPX lose Claude's built-in scheduling tools.** `CronCreate`, `CronDelete`, `CronList`, and `ScheduleWakeup` are denied and `CLAUDE_CODE_DISABLE_CRON=1` is set on every Claude launch; agents schedule through Paperclip routines and monitors instead. ([#21276](https://github.com/paperclipai/paperclip/pull/21276))
|
||||
- **Agents can only reach plugin tools through an installed connection.** Legacy plugin tools now run through an implicit plugin connector: migration `0491` seeds one record per installed legacy-tools plugin and company, and on boot the server turns each into a company-installed connection so existing access carries over. Agents without an installed connection get `deny_connection_not_installed`, and saved Off or Ask-first rules can only restrict access further. ([#22019](https://github.com/paperclipai/paperclip/pull/22019), [#22237](https://github.com/paperclipai/paperclip/pull/22237))
|
||||
- **Agents can no longer create unauthenticated routine webhooks.** An agent create, update, or revision restore that sets `signingMode: "none"` returns `403`; agents may use `bearer` (the default) or `hmac_sha256`, and board users keep every option. ([#21006](https://github.com/paperclipai/paperclip/pull/21006))
|
||||
- **Remote sandbox runs default to a warm sandbox.** When no lifecycle is set on the session, environment, or agent, Codex, OpenCode, and ACPX Claude runs on Daytona, CreateOS, or boxd keep their sandbox, Runner, and workspace between turns for the idle window (the environment's `runnerIdleTimeoutMs`, then the agent's `idleTimeoutMs`, then 5 minutes); with a managed AI account this applies to Codex only. Measured on Daytona, a Codex follow-up fell from 30.4 s to 7.6 s and a Claude follow-up from about 30 s to 11.0 s. Sandboxes stay up longer and use more provider time; to keep per-turn sandboxes, set the lifecycle on the environment or agent. ([#20048](https://github.com/paperclipai/paperclip/pull/20048))
|
||||
|
||||
## Highlights
|
||||
|
||||
- **Tasks continue on their own after interruptions** — Last release made Runner runs continue through restarts in far more cases; now, when an unfinished run cannot be resumed exactly for any reason that is not the person's, the task continues in a fresh run from its last saved workspace and conversation, and that run is told what the cut-off run already did ([#21135](https://github.com/paperclipai/paperclip/pull/21135), [#21257](https://github.com/paperclipai/paperclip/pull/21257)). A new sweep makes sure no open agent task is left with nothing running, nothing pending, and nobody else's move ([#21139](https://github.com/paperclipai/paperclip/pull/21139)). Restarts and deploys use their own lane and no longer spend the failure budget ([#21019](https://github.com/paperclipai/paperclip/pull/21019), [#21046](https://github.com/paperclipai/paperclip/pull/21046), [#21314](https://github.com/paperclipai/paperclip/pull/21314)); recovery is paced with person-started work first, continues only recent interruptions newest-first, and caps each task at six automatic attempts per hour ([#21234](https://github.com/paperclipai/paperclip/pull/21234), [#21222](https://github.com/paperclipai/paperclip/pull/21222), [#21347](https://github.com/paperclipai/paperclip/pull/21347)). During a deploy the replacement server takes new run starts while the old one drains, and a crashed server's runs end in about 2 minutes ([#21127](https://github.com/paperclipai/paperclip/pull/21127), [#21258](https://github.com/paperclipai/paperclip/pull/21258), [#21238](https://github.com/paperclipai/paperclip/pull/21238)). When a task moves to a new sandbox, the sandbox holding unsaved files is parked until they are saved, discarded, or 7 days pass ([#21304](https://github.com/paperclipai/paperclip/pull/21304)). Automatic recovery also pauses company-wide while runs keep failing before they start, and provider outages wait on a 1-, 2-, then 5-minute backoff for up to 30 minutes instead of asking for Retry ([#21443](https://github.com/paperclipai/paperclip/pull/21443), [#21561](https://github.com/paperclipai/paperclip/pull/21561), [#22139](https://github.com/paperclipai/paperclip/pull/22139), [#22194](https://github.com/paperclipai/paperclip/pull/22194)).
|
||||
- **Retry and the task view say what will happen** — Retry is offered only when it will work: it is hidden while an automatic continuation or scheduled retry is pending, a task with a queued continuation shows as **continuing**, and a parent waiting on open subtasks shows no false Retry ([#21264](https://github.com/paperclipai/paperclip/pull/21264), [#21353](https://github.com/paperclipai/paperclip/pull/21353), [#21315](https://github.com/paperclipai/paperclip/pull/21315), [#21320](https://github.com/paperclipai/paperclip/pull/21320)). After a continuation has waited 15 minutes, **Move it forward now** puts it at the front of the agent's queue without ever starting a second run ([#21373](https://github.com/paperclipai/paperclip/pull/21373), [#21385](https://github.com/paperclipai/paperclip/pull/21385)). A queued run whose agent is at its run limit shows its place in line ("X of Y in line") with a link to configure the limit, and the per-agent limit is now enforced in the claim itself, including across two servers during a deploy ([#21405](https://github.com/paperclipai/paperclip/pull/21405), [#21433](https://github.com/paperclipai/paperclip/pull/21433), [#21349](https://github.com/paperclipai/paperclip/pull/21349)). A model-unavailable failure offers **Try again**, which rechecks the model before starting, and plain-language notices replace internal recovery codes ([#21244](https://github.com/paperclipai/paperclip/pull/21244), [#21348](https://github.com/paperclipai/paperclip/pull/21348)).
|
||||
- **Connected apps in task chat** — Paperclip is now an MCP Apps host: when a connected MCP server publishes a view for a tool, the result renders as an interactive widget in task chat, in a sandboxed opaque-origin iframe whose tool calls need `tools:use` and reach only that connection's app-visible tools under existing policy, Ask first, and audit. Widgets can propose a message that is sent as your comment only after you click **Send**, share context the next run receives marked as untrusted, and open full screen ([#21119](https://github.com/paperclipai/paperclip/pull/21119), [#21266](https://github.com/paperclipai/paperclip/pull/21266)). When an app asks a form question, a person-only "*App* needs your input" card appears in chat; forms asking for passwords, keys, tokens, card numbers, or one-time codes are refused, and unanswered questions expire after 24 hours ([#21466](https://github.com/paperclipai/paperclip/pull/21466)). Long tool calls show live progress ([#21449](https://github.com/paperclipai/paperclip/pull/21449)), MCP resource reads get the same prompt-injection screening as tool results ([#21999](https://github.com/paperclipai/paperclip/pull/21999)), and **Circleback** joins the catalog as a native OAuth app.
|
||||
- **Skills from connected apps, and current MCP** — Connected apps can publish skills through the MCP Skills extension; they appear under **Skills from connected apps** and load for agents only after board approval, which is bound to the content digest and revoked when the manifest changes ([#21219](https://github.com/paperclipai/paperclip/pull/21219)). The MCP client negotiates the protocol version per server, speaking stateless MCP to 2026-07-28 servers and keeping the handshake for older ones, with OAuth `iss` validation ([#21140](https://github.com/paperclipai/paperclip/pull/21140)). Organization MCP connections can sign in as a machine with OAuth client credentials and rotate keys without downtime ([#21473](https://github.com/paperclipai/paperclip/pull/21473), [#21566](https://github.com/paperclipai/paperclip/pull/21566)). Behind the new experimental **Durable app actions (MCP Tasks)** setting, a long provider tool call becomes a durable task that survives timeouts, restarts, and deploys and is never started twice ([#21263](https://github.com/paperclipai/paperclip/pull/21263)).
|
||||
- **Tailscale networks for SSH environments** — Connectors gains Tailscale: you sign in by approving a Paperclip device in your own tailnet, with no OAuth app, API key, or hosted broker. SSH environments can then pick **Network → Tailscale**, choose a machine, and use **Prepare machine pairing**, which generates a vault-held key and a one-line command containing only the public key. Tailscale credentials are kept out of generic secret catalogs and bindings, and the Docker image now bundles the Tailscale client. ([#20617](https://github.com/paperclipai/paperclip/pull/20617), [#21526](https://github.com/paperclipai/paperclip/pull/21526))
|
||||
- **Plugins can add connectors** — Plugins can register connector types in the catalog and serve their tools from the plugin worker, with settings forms and per-tool timeouts (1–60 s, default 30 s); connectors with no sign-in or an API key connect through agent grants, a stopped worker returns a retryable `503 plugin_connector_unavailable`, plugin connector credentials are not exported, and the `create-paperclip-plugin` scaffold gains a `connector` template. ([#22004](https://github.com/paperclipai/paperclip/pull/22004), [#22019](https://github.com/paperclipai/paperclip/pull/22019), [#22201](https://github.com/paperclipai/paperclip/pull/22201), [#22237](https://github.com/paperclipai/paperclip/pull/22237), [#22249](https://github.com/paperclipai/paperclip/pull/22249))
|
||||
- **Fable 5.2 and GPT-6.2** — `claude-fable-5-2` (including Bedrock `global.anthropic.claude-fable-5-2`), `gpt-6.2-sol`, and `gpt-6.2-astra` are available, with Codex 0.170.0 and Claude Agent SDK 0.3.328 (Claude Code 2.1.328) now bundled. A CLI too old for the selected model stops with an error naming both versions, and native Codex on an older CLI falls back to `gpt-6.1-sol` or `gpt-6-astra` with a visible message; the Codex default stays `gpt-6.1-sol`. ([#22222](https://github.com/paperclipai/paperclip/pull/22222), [#22278](https://github.com/paperclipai/paperclip/pull/22278))
|
||||
- **Claude runs wait for their own background commands** — When Claude Code started a background shell command and ended its turn, the run used to fail with `native_finalization_missing`; native ACPX Claude runs now stay open while the command runs, for a bounded wait that ends early when a person comments, and continue in the turn Claude starts when it finishes. A Claude provider with no background work is also kept between turns of the same run. ([#21293](https://github.com/paperclipai/paperclip/pull/21293), [#21316](https://github.com/paperclipai/paperclip/pull/21316), [#21422](https://github.com/paperclipai/paperclip/pull/21422), [#21423](https://github.com/paperclipai/paperclip/pull/21423), [#21453](https://github.com/paperclipai/paperclip/pull/21453), [#21607](https://github.com/paperclipai/paperclip/pull/21607), [#21612](https://github.com/paperclipai/paperclip/pull/21612))
|
||||
- **Inbox requests you can claim and hand off** — Inbox adds personal, unassigned, company, all-assignee, and archived views; you can claim, transfer, personally close, snooze, and restore requests, and see receipts for work someone else handled for you, while domain permissions still decide who may resolve each request. Companies and projects get a decision owner and companies a budget owner, and compact cards open artifacts and approvals in a side panel next to the task thread. ([#20959](https://github.com/paperclipai/paperclip/pull/20959), [#20961](https://github.com/paperclipai/paperclip/pull/20961))
|
||||
- **Per-agent interaction permissions** — Admins can restrict, one agent at a time, whether other agents may assign it tasks, mention it, comment on or edit its tasks, or configure it, and the same in the outgoing direction, plus whether it may assign work to people. Every setting starts unrestricted and no existing agent changes; an explicit restriction cannot be overridden by CEO role, management, grants, or the responsible person, and human actions are unaffected. This release manages them through `paperclipai agent interaction-permissions` and the API (there is no UI yet); deploy all servers and workers on this release first, since older binaries do not enforce them. ([#20411](https://github.com/paperclipai/paperclip/pull/20411), [#20422](https://github.com/paperclipai/paperclip/pull/20422))
|
||||
- **Redesigned Routines and Secrets pages** — The routine page puts history (20 per page), version history, audit log, and Run now in one place; Edit saves in one revision-checked request, webhooks are created, tested, and removed (with Undo) from the Edit dialog, and the list gains project, agent, enabled, responsible-person, and source filters that remember your view ([#22205](https://github.com/paperclipai/paperclip/pull/22205), [#22182](https://github.com/paperclipai/paperclip/pull/22182), [#22009](https://github.com/paperclipai/paperclip/pull/22009), [#22177](https://github.com/paperclipai/paperclip/pull/22177)). Settings → Secrets is rebuilt around what people manage: folders always on, **Provided by** and **Used by** columns, managed secrets grouped by origin, a two-field New secret dialog that can bind the secret to selected agents, a sectioned details panel, and a Recently decided list for proposals ([#21225](https://github.com/paperclipai/paperclip/pull/21225)).
|
||||
|
||||
## Improvements
|
||||
|
||||
- **Delete data read through a connection** — A connection's Permissions tab gains **Delete data**, with counts in the confirmation, and removing a connection offers **Also delete data read through this connection**, which also deletes every copy of the affected run logs. ([#22010](https://github.com/paperclipai/paperclip/pull/22010))
|
||||
- **Onboarding finishes in agent chat** — Onboarding opens a chat with your first agent and starts a live welcome instead of creating an execution task and project; the agent proposes work for you to accept or creates a task when you ask for one. New standing chats are unnumbered, so the first execution task gets number 1; existing identifiers are unchanged. ([#22077](https://github.com/paperclipai/paperclip/pull/22077))
|
||||
- **SSH environments and AI accounts** — New SSH environments use the agent's Paperclip AI account by default; a new Advanced option, **Use authentication configured on the remote machine**, is off for new environments and on for existing ones, and saved configuration is not rewritten ([#21248](https://github.com/paperclipai/paperclip/pull/21248)). Codex and Claude subscription sign-in from Connections picks an eligible computer for you and says when none is available ([#20906](https://github.com/paperclipai/paperclip/pull/20906)).
|
||||
- **Sidebar and navigation** — Foldable subtasks in the sidebar ([#21649](https://github.com/paperclipai/paperclip/pull/21649)); pin tasks, agent chats, and projects from Recents, with pinned chat agents first and reorderable by drag or keyboard ([#22219](https://github.com/paperclipai/paperclip/pull/22219), [#20830](https://github.com/paperclipai/paperclip/pull/20830)); Recents keeps its order, hides archived tasks, and leaves automated work out of personal Recents ([#22251](https://github.com/paperclipai/paperclip/pull/22251), [#22024](https://github.com/paperclipai/paperclip/pull/22024), [#21904](https://github.com/paperclipai/paperclip/pull/21904), [#21859](https://github.com/paperclipai/paperclip/pull/21859)); projects open on Tasks ([#22264](https://github.com/paperclipai/paperclip/pull/22264)); and cancelling a parent can cancel its subtasks ([#22228](https://github.com/paperclipai/paperclip/pull/22228)).
|
||||
- **Faster task chat** — Tasks are preloaded in batches and cold tasks open in one request, the first frame is prepared before a task opens, a slow transcript no longer hides the chat, and Recents open from cache ([#20355](https://github.com/paperclipai/paperclip/pull/20355), [#20592](https://github.com/paperclipai/paperclip/pull/20592), [#20286](https://github.com/paperclipai/paperclip/pull/20286), [#21557](https://github.com/paperclipai/paperclip/pull/21557), [#21650](https://github.com/paperclipai/paperclip/pull/21650)). New tasks save in the background, so the composer closes immediately and queued creations resume after a reload ([#20831](https://github.com/paperclipai/paperclip/pull/20831)).
|
||||
- **GitHub pull request previews** — PR links in Markdown show a card with title, state, and mergeability, using your eligible GitHub connection, otherwise company credentials or public access, and failing closed when a configured connection cannot supply credentials; link status is cached in the database ([#20593](https://github.com/paperclipai/paperclip/pull/20593), [#20654](https://github.com/paperclipai/paperclip/pull/20654), [#21746](https://github.com/paperclipai/paperclip/pull/21746)).
|
||||
- **Agents and the org chart** — Org charts get three card tiers with refined identity editing and clearer save feedback, and instruction files can be renamed ([#20973](https://github.com/paperclipai/paperclip/pull/20973)); All Agents filters by model, status, harness, and connection ([#20317](https://github.com/paperclipai/paperclip/pull/20317)); instruction history credits the real writer of file-update saves ([#19515](https://github.com/paperclipai/paperclip/pull/19515), @lucktastic); and `paperclipai agent permission:grant` and `permission:revoke` change one permission key without touching other grants ([#20323](https://github.com/paperclipai/paperclip/pull/20323)). Agents can list routines and change a routine's fields, schedule, and filing with the new `list_routines` and `update_routine` tools; on a routine the agent does not run, reassigning it, turning it on, changing its schedule, starting a run, or restoring a revision needs the directing person's `tasks:assign` ([#22274](https://github.com/paperclipai/paperclip/pull/22274)).
|
||||
- **Usage limits and costs** — Usage-limit reset countdowns are live and in your time zone ([#22225](https://github.com/paperclipai/paperclip/pull/22225)); a limit with a calendar reset time waits until then and retries automatically, and a rate limit with no reported reset retries after an estimated hour while quota exhaustion still waits for a person ([#20692](https://github.com/paperclipai/paperclip/pull/20692), [#22216](https://github.com/paperclipai/paperclip/pull/22216)); chat agents receive your browser time zone ([#20898](https://github.com/paperclipai/paperclip/pull/20898)); and cost reports count unpriced events so missing charges show as unpriced rather than free ([#20889](https://github.com/paperclipai/paperclip/pull/20889)).
|
||||
- **Secrets stay out of agent output** — Values from secret-bound environment variables are masked in live logs, excerpts, adapter events, results, and native log export; values under 8 characters are not masked ([#21341](https://github.com/paperclipai/paperclip/pull/21341)). For OpenCode launches with configured secrets, exact secret values are filtered from shell output and stored tool results and redacted from model requests that go through Paperclip's proxy; encoded values such as base64 are not caught, and the launch is refused if `awk`, `mkfifo`, or `rm` is missing ([#21330](https://github.com/paperclipai/paperclip/pull/21330)). Claude MCP bearer tokens are no longer passed in process arguments ([#22206](https://github.com/paperclipai/paperclip/pull/22206)).
|
||||
- **Connections** — Connections to another Paperclip instance get a default name and agent instructions, and connecting an instance to itself is refused ([#22018](https://github.com/paperclipai/paperclip/pull/22018)); Assistant connections can create tasks for a person or unassigned and list people without emails ([#22011](https://github.com/paperclipai/paperclip/pull/22011)); Sentry gains a user auth token sign-in for unattended agents ([#20823](https://github.com/paperclipai/paperclip/pull/20823)); Slack's **Require at-mention in channels** no longer requires a mention for replies in existing threads, and Slack shows short agent progress notes instead of tool chatter ([#20821](https://github.com/paperclipai/paperclip/pull/20821), [#20827](https://github.com/paperclipai/paperclip/pull/20827)); the pasted MCP server setup shows one sign-in line with **Change** ([#21469](https://github.com/paperclipai/paperclip/pull/21469)); GitHub review bots take new messages into an active review and start the next turn for a queued push ([#22066](https://github.com/paperclipai/paperclip/pull/22066), [#22223](https://github.com/paperclipai/paperclip/pull/22223)); and agents can save a `call_api` GET response as an artifact ([#20606](https://github.com/paperclipai/paperclip/pull/20606)).
|
||||
- **Plugin environments** — Moving an agent to a plugin environment pauses it, prepares the new resources, and resumes only after verification ([#20375](https://github.com/paperclipai/paperclip/pull/20375)); subscription sign-in can run on the agent's own computer where the plugin supports it ([#20417](https://github.com/paperclipai/paperclip/pull/20417)); configured plain and secret variables reach plugin-environment Runner tasks ([#21280](https://github.com/paperclipai/paperclip/pull/21280)); and the plugin SDK adds warm managed Runners, async workspace preparation, turn-scoped attachment downloads, and retried activation after an `initialize` timeout ([#21065](https://github.com/paperclipai/paperclip/pull/21065), [#20865](https://github.com/paperclipai/paperclip/pull/20865), [#20956](https://github.com/paperclipai/paperclip/pull/20956), [#20982](https://github.com/paperclipai/paperclip/pull/20982)). After a restart, a provider that supports it relaunches a released task as the next run from its warm checkpoint ([#22343](https://github.com/paperclipai/paperclip/pull/22343)).
|
||||
- **Experimental: AWS connector and Areas & Responsibilities** — Behind **AWS connector** (`enableAwsConnector`), connections mint a one-hour AWS credential at call time, either with an access key or with a role assumed through a Paperclip-signed token from a new per-company workload identity issuer, which needs AWS to reach the instance's public `/oidc/companies/:companyId/...` routes ([#22195](https://github.com/paperclipai/paperclip/pull/22195), [#22083](https://github.com/paperclipai/paperclip/pull/22083)). Role setup is guided: copy a prompt that has your agent deploy a per-connection CloudFormation template, or follow the CloudFormation or IAM steps by hand, then paste the role ARN ([#22233](https://github.com/paperclipai/paperclip/pull/22233)). Behind **Areas & Responsibilities dashboard** (`enableResponsibilities`), a responsibilities dashboard replaces Dashboard ([#22069](https://github.com/paperclipai/paperclip/pull/22069), [#22180](https://github.com/paperclipai/paperclip/pull/22180)). Agents can read a person's areas and responsibilities, and a responsibility can now hold company skills ([#22253](https://github.com/paperclipai/paperclip/pull/22253), [#22275](https://github.com/paperclipai/paperclip/pull/22275)). An agent working for the person who directed its run can change that person's areas and responsibilities directly: most changes are saved as a Dashboard version that person can undo (the tools say when a change cannot be undone), and a delete still needs an accepted confirmation card. An agent with no directing person can still only propose changes ([#22261](https://github.com/paperclipai/paperclip/pull/22261)).
|
||||
- **Lighter and steadier server** — A finished session's tool authority is released, so heap no longer grows per run, and the tool catalog is shared across sessions at about 40–80 KB per extra session instead of 7.6–15 MB ([#21415](https://github.com/paperclipai/paperclip/pull/21415), [#21482](https://github.com/paperclipai/paperclip/pull/21482)); idle database connections release their buffers and dedicated connections are capped with a fair queue ([#21432](https://github.com/paperclipai/paperclip/pull/21432), [#21693](https://github.com/paperclipai/paperclip/pull/21693)); lease renewal is cheaper, which ends runs failing with lost controller leases under load ([#20924](https://github.com/paperclipai/paperclip/pull/20924), [#21242](https://github.com/paperclipai/paperclip/pull/21242)); run events are batched, recovery sweeps look only at changed rows, and many hot reads are cut down with new indexes ([#21460](https://github.com/paperclipai/paperclip/pull/21460), [#21872](https://github.com/paperclipai/paperclip/pull/21872), [#21435](https://github.com/paperclipai/paperclip/pull/21435), [#21434](https://github.com/paperclipai/paperclip/pull/21434)); readiness no longer waits for backlog-sized recovery and a slow start names its slow step ([#21014](https://github.com/paperclipai/paperclip/pull/21014), [#21247](https://github.com/paperclipai/paperclip/pull/21247)); workspace saves and restores are faster and identical captures reuse the last snapshot ([#20476](https://github.com/paperclipai/paperclip/pull/20476), [#20329](https://github.com/paperclipai/paperclip/pull/20329), [#20442](https://github.com/paperclipai/paperclip/pull/20442)); and the Runner reuses the sandbox's existing runnerd and provider packs ([#21949](https://github.com/paperclipai/paperclip/pull/21949)).
|
||||
- **Diagnostics** — A failed workspace setup command is named on the task page with its step, exit code, and redacted output tail ([#20478](https://github.com/paperclipai/paperclip/pull/20478)); generic adapter failures show a cause code without SQL text ([#20483](https://github.com/paperclipai/paperclip/pull/20483)); a queued turn says why it is waiting ([#21447](https://github.com/paperclipai/paperclip/pull/21447)); the runs read shows who started a retry ([#21486](https://github.com/paperclipai/paperclip/pull/21486)); remote MCP calls record why they failed ([#19768](https://github.com/paperclipai/paperclip/pull/19768), @Pavel-Guseynov); the reconciliation wake reason is shown ([#18236](https://github.com/paperclipai/paperclip/pull/18236), @DeadlySilent); and the opt-in `PAPERCLIP_SERVER_METRICS` exposes an admin-only server metrics endpoint ([#21708](https://github.com/paperclipai/paperclip/pull/21708)).
|
||||
- **Agent guidance** — Agents give clear final replies for tasks they cannot see (identical for missing, private, and other-company tasks), unreachable MCP servers, and board-only denials, name the page and the person for steps only a person can do, keep raw IDs out of replies, and get flatter tool schemas, named missing fields, and a stop after a repeated rejected call, which helps weaker models ([#20208](https://github.com/paperclipai/paperclip/pull/20208), [#20206](https://github.com/paperclipai/paperclip/pull/20206), [#21081](https://github.com/paperclipai/paperclip/pull/21081), [#21398](https://github.com/paperclipai/paperclip/pull/21398), [#21252](https://github.com/paperclipai/paperclip/pull/21252), [#21360](https://github.com/paperclipai/paperclip/pull/21360)). Links agents write with made-up hosts become board routes ([#21762](https://github.com/paperclipai/paperclip/pull/21762)), and generated chat titles follow agent renames ([#22102](https://github.com/paperclipai/paperclip/pull/22102)).
|
||||
- **Google Workspace connector** (still behind `enableGoogleWorkspaceConnector`) — The service picker shows a data-use disclosure, requests are limited to the submitted scopes, Read & write Calendar includes free/busy, and removing a Paperclip-managed Google connection revokes Google's access. ([#21998](https://github.com/paperclipai/paperclip/pull/21998), [#22001](https://github.com/paperclipai/paperclip/pull/22001), [#22026](https://github.com/paperclipai/paperclip/pull/22026), [#22065](https://github.com/paperclipai/paperclip/pull/22065))
|
||||
- **Star prompt** — Self-hosted instances ask once to star Paperclip on GitHub after five done tasks in a company, never during onboarding, over a dialog, or for established companies. ([#20453](https://github.com/paperclipai/paperclip/pull/20453), [#20713](https://github.com/paperclipai/paperclip/pull/20713), [#22031](https://github.com/paperclipai/paperclip/pull/22031))
|
||||
|
||||
## Fixes
|
||||
|
||||
- **Runs, Stop, and Retry** — Retry re-delivers the original wake, continues a connected task from saved work when an exact chat replay is refused, and is released once the decision it waited on is resolved ([#20970](https://github.com/paperclipai/paperclip/pull/20970), [#21038](https://github.com/paperclipai/paperclip/pull/21038), [#21267](https://github.com/paperclipai/paperclip/pull/21267)); a refused Retry says so instead of reporting "accepted" ([#21497](https://github.com/paperclipai/paperclip/pull/21497)); Retry on a scheduled retry starts it now or explains why not ([#20283](https://github.com/paperclipai/paperclip/pull/20283)); a person's Stop always ends the run as cancelled and is confirmed only after preparation settles, and Stop on a queued task removes it from the queue ([#21300](https://github.com/paperclipai/paperclip/pull/21300), [#21906](https://github.com/paperclipai/paperclip/pull/21906), [#21407](https://github.com/paperclipai/paperclip/pull/21407)); the board can confirm that a local run with no recorded process has stopped ([#20310](https://github.com/paperclipai/paperclip/pull/20310)); tasks continue after lost saved files, sandbox client timeouts, environment blockers, and failed warm-session cleanup ([#21541](https://github.com/paperclipai/paperclip/pull/21541), [#21736](https://github.com/paperclipai/paperclip/pull/21736), [#21959](https://github.com/paperclipai/paperclip/pull/21959), [#21977](https://github.com/paperclipai/paperclip/pull/21977)); a run that fills its sandbox disk stops retrying and a disk reserve keeps the Runner reachable ([#22239](https://github.com/paperclipai/paperclip/pull/22239), [#22068](https://github.com/paperclipai/paperclip/pull/22068)); done blockers release their dependents ([#21948](https://github.com/paperclipai/paperclip/pull/21948)); and a native worker reporting `done` or `needs_review` now starts the configured review stage ([#20882](https://github.com/paperclipai/paperclip/pull/20882), [#21005](https://github.com/paperclipai/paperclip/pull/21005)). An agent can no longer reopen or resume a task blocked by a recovery hold (it can still close it, and people can still change it) ([#22245](https://github.com/paperclipai/paperclip/pull/22245)), and a scheduled retry that has just come due shows as working for two minutes instead of offering Retry ([#22306](https://github.com/paperclipai/paperclip/pull/22306)).
|
||||
- **Messages, answers, and comments** — Your answer to an agent's question continues the task it blocked, including when the answer was saved before the agent closed the task ([#20931](https://github.com/paperclipai/paperclip/pull/20931), [#20996](https://github.com/paperclipai/paperclip/pull/20996)); a queued comment is redelivered unless the run cites it as handled, and a comment the closing run already read does not reopen a done task ([#21243](https://github.com/paperclipai/paperclip/pull/21243), [#21175](https://github.com/paperclipai/paperclip/pull/21175)); a person's comment merged into a system wake reopens a finished task ([#21914](https://github.com/paperclipai/paperclip/pull/21914)); a chat message over the agent's daily limit is held until the next UTC day instead of dropped, and messages from two conversations are never combined into one wake ([#20292](https://github.com/paperclipai/paperclip/pull/20292), [#20697](https://github.com/paperclipai/paperclip/pull/20697)); messages sent into a starting run no longer cause cancel or recovery errors ([#21661](https://github.com/paperclipai/paperclip/pull/21661), [#21747](https://github.com/paperclipai/paperclip/pull/21747)); parent and child results and chat outcomes are delivered once ([#21189](https://github.com/paperclipai/paperclip/pull/21189), [#21489](https://github.com/paperclipai/paperclip/pull/21489)); a `response_wake` with no response no longer wakes itself repeatedly ([#20935](https://github.com/paperclipai/paperclip/pull/20935)); board users can discard agent-authored queued messages ([#21458](https://github.com/paperclipai/paperclip/pull/21458)); and native document writes keep Markdown exactly ([#20605](https://github.com/paperclipai/paperclip/pull/20605)).
|
||||
- **Permissions and privacy** — Agent inbox reads and company artifact lists and search now apply private-task visibility ([#21092](https://github.com/paperclipai/paperclip/pull/21092), [#20595](https://github.com/paperclipai/paperclip/pull/20595)); invitation tokens are removed from HTTP request logs and from newly written run logs and excerpts, while existing logs are not rewritten ([#20343](https://github.com/paperclipai/paperclip/pull/20343), [#20360](https://github.com/paperclipai/paperclip/pull/20360)); ordinary managers can pick only themselves as a GitHub bot guest sponsor or automatic-task responsible member, while owners and admins can pick any eligible member ([#21218](https://github.com/paperclipai/paperclip/pull/21218)); an agent status change that would detach another run's live execution returns `409` ([#20271](https://github.com/paperclipai/paperclip/pull/20271)); agents can change a case to or from done or cancelled only as the assignee of its primary task ([#20686](https://github.com/paperclipai/paperclip/pull/20686)); tool gateway responses no longer include internal execution details, which stay in the audit ([#21464](https://github.com/paperclipai/paperclip/pull/21464)); and a tool approval stays valid through an OAuth refresh while a manual credential change still invalidates it ([#20340](https://github.com/paperclipai/paperclip/pull/20340)).
|
||||
- **Reassignment and handoff** — A native run can hand its task to a person without cancelling itself, reassignment starts the new owner right away without a stale lock or failed run, and a queued assignment run is withheld when its task moves to backlog. ([#20884](https://github.com/paperclipai/paperclip/pull/20884), [#20941](https://github.com/paperclipai/paperclip/pull/20941), [#21030](https://github.com/paperclipai/paperclip/pull/21030), [#21256](https://github.com/paperclipai/paperclip/pull/21256), [#21095](https://github.com/paperclipai/paperclip/pull/21095))
|
||||
- **Storage and sandboxes** — A storage outage on a run's critical path is waited out for about 10 minutes, small uploads retry, broken downloads resume, and expired or rotated S3 credentials are re-resolved ([#20299](https://github.com/paperclipai/paperclip/pull/20299), [#20313](https://github.com/paperclipai/paperclip/pull/20313), [#20456](https://github.com/paperclipai/paperclip/pull/20456)); a storage outage no longer blocks startup ([#21010](https://github.com/paperclipai/paperclip/pull/21010)); Daytona waits out state changes, forces a stop stuck for 30 s, retries a create that timed out before agent work, and retries connection failures ([#20212](https://github.com/paperclipai/paperclip/pull/20212), [#20609](https://github.com/paperclipai/paperclip/pull/20609), [#20828](https://github.com/paperclipai/paperclip/pull/20828), [#22087](https://github.com/paperclipai/paperclip/pull/22087)); warm sandboxes stop when their window ends ([#21410](https://github.com/paperclipai/paperclip/pull/21410)); a reusable sandbox that will not resume is safely replaced ([#20626](https://github.com/paperclipai/paperclip/pull/20626)); remote workspaces with outside-pointing symlinks are saved without those links ([#20569](https://github.com/paperclipai/paperclip/pull/20569)); image attachments open in remote native workspaces ([#20939](https://github.com/paperclipai/paperclip/pull/20939)); environment delete stops idle warm Runners ([#20957](https://github.com/paperclipai/paperclip/pull/20957)); fresh retries after unowned task storage use project storage ([#20756](https://github.com/paperclipai/paperclip/pull/20756), @lucktastic); blank lease IDs skip the database lookup ([#15200](https://github.com/paperclipai/paperclip/pull/15200), @xiehuanyi); and deleting a secret referenced by a binding proposal works ([#20193](https://github.com/paperclipai/paperclip/pull/20193)).
|
||||
- **Adapters** — Codex planning on Daytona no longer fails with `bwrap: loopback`, managed `git` and `gh` work in sandboxes that inject a runtime CA, and a slow but healthy Codex start is waited out ([#20820](https://github.com/paperclipai/paperclip/pull/20820), [#20364](https://github.com/paperclipai/paperclip/pull/20364), [#21329](https://github.com/paperclipai/paperclip/pull/21329)); native Claude's `git` and `gh` work again through the GitHub broker, and a Claude conversation continues after a Runner upgrade ([#20463](https://github.com/paperclipai/paperclip/pull/20463), [#21220](https://github.com/paperclipai/paperclip/pull/21220)); Claude ACP runs fail early with `claude_cli_version_incompatible`, naming both versions, when the bundled Claude Code is too old for Opus 5.5, and Bedrock `jp.` and `au.` model prefixes are recognized ([#13927](https://github.com/paperclipai/paperclip/pull/13927), @kimnamu) and `claude-opus-4-5` is in the Claude fallback list ([#12379](https://github.com/paperclipai/paperclip/pull/12379), @dan1d); OpenCode never saves reasoning as the reply, keeps tool-call markup and control tokens out of chat, answers MCP tool calls reliably, and refuses to start without its Paperclip tools ([#21051](https://github.com/paperclipai/paperclip/pull/21051), [#21761](https://github.com/paperclipai/paperclip/pull/21761), [#20886](https://github.com/paperclipai/paperclip/pull/20886), [#20964](https://github.com/paperclipai/paperclip/pull/20964)); Claude-through-ACPX runs with an older task session no longer fail about 20 s in ([#21062](https://github.com/paperclipai/paperclip/pull/21062)); remote MCP calls on the default deadline get 30 s ([#19768](https://github.com/paperclipai/paperclip/pull/19768), @Pavel-Guseynov); parallel tool calls over the limit reject only the overflow call, and assigned tool names resolve to their authorized alias ([#21913](https://github.com/paperclipai/paperclip/pull/21913), [#22213](https://github.com/paperclipai/paperclip/pull/22213)); agents are told which field a refused call failed ([#22037](https://github.com/paperclipai/paperclip/pull/22037), @lucktastic); and grok-local copies SSH skill contents correctly ([#22120](https://github.com/paperclipai/paperclip/pull/22120), @lucktastic).
|
||||
- **Connections** — Expired sign-ins are named in connection search, failed app sign-ins are explained with GitHub app install guidance, Permissions shows the selected ChatGPT workspace, large permission forms stay responsive, Railway reports restricted environments instead of a consent error, and OpenRouter returns `503` when its catalog is down and its setup models are searchable. ([#22211](https://github.com/paperclipai/paperclip/pull/22211), [#22234](https://github.com/paperclipai/paperclip/pull/22234), [#22023](https://github.com/paperclipai/paperclip/pull/22023), [#22008](https://github.com/paperclipai/paperclip/pull/22008), [#22214](https://github.com/paperclipai/paperclip/pull/22214), [#21468](https://github.com/paperclipai/paperclip/pull/21468), [#22034](https://github.com/paperclipai/paperclip/pull/22034)). GitHub Copilot is now its own connector, and older Copilot accounts, drafts, and links keep working ([#22238](https://github.com/paperclipai/paperclip/pull/22238)).
|
||||
- **Board UI** — The inbox badge counts only your items ([#21953](https://github.com/paperclipai/paperclip/pull/21953)); steering messages show screenshots and Markdown ([#20367](https://github.com/paperclipai/paperclip/pull/20367)); chat activity no longer freezes at "Working for 0s" ([#20559](https://github.com/paperclipai/paperclip/pull/20559)); breadcrumbs show the parent task, labeling a private parent as Private ([#20366](https://github.com/paperclipai/paperclip/pull/20366), [#20804](https://github.com/paperclipai/paperclip/pull/20804)); pinned sidebar links are back above More ([#20369](https://github.com/paperclipai/paperclip/pull/20369)); Request changes on a plan always takes a note ([#21721](https://github.com/paperclipai/paperclip/pull/21721)); composer autocomplete adds a space ([#21754](https://github.com/paperclipai/paperclip/pull/21754)); chat submission works on plain-HTTP origins and tablet composers stay above the keyboard ([#20308](https://github.com/paperclipai/paperclip/pull/20308), [#19725](https://github.com/paperclipai/paperclip/pull/19725)); company and unprefixed links resolve correctly ([#21026](https://github.com/paperclipai/paperclip/pull/21026), [#21794](https://github.com/paperclipai/paperclip/pull/21794), [#22100](https://github.com/paperclipai/paperclip/pull/22100)); artifact previews stay in agent chat ([#22252](https://github.com/paperclipai/paperclip/pull/22252)); and a task stays open when one of its reads returns 404 ([#21684](https://github.com/paperclipai/paperclip/pull/21684)).
|
||||
- **Other** — Secret proposals missing a name or justification return `422` instead of `500` ([#15348](https://github.com/paperclipai/paperclip/pull/15348), @awss1i); contended budget writes retry instead of returning `503` ([#21185](https://github.com/paperclipai/paperclip/pull/21185)); local agent processes no longer inherit systemd `NOTIFY_SOCKET` and `LISTEN_*` variables ([#11584](https://github.com/paperclipai/paperclip/pull/11584), @dzianisv); feedback-bundle phone redaction no longer mangles UUIDs or dates ([#21251](https://github.com/paperclipai/paperclip/pull/21251)); audit summaries no longer break when truncation cuts an emoji ([#22207](https://github.com/paperclipai/paperclip/pull/22207)); and the private-mode docs note adding the chat webhook ingress hostname to `PAPERCLIP_ALLOWED_HOSTNAMES` ([#18301](https://github.com/paperclipai/paperclip/pull/18301), @EldarPolitkin). A mistyped assigned tool name now lists up to three close assigned names ([#22327](https://github.com/paperclipai/paperclip/pull/22327)); a tool audit write that hits a deadlock retries instead of failing the call ([#22329](https://github.com/paperclipai/paperclip/pull/22329)); a superseded automatic GitHub review ends with a message that says whether a newer review is queued ([#22218](https://github.com/paperclipai/paperclip/pull/22218)); and installed Core plugin bundles refresh their descriptions without a version change ([#22295](https://github.com/paperclipai/paperclip/pull/22295)).
|
||||
|
||||
## Upgrade Guide
|
||||
|
||||
- **Before upgrading, check for duplicate Better Auth accounts.** Better Auth moves from 1.7.2 to the 1.7.16 security release, and migration `0465` replaces the account issuer index with a unique `account(provider_id, account_id)` index, which fails if duplicate provider/account pairs exist. Find them with `SELECT provider_id, account_id, count(*) FROM account GROUP BY provider_id, account_id HAVING count(*) > 1;` and resolve any rows it returns before upgrading; an empty result means `0465` can apply. Apply migrations before starting the new server; a 1.7.2 server still running during a rolling overlap keeps signing in new email/password users. ([#18906](https://github.com/paperclipai/paperclip/pull/18906), [#20839](https://github.com/paperclipai/paperclip/pull/20839))
|
||||
- **Migrations `0452`–`0499`** run on upgrade; none drops a table. `0466` drops `projects.environment_id` and `0467` re-adds it in the same transaction with its values preserved, briefly taking an exclusive lock on `projects` ([#20835](https://github.com/paperclipai/paperclip/pull/20835), [#20860](https://github.com/paperclipai/paperclip/pull/20860)). New tables: `0462` plugin lifecycle cursors (with a backfill); `0473`, `0474`, `0477`, `0478`, and `0483` MCP App views, skills, tasks, and app questions; `0480`–`0482` Tailscale connections (with a `company_secrets.system_purpose` backfill for Tailscale secrets only); `0485` automatic recovery brakes; `0488` recovery deferrals; `0489` link previews; `0490` connection data deletions; `0491` plugin legacy access (with a backfill, and the connection transport check re-added `NOT VALID`); `0492`–`0497` responsibilities, unused unless `enableResponsibilities` is on; `0498` per-company workload identity keys. New columns: `0452` cascades secret proposals when their secret is deleted; `0463` gateway token pending reveal; `0464` project environment (superseded by `0466`/`0467`); `0468` your time zone; `0469` decision and budget owners; `0471` deploy dispatch markers; `0472`, `0479`, and `0484` run, storage, and tool-progress bookkeeping; `0499` lets a responsibility hold a company skill (its constraints are validated without blocking reads or writes, and its indexes are built `CONCURRENTLY`). `0465` (Better Auth, above) and `0475` rebuild an index inside a transaction on small tables. The index-only migrations `0453`–`0461`, `0470`, `0476`, `0486`, and `0487`, and the indexes in `0469` and `0472`, are built `CONCURRENTLY` outside a transaction and are safe to rerun if interrupted. Expect `0462`, the `heartbeat_runs` indexes (`0453`, `0455`–`0457`, `0460`, `0470`, `0486`, `0487`), `0454`, `0469`, and `0495`'s constraint validation on `cost_events` (which does not block reads or writes) to take longer on instances with large run, activity, or cost histories.
|
||||
- **New environment variables**, none required. `DATABASE_DEDICATED_CONNECTION_MAX` (`24`) and `DATABASE_DEDICATED_CONNECTION_WAIT_MS` (`30000`) cap dedicated database connections with a fair queue ([#21693](https://github.com/paperclipai/paperclip/pull/21693)); `PAPERCLIP_REATTACH_PHASE_CAP_MS` (`180000`, clamped to 5000–600000, `0` or less turns it off) caps how long a new server spends reattaching the previous server's live runs after a swap ([#21450](https://github.com/paperclipai/paperclip/pull/21450)); `PAPERCLIP_SERVER_METRICS` (off; `true`/`1` or `false`/`0`, and any other value stops startup with an error) enables the instance-admin `GET /api/instance/server-metrics` ([#21708](https://github.com/paperclipai/paperclip/pull/21708)); `PAPERCLIP_DEBUG_WORK_SIGNALS` (off) writes database work-signal diagnostics to stderr ([#21640](https://github.com/paperclipai/paperclip/pull/21640)); and `PAPERCLIP_TAILSCALE_CLI` (`tailscale`) and `PAPERCLIP_TAILSCALED` (`tailscaled`) override the Tailscale binaries ([#20617](https://github.com/paperclipai/paperclip/pull/20617)). Remove any `ACPX_AUTH_*` variable from the server environment (see Breaking Changes).
|
||||
- **Experimental settings**: new `enableMcpTasks`, `enableAwsConnector`, and `enableResponsibilities`, all off by default ([#21263](https://github.com/paperclipai/paperclip/pull/21263), [#22195](https://github.com/paperclipai/paperclip/pull/22195), [#22069](https://github.com/paperclipai/paperclip/pull/22069)); `enablePublicMcp` is retired and always on (see Breaking Changes) ([#22015](https://github.com/paperclipai/paperclip/pull/22015)).
|
||||
- **Reverse proxies**: the AWS connector's role sign-in needs the public, unauthenticated `/oidc/companies/:companyId/.well-known/openid-configuration` and `/oidc/companies/:companyId/jwks.json` routes, which sit outside `/api` and return 404 until a key exists ([#22083](https://github.com/paperclipai/paperclip/pull/22083)).
|
||||
- **API clients**: gateway token creation by agents returns no token value (see Breaking Changes); `PATCH /projects/:id` returns `409 project_storage_locked` for storage changes and `Project.environmentId` is gone ([#20835](https://github.com/paperclipai/paperclip/pull/20835)); `POST /api/issues/:id/retry` waits up to 5 seconds and returns a refusal instead of "accepted" ([#21497](https://github.com/paperclipai/paperclip/pull/21497)); runs started by an agent from the run-now route are recorded as `manual` ([#21183](https://github.com/paperclipai/paperclip/pull/21183)); cost reports add `unpricedEventCount` ([#20889](https://github.com/paperclipai/paperclip/pull/20889)); issue runs add `retriedBy` ([#21486](https://github.com/paperclipai/paperclip/pull/21486)); and new routes include `PATCH /api/agents/:id/permission-grants`, `GET`/`PATCH /api/agents/:id/interaction-permissions`, `POST /api/issues/:id/recovery-actions/confirm-run-stopped`, the MCP App view routes under `/api/issues/:issueId/mcp-app-views`, `GET /api/companies/:companyId/issue-documents` (up to 200 documents), and the connection stored-content deletion routes.
|
||||
- **Telemetry**: when telemetry is enabled, `model.connected`, `task.created`, `task.completed`, `task.blocked`, `plan.created`, `plan.approved`, and `artifact.created` events with only enum, boolean, or count fields are sent, and `agent.task_run` gains a failure cause; `PAPERCLIP_TELEMETRY_DISABLED=1` and `DO_NOT_TRACK=1` still turn telemetry off ([#22250](https://github.com/paperclipai/paperclip/pull/22250)).
|
||||
- **Harness pins**: Codex 0.160.0 → 0.170.0 and Claude Agent SDK 0.3.286 → 0.3.328 (Claude Code 2.1.328) ([#22278](https://github.com/paperclipai/paperclip/pull/22278)); ACPX 0.13.1 → 0.22.0 ([#20770](https://github.com/paperclipai/paperclip/pull/20770)); the Daytona sandbox image updates Grok, Gemini CLI, Cursor, and GitHub CLI ([#22222](https://github.com/paperclipai/paperclip/pull/22222)). OpenCode 1.18.34, GitHub Copilot CLI 1.0.88, and Kimi Code 2.3.3 are unchanged. Older sandbox images keep their previous CLIs until a newer image is promoted.
|
||||
- No other configuration or API changes require action.
|
||||
|
||||
## Contributors
|
||||
|
||||
This release has 1,222 commits from 16 contributors. Thank you to everyone who contributed to this release!
|
||||
|
||||
@awss1i, @dan1d, @DeadlySilent, @dzianisv, @EldarPolitkin, @kimnamu, @lucktastic, @Pavel-Guseynov, @xiehuanyi, @zwidny
|
||||
Reference in new issue
Block a user