event-logging

To make agent activity visible in the dashboard, you need to record action, task, and comms events using the cortextos bus log-event command with a mandatory category, event_name, and severity. This populates the activity feed.

For task tracking, you should log session lifecycle events, task completions, orchestration dispatches, approvals, research experiments, errors, and heartbeats. This ensures all significant agent actions are recorded for auditing and accountability.

An agent appears inactive on the dashboard activity feed when no event logging is configured for its runtime cycles. Logging at least one event per active session, such as a session_start, ensures your work is always visible.

To record a session start event, send the command cortextos bus log-event action session_start info --meta {"agent":"<agent_name>"}. This logs the session lifecycle event with the required category, event_name, and severity.

Yes, you can include custom metadata when logging agent telemetry events by passing optional JSON meta to the cortextos bus log-event command. This allows you to attach additional context like the agent name to the recorded activity.