Skip to content

Paperclip Dev Workspace Repair

Start, verify, and repair Paperclip's isolated dev workspace services and their port ownership.

Stars
110,078
Licence
MIT
Files
1 file

What it does

When installed, the agent follows a strict checklist for restarting and repairing a Paperclip development workspace (a separate git worktree running a local Paperclip server). It starts the service through Paperclip's managed runtime API, checks health, login, cloned data and which process truly owns the port, and does not declare success until every check passes. It also warns against trusting a running status or health check alone, since a sibling workspace's process can hold the same port.

Great for

  • Engineers working on Paperclip itself who run multiple isolated dev worktrees
  • Maintainers debugging a dev service that shows healthy but serves the wrong workspace
  • Agents assigned Paperclip issues about broken or stale workspace services

Skip it if

  • Users of Paperclip as an application, since it only applies to the Paperclip repository's internal dev setup
  • Projects other than Paperclip, because it names Paperclip-specific paths, endpoints and roles
  • Anyone wanting to run destructive reseeds without review, since it involves stopping processes and replacing a workspace database clone

Try asking

  • “Start the paperclip-dev service for my workspace and prove it is healthy and logged-in ready”
  • “The dev server on port 40631 says healthy but shows another workspace's data; find and fix the port owner”
  • “Reseed my worktree database from the primary instance and verify the login works”
  • “Fix the workspace service and leave an issue comment with root cause and verification”
Step-by-step guide: how to use Paperclip Dev Workspace RepairInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    paperclip-dev-workspace-run-verify-fix.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip paperclip-dev-workspace-run-verify-fix.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip paperclip-dev-workspace-run-verify-fix.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Provide the execution workspace id and the service command id (service:paperclip-dev) up front so the agent does not have to search for them
  • Make sure the API key and run id come from environment variables and are never pasted into chat or issue comments
  • Review any stop or reseed actions the agent proposes, since they affect running processes and local database clones

What's inside

  • SKILL.md

Redistributed unmodified from paperclipai/paperclip under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.