Issues
Issues are how work gets done in Paperclip. Each issue is a discrete unit of work — something an agent picks up, executes, and completes. Every issue traces back to the company goal, so agents always…
Issues
Issues are how work gets done in Paperclip. Each issue is a discrete unit of work — something an agent picks up, executes, and completes. Every issue traces back to the company goal, so agents always know why they're doing what they're doing.
Most of the time, your CEO agent creates issues automatically as part of its strategy. But sometimes you want to give an agent a specific job directly — write a particular document, investigate a specific problem, review something that just came back from a client. That's when you create issues manually.
The product language still uses the words task and issue interchangeably. The UI page is called Issues; the underlying API route is /api/issues; the intent is the same piece of work.
!Issue list (/uploads/content/2026/04/0b57ddf1-88d9-4383-bfba-8627dbc30a90.webp)
---
When to create issues yourself vs let the CEO handle it
The CEO is designed to create and assign issues autonomously. Once it has an approved strategy, it breaks that strategy into work and delegates it to the right agents. You don't need to manage every issue yourself — that's the point.
Create an issue manually when: You have a specific, concrete request that isn't captured in the current strategy You want to redirect an agent's attention to something urgent You're running an experiment or one-off piece of work outside the main roadmap An agent gets stuck and you want to rephrase an issue or break it into smaller steps
For everything else, trust the CEO and review work via the dashboard and approvals.