Answer: To troubleshoot Claude not responding to @claude commands, verify the GitHub App is installed on the repository, check that workflows are enabled, ensure your API key or OAuth token is set in repository secrets, confirm the comment contains @claude as a complete word, and confirm the commenting user has write access to the repository. Status: Confirmed Entry: tool/claude-code/troubleshooting/troubleshoot-claude-not-responding Revision: 3 Digest: sha256:e222087e47fee224 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:04:14Z Last changed: 2026-11-20T12:20:55Z (Step 5: — → Confirm the commenting user has write access to the repository.) Last verified: 2026-11-20T12:20:55Z Next check: 2026-11-21T12:20:55Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Step 1 | Verify the GitHub App is installed on the repository | [1] | 2026-11-20 Step 2 | Check that workflows are enabled for the repository | [1] | 2026-11-20 Step 3 | Ensure your API key or OAuth token is set in repository secrets | [1] | 2026-11-20 Step 4 | Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot` | [1] | 2026-11-20 Step 5 | Confirm the commenting user has write access to the repository. | [1] | 2026-11-20 Sources: [1] Anthropic. "Claude Code GitHub Actions". https://code.claude.com/docs/en/github-actions.md Role: primary. Accessed: 2026-11-20T12:20:55Z Quote: "Verify the GitHub App is installed on the repository" (Supports: Step 1) Quote: "Check that workflows are enabled for the repository" (Supports: Step 2) Quote: "Ensure your API key or OAuth token is set in repository secrets" (Supports: Step 3) Quote: "Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot`" (Supports: Step 4) Quote: "Confirm the commenting user has write access to the repository." (Supports: Step 5) Published: 2026-11-20T02:53:03Z Snapshot SHA-256: 584a1e56f0aacc3ea5a0d98ad3a0eb1e473c475ce51fdc3f22f59e538218f1a2 (captured 2026-11-20T12:20:53Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:20:55Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:20:55Z Last attempt: 2026-11-20T12:20:55Z Notes and limitations: Extracted automatically from a single official source (section "Claude not responding to @claude commands"). Related: https://latestn.com/tool/claude-code/troubleshooting/troubleshoot-gateway-errors How do I troubleshoot LLM gateway errors in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/validate-test-marketplace How do I validate and test a Claude Code plugin marketplace locally before hosting it? https://latestn.com/tool/claude-code/troubleshooting/verify-gateway-connection How do I verify that Claude Code is connected to the LLM gateway? https://latestn.com/tool/claude-code/troubleshooting/structured-output-error-handling What happens when Claude Code structured output validation fails and how is it handled? https://latestn.com/tool/claude-code/troubleshooting/structured-output-none Why does the Claude Code Agent SDK return a successful result but structured_output is None? https://latestn.com/tool/claude-code/troubleshooting/test-clean-configuration How do I test Claude Code with a clean configuration to find what's overriding my settings? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:20:55Z | changed | Step 5: — → Confirm the commenting user has write access to the repository. | [1] 2026-11-20T12:20:55Z | changed | Step 4: — → Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot` | [1] 2026-11-20T12:20:55Z | changed | Step 3: — → Ensure your API key or OAuth token is set in repository secrets | [1] 2026-11-20T12:20:55Z | changed | Step 2: — → Check that workflows are enabled for the repository | [1] 2026-11-20T12:20:55Z | changed | Step 1: — → Verify the GitHub App is installed on the repository | [1] 2026-11-20T12:20:55Z | changed | User access check: Confirm the commenting user has write access to the repository. → — | [1] 2026-11-20T12:20:55Z | changed | Comment format check: Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot` → — | [1] 2026-11-20T12:20:55Z | changed | Secrets check: Ensure your API key or OAuth token is set in repository secrets → — | [1] 2026-11-20T12:20:55Z | changed | Workflows check: Check that workflows are enabled for the repository → — | [1] 2026-11-20T12:20:55Z | changed | GitHub App check: Verify the GitHub App is installed on the repository → — | [1] 2026-11-14T12:16:42Z | changed | User access check: — → Confirm the commenting user has write access to the repository. | [1] 2026-11-14T12:16:42Z | changed | Comment format check: — → Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot` | [1] 2026-11-14T12:16:42Z | changed | Secrets check: — → Ensure your API key or OAuth token is set in repository secrets | [1] 2026-11-14T12:16:42Z | changed | Workflows check: — → Check that workflows are enabled for the repository | [1] 2026-11-14T12:16:42Z | changed | GitHub App check: — → Verify the GitHub App is installed on the repository | [1] 2026-11-14T12:16:42Z | changed | Fifth step: Confirm the commenting user has write access to the repository → — | [1] 2026-11-14T12:16:42Z | changed | Fourth step: Confirm the comment contains `@claude` as a complete word, not `/claude` or `@claude-bot` → — | [1] 2026-11-14T12:16:42Z | changed | Third step: Ensure your API key or OAuth token is set in repository secrets → — | [1] 2026-11-14T12:16:42Z | changed | Second step: Check that workflows are enabled for the repository → — | [1] 2026-11-14T12:16:42Z | changed | First step: Verify the GitHub App is installed on the repository → — | [1] 2026-11-13T03:04:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot Claude Code GitHub Actions when Claude is not responding to @claude commands? Revision 3, last verified 2026-11-20T12:20:55Z. https://latestn.com/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding (accessed 2026-11-21T10:03:42Z). @misc{LatestN_tool_claude_code_troubleshooting_troubleshoot_claude_not_responding_r3, title = {How do I troubleshoot Claude Code GitHub Actions when Claude is not responding to @claude commands?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding}}, note = {Revision 3; digest sha256:e222087e47fee224; last verified 2026-11-20T12:20:55Z; accessed 2026-11-21T10:03:42Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/troubleshoot-claude-not-responding