get-session-logs

To retrieve session logs for troubleshooting failed commands, use this Skill to fetch recent system entries. It returns a configurable number of logs to help you inspect command details and error traces.

Yes, you can filter system logs by severity level such as ERROR, WARNING, INFO, or DEBUG. This level filtering surfaces relevant messages faster when diagnosing unexpected behavior.

The best way to review recent system activities is to retrieve session logs within the current agent session. You can configure the number of log entries returned to focus on recent operations and diagnose failures.

No, this log retrieval tool requires no external dependencies or components. It directly accesses session system logs to diagnose command failures without needing additional environment setup.

You need session logs to understand what happened and why unexpected behavior occurred. Retrieving these entries provides command details, error traces, and system status to pinpoint the root cause of failures.

To get the last 50 session logs filtered to show ERROR level entries, request a configurable number of logs with level filtering applied. This limits output and focuses on recent critical failures.