Cursor rule

1---
2description:
3globs:
4alwaysApply: true
5---
6# Debugging with Script Kit Logs
7 
8## Log System Overview
9 
10Script Kit has a comprehensive logging system defined in [./src/main/logs.ts](./src/main/logs.ts). Logs are written to `~/Library/Logs/ScriptKit/` and are organized by component type.
11 
12## Available Log Files
13 
14The system creates separate log files for different components:
15- `main.log` - Main application logs
16- `term.log` - Terminal/PTY related logs (useful for invoke-pty debugging)
17- `process.log` - Process management logs
18- `script.log` - Script execution logs
19- `error.log` - Error logs across all components
20- `prompt.log` - Prompt-related logs
21- `ipc.log` - Inter-process communication logs
22- `debug.log` - Debug-specific logs
23- And many others (see [./src/main/logs.ts](./src/main/logs.ts) for the full list)
24 
25## Debugging Workflow
26 
27When debugging issues, follow this process:
28 
29### 1. Ask User to Run the Application
30Before checking logs, always ask the user to:
311. Run the Script Kit application
322. Confirm when the app is running
333. Perform the specific actions that are causing issues
34 
35### 2. Wait for User Confirmation
36Wait for the user to explicitly tell you:
37- "The app is running"
38- That they have performed the problematic actions
39- Any specific error messages they see in the UI
40 
41### 3. Check Relevant Logs
42Once the user confirms they've reproduced the issue, check the appropriate log files:
43 
44```bash
45# For terminal/PTY issues (like invoke-pty problems)
46tail -n 100 ~/Library/Logs/ScriptKit/term.log
47 
48# For general application issues
49tail -n 100 ~/Library/Logs/ScriptKit/main.log
50 
51# For errors
52tail -n 100 ~/Library/Logs/ScriptKit/error.log
53 
54# For process-related issues
55tail -n 100 ~/Library/Logs/ScriptKit/process.log
56```
57 
58### 4. Log Analysis
59Look for:
60- Error messages and stack traces
61- Performance timing information (console.log messages with timing)
62- Component-specific debug output
63- PTY pool behavior (for terminal issues)
64 
65## Example Debug Session
66 
67```
68Assistant: "Please run the Script Kit application and let me know when it's running."
69User: "The app is running"
70Assistant: "Great! Now please try the action that's causing the issue."
71User: "I tried running a script and it's slow"
72Assistant: "Perfect. Let me check the logs to see what's happening."
73```
74 
75Then check relevant logs based on the issue type.