You Need to Try Paperclip RIGHT NOW!
Tired of managing AI agents? Discover Paperclip, a meta-harness that turns your AIs into a company! Solve real problems, like network glitches caused by toilet flushes.
The management and interaction of multiple AI agents present a significant challenge for organizations. To address this, Paperclip has emerged as a meta-harness designed to integrate and manage diverse AI agents, treating them as functional employees within a structured company framework. This approach allows for task assignment, inter-agent communication through focused tasks, and centralized oversight.
Core Functionality and Architecture
Paperclip operates as a meta-harness, meaning it can incorporate various existing agent harnesses and models. Users can bring agents such as Claude Code, Codex, Hermes, and Open Claude into the Paperclip environment. Within Paperclip, these agents are assigned roles, managers, and specific tasks. Communication between agents is facilitated through task-oriented interactions, avoiding unstructured "conference room" style dialogues.
The system requires a dedicated environment for operation. For initial testing and development, users can run Paperclip on their current computer using macOS, Linux, or WSL2 on Windows. For more robust deployment, a dedicated server, virtual machine (e.g., Proxmox), or cloud-based VPS is recommended.
Setting Up a Paperclip Company
The process of establishing a Paperclip company involves several key steps: installation, onboarding the CEO, hiring employees, and assigning tasks.
Installation
Paperclip can be installed on Ubuntu with two commands: downloading an installation script and then executing it. Similar procedures apply to macOS, Linux, and WSL2. For advanced setups, users can configure network access and start the Paperclip service. The interface is accessible via localhost:3100 or the server's IP address/domain name on port 3100.
Onboarding and Initial Setup
Upon first access, users onboard their company and set up an initial account. The system assigns a CEO agent, which can be configured to run specific models, such as Claude Code. The onboarding process includes an initial task designed to guide the user through the system's capabilities.
Hiring Employees
Agents are onboarded as "employees" with specific roles. For instance, three Hermes agents were hired: Ron as CTO, Fred as Network Engineer, and George as Storage Engineer. These agents, being pre-trained and possessing existing skills, function as ready-to-deploy personnel. Additional roles can be filled by agents running different models, such as a security engineer using Codex or a helpdesk engineer using a local model. The organizational hierarchy is visualized through an org chart, with the user acting as the "board of directors."
Task Management and Inter-Agent Communication
Paperclip facilitates agent collaboration through a task-based system.
Task Assignment and Execution
Tasks are assigned to agents, initiating a workflow. For example, a task assigned to the CEO agent, Dumbledore, to "Test Ron, make sure he works," resulted in Dumbledore assigning a sub-task to Ron. This demonstrates the direct agent-to-agent communication within the Paperclip framework.
Project and Case Management
Complex problems can be organized into projects, with individual tasks contributing to the overall project goal. Paperclip supports experimental features like "cases," where an agent can create a case to manage a complex issue. If an agent encounters an issue, it can escalate it to its manager or, if unresolved, to the user (the board).
Artifacts and Monitoring
The system generates "artifacts," which are outputs created by agents during their tasks. These can include reports, network maps, and logs. Users can access these artifacts for review and analysis. The "timeline" feature provides a chronological overview of agent activities.
Advanced Features and Integrations
Paperclip offers advanced functionalities, including routines, secrets management, and integration with external services.
Routines
Routines are scheduled tasks that can be automated. For example, a routine can be set to check server storage daily and report any low capacity issues, creating a decision point for the user. These routines can be triggered on a schedule or manually.
Secrets Management
Paperclip allows for secure storage and management of API keys and other sensitive information through a "secrets" feature. These secrets can be assigned to specific agents, enabling them to interact with external services.
Flare Integration
The platform supports integration with external threat intelligence platforms like Flare. By creating a secret for the Flare API key and assigning it to an agent, Paperclip agents can perform security sweeps and threat analysis. This integration allows agents to monitor the dark web, hacker forums, and identify leaked credentials or compromised devices.
Case Study: Network Disruption Resolution
A practical application demonstrated involved diagnosing a recurring network disconnection issue triggered by flushing a toilet. The Paperclip IT department, comprising various AI agents, was tasked with identifying the root cause.
The investigation involved:
- Network Scanning: Agents like Fred (Network Engineer) and the scanner agent analyzed network configurations, switches, and client disconnections.
- Log Analysis: Agents correlated logs from various network devices and identified patterns.
- Hypothesis Testing: The agents explored multiple hypotheses, including issues with the NAS, router, spanning tree, and individual ports.
- Artifact Generation: Network maps and detailed reports were generated as artifacts.
- Decision Making: The system presented decisions to the user based on agent findings, such as whether to replace network components.
The investigation revealed that the issue was not directly related to the toilet flush but rather to faulty third-party SFPs (Small Form-Factor Pluggables) on a MikroTik switch. These SFPs were susceptible to physical disturbances, such as those caused by forceful movements associated with using the adjacent bathroom. The solution involved replacing these faulty SFPs with official MikroTik branded ones.
Stand-ups and Organizational Management
Paperclip supports daily stand-up meetings for agents, managed as a routine. Each agent reports on its activities, and inter-agent questions and clarifications are handled. The system allows for exporting and importing the entire organizational structure, including agents, routines, and tasks, enabling portability and backup.
The platform's capabilities extend to managing complex workflows, integrating with security tools, and automating routine checks, positioning it as a comprehensive solution for orchestrating AI agent operations.
Introduction to Paperclip and Agent Management Challenges
The current challenge of managing multiple AI agents (Hermes, Codex, Claude Code) is discussed, highlighting issues with communication, task assignment, and security. Paperclip is introduced as a solution, a meta-harness that integrates various agents, treating them as employees within a company structure. The creator, Doda, is introduced, and the concept of agents talking to each other intentionally through tasks is explained, contrasting it with less structured 'agent conference rooms'.
- Managing multiple AI agents is complex due to communication and coordination challenges.
- Paperclip is a meta-harness designed to manage and integrate various AI agents.
- In Paperclip, agents function as employees with assigned roles and tasks.
- Agent communication in Paperclip is intentional and task-focused, not aimless chatter.
The Toilet Flush Network Problem and AI IT Department Setup
A specific, unusual problem is presented: network disconnections occurring whenever a toilet is flushed at Network Chuck Studios. To solve this, an AI-driven IT department is to be set up using Paperclip. This department will include network engineers, storage specialists, and security personnel, all running as AI agents within the Paperclip framework. The setup process will involve installing Paperclip and configuring the AI company.
- The video aims to solve a peculiar problem: network disconnections linked to toilet flushing.
- An AI-powered IT department will be established using Paperclip to address the issue.
- The AI IT department will comprise agents for network, storage, and security roles.
- The setup involves installing Paperclip and configuring the AI company structure.
Paperclip Installation and Setup
The technical requirements and installation process for Paperclip are detailed. It can be run on a local machine (Mac, Linux, WSL2) for quick testing or on a dedicated server (VM or cloud VPS) for commitment. The installation involves downloading and running a script, with options for quick start or advanced setup. The user interface is accessed via localhost or an IP address on port 3100, where the company onboarding and initial account setup occur.
- Paperclip can be run on local machines (Mac, Linux, WSL2) or dedicated servers.
- Installation involves a simple script with quick start and advanced options.
- Access to the Paperclip interface is via
localhost:3100or an IP address. - The initial setup includes company onboarding and account creation.
Hiring AI Agents for the IT Department
The process of hiring AI agents for the IT department begins. Three Hermes agents are hired: Ron (CTO), Fred (Network Engineer), and George (Storage Engineer). These agents are pre-trained and possess necessary skills. A CEO agent, running Claude Code, is hired, followed by a Security Engineer (Codex) and a Helpdesk Engineer (local model). The organizational structure (org chart) is visualized, with agents reporting to managers and a CEO.
- Three Hermes agents (Ron, Fred, George) are hired for CTO, Network, and Storage roles.
- A CEO agent running Claude Code is hired.
- Additional agents include a Security Engineer (Codex) and a Helpdesk Engineer.
- The hiring process establishes an organizational hierarchy within Paperclip.
Agent Communication and Task Assignment
Paperclip's core functionality is explained: it's a meta-harness capable of integrating any agent harness or model. The video demonstrates assigning the first task to the CEO, Dumbledore, to test communication by having him talk to Ron (CTO). This interaction showcases agents talking to each other through assigned tasks. Subsequently, Fred and George are hired, and Dumbledore is tasked with hiring them, further illustrating agent delegation and collaboration.
- Paperclip acts as a meta-harness, adaptable to new models and harnesses.
- Tasks are assigned to agents to initiate communication and work.
- The first inter-agent communication is demonstrated between Dumbledore (CEO) and Ron (CTO).
- Dumbledore is tasked with hiring additional employees, showcasing delegation.
Flare Integration and Threat Intelligence
The video briefly mentions Flare, a sponsor, as an identity-focused threat intelligence platform that monitors the dark web and hacker forums for leaked company data. The creator shares personal findings from Flare, including leaked credentials and infected devices, emphasizing the speed of breaches versus detection times. The potential to connect Flare to Paperclip via API for agent-driven threat analysis is noted.
- Flare is an identity-focused threat intelligence platform.
- It monitors the dark web and hacker forums for leaked company data.
- The creator shares alarming personal data found via Flare (leaked credentials, infected devices).
- There's a plan to integrate Flare with Paperclip for agent-driven security analysis.
Paperclip Installation and Initial Onboarding
The installation of Paperclip is completed using two commands on an Ubuntu VM. The advanced setup is chosen for the VM, configuring network access. Onboarding involves setting up the CEO (Dumbledore) with Claude Code. Initial setup failures are encountered due to missing agent installations (Claude Code), but retrying after installation resolves the issue. The onboarding process includes a questionnaire and leads to hiring employees.
- Paperclip installation is confirmed via a script on Ubuntu VM.
- Advanced setup configures network access for the VM.
- CEO Dumbledore is set up using Claude Code.
- Initial setup failures are resolved by installing required agent models.
Hiring, Hierarchy, and Agent Communication Testing
The hiring process continues with Ron (CTO) being approved. The organizational hierarchy is visualized, placing the user as the 'board of directors'. Tasks are the primary interface for agent interaction. A test task is assigned to Dumbledore to 'talk to Ron', demonstrating agent-to-agent communication. Fred and George are hired, and Dumbledore is tasked with hiring them, showcasing delegation and the creation of an org chart.
- The user acts as the 'board of directors' in the Paperclip hierarchy.
- Tasks are the main method for interacting with and directing agents.
- A test task confirms Dumbledore can communicate with Ron.
- Dumbledore is delegated the task of hiring Fred and George.
Expanding the AI Team and Interaction Methods
The AI team expands with agents like Arthur Weasley (Codex), Watchdog (Pi), Helpdesk (Pi), Mad-Eye Moody (Codex), and a Scanner (Pi). The video highlights that agents can be interacted with not just through the Paperclip interface but also via direct prompts if they have the 'Paperclip skill'. The organizational structure, activity tracking, and timelines are emphasized as key features for managing complex projects.
- The AI team includes agents with various roles and running different models/harnesses (Codex, Pi).
- Agents with the 'Paperclip skill' can be interacted with directly, not just via the UI.
- Paperclip provides features like org charts, activity logs, and timelines for traceability.
- These features are crucial for managing complex problem-solving initiatives.
Initiating the Toilet Problem Investigation
A project is created for the 'toilet issues'. A task is assigned to Dumbledore to investigate. Dumbledore utilizes an experimental 'cases' feature, creating a case and assigning sub-tasks to various agents (Arthur, George, Fred). The task management interface allows pausing, canceling, and viewing task properties, including blocking tasks and reviewers. Agents escalate issues to Dumbledore if they encounter blocks.
- A project named 'toilet issues' is created within Paperclip.
- Dumbledore is assigned the main investigation task.
- An experimental 'cases' feature is used to manage sub-tasks.
- Agents can escalate issues to Dumbledore if they face problems.
- Task management offers options like pause, cancel, and detailed properties viewing.
Agent Work, Artifacts, and Initial Findings
The agents begin working on the toilet problem. Fred completes a task, generating a network map artifact. Arthur builds a harness to capture events, assigning Mad-Eye Moody to review security. A 'decision' point arises, asking about the nature of the disconnections (simultaneous vs. individual) and proposing a 'control flush test'. The creator makes a decision to replace an optic based on preliminary findings.
- Agents like Fred and Arthur start working on the toilet problem, generating artifacts like network maps.
- A decision point is reached regarding the nature of the network disconnections.
- A 'control flush test' is proposed.
- The creator decides to replace an optic based on initial agent findings.
Deep Dive Investigation and SFP Suspicions
The investigation deepens, with agents analyzing switch logs, spanning tree, and NAS client behavior. Artifacts like a studio network map are generated. The agents identify that the issue is not the NAS, router, or spanning tree, and not a single bad port. They report an inability to name the exact trigger but note that a shared external physical event drops four specific fiber runs on the switch. The creator suspects faulty third-party SFPs (transceivers) as the cause.
- Agents analyze network components like switches, NAS, and spanning tree.
- A network map artifact is generated.
- The investigation rules out common network issues and single faulty ports.
- A recurring physical event is identified as the cause of fiber link drops.
- Faulty third-party SFPs are suspected as the root cause.
SFP Replacement and Flare Integration Setup
The creator decides to replace the suspect third-party SFPs with official MikroTik branded ones. This involves a brief network interruption. The video then revisits the Flare integration, showing how Dumbledore hires an agent (Filch) using Clock Code Opus 5, and grants it access to Flare API keys via secrets. Filch encounters an issue with a missing Flare Tenant ID, which is then added as a new secret, allowing the sweep to proceed.
- Suspect third-party SFPs are replaced with official MikroTik branded ones.
- Flare integration is demonstrated: Dumbledore hires Filch (Clock Code Opus 5).
- Flare API keys and Tenant ID are managed as secrets within Paperclip.
- Filch uses a Flare skill to perform a security sweep.
Flare Sweep Results, Routines, and Export/Import
Filch's Flare sweep uncovers significant issues, leading to tasks assigned to Ron (password resets) and Mad-Eye Moody (security checks). The creator can pause agent work if needed. The organization structure can be exported and imported, allowing for company migration. The video also demonstrates Paperclip's 'routines' feature, setting up a scheduled task for Fred to check storage daily and create decisions if capacity is low.
- Filch's Flare sweep reveals security issues, triggering further agent tasks.
- Agent work can be paused or controlled via the Paperclip interface.
- Paperclip organizations (agents, tasks, routines) can be exported and imported.
- Routines enable scheduled tasks, like daily storage checks.
Final Verdict on the Toilet Flush Problem
The toilet problem investigation concludes with the agents unable to definitively name the trigger but confirming it's not the NAS or router. They identify that a shared external physical event drops four specific fiber runs on the switch. The final verdict points to faulty third-party SFPs causing link instability, especially when disturbed by building vibrations (potentially from flushing or other activities). The creator replaces the SFPs and awaits results.
- Agents could not definitively name the trigger for network drops.
- The issue is linked to specific fiber runs on the switch being affected by physical events.
- Faulty third-party SFPs are identified as the likely cause of instability.
- The creator replaces the SFPs and will monitor for resolution.
Daily Stand-ups, Agent Collaboration, and Conclusion
The creator shows how they use Paperclip for daily stand-ups via a routine. Agents report on their activities, and Q&A sessions occur between them. An example shows Taylor asking Hermione about footage backup due to restream recordings expiring. The video concludes with a prayer for the audience, followed by a final sign-off.
- Daily stand-ups are conducted using a Paperclip routine.
- Agents report on their daily activities and engage in Q&A.
- An example highlights agent collaboration on ensuring footage backups.
- The video ends with a personal prayer for the viewers.