console-get-logs

Retrieve Unity Editor logs via HTTP API with configurable filters.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/lightvu25/Echoes --skill console-get-logs-lightvu25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: console-get-logs
Source: https://github.com/lightvu25/Echoes/tree/main/SKILLS/console-get-logs
Command: npx skills add https://github.com/lightvu25/Echoes --skill console-get-logs-lightvu25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieves Unity Editor logs for debugging and monitoring Unity activity.

Core Features & Use Cases

  • Retrieves logs via HTTP API with optional filters (maxEntries, logTypeFilter, includeStackTrace, lastMinutes).
  • Supports authorized requests and token-based access.
  • Useful for real-time monitoring and post-mortem debugging of Unity projects.

Quick Start

Call the HTTP API endpoint http://localhost:57228/api/tools/console-get-logs with appropriate filters to fetch logs.

Frequently Asked Questions about console-get-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve Unity Editor logs for debugging?

Retrieve Unity Editor logs by calling the HTTP API endpoint at localhost:57228 with parameters like maxEntries, logTypeFilter, includeStackTrace, and lastMinutes to fetch entries for debugging.

Can I filter Unity console logs by type and time range?

Yes, you can filter Unity console logs using the logTypeFilter and lastMinutes parameters when calling the API endpoint, allowing you to retrieve specific log types generated within a designated recent timeframe.

Does fetching Unity Editor logs via API require authorization?

Fetching Unity Editor logs supports optional authorization and token-based access, meaning you can configure authorized requests if your monitoring or debugging environment requires secure API access.

What is the best way to monitor Unity project activity in real-time?

The best way to monitor Unity project activity in real-time is querying the console log API endpoint with the lastMinutes filter, continuously retrieving recent editor logs to track active project behavior and errors.

Do I need to include stack traces when retrieving Unity logs for post-mortem debugging?

You do not need to include stack traces by default, but setting the includeStackTrace parameter to true when fetching Unity logs provides detailed error origins for more effective post-mortem debugging.