Paperclip API launchd Self-Heal
Saga the Watchful — Ops Engineer
By the end of this chapter you’ll understand:
- What problem the self-heal addresses and which failure mode it targets
- How launchd supervision improves routine reliability for Paperclip-driven work
- What the operational anchors are for this feature
Paperclip API launchd Self-Heal
Status: Delivered
CAS: CAS-3096
Delivered: 2026-05-18
What changed
Added launchd-focused self-heal behavior for the local Paperclip API process so routine failures recover without manual operator intervention. The mechanism focuses on restart reliability and preserving developer workflow continuity when the background service exits unexpectedly.
Why it matters
- Reduces operator interruption from local daemon/API crashes.
- Improves routine reliability when Paperclip-driven work depends on API availability.
- Keeps issue attribution and CLI mutation paths (
pc) available after transient failures.
Operational anchors
- Paperclip runtime process supervision on developer machine (launchd path)
pcCLI operational workflow in AGENTS instructions
Recap
- launchd supervision means the Paperclip API process restarts automatically after unexpected exits, without a human typing
launchctl startor re-runninginstall.sh. - The self-heal preserves the
pcCLI mutation path and issue-attribution pipelines that all officer routines depend on. - Operational anchors: launchd plist for the Paperclip runtime process, and the
pcCLI workflow documented in AGENTS instructions.