v1.0.5 runs but can't pick up the PR context nor post the output as a comment on the PR itself.

[polis80cy]

Describe the bug
GH Claude v1.0.5 actions runs as a result of tagging @claude in a comment with an ask to review the PR. However, it the action doesn't seem able to pick up the PR context, and won't post anything on the PR itself as a comment.

What am I missing?

To Reproduce
Steps to reproduce the behavior:

1. Go to open PR
2. Tag @claude in a comment with an ask to review PR
3. GH Claude action runs
4. No output / comment gets posted on PR

Expected behavior
GH Claude action runs successfully, picks up the PR context, posts the output as a comment on the PR itself.

Screenshots

Triggering Claude:

Claude action summary:

Workflow yml file

name: Claude Code Review

on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  pull_request_review:
    types: [submitted]

jobs:
  claude-review:
    if: |
      (github.event_name == 'issue_comment' && github.event.issue.pull_request && contains(github.event.comment.body, '@claude')) ||
      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude'))
    
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
      issues: write
      id-token: write
    
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Run Claude Code Review
        uses: anthropics/claude-code-action@v1.0.5
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

          # Minimal, actionable review prompt - no positive feedback
          prompt: |
            Review this PR and provide ONLY specific, actionable feedback. Do not provide:
            - Positive feedback, praise, or "LGTM" comments
            - General suggestions or best practices
            - Formatting or style nitpicks
            - Explanations of what the code does
            
            ONLY comment if you find:
            - Security vulnerabilities with exact fix
            - Bugs with specific line numbers and solutions
            - Breaking changes that need addressing
            - Missing error handling with exact implementation
            - Performance issues with specific optimization
            - Code quality issues like violations of established patterns, maintainability concerns, and significant readability issues
            
            Format: "[file:line]" for line-specific issues, "[file]" for file-level issues. Always include exact fix.
            
            If nothing actionable found, return "Nothing actionable found 👍"
          # Use sticky comments to make Claude reuse the same comment on subsequent pushes to the same PR
          use_sticky_comment: true
          
          # Tools for comprehensive PR review
          claude_args: |
           --append-system-prompt "Please refer to the project's CLAUDE.md file and .claude/agents/ documentation for:
            - Architecture patterns and conventions to follow
            - Testing patterns and requirements  
            - Code style guidelines and established practices
            - Technology stack and framework usage
            Pay special attention to violations of established patterns documented in these files."
            --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"

API Provider

[ x] Anthropic First-Party API (default)
[ ] AWS Bedrock
[ ] GCP Vertex

[polis80cy]

is this the fix?

prompt: |
            REPO: ${{ github.repository }}
            PR NUMBER: ${{ github.event.pull_request.number }}

            Review this PR.....

[uzairash]

Facing the same issue with this

name: Claude Auto Review
on:
  pull_request:
    types: [opened, synchronize]

jobs:
  review:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
      id-token: write
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
          track_progress: true
          prompt: |
            REPO: ${{ github.repository }}
            PR NUMBER: ${{ github.event.pull_request.number }}

            Please review this pull request with a focus on:
            - Code quality and best practices
            - Potential bugs or issues
            - Security implications
            - Performance considerations

            Note: The PR branch is already checked out in the current working directory.

            Use `gh pr comment` for top-level feedback.
            Use `mcp__github_inline_comment__create_inline_comment` to highlight specific code issues.
            Only post GitHub comments - don't submit review text as messages.

          claude_args: |
            --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"

It only comments this

[polis80cy]

Adding this:

prompt: |
            REPO: ${{ github.repository }}
            PR NUMBER: ${{ github.event.pull_request.number }}

            Review this PR.....

did not work.

Here's the new output, still not able to pick up the PR (it's running gh pr list instead, trying to pick the latest one), and complains about approval.

I'll help you review the PR. Let me first gather information about the current PR and repository status.

Token usage: .......

🔧 Bash
Parameters:

{
  "command": "gh pr list --state open --limit 1",
  "description": "Get the most recent open PR"
}
❌ Error: This command requires approval

🔧 Bash
Parameters:

{
  "command": "git log --oneline -10",
  "description": "Check recent commits to understand current state"
}
Result:

e5c01f ........

Let me check if there are any staged changes or recent modifications:

🔧 Bash
Parameters:

{
  "command": "git status",
  "description": "Check current git status for any changes"
}
Result:

On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

Since no specific PR number was provided and there are no current changes to review, I need more information to proceed with the PR review. Could you please provide:

The PR number you'd like me to review, or
A link to the specific PR, or
Tell me which branch contains the changes you want reviewed
Without this information, I cannot access the specific changes that need to be reviewed.

[ashwin-ant]

Addressing in #558

[ashwin-ant]

Fixed in 1.0.6, can you try upgrading?

[polis80cy]

@ashwin-ant v1.0.6 still doesn't work:

Claude Code Report
🚀 System Initialization
Available Tools: 16 tools loaded

I need to see the PR to review it. Let me check what PR is currently available.

Token usage: 20829 input, 2 output

🔧 Bash
Parameters:

{
  "command": "gh pr list --limit 1",
  "description": "List current PR to review"
}
❌ Error: This command requires approval

