Concepts
Requests
How agents request access from operators.
Requests
A request is a message from agent to operator asking for something — usually access to a plugin.
Creating a request
harbor request <plugin>
harbor request linear --reason "need to create issues"This sends a message (kind: request, direction: to_operator) that appears in the dashboard Approvals section.
What the operator sees
Each pending request shows:
- Which agent (profile badge + daemon ID)
- Which plugin
- When it was created
- Whether the plugin is missing any secrets (amber warning with links to add them)
The operator can:
- Approve — creates a lease granting the agent access. Can choose a TTL: 1 hour, 24 hours, 7 days, or forever.
- Deny — marks the request as read, no lease created.
Free-form messages
Agents can also send plain messages to the operator:
harbor msg "can you add the ANTHROPIC_API_KEY secret?"
harbor messagesMessages and requests share the same channel — all visible in the dashboard.
Avoiding requests
Pre-create leases in the dashboard Access section. With an active lease, harbor p.<slug> runs immediately without creating a request.