Paperclip
Paperclip brings prior-run knowledge into the heartbeat
Paperclip proposes bounded retrieval of up to five recent same-domain decisions for one assignee, alongside a selected-agent Conference Room and creator-owned question cancellation. The cluster turns prior work and live interaction into explicit control-plane records instead of prompt folklore.
paperclipai/paperclip PR #11139 is the inspected primary source: “feat(server): expose prior-run knowledge in heartbeat context.” The related records below were inspected as supporting context rather than independent confirmation.
The facts
- paperclipai/paperclip PR #11139 was created 2026-08-09T20:45:19Z and was open at inspection; its title is “feat(server): expose prior-run knowledge in heartbeat context.” - paperclipai/paperclip PR #9693 was created 2026-07-16T14:06:18Z and was open at inspection; its title is “feat(conference-room): add selected-agent assistant chat.” - paperclipai/paperclip PR #11022 was created 2026-08-06T22:51:56Z and was open at inspection; its title is “fix(server): allow interaction creators to cancel questions.” - The repository reported 76101 stars, 5058 open issues, default branch master, and last push 2026-08-09T22:47:40Z. - The latest tagged-release baseline checked was v2026.722.0 published 2026-07-22T23:05:41Z.
What changed
paperclipai/paperclip PR #11139 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - The server exposes heartbeat context so an agent can start work with the right task state - Completed work is written to a local knowledge index and YAML task records - The heartbeat-context route did not read those records, so prior decisions were unavailable at runtime - This pull request adds a read-only SSI Director retrieval path with bounded recency ordering and YAML projection - The benefit is reusable prior-run context without changing behavior for other assignees Linked Issues or Issue Description Refs #8132. This pull request supersedes the unmerged implementation path in that pull request and keeps the landing branch focused on the current master base. What Changed Add a file-backed reader that selects up to five same-domain entries in decided-at descending order. Project summaries, anti-patterns, and decisions from YAML with JSONL fallback behavior. Gate priorRunKnowledge to the SSI Director assignee and omit it for other assignees or no assignee. Add route contract coverage for ordering,
paperclipai/paperclip PR #9693 reports: Thinking Path - Paperclip is the control plane people use to manage AI-agent companies, so conversations with agents should remain company-scoped, inspectable, and connected to durable issues and runs. - The Conference Room already provides the natural operator-facing entry point, but it needs a selected-agent assistant mode that preserves history, active-run state, authorization, and task handoff semantics. - The implementation evolved across backend contracts, shared validation, UI composition, default agent instructions, documentation, and regression coverage; keeping those layers together avoids a partially functional chat surface. - The branch also carries the optional OKF knowledge skill used to export and import durable company knowledge, plus its generated catalog metadata and tests. - Rebasing the complete branch onto current master, resolving newer authorization and task-chat behavior, and publishing it through the existing Conference Room PR keeps the work reviewable as one requested change set without opening a duplicate PR. Linked Issues or Issue Description Refs #49 Refs #5948 Refs #6260 Related prior attempts: #9314 and #9325 Operators need a conversational surface where they can select an agent,
paperclipai/paperclip PR #11022 reports: Thinking Path - Paperclip is the open source app that teams use to run agent work - This change is in the server route layer for issue-thread interactions - Question interactions already support cancel, but the route only allowed board users and the current issue assignee - An agent that created the interaction could withdraw it, but it could not cancel its own question when the issue moved to a different assignee - That created an auth gap in the interaction lifecycle and forced unnecessary board intervention - This pull request lets the creator agent cancel only the interaction that it created, while it keeps the stricter issue-mutation path for assignee cancellations - The benefit is a complete and narrow agent interaction flow with the existing watchdog, boundary, and low-trust checks still applied Linked Issues or Issue Description What happened?** An agent could create a question interaction on an issue thread, but later it could not cancel that same question unless it was still the current assignee. The route rejected the creator path even though
Why it matters
Agent continuity is safer when history, active-run ownership and cancellation authority are visible server contracts. Otherwise context becomes accidental and human intervention becomes the only recovery path. The operator test is whether visible output, retained state and authority still describe the same event after retries, background work or restart.
Current
The primary record was open when captured on 2026-08-10. The tagged-release baseline was v2026.722.0 published 2026-07-22T23:05:41Z. Repository metadata, full source bodies, current pull requests and issues, releases, Google News, Hacker News, Lobsters, Metamesh and the rendered ClawCharts row were inspected. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/paperclipai/paperclip/pull/11139. Supporting records are https://github.com/paperclipai/paperclip/pull/9693 and https://github.com/paperclipai/paperclip/pull/11022. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts and reproductions remain attributed to their authors unless identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Keep retrieval read-only and assignee-scoped, preserve stable conversation URLs, and let creators cancel only their own interactions while unrelated agents remain blocked. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.