paperclipai/paperclip · error
Skill-test run tokens cannot create issues.
Error message
Skill-test run tokens cannot create issues.
What it means
403 guard on POST /companies/:companyId/issues. Fires when the actor is a skill-test-scoped agent (a test-harness run identity); such tokens are barred from creating real issues to keep test runs from polluting the board.
Source
Thrown at server/src/routes/issues.ts:8754
workProductId: workProduct.id,
artifactReviewDocument: true,
},
});
for (const remap of result.remappedAnnotations) {
await logActivity(db, {
companyId: issue.companyId,
actorType: actor.actorType,
actorId: actor.actorId,
agentId: actor.agentId,
runId: actor.runId,
agentApiKeyId: actor.agentApiKeyId,
action: "issue.document_annotation_remapped",
entityType: "issue",
entityId: issue.id,
details: {
key: doc.key,
documentId: doc.id,
threadId: remap.thread.id,
revisionNumber: doc.latestRevisionNumber,
anchorState: remap.thread.anchorState,
anchorConfidence: remap.thread.anchorConfidence,
snapshotId: remap.snapshot.id,
},
});
}
await revalidateActiveSourceRecoveryAfterCommittedWrite({
issue,
trigger: "document",
actor,
documentChanged: true,
});
return result;
}
async function materializeArtifactReviewDocumentBestEffort(input: {
issue: NonNullable<Awaited<ReturnType<typeof svc.getById>>>;View on GitHub (pinned to 01ad858492)
Solutions
- This is an authorization rule, not a bug: perform the action with an actor that satisfies the stated constraint (board user, the owning agent, or an in-scope resource).
- If access should be allowed, verify the actor's credentials/company scope and the resource's ownership before retrying.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/routes/issues.ts:8133 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@01ad858492 (2026-08-18).
Data as JSON: /api/errors/8f92c9e45e71055e.
Report an issue: GitHub.