operations / agent
Paperclip
A Node.js server and React UI for managing a team of AI agents, with goals, budgets, approvals and an org chart in one dashboard.
At a glance
- Purpose
- A Node.js server and React UI for managing a team of AI agents, with goals, budgets, approvals and an org chart in one dashboard.
- Runs in
- Web service
- Operating systems
- Not stated
- Needs
- Runtime: Node.js 24.11+; Needs internet: Yes; Needs accounts or API keys beyond your agent: No
- Files and data
- Reads files: Not stated; Writes files: Yes; Sends data to other services: Yes
- Tool type
- Agent
- Delivery
- From GitHub
- Version
- Latest on the master branch
- Access
- Code on GitHub
- Compatibility
- According to the README, Paperclip works with OpenClaw, Claude Code, Codex, Cursor and Cursor Cloud, Gemini CLI, OpenCode, Pi, Hermes and Hermes Gateway, Grok Build and Kimi Code, plus custom processes, HTTP endpoints and external adapter packages. It names Node.js 24.11 or newer, Docker for a persistent server, and a private-network bind such as Tailscale for remote access. It names GitHub, Notion, Railway and MCP servers as connections, and Slack, Discord, Telegram and AgentMail for the experimental chat and email connectors.
- External costs
- According to the README, Paperclip is open source and self-hosted, and no Paperclip account is required. The README's test-drive examples set an ANTHROPIC_API_KEY, an OPENAI_API_KEY or an OPENROUTER_API_KEY. The README says local Claude and Codex subscription sign-in needs the matching provider CLI. It links a sign-up for the Paperclip Cloud waitlist. The agents, model providers and services you connect may charge for usage.
- Permissions
- The README describes npx or source/pnpm install and sharing an installation guide with an agent. The README says Paperclip invokes agents, supplies credentials to authorized runs and supports optional git worktrees, operator branches and runtime services such as dev servers. The README says connection controls govern access by people and agents; managed GitHub operations can use the directing person's account. The README describes optional timer heartbeats, cron/webhook/API routines and experimental Slack, Discord, Telegram and AgentMail chat/email connectors. The README says gateway actions can be set to Allowed, Ask first or Off. The README says quickstart defaults to trusted local loopback mode; --bind lan or --bind tailnet selects authenticated/private mode. The README says pnpm dev watches files; pnpm dev:once runs without file watching. The README describes approvals, recorded-spend budgets and agent pause/resume/termination.
- Usage terms
- MIT License, as stated in the repository. See its LICENSE file for the exact terms.
- Interface
- web
Code on GitHub
paperclipai/paperclip
MITThe open-source app everyone uses to manage agents at work
Topics: acpx agent-orchestration agent-skills agentic-ai ai-agents ai-engineering ai-governance ai-tools
Public GitHub data fetched · 0 days old
View on GitHub ↗What it does
According to the README, Paperclip is a Node.js server and React UI for orchestrating teams of AI agents. The README says users bring their own agents, assign goals, track work and costs, and choose models and harnesses per agent while keeping tasks, skills, permissions and history in one place.The README lists task threads, approval stages, an org chart, company, agent and project budgets, scheduled routines and shared skills with a Skill Studio. The README also lists connections such as GitHub, Notion, Railway and MCP servers, organization-package export and import, and multiple organizations in one deployment.
The README names OpenClaw, Claude Code, Codex, Cursor and Cursor Cloud, Gemini CLI, OpenCode, Pi, Hermes and Hermes Gateway, Grok Build and Kimi Code as integrations. The README says custom processes, HTTP endpoints and external adapter packages extend that roster.
Who it is for
The README says Paperclip suits people who coordinate many different agents toward a common goal and want to monitor costs and enforce budgets.Example tasks
Define a goal, hire a team of agents, set budgets and start the run.Set company, agent or project budgets and track reported spend.
Create a routine that runs recurring work on a schedule or from a webhook.
Connect a service such as GitHub or your own MCP server and set its gateway actions to Allowed, Ask first or Off.
Preview, export or import an organization package with its agents and skills.
Getting started
According to the README, install with Node.js 24.11 or newer by running npx paperclipai@latest onboard --yes. The README says the CLI runs from npm's cache and your instance configuration and data persist locally. It also describes a test-drive command for an isolated test instance, and a source route that clones the repository and runs pnpm install and pnpm dev. The README says the source route starts the UI and API on localhost port 3100 and creates an embedded PostgreSQL database automatically. The README has the exact commands. The README says instance configuration and data persist locally, and npx paperclipai configure edits settings. The README says test-drive creates a retained temporary directory unless --data-dir is supplied, opens a browser after setup unless --no-browser is supplied, and enables task execution in a linked Git worktree when invoked from one.Limitations
The README says users bring their own agents and that Paperclip is not an agent framework for building them. The README requires Node.js 24.11 or newer for quickstart and pnpm 9.15 or newer for the source route. The README says local Claude and Codex subscription sign-in needs Python 3 and the corresponding provider CLI on the host, which the Docker image includes.The README says source development builds the native Paperclip Runner when enabled, identifies this as the self-hosted default, and requires Rust or a compatible prebuilt runner supplied through PAPERCLIP_RUNNER_BINARY. The README labels Agent Chat, chat and email connectors, and pipelines experimental. The README says sandbox availability depends on the configured environment and adapter.
The README says budget enforcement uses recorded spend and that usage reporting and in-flight work can delay a stop. The README warns that exported organization packages can retain plain environment values and local paths and that full-instance recovery uses backups.
The repository can change at any time; check its README before you install.
Data practices
The README says a local setup uses a Node.js process, embedded PostgreSQL and local file storage, with configuration and data persisted locally. The README describes user-supplied Postgres for production and local or S3-compatible file storage. The README says referenced credentials are supplied to authorized runs and omitted from exported organization packages, but plain environment values and local paths can remain in exports.The README says anonymous usage telemetry is enabled by default to understand product use and improve it, and that private repository references are hashed with a per-install salt before transmission. The README lists these ways to disable it: PAPERCLIP_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1, CI=true, or telemetry.enabled: false in the configuration.
The README describes opt-in server OpenTelemetry traces, activated by OTEL_EXPORTER_OTLP_ENDPOINT, with protocol selected through OTEL_EXPORTER_OTLP_PROTOCOL. The README also describes opt-in Sentry error monitoring, activated by SENTRY_DSN_FRONTEND for the browser or SENTRY_DSN_BACKEND for the server, with SENTRY_DSN as a legacy fallback. The README points to doc/observability.md for privacy settings and the default capture set.