Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/triage-issue.yml
Original file line number Diff line number Diff line change
Expand Up @@ -68,4 +68,4 @@ jobs:
/triage-issue ${{ steps.parse-issue.outputs.issue_number }} --ci
IMPORTANT: Do NOT wait for approval.
claude_args: |
--max-turns 20 --allowedTools "Bash(gh api *),Bash(gh pr list *),Bash(python3 .claude/skills/triage-issue/assets/post_linear_comment.py *),Bash(rm -f /tmp/triage_report.md)"
--max-turns 20 --allowedTools "Write(//tmp/triage_report.md),Bash(gh api *),Bash(gh pr list *),Bash(python3 .claude/skills/triage-issue/assets/post_linear_comment.py *),Bash(rm -f /tmp/triage_report.md)"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double slash in Write tool path causes mismatch

High Severity

The Write tool permission path is //tmp/triage_report.md (double leading slash), but the SKILL.md instructs writing to /tmp/triage_report.md (single slash), and both the post_linear_comment.py script and the rm -f cleanup command also reference /tmp/triage_report.md. If --allowedTools does exact pattern matching, the Claude agent's attempt to write to /tmp/triage_report.md won't match the //tmp/triage_report.md permission, causing the write to be denied and the triage workflow to fail.

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the correct syntax: https://code.claude.com/docs/en/permissions#read-and-edit

In Claude Code's permission syntax, // is the rule prefix for "absolute path from filesystem root" — it denotes how the rule is interpreted, not the literal path string.

Loading