Paperclip
Paperclip blocks agent work from bouncing in circles
Paperclip now refuses a child task that delegates work back to the creator of an open ancestor, after a real capability gap produced an A-to-B-to-A chain. A companion change warns when an escalation path ends at a paused manager, making two forms of organisational deadlock visible before the queue grows.
paperclipai/paperclip PR #10658 is the inspected primary source: “fix(server): refuse agent delegation cycles back to an open ancestor's creator.” The two related records below were inspected as supporting context, not treated as independent confirmation.
The facts
- paperclipai/paperclip PR #10658 was created 2026-08-01T22:20:32Z and was closed at inspection; its title is “fix(server): refuse agent delegation cycles back to an open ancestor's creator.” - paperclipai/paperclip PR #10657 was created 2026-08-01T22:13:12Z and was closed at inspection; its title is “feat(agents): warn when an agent's escalation path routes to a paused manager.” - paperclipai/paperclip issue #10642 was created 2026-08-01T21:04:22Z and was closed at inspection; its title is “No guard against delegation cycles: two agents ping-pong subtasks over the same missing capability.” - The repository reported 75361 stars, 4960 open issues, default branch master, and last push 2026-08-02T00:53:21Z. - The latest tagged-release baseline checked was v2026.722.0 published 2026-07-22T23:05:41Z.
What changed
paperclipai/paperclip PR #10658 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - Agents decompose work by creating child issues assigned to other agents - When two agents each lack a capability the other assumed (e.g. neither can push to GitHub), each can "resolve" its blocker by delegating the same step to the other: A creates a child for B, B creates a grandchild back for A - Nothing detects the cycle; the chain of blocked issues grows and no signal reaches the human who could actually fix the capability gap - This pull request refuses agent-initiated child creation when
paperclipai/paperclip PR #10657 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - Agents escalate work up the org chart (reports_to), and operators pause agents — notably, instance imports pause every agent by default - A paused manager does not invalidate the chain (subordinates stay invokable), so nothing surfaces when an operator unpauses workers but leaves their manager paused - Escalations then dead-letter silently: agent-created issues assigned to the paused manager sit in a queue nothing will ever run - This pull request computes paused ancestors in the existing org-chain health model and surfaces a non-blocking warning on the agent
paperclipai/paperclip issue #10642 reports: What happened?** Agent A finished an implementation but could not push (no GitHub write credentials in its runtime). It created a subtask "review and open PR" for agent B. B approved the change but also had no push credentials, so B created a subtask "push and open PR" right back for A's counterpart. Result: an A→B→A delegation chain over the same capability gap, three levels of blocked issues (parent blocked by child blocked by grandchild), and no signal to the human that *no agent in the org can push*. The chain only resolved after a human noticed, added a token, and manually commented "try again"
Why it matters
Delegation is not progress when every agent lacks the same credential or when the manager receiving escalation is paused. Mechanical cycle checks and visible chain health turn organisational topology into an enforceable runtime contract. This is an operator boundary: persisted state, execution ownership and visible controls must describe the same event. A workaround that broadens access, deletes state or hides the symptom would trade a visible defect for an unmeasured one.
Current
The primary record was closed when captured on 2026-08-02. The release baseline was v2026.722.0 published 2026-07-22T23:05:41Z. Current repository metadata, pull requests, issues, release records, Google News discovery, Hacker News discovery, Lobsters, Metamesh and the rendered ClawCharts row were checked. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/paperclipai/paperclip/pull/10658. Supporting records are https://github.com/paperclipai/paperclip/pull/10657 and https://github.com/paperclipai/paperclip/issues/10642. Their source bodies, timestamps and states were captured in the daily evidence bundle. Test counts, reproductions and deployment observations remain attributed to their authors unless explicitly 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. Issue closure would not by itself prove a deployed fix. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Keep human rerouting possible, cap ancestor walks, distinguish closed work from live cycles, and escalate missing capabilities to an operator instead of manufacturing another task. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently after intervention.
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.