studio-dev-logs

Name: studio-dev-logs
Availability: InStock
Author: Instrument

Parse JSON lines from Studio's `.logs/` directory for debug, info, warn, and error messages.

3|Updated Apr 6, 2026

Search Tags:#development #debugging #logs #electron #system diagnostics

Ready to run

npx skills add https://github.com/instrument-org/instrument --skill studio-dev-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: studio-dev-logs
Source: https://github.com/instrument-org/instrument/tree/main/.agents/skills/studio-dev-logs
Command: npx skills add https://github.com/instrument-org/instrument --skill studio-dev-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides easy access to the logs generated by the Studio main process during local development, allowing users to quickly inspect the system's activity and diagnose issues.

Core Features & Use Cases

View Development Logs: Directly read the Electron main process logs from the .logs/ directory.
Log Layout: Organized by boot time with symlinks for easy access on macOS/Linux.
Error Filtering: Filter logs for errors or renderer-forwarded entries for specific troubleshooting.
Live Log Tailing: Continuously monitor the latest log activity while Studio is running.

Quick Start

To check the current Studio development logs, run:

cat apps/studio/.logs/current.jsonl

Frequently Asked Questions about studio-dev-logs

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

FAQPage Schema

How do I access Electron main process logs during local development?▼

You can access Electron main process logs by reading the JSON lines directly from the `.logs/` directory, specifically targeting the `current.jsonl` file to inspect system activity during local development sessions.

How do I filter Studio development logs for error messages?▼

To filter Studio development logs for errors, parse the JSON lines in the `.logs/` directory and isolate entries containing error or warn messages to streamline troubleshooting for specific renderer-forwarded issues.

Can I live tail logs while the Studio application is running?▼

Yes, you can continuously monitor the latest log activity while Studio is running by live tailing the `current.jsonl` file, allowing you to track real-time system diagnostics and debug messages.

Do I need a JSON parser to read the logs in the .logs directory?▼

Yes, parsing the log files requires JSON parsing capabilities because the Studio main process writes system diagnostics and debug entries as structured JSON lines within the `.logs/` directory.

What is the best way to organize development logs by boot time on macOS?▼

Development logs are organized by boot time using symlinks for easy access on macOS and Linux, allowing you to quickly locate specific local development sessions via the `current.jsonl` symlink.