Step-by-step: How to generate a plugin conflict report to send to Claw support.

Hey everyone! 👋 I've been working with Claw's plugin ecosystem for a while now, and I've found that when you hit a weird slowdown or a language server feature just stops working, a structured report is the fastest way to get help from support. They'll usually ask for specific data, so getting it right the first time saves everyone a ton of back-and-forth.

Here's my step-by-step method, which I basically keep as a checklist in a spreadsheet. I break it down into three parts: the environment snapshot, the conflict test, and the performance baseline.

**1. Environment Snapshot (The Essentials)**
Support always needs this. I copy-paste it directly from my terminal or editor.
* **Editor & Version:** e.g., Claw 2024.1.3 (Community Edition)
* **OS & Version:** e.g., macOS Sonoma 14.5, Windows 11 Pro 23H2
* **Installed Plugins:** Use the command `claw plugin list --format=table` from your terminal. This gives a clean list with versions.

**2. The Conflict Test (Isolating the Issue)**
This is the most important part. You need to find the minimal set of plugins that causes the problem.
1. **Disable all plugins** in your Claw settings.
2. **Enable plugins one-by-one** (or in small, logical groups if you have many). Restart Claw after each change.
3. **Note the exact point** where the issue reappears. The last plugin (or group) you enabled is likely part of the conflict.
4. **Document the exact behavior:** "Language server for Python stops providing auto-complete" is better than "Python plugin is broken."

**3. Performance Baseline (For Slowdowns/Memory)**
If the issue is general slowness or high memory, capture some numbers.
* **Startup Time:** Note the time from launch to being fully ready to use.
* **Memory Usage:** Use your OS's activity monitor/task manager. Note Claw's memory footprint when idle and when the issue is triggered.
* **CPU Spike:** Does a specific action (like opening a file type) cause a sustained CPU spike?

**What to Send to Support**
Bundle all of the above into a single report. I usually structure it like this:

```
**Summary:** [One-line description, e.g., "JavaScript language server crashes when both 'Theme Purple' and 'NodeJS Helper' plugins are active."]

**Environment:**
- Editor: [Your Claw version]
- OS: [Your OS]
- Plugin List: [Paste the table/list here]

**Reproduction Steps:**
1. Have plugins A, B, and C enabled.
2. Open a .js file from project type X.
3. Attempt to use 'Go to Definition'.
4. Observe [specific error or behavior].

**Performance Data (if applicable):**
- Startup time with all plugins: ~45 seconds
- Startup time with only core plugins: ~8 seconds
- Memory spike occurs when [specific action].
```

This method has saved me hours of frustration. It turns a vague "things are slow" into a actionable ticket. Has anyone else developed a similar process? I'm always tweaking my checklist.

— alex