uloop-clear-console
uloop clear-console
Clear Unity console logs.
Usage
uloop clear-console [--add-confirmation-message]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--add-confirmation-message |
boolean | false |
Add confirmation message after clearing |
Global Options
| Option | Description |
|---|---|
--project-path <path> |
Optional. Use only when the target Unity project is not the current directory. |
Examples
# Clear console
uloop clear-console
# Clear with confirmation
uloop clear-console --add-confirmation-message
Output
Returns JSON with:
Success(boolean): Whether the clear operation succeededClearedLogCount(number): Total number of log entries that were clearedClearedCounts(object): Breakdown by log typeErrorCount(number): Errors clearedWarningCount(number): Warnings clearedLogCount(number): Info logs cleared
Message(string): Description of the result; carries the failure summary when the operation fails (e.g."Failed to clear console: ...")ErrorMessage(string): Currently always empty for this tool — readMessagefor failure details
More from hatayama/uloopmcp
uloop-find-game-objects
Use first when the user asks about the currently selected GameObject in the Unity Hierarchy. Inspect selected object details with `--search-mode Selected` before using `execute-dynamic-code`. Use when you need to: (1) Get details and component properties for selected GameObject(s), (2) Search for objects by name, regex, or path, (3) Find objects with specific components, tags, or layers. Use get-hierarchy when the child tree under the selection is needed. Returns hierarchy paths, active state, tags, layers, and components (or writes to a file when multiple GameObjects are selected).
37uloop-unity-search
Search Unity project assets using Unity Search engine. Use when you need to: (1) Find scenes, prefabs, scripts, materials, or other assets, (2) Filter assets by file extension or type, (3) Search with Unity Search query syntax and specific providers. Returns asset paths and metadata.
36uloop-run-tests
Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Single-flight only — never run multiple `uloop run-tests` in parallel.
35uloop-launch
Launch Unity project with matching Editor version via uloop CLI. Use when you need to: (1) Open a Unity project with the correct Editor version, (2) Restart Unity to apply changes, (3) Switch build target when launching.
35uloop-get-logs
Retrieve current Unity Console entries via uloop CLI. Use when you need to: (1) inspect errors, warnings, or logs after compile, tests, PlayMode, or dynamic code execution, (2) search current Console messages or stack traces, (3) confirm whether a recent Unity operation emitted logs. Prefer this over reading Editor.log or Unity log files for normal Console contents; use log files only for startup, crash, freeze, or uloop connection failures.
35uloop-control-play-mode
Control Unity Editor play mode (play/stop/pause). Use when you need to: (1) Start play mode to test game behavior, (2) Stop play mode to return to edit mode, (3) Pause play mode for frame-by-frame inspection.
35