Paperclip adds persistent application overlays and catalog images to plugins

Paperclip contributors opened PR #13646 on September 19, 2026, expanding the platform's plugin architecture with persistent application overlays and structured catalog images. The pull request allows extension modules to mount persistent visual interfaces and stateful tools directly into company workspaces without requiring dedicated web hosting or separate reverse proxies. Concurrently, issue #13640 reveals a severe state machine dead-end where tasks cancelled prior to dispatch enter an unrecoverable hold marked replay: blocked, offering no administrative board, API, or user comment recovery path. Furthermore, issue #13632 highlights technical debt in the execution engine, where durable-wait timeout rules have been duplicated across six separate service locations, resulting in conflicting retry intervals, dropped task events, and inconsistent recovery sweeps across distributed execution nodes.

The facts

- PR #13646 introduces application overlay mounting and cached catalog images for Paperclip's company plugin ecosystem. - Enables persistent visual dashboards and interactive widgets to survive agent task teardowns within company environments. - Issue #13640 details how pre-dispatch task cancellation sets replay: blocked, creating permanent orphan tasks that cannot be dismissed or resumed. - Issue #13632 documents six divergent implementations of durable-wait timeout rules across task runners, scheduling queues, and recovery loops. - The divergent wait rules cause state drift between the front-end status board and back-end execution workers during network interruptions.

Why it matters

As enterprise agent frameworks mature, plugins require richer graphical interfaces to display task trajectories, intermediate documents, and human-in-the-loop approvals. Providing application overlays as a native platform capability eliminates the need for fragile sidecar web servers. However, state machine deadlocks during task cancellation demonstrate that background execution guarantees must be hardened before complex UI overlays can be safely entrusted with production orchestration.

Current

Inspected on 2026-09-19. The Paperclip stable-channel baseline is v2026.916.0 published 2026-09-16T18:15:11Z. The primary source was open (not merged) when captured. Mainline merges, open proposals and packaged releases are distinct availability states; the release baseline does not establish that a proposal has shipped.

Evidence

Primary evidence: paperclipai/paperclip PR #13646 (https://github.com/paperclipai/paperclip/pull/13646). Supporting context: paperclipai/paperclip issue #13640 (https://github.com/paperclipai/paperclip/issues/13640); paperclipai/paperclip issue #13632 (https://github.com/paperclipai/paperclip/issues/13632). The source bodies and linked context were inspected. Test results quoted from contributors remain attributed reports, not independently reproduced experiments.

Operator take

Expanding plugin capabilities with visual overlays is valuable for enterprise visibility, but internal orchestration invariants must remain the primary architectural focus. A task lifecycle that can be permanently wedged by cancelling an unassigned issue represents a fundamental reliability flaw for automated execution pipelines. Engineering teams using Paperclip should audit task state machines and consolidate duplicated wait rules before deploying extensive custom plugin overlays in high-volume production workspaces.

Caveat

Plugin overlays run within sandboxed iframe boundaries and inherit company-level security policies, preventing unauthorized data exfiltration across tenant accounts. The pre-dispatch cancellation bug currently requires direct database intervention to clear blocked task flags until a formal state machine patch is merged.