# AI use cases for Paperclip Guide (theNetworkChuck/paperclip-guide) Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Use cases: 5 | Page: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/ A companion guide that walks you through installing Paperclip, an open-source app for running a team of AI agents like a company, and building an AI IT department with it. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build an AI IT department with Paperclip: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/build-ai-it-department/ - Assign agent work with approvals and watchdog checks: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/run-agents-with-approvals-and-watchdogs/ - Schedule a daily storage check and agent standup: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/schedule-daily-storage-check-and-standup/ - Watch for leaked credentials with a Flare agent: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/watch-leaked-credentials-with-flare-agent/ - Export a Paperclip company and import it on another machine: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/export-company-and-import-elsewhere/ ## How to build an AI IT department with Paperclip with Paperclip Guide Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Difficulty: Intermediate | Time: 3 hours | Basis: From the README Install Paperclip, hire a CEO agent, and bring in specialist agents for IT work. **Who it is for:** An IT lead or developer who wants a team of AI agents handling network, storage, security and help desk tasks, and who has at least one AI account already. **The problem:** Running several AI agents one by one means no shared structure, no managers, and no clear record of who did what. **The outcome:** A Paperclip company with a Claude Code CEO that proposes and hires specialist agents on Codex and a local model, with you approving each hire. ### Steps 1. Read chapter 1 (guide/01-pick-a-machine.md) and decide whether Paperclip runs on your computer or a server. 2. Follow chapter 2 (guide/02-install-paperclip.md) to install Node 24 and Paperclip, then complete onboarding. 3. Follow chapter 3 (guide/03-first-company-and-ceo.md) to create the company and hire a Claude Code CEO using prompts/ceo-job-description.md. 4. Follow chapter 4 (guide/04-hire-remote-hermes-agents.md) to bring in any Hermes agents you already run on other machines. 5. Follow chapter 5 (guide/05-build-the-team.md) and use the hire tickets in prompts/hire/ so the CEO hires Codex and local-model agents, approving each one. ### Prompt to paste into your agent ```text Using the repo theNetworkChuck/paperclip-guide, follow chapters 2 through 5 to set up a Paperclip company on . Report the list of hired agents with their harness and manager. Verify that every hire shows an approval by the board before it became active. ``` ### Caveat The guide was tested on Paperclip 2026.916.1 and the official docs at docs.paperclip.ing win if screens have changed. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/build-ai-it-department/ ## How to assign agent work with approvals and watchdog checks with Paperclip Guide Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Create projects and tasks for agents, with human approvals and a watchdog that verifies done work. **Who it is for:** A team lead who has agents ready and needs to keep humans in charge of what they produce and what counts as finished. **The problem:** Agents can mark work as done without anyone checking it, and it is hard to see who decided what. **The outcome:** Agents working through projects, tasks, Cases, Decisions and Artifacts, with approvals gating key steps and a watchdog double-checking completion. ### Steps 1. Follow chapter 6 (guide/06-give-them-work.md) to create a project and assign tasks to your agents. 2. Use Cases, Decisions and Artifacts to record what the agents produce, as the chapter describes. 3. Follow chapter 7 (guide/07-approvals-and-watchdogs.md) to set approvals so the board signs off on key actions. 4. Hire the Watchdog using prompts/hire/ and confirm it reviews tasks marked done. 5. Use prompts/tasks/ to run the test-the-team task and check the results. ### Prompt to paste into your agent ```text Using the repo theNetworkChuck/paperclip-guide, follow chapters 6 and 7 to create one project in Paperclip with a test task for . Report the task status, any approval requests, and the Watchdog's verdict. Verify that the task cannot be closed without the required approval. ``` ### Caveat The guide describes approvals and watchdogs but its exact behavior depends on the Paperclip version you install, which the guide tested as 2026.916.1. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/run-agents-with-approvals-and-watchdogs/ ## How to schedule a daily storage check and agent standup with Paperclip Guide Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Set up recurring routines so agents run a storage check and hold a daily standup. **Who it is for:** An operator who wants agents to report on storage health each day without asking them by hand. **The problem:** Routine checks get skipped when nobody remembers to run them, and status updates are scattered across agents. **The outcome:** Scheduled routines that run the daily storage check and daily agent standup, where agents ask each other questions. ### Steps 1. Follow chapter 8 (guide/08-routines-and-standups.md) to set up routines in your Paperclip company. 2. Copy the daily storage check from prompts/routines/ into a routine and assign it to the storage agent. 3. Copy the daily agent standup from prompts/routines/ into a second routine. 4. Run each routine once by hand and read the output before you rely on the schedule. ### Prompt to paste into your agent ```text Using the repo theNetworkChuck/paperclip-guide, set up the daily storage check and daily agent standup routines from prompts/routines/ in a Paperclip company on . Report each routine's schedule and the output of one manual run. Verify that the standup output includes questions the agents sent to each other. ``` ### Caveat The guide's routines and standup are described in chapter 8 and the take-home prompts, and their exact screens may differ in the current Paperclip release. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/schedule-daily-storage-check-and-standup/ ## How to watch for leaked credentials with a Flare agent with Paperclip Guide Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Hire an exposure analyst that checks your Flare feed for leaked credentials and sessions. **Who it is for:** A security-minded admin at a small team who wants an agent to monitor leaked logins tied to the company. **The problem:** Stealer logs, Telegram and dark web leaks of company credentials are easy to miss without regular checks. **The outcome:** An Exposure Analyst agent that reads your Flare feed through the Flare skill and reports exposures without printing any credential. ### Steps 1. Get a Flare account at ntck.co/flare if you do not have one. 2. Follow chapter 9 (guide/09-plug-in-flare.md) to connect Flare to Paperclip through the skill in skills/flare/. 3. Hire the Exposure Analyst using prompts/hire/ and give it the first Flare sweep from prompts/tasks/. 4. Review the sweep report and confirm it lists exposure types without showing any raw credential. ### Prompt to paste into your agent ```text Using the repo theNetworkChuck/paperclip-guide, install the Flare skill from skills/flare/ and run the first Flare sweep from prompts/tasks/ for . Report the number of exposures by type. Verify that no credential or password appears in the output. ``` ### Caveat Flare is the video sponsor, and the guide's Flare skill is one way to connect it, not the only option. Risk, credentials: The Flare feed contains leaked credentials and sessions, so keep the skill output redacted and store your Flare access in a secure place. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/watch-leaked-credentials-with-flare-agent/ ## How to export a Paperclip company and import it on another machine with Paperclip Guide Repo: [theNetworkChuck/paperclip-guide](https://github.com/theNetworkChuck/paperclip-guide) | Difficulty: Advanced | Time: 2 hours | Basis: From the README Package a whole agent department and move it to a different Paperclip install. **Who it is for:** An operator moving an AI department from a test laptop to a server, or copying it for a second site. **The problem:** Rebuilding a multi-agent company by hand on a new machine takes hours and invites mistakes. **The outcome:** The full company packaged as an export and imported into a new Paperclip install, with agents and tasks in place. ### Steps 1. Follow chapter 10 (guide/10-export-your-company.md) to export the whole company from your current install. 2. Follow chapter 2 (guide/02-install-paperclip.md) to install Paperclip on the new machine. 3. Import the exported company into the new install as chapter 10 describes. 4. Check the imported company's agents and tasks against the original before you run them. ### Prompt to paste into your agent ```text Using the repo theNetworkChuck/paperclip-guide, follow chapter 10 to export the company from and import it into . Report the agent count and task count in both installs. Verify that the counts match and that agent approvals still apply after import. ``` ### Caveat Exports depend on the Paperclip version used, and the guide was tested on 2026.916.1, so match versions on both installs where possible. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/thenetworkchuck-paperclip-guide/export-company-and-import-elsewhere/