// Read current Unity Console entries from a running Editor. Use during bug investigation after compile, tests, PlayMode, or dynamic code to inspect logs, warnings, errors, and stack traces.
Use when Unity Editor is not running or needs a clean restart.
Clear Unity Console entries. Use before compile, tests, or debugging when stale logs would hide the current result.
Compile the Unity project and report errors/warnings. Use after C# edits or when a full Domain Reload compile is needed.
Control Unity Editor Play Mode. Use to start, stop, or pause Play Mode for runtime behavior checks and frame inspection.
Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for scene, prefab, SerializedObject, AssetDatabase refresh/.meta generation, menu, or PlayMode automation.
Find or inspect Unity GameObjects, especially objects the user currently selected in the Hierarchy. Use for details, components, tags, layers, or name/path searches.
| name | uloop-get-logs |
| description | Read current Unity Console entries from a running Editor. Use during bug investigation after compile, tests, PlayMode, or dynamic code to inspect logs, warnings, errors, and stack traces. |
Retrieve logs from Unity Console.
uloop get-logs [options]
| 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 |
| Option | Description |
|---|---|
--project-path <path> | Optional. Use only when the target Unity project is not the current directory. |
# 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
Returns JSON with:
TotalCount (number): Total logs available before max-count clippingDisplayedCount (number): Logs returned in this response (≤ --max-count)LogType (string): The --log-type filter that was appliedMaxCount (number): The --max-count cap that was appliedSearchText (string): The --search-text filter that was applied (empty when omitted)IncludeStackTrace (boolean): Whether stack traces are included in Logs[]Logs (array): Each entry has:
Type (string): "Error", "Warning", or "Log"Message (string): Log message bodyStackTrace (string): Stack trace text. Empty when --include-stack-trace is false.