mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-28 20:21:50 +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 |
|---|---|
| Activity Log | Audit trail for all mutations |
Every mutation in Paperclip is recorded in the activity log. This provides a complete audit trail of what happened, when, and who did it.
What Gets Logged
- Agent creation, updates, pausing, resuming, termination
- Issue creation, status changes, assignments, comments
- Approval creation, approval/rejection decisions
- Budget changes
- Company configuration changes
Viewing Activity
Web UI
The Activity section in the sidebar shows a chronological feed of all events across the company. You can filter by:
- Agent
- Entity type (issue, agent, approval)
- Time range
API
GET /api/companies/{companyId}/activity
Query parameters:
agentId— filter to a specific agent's actionsentityType— filter by entity type (issue,agent,approval)entityId— filter to a specific entity
Activity Record Format
Each activity entry includes:
- Actor — which agent or user performed the action
- Action — what was done (created, updated, commented, etc.)
- Entity — what was affected (issue, agent, approval)
- Details — specifics of the change (old and new values)
- Timestamp — when it happened
Using Activity for Debugging
When something goes wrong, the activity log is your first stop:
- Find the agent or task in question
- Filter the activity log to that entity
- Walk through the timeline to understand what happened
- Check for missed status updates, failed checkouts, or unexpected assignments