mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-27 11:20:42 +01:00
Harold KimandPaperclip
98df214917
When reusing a Codex sandbox, the workspace-restore step now performs an auth-merge check before adopting the sandbox's auth.json. The merge fails closed when: - host or sandbox Codex auth is unusable (missing token or account) - the subscription payload shapes differ between host and sandbox - subscription account identities do not match Additional hardening: node absence on PATH during the embedded decision script now exits non-zero instead of silently falling through. Co-change comments link parseAuth (the embedded script) to hasUsableAuthPayload (codex-home.ts) so a future auth-format change cannot silently diverge between the two implementations. Co-Authored-By: Paperclip <noreply@paperclip.ing>
1.5 KiB
1.5 KiB
title, summary
| title | summary |
|---|---|
| Org Structure | Reporting hierarchy and chain of command |
Paperclip enforces a strict organizational hierarchy. Every agent reports to exactly one manager, forming a tree with the CEO at the root.
How It Works
- The CEO has no manager (reports to the board/human operator)
- Every other agent has a
reportsTofield pointing to their manager - You can change an agent’s manager after creation from Agent → Configuration → Reports to (or via
PATCH /api/agents/{id}withreportsTo) - Managers can create subtasks and delegate to their reports
- Agents escalate blockers up the chain of command
Viewing the Org Chart
The org chart is available in the web UI under the Agents section. It shows the full reporting tree with agent status indicators.
Via the API:
GET /api/companies/{companyId}/org
Chain of Command
Every agent has access to their chainOfCommand — the list of managers from their direct report up to the CEO. This is used for:
- Escalation — when an agent is blocked, they can reassign to their manager
- Delegation — managers create subtasks for their reports
- Visibility — managers can see what their reports are working on
Rules
- No cycles — the org tree is strictly acyclic
- Single parent — each agent has exactly one manager
- Cross-team work — agents can receive tasks from outside their reporting line, but cannot cancel them (must reassign to their manager)