f60c1001ec
Rename all workspace packages from @paperclip/* to @paperclipai/* and the CLI binary from `paperclip` to `paperclipai` in preparation for npm publishing. Bump CLI version to 0.1.0 and add package metadata (description, keywords, license, repository, files). Update all imports, documentation, user-facing messages, and tests accordingly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
title, summary
| title | summary |
|---|---|
| CLI Overview | CLI installation and setup |
The Paperclip CLI handles instance setup, diagnostics, and control-plane operations.
Usage
pnpm paperclipai --help
Global Options
All commands support:
| Flag | Description |
|---|---|
--data-dir <path> |
Local Paperclip data root (isolates from ~/.paperclip) |
--api-base <url> |
API base URL |
--api-key <token> |
API authentication token |
--context <path> |
Context file path |
--profile <name> |
Context profile name |
--json |
Output as JSON |
Company-scoped commands also accept --company-id <id>.
For clean local instances, pass --data-dir on the command you run:
pnpm paperclipai run --data-dir ./tmp/paperclip-dev
Context Profiles
Store defaults to avoid repeating flags:
# Set defaults
pnpm paperclipai context set --api-base http://localhost:3100 --company-id <id>
# View current context
pnpm paperclipai context show
# List profiles
pnpm paperclipai context list
# Switch profile
pnpm paperclipai context use default
To avoid storing secrets in context, use an env var:
pnpm paperclipai context set --api-key-env-var-name PAPERCLIP_API_KEY
export PAPERCLIP_API_KEY=...
Context is stored at ~/.paperclip/context.json.
Command Categories
The CLI has two categories:
- Setup commands — instance bootstrap, diagnostics, configuration
- Control-plane commands — issues, agents, approvals, activity