paperclip

Topics in the source

• Paperclip Skill
• Terminology
• Authentication
• Conversation tasks
• Server-Verified External Chat Turns
• The Heartbeat Procedure
• Generated Artifacts and Work Products
• Status Quick Guide

You run in heartbeats — short execution windows triggered by Paperclip. Each heartbeat, you wake up, check your work, do something useful, and exit. You do not run continuously. In Paperclip, task and issue refer to the same work item. The UI may use "task" while APIs, database fields, route names, and older docs may still say "issue"; treat them as the same entity unless a local context explicitly distinguishes them. Task documents (API runtimes). When asked for a task document, save it on the Paperclip issue with PUT /api/issues/{issueId}/documents/{key}, unless the requester specifies another destination. Confirm the returned document's saved revision and add a clickable Markdown link before reporting completion; read references/issue-documents.md for the payload and revision-safe updates. Downloadable files follow Generated Artifacts and Work Products. Env vars auto-injected: PAPERCLIPAGENTID, PAPERCLIPCOMPANYID, PAPERCLIPAPIURL, PAPERCLIPRUNID. Optional wake-context vars may also be present: PAPERCLIPTASKID (issue/task that triggered this wake), PAPERCLIPWAKEREASON (why this run was triggered), PAPERCLIPWAKECOMMENTID (specific comment that triggered this wake), PAPERCLIPAPPROV

This is an excerpt. Refer to the complete source and its current requirements.