uloop-get-logs
Retrieve Unity Console logs via uloop CLI. Use when you need to: (1) Check for errors or warnings after operations, (2) Debug runtime issues in Unity Editor, (3) Investigate unexpected behavior or exceptions.
When & Why to Use This Skill
This Claude skill enables developers to retrieve and analyze Unity Console logs directly through the uloop CLI. It streamlines the debugging process by allowing users to filter for errors, warnings, or specific log messages, facilitating rapid identification of runtime issues and exceptions within the Unity Editor.
Use Cases
- 1. Error Diagnosis: Quickly identify and isolate runtime exceptions or null reference errors by filtering logs by type or searching for specific error messages.
- 2. Automated Log Monitoring: Integrate log retrieval into automated workflows to check for warnings or performance issues after specific operations or builds.
- 3. Remote Debugging Support: Assist in troubleshooting unexpected behaviors in the Unity Editor by fetching relevant stack traces and log history without manual console navigation.
| name | uloop-get-logs |
|---|---|
| description | "Check Unity Console logs. Use when: checking logs, debugging errors, investigating failures, or when user asks about console output. Key options: --log-type (Error/Warning/Log/All), --max-count, --search-text. Retrieves errors, warnings, and Debug.Log messages." |
uloop get-logs
Retrieve logs from Unity Console.
Usage
uloop get-logs [options]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--log-type |
string | All |
Log type filter: Error, Warning, Log, All |
--max-count |
integer | 100 |
Maximum number of logs to retrieve |
--search-text |
string | - | Text to search within logs |
--include-stack-trace |
boolean | false |
Include stack trace in output |
--use-regex |
boolean | false |
Use regex for search |
--search-in-stack-trace |
boolean | false |
Search within stack trace |
Examples
# Get all logs
uloop get-logs
# Get only errors
uloop get-logs --log-type Error
# Search for specific text
uloop get-logs --search-text "NullReference"
# Regex search
uloop get-logs --search-text "Missing.*Component" --use-regex
Output
Returns JSON array of log entries with message, type, and optional stack trace.