Activity Log
The activity log tracks everything that happens in your workspace: imports, status changes, spec generation, exports and integration events.
Opening the Log
Click Circuit Log in the main navigation. All team members see the same log — it is shared across the workspace.
The log has two tabs: Feedback In and Specs Out.
Feedback In
The Feedback In tab shows a running total of all feedback ingested during the current retention window (30 days), broken down by source.
| Source | Detail |
|---|---|
| Slack | Total items + per-channel breakdown (e.g. #feedback: 312, #support: 89) |
| Surface | Total items + per-surface breakdown (by the name you set on each widget) |
| CSV | Total items across all uploads |
| Transcripts | Total items (Otter, Fireflies, Grain, Whisper) |
| Manual | Total items entered directly |
| API | Total items submitted via API key |
Totals reflect ingested items — duplicates and filtered-out submissions are excluded.
Use the source breakdown to spot imbalances. If one Slack channel is driving most of your feedback, the priorities will reflect that skew.
Below the totals, the Feedback In tab also records these events:
| Event | What It Captures |
|---|---|
| Import | Source and item count |
| Rank change | Priority moved up or down in the ranked list; priority dropped off the list |
| Domain vocabulary built | Website context scraped and classification vocabulary updated |
| Connection | Integration connected (Slack, GitHub, Google Sheets, Surface) |
| Disconnection | Integration removed |
| Data reset | Workspace data cleared |
| Connection expired | GitHub, Slack or Google Sheets token needs reauthorising |
| Quota warning | Approaching the monthly feedback limit |
Specs Out
The Specs Out tab is a chronological record of spec activity.
| Event | What It Captures |
|---|---|
| Spec created | Which priority, when the spec was generated |
| Status change | Priority moved to Ready, Building, Shipped or Shared |
| Shipped | Spec marked as shipped, customer notifications sent |
| Export | Format (CSV, JSON, Markdown, Cursor, Claude Code, GitHub) |
| Stale spec alert | Specs flagged as needing a refresh due to new feedback |
Each entry shows the event type, details, timestamp and which team member triggered it (where applicable). Both tabs paginate — use the controls at the bottom to browse older events.
Retention
Events and totals are kept for 30 days. Older data is removed automatically. Retention is the same on all plans.
Live Processing View
When feedback is being processed, the Events tab updates in real time. You can watch each stage — classification, clustering, spec generation — as it completes. Progress shows per-spec, so you know which specs are ready to use before the full pipeline finishes.