v2026.513.0
Developer-Y/cs-video-coursesv2026.513.0May 13, 2026by github-actions[bot]
AI Summary
This release introduces source-scoped recovery actions to manage stalled issues directly on the source, adds a new Blocked Inbox tab for triaging blocked work, and enhances local plugin development with CLI scaffolding and dev watcher support.
Key Highlights
- Source-scoped recovery actions create first-class recovery indicators on issue rows and detail surfaces, with resolution outcomes like restored, blocked, cancelled, or false_positive.
- A new Blocked Inbox tab surfaces blocked work with reason chips, filtering, search, and deterministic urgency sorting for clearer triage paths.
- Local plugin development is improved with CLI scaffolding, local-path installs, dashboard capabilities, and a dev watcher for instant reloads.
New Features
- Source-scoped recovery actions on the source issue with owner, evidence, wake policy, and resolution outcomes.
- Blocked Inbox attention view with chips, filtering, and urgency sorting.
- Local plugin development workflow with `paperclipai plugin init` scaffolding and dev watcher.
- Ordered sub-issue navigation in issue detail footers.
Full Release Notes
# v2026.513.0 > Released: 2026-05-13 ## Highlights - **Source-scoped recovery actions** — Stalled or missing-disposition recovery now creates first-class recovery actions on the source issue itself, with owner, evidence, wake policy, and resolution outcome (`restored`, `blocked`, `cancelled`, or `false_positive`). Recovery indicators surface on issue rows, detail surfaces, active run panels, and blocker notices, and blocked resolutions require a real first-class blocker instead of a comment. ([#5599](https://github.com/paperclipai/paperclip/pull/5599)) - **Blocked Inbox attention view** — A new Blocked Inbox tab surfaces blocked work alongside active assignments, with blocked-reason chips, filtering and search, deterministic urgency sorting, responsive layouts, and a backend blocker-attention contract so operators have a clear triage path for stalled tasks. ([#5603](https://github.com/paperclipai/paperclip/pull/5603)) - **Local plugin development workflow** — `paperclipai plugin init` scaffolding now ships with a CLI-first authoring loop covering local-path installs, plugin key routing, dashboard capabilities, dev watcher startup and reload, and SDK worker entrypoint validation for symlinked package layouts. A new local plugin development guide and refreshed `paperclip-create-plugin` skill instructions document the full happy path. ([#5821](https://github.com/paperclipai/paperclip/pull/5821)) ## Improvements - **Ordered sub-issue navigation** — Issue detail footers now expose previous/next ordered navigation that walks siblings and continues into a parent's first ordered child, with hidden-issue filtering and dependency-aware ordering preserved. The quicklook blur/click race is also fixed so portaled link clicks complete reliably. ([#5938](https://github.com/paperclipai/paperclip/pull/5938)) ## Fixes - **Comment date binding regression** — Issue comment listing no longer fails with `ERR_INVALID_ARG_TYPE` when the derived-attribution heartbeat scan binds a `Date` into postgres-js. Window bounds are now bound as ISO timestamp strings with explicit `::timestamptz` casts so comments load on issues such as `PAP-9284` without weakening the conservative attribution recovery. ([#5919](https://github.com/paperclipai/paperclip/pull/5919)) - **Remote sandbox host workspace resumes** — `claude_local` sessions now persist the host workspace cwd (not the remote sandbox cwd), reject saved cwds that point at system roots before falling back to the agent home workspace, skip sockets, FIFOs, devices, and other non-file entries during workspace restore snapshot capture, and pass only a small model-provider API-key allowlist to plugins that declare `environment.drivers.register`. ([#5922](https://github.com/paperclipai/paperclip/pull/5922)) ## Upgrade Guide One new database migration runs automatically on startup: - `0084_issue_recovery_actions` — adds the `issue_recovery_actions` table and supporting indexes for source-scoped recovery. The migration is idempotent so it is safe for anyone who previously applied an earlier branch-local recovery-action migration. Existing child recovery issue paths remain guarded; new source-scoped flows will surface recovery indicators in additional places on the board UI. No application configuration changes are required to take this release.