local-log-debug

Inspect and query UniClipboard's per-role JSONL logs on a single machine.

1.6k|73|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill local-log-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-log-debug
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.agents/skills/local-log-debug
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill local-log-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Diagnosing bugs in UniClipboard requires reading JSONL logs spread across three process roles (gui, daemon, cli) in platform-specific directories, which is tedious and error-prone to do by hand.

Core Features & Use Cases

  • Log Discovery & Freshness Check: Resolves the correct per-platform log directory (macOS, Linux, Windows, portable) and reports whether each role's log file is live, stale, or missing.
  • Query & Time-Merge: Tail, grep, run jq filters, and time-interleave logs across roles into one chronological stream to trace cross-process symptoms.
  • Use Case: A user reports "pairing failed on my Mac". Run the status command to confirm the daemon log is live, then merge gui and daemon logs since the failure time and grep the request_id across roles to find where the flow broke.

Quick Start

Ask the assistant to check the UniClipboard logs on this machine and explain why the recent sync or pairing attempt failed.

Frequently Asked Questions about local-log-debug

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

FAQPage Schema
How do I check UniClipboard logs on my machine?

Run the uc-logs.sh status command first to resolve the log directory and see per-role file freshness. Then use tail for recent lines, grep for a string, query with a jq filter, or merge to time-interleave roles.

How do I trace an error across the gui and daemon processes?

Use the merge command with a --since UTC timestamp to interleave gui and daemon logs chronologically. Then grep the same request_id, transfer_id, or device_id across roles to correlate the flow.

Where are UniClipboard log files stored on macOS, Linux, and Windows?

Logs live in ~/Library/Logs/<app>/ on macOS, $XDG_STATE_HOME/<app>/logs/ on Linux, and %LOCALAPPDATA%\<app>\logs\ on Windows, where <app> is app.uniclipboard.desktop plus an optional profile suffix. UC_LOG_DIR overrides resolution.

Why does the log file look stale or missing?

A stale or cold file usually means that process role is not currently running, or you are resolving the wrong profile. Try --profile default or check sibling directories before concluding the daemon is broken.

When should I not use local log debugging?

Do not use it for cross-device peer debugging, which needs the dual-side-debug approach, or for writing tracing instrumentation code. It also does not cover build failures or daemon sqlite state, since logs are observability only.