Activity Log

The Activity Log is the full history behind the Dashboard's Live feed. The Live box shows the last few events; the Log shows everything still retained — filesystem changes, routine runs, daemon transitions, mission edits, and session starts — grouped by day, newest first. Open it from Dashboard ▸ Live ▸ Log.

Use it to answer "what did the system do while I was away": scan a day's group, filter to one event class, and jump straight into any file an agent touched.

Reading the log

• Date groups. Events are grouped under sticky day headers with a count per day.
• Filter chips. All · Files · Routines · Daemons · Missions · Sessions — one click narrows the list to that event class; the retained-event count in the header follows the filter.
• Live tail. While you are at the top of the list, new events appear as they land. Once you page into history, the view stays put so your reading position is not disturbed.
• Load older. The log paginates 200 events at a time; the button at the bottom loads the next page.
• Refresh re-reads the current filter from the store.

Acting on an event

File events are links:

• Click a created/modified file event to reveal that file in Documents.
• Shift-click (or the ⧉ icon on hover) opens it in a new Documents window instead — useful when you are triaging a batch of agent writes.

Other event types are informational.

Retention — how long history lives

The log is a local store with a rolling retention window (48 hours by default). An hourly cleanup removes events older than the window, plus a row cap as a safety net. Change the window at Settings ▸ Activity Log (up to 30 days).

Two deliberate properties worth knowing:

• Clearing the Dashboard box deletes nothing. The Live panel's Clear only hides events from that box; they remain here until retention removes them.
• There is no destructive clear in the Log itself. Retention is the only thing that removes history, so the log always answers honestly for its window.

The store is operational history, not a system of record — it is one of the regenerable local stores listed in the Data Layer, safe to lose and rebuilt from new events. Agent terminal-control actions additionally have their own audit trail on the terminal control plane, separate from this feed.

Related pages

• Dashboard — the Live feed this log backs
• Documents — where file events land when you click them
• Data Layer — the store behind the log and its tier
• Settings — the retention window