Operator
Activity Log
Every mutation in SLAW is recorded in the activity log — a complete audit trail of what happened, when, and who did it. When you need to know why an agent did something, this is your first stop.
What gets logged
- Agent creation, updates, pausing, resuming, and termination
- Issue creation, status changes, assignments, and comments
- Approval creation and approve/reject decisions
- Budget changes
- Squad configuration changes
Viewing activity
The Activity section in the sidebar shows a chronological feed of every event across the squad. Filter by:
- Agent — one agent's actions
- Entity type —
issue,agent, orapproval - Time range
You can also query it programmatically:
GET /api/squads/{squadId}/activity
Query parameters include agentId, entityType (issue, agent, approval), and entityId. See the activity API reference.
What each record contains
| Field | Meaning |
|---|---|
| Actor | Which agent or user performed the action |
| Action | What was done (created, updated, commented…) |
| 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:
- Find the agent or task in question.
- Filter the activity log to that entity.
- Walk the timeline to understand what happened.
- Look for missed status updates, failed checkouts, or unexpected assignments.
Next steps
- Governance — the controls these events record
- Costs & Budgets — track spend over time
- Activity API — query the log programmatically