Token usage: 20829 input, 2 output

I don't see a specific PR number provided in your request. Could you please specify which PR you'd like me to review by providing either:

A PR number (e.g., "#123")
A GitHub URL to the PR
Or tell me to review the most recent PR
Once you provide the PR identifier, I'll review it and provide specific, actionable feedback only for security vulnerabilities, bugs, breaking changes, missing error handling, performance issues, or significant code quality violations.

Token usage: 20952 input, 1 output

✅ Final Result
I don't see a specific PR number provided in your request. Could you please specify which PR you'd like me to review by providing either:

A PR number (e.g., "#123")
A GitHub URL to the PR
Or tell me to review the most recent PR
Once you provide the PR identifier, I'll review it and provide specific, actionable feedback only for security vulnerabilities, bugs, breaking changes, missing error handling, performance issues, or significant code quality violations.

Cost: $0.0888 | Duration: 15.4s

I see no 403 errors anymore, and I see the PR number in the logs but for some reason the final output still isn't aware, and still nothing gets posted on the PR itself (the output used to be posted as a comment with the beta action):

Custom Claude arguments: --mcp-config '{
  "mcpServers": {
    "github_inline_comment": {
      "command": "bun",
      "args": [
        "run",
        "/home/runner/work/_actions/anthropics/claude-code-action/v1.0.6/src/mcp/github-inline-comment-server.ts"
      ],
      "env": {
        "GITHUB_TOKEN": "***",
        "REPO_OWNER": "xxxx",
        "REPO_NAME": "yyyy",
        "PR_NUMBER": "26283",
        "GITHUB_API_URL": "https://api.github.com/"
      }
    }
  }
}' --append-system-prompt "Please refer to the project's CLAUDE.md file and .claude/agents/ documentation for:
 - Architecture patterns and conventions to follow
 - Testing patterns and requirements  
 - Code style guidelines and established practices
 - Technology stack and framework usage
 Pay special attention to violations of established patterns documented in these files."
 --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"
Running Claude with prompt from file: /home/runner/work/_temp/claude-prompts/claude-prompt.txt
Full command: claude -p --mcp-config {
  "mcpServers": {
    "github_inline_comment": {
      "command": "bun",
      "args": [
        "run",
        "/home/runner/work/_actions/anthropics/claude-code-action/v1.0.6/src/mcp/github-inline-comment-server.ts"
  "session_id": ".......",
  "uuid": "........."
}
{
  "type": "result",
  "subtype": "success",
  "is_error": false,
  "duration_ms": 15433,
  "duration_api_ms": 17003,
  "num_turns": 4,
  "result": "I don't see a specific PR number provided in your request. Could you please specify which PR you'd like me to review by providing either:\n\n1. A PR number (e.g., \"#123\")\n2. A GitHub URL to the PR\n3. Or tell me to review the most recent PR\n\nOnce you provide the PR identifier, I'll review it and provide specific, actionable feedback only for security vulnerabilities, bugs, breaking changes, missing error handling, performance issues, or significant code quality violations.",
  "session_id": ".........",
  "total_cost_usd": 0.08880935,
  "usage": {
    "input_tokens": 7,
    "cache_creation_input_tokens": 119,
    "cache_read_input_tokens": 20826,
    "output_tokens": 110,
    "server_tool_use": {
      "web_search_requests": 0
    },
    "service_tier": "standard",
    "cache_creation": {
      "ephemeral_1h_input_tokens": 0,
      "ephemeral_5m_input_tokens": 119
    }
  },
  "permission_denials": [
    {
      "tool_name": "Bash",
      "tool_use_id": ".........",
      "tool_input": {
        "command": "gh pr list --limit 1",
        "description": "List current PR to review"
      }
    }
  ],
  "uuid": "........."
} 

[ashwin-ant]

@polis80cy I think you may need to add track_progress: true to your inputs. I was able to reproduce your issue and then resolve it once I added that.

[polis80cy]

Thank you for that @ashwin-ant. It finally works with the addition of track_progress.

One more question; how can I get the inline commenting behavior?

Right now, the output is always part of one single comment, which I assume it's, at least partly, because I am asking for that in the prompt with this line: "Format: "[file:line]" for line-specific issues, "[file]" for file-level issues. Always include exact fix."). Here's what the Claude ouput looks like currently:

Claude finished @polis80cy's task

Code Review Tasks
 - Read changed files and understand the implementation
 - Analyze for security vulnerabilities and bugs
 - Check for performance issues and code quality problems
 - Provide actionable feedback with specific fixes
 - Complete review

Review Findings
[packages/button.vue:2] Positioning bug - absolute position causes scroll issues (confirmed by existing review):

/* BROKEN - button moves with page scroll */
position: absolute;

/* FIX - button should stay fixed on screen */
position: fixed;

What I would like it to look like:

[polis80cy]

@ashwin-ant did you get a chance to take at my last question by any chance? still struggling to get Claude to output inline comments.

[colachg]

@polis80cy Try adding --max-turns to claude_args. In my case, increasing it from 10 to 20 worked.

I'm using the latest v1 version.