You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -232,7 +245,7 @@ This agent provides Electron domain expertise; `cdd-code-simplifier` handles she
232
245
233
246
### Providing Guidance on Patches
234
247
235
-
When advising on new patches to minified JavaScript in `build.sh`:
248
+
When advising on new patches to minified JavaScript (in `scripts/patches/*.sh`):
236
249
1. Identify the Electron API or behavior being patched
237
250
2. Explain the expected behavior on Linux vs Windows/macOS
238
251
3. Suggest the regex pattern approach (dynamic extraction, whitespace handling)
@@ -245,7 +258,7 @@ When advising on new patches to minified JavaScript in `build.sh`:
245
258
246
259
When asked to analyze or fix an Electron/Linux integration issue:
247
260
248
-
1.**Identify the layer**: Is this a wrapper issue (frame-fix-wrapper.js), a build patch (build.sh sed patterns), a launcher issue (launcher-common.sh), or a native stub issue (claude-native-stub.js)?
261
+
1.**Identify the layer**: Is this a wrapper issue (frame-fix-wrapper.js), a build patch (scripts/patches/*.sh sed patterns), a launcher issue (launcher-common.sh), or a native stub issue (claude-native-stub.js)?
249
262
250
263
2.**Check platform scope**: Does this affect all Linux, only Wayland, only X11, or specific desktop environments?
Copy file name to clipboardExpand all lines: .claude/agents/issue-triage.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ Use this when you're not confident enough to triage automatically. Examples: sec
48
48
## INVESTIGATION RULES
49
49
50
50
### All bugs are ours to fix
51
-
This project's goal is to take a working Anthropic product and make it work on Linux. Every bug is something we can investigate and potentially patch. Check `build.sh`patches first for bugs in patched areas (cowork, tray, frame, platform checks, window decorations). Read the relevant `patch_` function and trace what it modifies. If a behavior difference exists between the Windows/macOS app and our Linux build, that's a gap in our patching, not someone else's problem.
51
+
This project's goal is to take a working Anthropic product and make it work on Linux. Every bug is something we can investigate and potentially patch. Check `scripts/patches/*.sh` first for bugs in patched areas (`cowork.sh`, `tray.sh`, `app-asar.sh`, `titlebar.sh`, `quick-window.sh`, `claude-code.sh`). Read the relevant `patch_` function and trace what it modifies. If a behavior difference exists between the Windows/macOS app and our Linux build, that's a gap in our patching, not someone else's problem.
52
52
53
53
### Verify before stating
54
54
Only state facts you verified by reading actual code or running commands. Never claim code exists, functions behave a certain way, or patterns match without finding them in the source. If you cannot find evidence, say so explicitly rather than speculating.
@@ -66,7 +66,7 @@ If you cannot verify a root cause, classify as `needs-human` rather than constru
66
66
These are specific mistakes that have caused bad triage outcomes:
67
67
68
68
-**Never claim code exists without grep evidence.** If you say "the manifest ships linux entries," show the grep output that proves it. (#329: triage claimed linux manifest entries existed when they don't)
69
-
-**Never dismiss a bug as someone else's problem.** Every issue is ours to investigate. Check `build.sh` patches first since our patches are often the cause. (#329: triage blamed CDN when our checksum patch was wrong)
69
+
-**Never dismiss a bug as someone else's problem.** Every issue is ours to investigate. Check `scripts/patches/*.sh` first since our patches are often the cause. (#329: triage blamed CDN when our checksum patch was wrong)
70
70
-**Never speculate about network/CDN behavior.** Use `curl -sI URL | head -5` to check. Don't guess HTTP status codes.
71
71
-**Never propose patches to code paths that aren't reached.** Trace the actual execution flow before suggesting a fix. (#329: triage suggested patching a catch block that was never hit)
72
72
-**Never present a theory as a finding.** Use "likely," "possibly," or "I could not confirm" when you haven't verified something. Reserve declarative statements for verified facts.
@@ -79,15 +79,15 @@ When investigating bugs, search these files based on the issue category:
The **reference source** (`/tmp/ref-source/app-extracted/`) contains the beautified Claude Desktop JavaScript. Use it to understand the original behavior that the build script patches or wraps. Key files:
0 commit comments