fix: use proper type guards instead of manual property checks

Address review feedback by using isEntityContext() type guard instead of checking 'isPR' in context manually. This provides better type safety and uses the existing type guard infrastructure.
Merge branch 'main' into km/add-mcp-to-agent
2026-01-23 15:04:13 +08:00 · 2025-08-01 15:43:07 -07:00 · 2025-08-01 15:38:20 -07:00 · 2025-08-01 14:35:42 -07:00 · 2025-08-01 14:26:31 -07:00 · 2025-08-01 14:26:15 -07:00
24 changed files with 1011 additions and 1155 deletions
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -53,7 +53,7 @@ Execution steps:
 #### Mode System (`src/modes/`)

 - **Tag Mode** (`tag/`): Responds to `@claude` mentions and issue assignments
- **Agent Mode** (`agent/`): Automated execution for workflow_dispatch and schedule events only
+- **Agent Mode** (`agent/`): Automated execution without trigger checking
 - Extensible registry pattern in `modes/registry.ts`

 #### GitHub Integration (`src/github/`)
@@ -118,7 +118,7 @@ src/

 - Modes implement `Mode` interface with `shouldTrigger()` and `prepare()` methods
 - Registry validates mode compatibility with GitHub event types
- Agent mode only works with workflow_dispatch and schedule events
+- Agent mode bypasses all trigger checking for automation scenarios

 ### Comment Threading

--- a/docs/faq.md
+++ b/docs/faq.md
@@ -135,14 +135,6 @@ allowed_tools: "Bash(npm:*),Bash(git:*)" # Allows only npm and git commands

 No, Claude's GitHub app token is sandboxed to the current repository only. It cannot push to any other repositories. It can, however, read public repositories, but to get access to this, you must configure it with tools to do so.

-### Why aren't comments posted as claude[bot]?
-
-Comments appear as claude[bot] when the action uses its built-in authentication. However, if you provide a `github_token` in your workflow, the action will use that token's authentication instead, causing comments to appear under a different username.
-
-**Solution**: Remove `github_token` from your workflow file unless you're using a custom GitHub App.
-
-**Note**: The `use_sticky_comment` feature only works with claude[bot] authentication. If you're using a custom `github_token`, sticky comments won't update properly since they expect the claude[bot] username.
-
 ## MCP Servers and Extended Functionality

 ### What MCP servers are available by default?
--- a/README.md
+++ b/README.md
@@ -23,23 +23,963 @@ This command will guide you through setting up the GitHub app and required secre
 **Note**:

 - You must be a repository admin to install the GitHub app and add secrets
- This quickstart method is only available for direct Anthropic API users. For AWS Bedrock or Google Vertex AI setup, see [docs/cloud-providers.md](./docs/cloud-providers.md).
+- This quickstart method is only available for direct Anthropic API users. If you're using AWS Bedrock, please see the instructions below.

-## Documentation
+### Manual Setup (Direct API)

- [Setup Guide](./docs/setup.md) - Manual setup, custom GitHub apps, and security best practices
- [Usage Guide](./docs/usage.md) - Basic usage, workflow configuration, and input parameters
- [Custom Automations](./docs/custom-automations.md) - Examples of automated workflows and custom prompts
- [Configuration](./docs/configuration.md) - MCP servers, permissions, environment variables, and advanced settings
- [Experimental Features](./docs/experimental.md) - Execution modes and network restrictions
- [Cloud Providers](./docs/cloud-providers.md) - AWS Bedrock and Google Vertex AI setup
- [Capabilities & Limitations](./docs/capabilities-and-limitations.md) - What Claude can and cannot do
- [Security](./docs/security.md) - Access control, permissions, and commit signing
- [FAQ](./docs/faq.md) - Common questions and troubleshooting
+**Requirements**: You must be a repository admin to complete these steps.
+
+1. Install the Claude GitHub app to your repository: https://github.com/apps/claude
+2. Add authentication to your repository secrets ([Learn how to use secrets in GitHub Actions](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions)):
+   - Either `ANTHROPIC_API_KEY` for API key authentication
+   - Or `CLAUDE_CODE_OAUTH_TOKEN` for OAuth token authentication (Pro and Max users can generate this by running `claude setup-token` locally)
+3. Copy the workflow file from [`examples/claude.yml`](./examples/claude.yml) into your repository's `.github/workflows/`
+
+### Using a Custom GitHub App
+
+If you prefer not to install the official Claude app, you can create your own GitHub App to use with this action. This gives you complete control over permissions and access.
+
+**When you may want to use a custom GitHub App:**
+
+- You need more restrictive permissions than the official app
+- Organization policies prevent installing third-party apps
+- You're using AWS Bedrock or Google Vertex AI
+
+**Steps to create and use a custom GitHub App:**
+
+1. **Create a new GitHub App:**
+
+   - Go to https://github.com/settings/apps (for personal apps) or your organization's settings
+   - Click "New GitHub App"
+   - Configure the app with these minimum permissions:
+     - **Repository permissions:**
+       - Contents: Read & Write
+       - Issues: Read & Write
+       - Pull requests: Read & Write
+     - **Account permissions:** None required
+   - Set "Where can this GitHub App be installed?" to your preference
+   - Create the app
+
+2. **Generate and download a private key:**
+
+   - After creating the app, scroll down to "Private keys"
+   - Click "Generate a private key"
+   - Download the `.pem` file (keep this secure!)
+
+3. **Install the app on your repository:**
+
+   - Go to the app's settings page
+   - Click "Install App"
+   - Select the repositories where you want to use Claude
+
+4. **Add the app credentials to your repository secrets:**
+
+   - Go to your repository's Settings → Secrets and variables → Actions
+   - Add these secrets:
+     - `APP_ID`: Your GitHub App's ID (found in the app settings)
+     - `APP_PRIVATE_KEY`: The contents of the downloaded `.pem` file
+
+5. **Update your workflow to use the custom app:**
+
+   ```yaml
+   name: Claude with Custom App
+   on:
+     issue_comment:
+       types: [created]
+     # ... other triggers
+
+   jobs:
+     claude-response:
+       runs-on: ubuntu-latest
+       steps:
+         # Generate a token from your custom app
+         - name: Generate GitHub App token
+           id: app-token
+           uses: actions/create-github-app-token@v1
+           with:
+             app-id: ${{ secrets.APP_ID }}
+             private-key: ${{ secrets.APP_PRIVATE_KEY }}
+
+         # Use Claude with your custom app's token
+         - uses: anthropics/claude-code-action@beta
+           with:
+             anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+             github_token: ${{ steps.app-token.outputs.token }}
+             # ... other configuration
+   ```
+
+**Important notes:**
+
+- The custom app must have read/write permissions for Issues, Pull Requests, and Contents
+- Your app's token will have the exact permissions you configured, nothing more
+
+For more information on creating GitHub Apps, see the [GitHub documentation](https://docs.github.com/en/apps/creating-github-apps).

 ## 📚 FAQ

-Having issues or questions? Check out our [Frequently Asked Questions](./docs/faq.md) for solutions to common problems and detailed explanations of Claude's capabilities and limitations.
+Having issues or questions? Check out our [Frequently Asked Questions](./FAQ.md) for solutions to common problems and detailed explanations of Claude's capabilities and limitations.
+
+## Usage
+
+Add a workflow file to your repository (e.g., `.github/workflows/claude.yml`):
+
+```yaml
+name: Claude Assistant
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned, labeled]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude-response:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: anthropics/claude-code-action@beta
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          # Or use OAuth token instead:
+          # claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          # Optional: set execution mode (default: tag)
+          # mode: "tag"
+          # Optional: add custom trigger phrase (default: @claude)
+          # trigger_phrase: "/claude"
+          # Optional: add assignee trigger for issues
+          # assignee_trigger: "claude"
+          # Optional: add label trigger for issues
+          # label_trigger: "claude"
+          # Optional: add custom environment variables (YAML format)
+          # claude_env: |
+          #   NODE_ENV: test
+          #   DEBUG: true
+          #   API_URL: https://api.example.com
+          # Optional: limit the number of conversation turns
+          # max_turns: "5"
+          # Optional: grant additional permissions (requires corresponding GitHub token permissions)
+          # additional_permissions: |
+          #   actions: read
+```
+
+## Inputs
+
+| Input                          | Description                                                                                                                           | Required | Default   |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | -------- | --------- |
+| `mode`                         | Execution mode: 'tag' (default - triggered by mentions/assignments), 'agent' (for automation), 'experimental-review' (for PR reviews) | No       | `tag`     |
+| `anthropic_api_key`            | Anthropic API key (required for direct API, not needed for Bedrock/Vertex)                                                            | No\*     | -         |
+| `claude_code_oauth_token`      | Claude Code OAuth token (alternative to anthropic_api_key)                                                                            | No\*     | -         |
+| `direct_prompt`                | Direct prompt for Claude to execute automatically without needing a trigger (for automated workflows)                                 | No       | -         |
+| `override_prompt`              | Complete replacement of Claude's prompt with custom template (supports variable substitution)                                         | No       | -         |
+| `base_branch`                  | The base branch to use for creating new branches (e.g., 'main', 'develop')                                                            | No       | -         |
+| `max_turns`                    | Maximum number of conversation turns Claude can take (limits back-and-forth exchanges)                                                | No       | -         |
+| `timeout_minutes`              | Timeout in minutes for execution                                                                                                      | No       | `30`      |
+| `use_sticky_comment`           | Use just one comment to deliver PR comments (only applies for pull_request event workflows)                                           | No       | `false`   |
+| `github_token`                 | GitHub token for Claude to operate with. **Only include this if you're connecting a custom GitHub app of your own!**                  | No       | -         |
+| `model`                        | Model to use (provider-specific format required for Bedrock/Vertex)                                                                   | No       | -         |
+| `fallback_model`               | Enable automatic fallback to specified model when primary model is unavailable                                                        | No       | -         |
+| `anthropic_model`              | **DEPRECATED**: Use `model` instead. Kept for backward compatibility.                                                                 | No       | -         |
+| `use_bedrock`                  | Use Amazon Bedrock with OIDC authentication instead of direct Anthropic API                                                           | No       | `false`   |
+| `use_vertex`                   | Use Google Vertex AI with OIDC authentication instead of direct Anthropic API                                                         | No       | `false`   |
+| `allowed_tools`                | Additional tools for Claude to use (the base GitHub tools will always be included)                                                    | No       | ""        |
+| `disallowed_tools`             | Tools that Claude should never use                                                                                                    | No       | ""        |
+| `custom_instructions`          | Additional custom instructions to include in the prompt for Claude                                                                    | No       | ""        |
+| `mcp_config`                   | Additional MCP configuration (JSON string) that merges with the built-in GitHub MCP servers                                           | No       | ""        |
+| `assignee_trigger`             | The assignee username that triggers the action (e.g. @claude). Only used for issue assignment                                         | No       | -         |
+| `label_trigger`                | The label name that triggers the action when applied to an issue (e.g. "claude")                                                      | No       | -         |
+| `trigger_phrase`               | The trigger phrase to look for in comments, issue/PR bodies, and issue titles                                                         | No       | `@claude` |
+| `branch_prefix`                | The prefix to use for Claude branches (defaults to 'claude/', use 'claude-' for dash format)                                          | No       | `claude/` |
+| `claude_env`                   | Custom environment variables to pass to Claude Code execution (YAML format)                                                           | No       | ""        |
+| `settings`                     | Claude Code settings as JSON string or path to settings JSON file                                                                     | No       | ""        |
+| `additional_permissions`       | Additional permissions to enable. Currently supports 'actions: read' for viewing workflow results                                     | No       | ""        |
+| `experimental_allowed_domains` | Restrict network access to these domains only (newline-separated).                                                                    | No       | ""        |
+| `use_commit_signing`           | Enable commit signing using GitHub's commit signature verification. When false, Claude uses standard git commands                     | No       | `false`   |
+
+\*Required when using direct Anthropic API (default and when not using Bedrock or Vertex)
+
+> **Note**: This action is currently in beta. Features and APIs may change as we continue to improve the integration.
+
+## Execution Modes
+
+The action supports three execution modes, each optimized for different use cases:
+
+### Tag Mode (Default)
+
+The traditional implementation mode that responds to @claude mentions, issue assignments, or labels.
+
+- **Triggers**: `@claude` mentions, issue assignment, label application
+- **Features**: Creates tracking comments with progress checkboxes, full implementation capabilities
+- **Use case**: General-purpose code implementation and Q&A
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    # mode: tag is the default
+```
+
+### Agent Mode
+
+For automation and scheduled tasks without trigger checking.
+
+- **Triggers**: Always runs (no trigger checking)
+- **Features**: Perfect for scheduled tasks, works with `override_prompt`
+- **Use case**: Maintenance tasks, automated reporting, scheduled checks
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    mode: agent
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    override_prompt: |
+      Check for outdated dependencies and create an issue if any are found.
+```
+
+### Experimental Review Mode
+
+> **EXPERIMENTAL**: This mode is under active development and may change significantly. Use with caution in production workflows.
+
+Specialized mode for automated PR code reviews using GitHub's review API.
+
+- **Triggers**: Automatically on PR events (opened, synchronize, reopened) when configured in workflow
+- **Features**: Creates inline review comments with suggestions, batches feedback into a single review
+- **Use case**: Automated code reviews, security scanning, best practices enforcement
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    mode: experimental-review
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    custom_instructions: |
+      Focus on security vulnerabilities, performance issues, and code quality.
+```
+
+Review mode automatically includes GitHub MCP tools for creating pending reviews and inline comments. See [`examples/claude-experimental-review-mode.yml`](./examples/claude-experimental-review-mode.yml) for a complete example.
+
+See [`examples/claude-modes.yml`](./examples/claude-modes.yml) for complete examples of available modes.
+
+### Using Custom MCP Configuration
+
+The `mcp_config` input allows you to add custom MCP (Model Context Protocol) servers to extend Claude's capabilities. These servers merge with the built-in GitHub MCP servers.
+
+#### Basic Example: Adding a Sequential Thinking Server
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    mcp_config: |
+      {
+        "mcpServers": {
+          "sequential-thinking": {
+            "command": "npx",
+            "args": [
+              "-y",
+              "@modelcontextprotocol/server-sequential-thinking"
+            ]
+          }
+        }
+      }
+    allowed_tools: "mcp__sequential-thinking__sequentialthinking" # Important: Each MCP tool from your server must be listed here, comma-separated
+    # ... other inputs
+```
+
+#### Passing Secrets to MCP Servers
+
+For MCP servers that require sensitive information like API keys or tokens, use GitHub Secrets in the environment variables:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    mcp_config: |
+      {
+        "mcpServers": {
+          "custom-api-server": {
+            "command": "npx",
+            "args": ["-y", "@example/api-server"],
+            "env": {
+              "API_KEY": "${{ secrets.CUSTOM_API_KEY }}",
+              "BASE_URL": "https://api.example.com"
+            }
+          }
+        }
+      }
+    # ... other inputs
+```
+
+#### Using Python MCP Servers with uv
+
+For Python-based MCP servers managed with `uv`, you need to specify the directory containing your server:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    mcp_config: |
+      {
+        "mcpServers": {
+          "my-python-server": {
+            "type": "stdio",
+            "command": "uv",
+            "args": [
+              "--directory",
+              "${{ github.workspace }}/path/to/server/",
+              "run",
+              "server_file.py"
+            ]
+          }
+        }
+      }
+    allowed_tools: "my-python-server__<tool_name>" # Replace <tool_name> with your server's tool names
+    # ... other inputs
+```
+
+For example, if your Python MCP server is at `mcp_servers/weather.py`, you would use:
+
+```yaml
+"args":
+  ["--directory", "${{ github.workspace }}/mcp_servers/", "run", "weather.py"]
+```
+
+**Important**:
+
+- Always use GitHub Secrets (`${{ secrets.SECRET_NAME }}`) for sensitive values like API keys, tokens, or passwords. Never hardcode secrets directly in the workflow file.
+- Your custom servers will override any built-in servers with the same name.
+
+## Examples
+
+### Ways to Tag @claude
+
+These examples show how to interact with Claude using comments in PRs and issues. By default, Claude will be triggered anytime you mention `@claude`, but you can customize the exact trigger phrase using the `trigger_phrase` input in the workflow.
+
+Claude will see the full PR context, including any comments.
+
+#### Ask Questions
+
+Add a comment to a PR or issue:
+
+```
+@claude What does this function do and how could we improve it?
+```
+
+Claude will analyze the code and provide a detailed explanation with suggestions.
+
+#### Request Fixes
+
+Ask Claude to implement specific changes:
+
+```
+@claude Can you add error handling to this function?
+```
+
+#### Code Review
+
+Get a thorough review:
+
+```
+@claude Please review this PR and suggest improvements
+```
+
+Claude will analyze the changes and provide feedback.
+
+#### Fix Bugs from Screenshots
+
+Upload a screenshot of a bug and ask Claude to fix it:
+
+```
+@claude Here's a screenshot of a bug I'm seeing [upload screenshot]. Can you fix it?
+```
+
+Claude can see and analyze images, making it easy to fix visual bugs or UI issues.
+
+### Custom Automations
+
+These examples show how to configure Claude to act automatically based on GitHub events, without requiring manual @mentions.
+
+#### Supported GitHub Events
+
+This action supports the following GitHub events ([learn more GitHub event triggers](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)):
+
+- `pull_request` - When PRs are opened or synchronized
+- `issue_comment` - When comments are created on issues or PRs
+- `pull_request_comment` - When comments are made on PR diffs
+- `issues` - When issues are opened or assigned
+- `pull_request_review` - When PR reviews are submitted
+- `pull_request_review_comment` - When comments are made on PR reviews
+- `repository_dispatch` - Custom events triggered via API (coming soon)
+- `workflow_dispatch` - Manual workflow triggers (coming soon)
+
+#### Automated Documentation Updates
+
+Automatically update documentation when specific files change (see [`examples/claude-pr-path-specific.yml`](./examples/claude-pr-path-specific.yml)):
+
+```yaml
+on:
+  pull_request:
+    paths:
+      - "src/api/**/*.ts"
+
+steps:
+  - uses: anthropics/claude-code-action@beta
+    with:
+      direct_prompt: |
+        Update the API documentation in README.md to reflect
+        the changes made to the API endpoints in this PR.
+```
+
+When API files are modified, Claude automatically updates your README with the latest endpoint documentation and pushes the changes back to the PR, keeping your docs in sync with your code.
+
+#### Author-Specific Code Reviews
+
+Automatically review PRs from specific authors or external contributors (see [`examples/claude-review-from-author.yml`](./examples/claude-review-from-author.yml)):
+
+```yaml
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  review-by-author:
+    if: |
+      github.event.pull_request.user.login == 'developer1' ||
+      github.event.pull_request.user.login == 'external-contributor'
+    steps:
+      - uses: anthropics/claude-code-action@beta
+        with:
+          direct_prompt: |
+            Please provide a thorough review of this pull request.
+            Pay extra attention to coding standards, security practices,
+            and test coverage since this is from an external contributor.
+```
+
+Perfect for automatically reviewing PRs from new team members, external contributors, or specific developers who need extra guidance.
+
+#### Custom Prompt Templates
+
+Use `override_prompt` for complete control over Claude's behavior with variable substitution:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    override_prompt: |
+      Analyze PR #$PR_NUMBER in $REPOSITORY for security vulnerabilities.
+
+      Changed files:
+      $CHANGED_FILES
+
+      Focus on:
+      - SQL injection risks
+      - XSS vulnerabilities
+      - Authentication bypasses
+      - Exposed secrets or credentials
+
+      Provide severity ratings (Critical/High/Medium/Low) for any issues found.
+```
+
+The `override_prompt` feature supports these variables:
+
+- `$REPOSITORY`, `$PR_NUMBER`, `$ISSUE_NUMBER`
+- `$PR_TITLE`, `$ISSUE_TITLE`, `$PR_BODY`, `$ISSUE_BODY`
+- `$PR_COMMENTS`, `$ISSUE_COMMENTS`, `$REVIEW_COMMENTS`
+- `$CHANGED_FILES`, `$TRIGGER_COMMENT`, `$TRIGGER_USERNAME`
+- `$BRANCH_NAME`, `$BASE_BRANCH`, `$EVENT_TYPE`, `$IS_PR`
+
+## How It Works
+
+1. **Trigger Detection**: Listens for comments containing the trigger phrase (default: `@claude`) or issue assignment to a specific user
+2. **Context Gathering**: Analyzes the PR/issue, comments, code changes
+3. **Smart Responses**: Either answers questions or implements changes
+4. **Branch Management**: Creates new PRs for human authors, pushes directly for Claude's own PRs
+5. **Communication**: Posts updates at every step to keep you informed
+
+This action is built on top of [`anthropics/claude-code-base-action`](https://github.com/anthropics/claude-code-base-action).
+
+## Capabilities and Limitations
+
+### What Claude Can Do
+
+- **Respond in a Single Comment**: Claude operates by updating a single initial comment with progress and results
+- **Answer Questions**: Analyze code and provide explanations
+- **Implement Code Changes**: Make simple to moderate code changes based on requests
+- **Prepare Pull Requests**: Creates commits on a branch and links back to a prefilled PR creation page
+- **Perform Code Reviews**: Analyze PR changes and provide detailed feedback
+- **Smart Branch Handling**:
+  - When triggered on an **issue**: Always creates a new branch for the work
+  - When triggered on an **open PR**: Always pushes directly to the existing PR branch
+  - When triggered on a **closed PR**: Creates a new branch since the original is no longer active
+- **View GitHub Actions Results**: Can access workflow runs, job logs, and test results on the PR where it's tagged when `actions: read` permission is configured (see [Additional Permissions for CI/CD Integration](#additional-permissions-for-cicd-integration))
+
+### What Claude Cannot Do
+
+- **Submit PR Reviews**: Claude cannot submit formal GitHub PR reviews
+- **Approve PRs**: For security reasons, Claude cannot approve pull requests
+- **Post Multiple Comments**: Claude only acts by updating its initial comment
+- **Execute Commands Outside Its Context**: Claude only has access to the repository and PR/issue context it's triggered in
+- **Run Arbitrary Bash Commands**: By default, Claude cannot execute Bash commands unless explicitly allowed using the `allowed_tools` configuration
+- **Perform Branch Operations**: Cannot merge branches, rebase, or perform other git operations beyond pushing commits
+
+## Advanced Configuration
+
+### Additional Permissions for CI/CD Integration
+
+The `additional_permissions` input allows Claude to access GitHub Actions workflow information when you grant the necessary permissions. This is particularly useful for analyzing CI/CD failures and debugging workflow issues.
+
+#### Enabling GitHub Actions Access
+
+To allow Claude to view workflow run results, job logs, and CI status:
+
+1. **Grant the necessary permission to your GitHub token**:
+
+   - When using the default `GITHUB_TOKEN`, add the `actions: read` permission to your workflow:
+
+   ```yaml
+   permissions:
+     contents: write
+     pull-requests: write
+     issues: write
+     actions: read # Add this line
+   ```
+
+2. **Configure the action with additional permissions**:
+
+   ```yaml
+   - uses: anthropics/claude-code-action@beta
+     with:
+       anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+       additional_permissions: |
+         actions: read
+       # ... other inputs
+   ```
+
+3. **Claude will automatically get access to CI/CD tools**:
+   When you enable `actions: read`, Claude can use the following MCP tools:
+   - `mcp__github_ci__get_ci_status` - View workflow run statuses
+   - `mcp__github_ci__get_workflow_run_details` - Get detailed workflow information
+   - `mcp__github_ci__download_job_log` - Download and analyze job logs
+
+#### Example: Debugging Failed CI Runs
+
+```yaml
+name: Claude CI Helper
+on:
+  issue_comment:
+    types: [created]
+
+permissions:
+  contents: write
+  pull-requests: write
+  issues: write
+  actions: read # Required for CI access
+
+jobs:
+  claude-ci-helper:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: anthropics/claude-code-action@beta
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          additional_permissions: |
+            actions: read
+          # Now Claude can respond to "@claude why did the CI fail?"
+```
+
+**Important Notes**:
+
+- The GitHub token must have the `actions: read` permission in your workflow
+- If the permission is missing, Claude will warn you and suggest adding it
+- Currently, only `actions: read` is supported, but the format allows for future extensions
+
+### Custom Environment Variables
+
+You can pass custom environment variables to Claude Code execution using the `claude_env` input. This is useful for CI/test setups that require specific environment variables:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    claude_env: |
+      NODE_ENV: test
+      CI: true
+      DATABASE_URL: postgres://test:test@localhost:5432/test_db
+    # ... other inputs
+```
+
+The `claude_env` input accepts YAML format where each line defines a key-value pair. These environment variables will be available to Claude Code during execution, allowing it to run tests, build processes, or other commands that depend on specific environment configurations.
+
+### Limiting Conversation Turns
+
+You can use the `max_turns` parameter to limit the number of back-and-forth exchanges Claude can have during task execution. This is useful for:
+
+- Controlling costs by preventing runaway conversations
+- Setting time boundaries for automated workflows
+- Ensuring predictable behavior in CI/CD pipelines
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    max_turns: "5" # Limit to 5 conversation turns
+    # ... other inputs
+```
+
+When the turn limit is reached, Claude will stop execution gracefully. Choose a value that gives Claude enough turns to complete typical tasks while preventing excessive usage.
+
+### Custom Tools
+
+By default, Claude only has access to:
+
+- File operations (reading, committing, editing files, read-only git commands)
+- Comment management (creating/updating comments)
+- Basic GitHub operations
+
+Claude does **not** have access to execute arbitrary Bash commands by default. If you want Claude to run specific commands (e.g., npm install, npm test), you must explicitly allow them using the `allowed_tools` configuration:
+
+**Note**: If your repository has a `.mcp.json` file in the root directory, Claude will automatically detect and use the MCP server tools defined there. However, these tools still need to be explicitly allowed via the `allowed_tools` configuration.
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    allowed_tools: |
+      Bash(npm install)
+      Bash(npm run test)
+      Edit
+      Replace
+      NotebookEditCell
+    disallowed_tools: |
+      TaskOutput
+      KillTask
+    # ... other inputs
+```
+
+**Note**: The base GitHub tools are always included. Use `allowed_tools` to add additional tools (including specific Bash commands), and `disallowed_tools` to prevent specific tools from being used.
+
+### Custom Model
+
+Use a specific Claude model:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    # model: "claude-3-5-sonnet-20241022"  # Optional: specify a different model
+    # ... other inputs
+```
+
+### Network Restrictions
+
+For enhanced security, you can restrict Claude's network access to specific domains only. This feature is particularly useful for:
+
+- Enterprise environments with strict security policies
+- Preventing access to external services
+- Limiting Claude to only your internal APIs and services
+
+When `experimental_allowed_domains` is set, Claude can only access the domains you explicitly list. You'll need to include the appropriate provider domains based on your authentication method.
+
+#### Provider-Specific Examples
+
+##### If using Anthropic API or subscription
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    # Or: claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+    experimental_allowed_domains: |
+      .anthropic.com
+```
+
+##### If using AWS Bedrock
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    use_bedrock: "true"
+    experimental_allowed_domains: |
+      bedrock.*.amazonaws.com
+      bedrock-runtime.*.amazonaws.com
+```
+
+##### If using Google Vertex AI
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    use_vertex: "true"
+    experimental_allowed_domains: |
+      *.googleapis.com
+      vertexai.googleapis.com
+```
+
+#### Common GitHub Domains
+
+In addition to your provider domains, you may need to include GitHub-related domains. For GitHub.com users, common domains include:
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    experimental_allowed_domains: |
+      .anthropic.com  # For Anthropic API
+      .github.com
+      .githubusercontent.com
+      ghcr.io
+      .blob.core.windows.net
+```
+
+For GitHub Enterprise users, replace the GitHub.com domains above with your enterprise domains (e.g., `.github.company.com`, `packages.company.com`, etc.).
+
+To determine which domains your workflow needs, you can temporarily run without restrictions and monitor the network requests, or check your GitHub Enterprise configuration for the specific services you use.
+
+### Claude Code Settings
+
+You can provide Claude Code settings to customize behavior such as model selection, environment variables, permissions, and hooks. Settings can be provided either as a JSON string or a path to a settings file.
+
+#### Option 1: Settings File
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    settings: "path/to/settings.json"
+    # ... other inputs
+```
+
+#### Option 2: Inline Settings
+
+```yaml
+- uses: anthropics/claude-code-action@beta
+  with:
+    settings: |
+      {
+        "model": "claude-opus-4-20250514",
+        "env": {
+          "DEBUG": "true",
+          "API_URL": "https://api.example.com"
+        },
+        "permissions": {
+          "allow": ["Bash", "Read"],
+          "deny": ["WebFetch"]
+        },
+        "hooks": {
+          "PreToolUse": [{
+            "matcher": "Bash",
+            "hooks": [{
+              "type": "command",
+              "command": "echo Running bash command..."
+            }]
+          }]
+        }
+      }
+    # ... other inputs
+```
+
+The settings support all Claude Code settings options including:
+
+- `model`: Override the default model
+- `env`: Environment variables for the session
+- `permissions`: Tool usage permissions
+- `hooks`: Pre/post tool execution hooks
+- And more...
+
+For a complete list of available settings and their descriptions, see the [Claude Code settings documentation](https://docs.anthropic.com/en/docs/claude-code/settings).
+
+**Notes**:
+
+- The `enableAllProjectMcpServers` setting is always set to `true` by this action to ensure MCP servers work correctly.
+- If both the `model` input parameter and a `model` in settings are provided, the `model` input parameter takes precedence.
+- The `allowed_tools` and `disallowed_tools` input parameters take precedence over `permissions` in settings.
+- In a future version, we may deprecate individual input parameters in favor of using the settings file for all configuration.
+
+## Cloud Providers
+
+You can authenticate with Claude using any of these three methods:
+
+1. Direct Anthropic API (default)
+2. Amazon Bedrock with OIDC authentication
+3. Google Vertex AI with OIDC authentication
+
+For detailed setup instructions for AWS Bedrock and Google Vertex AI, see the [official documentation](https://docs.anthropic.com/en/docs/claude-code/github-actions#using-with-aws-bedrock-%26-google-vertex-ai).
+
+**Note**:
+
+- Bedrock and Vertex use OIDC authentication exclusively
+- AWS Bedrock automatically uses cross-region inference profiles for certain models
+- For cross-region inference profile models, you need to request and be granted access to the Claude models in all regions that the inference profile uses
+
+### Model Configuration
+
+Use provider-specific model names based on your chosen provider:
+
+```yaml
+# For direct Anthropic API (default)
+- uses: anthropics/claude-code-action@beta
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    # ... other inputs
+
+# For Amazon Bedrock with OIDC
+- uses: anthropics/claude-code-action@beta
+  with:
+    model: "anthropic.claude-3-7-sonnet-20250219-beta:0" # Cross-region inference
+    use_bedrock: "true"
+    # ... other inputs
+
+# For Google Vertex AI with OIDC
+- uses: anthropics/claude-code-action@beta
+  with:
+    model: "claude-3-7-sonnet@20250219"
+    use_vertex: "true"
+    # ... other inputs
+```
+
+### OIDC Authentication for Bedrock and Vertex
+
+Both AWS Bedrock and GCP Vertex AI require OIDC authentication.
+
+```yaml
+# For AWS Bedrock with OIDC
+- name: Configure AWS Credentials (OIDC)
+  uses: aws-actions/configure-aws-credentials@v4
+  with:
+    role-to-assume: ${{ secrets.AWS_ROLE_TO_ASSUME }}
+    aws-region: us-west-2
+
+- name: Generate GitHub App token
+  id: app-token
+  uses: actions/create-github-app-token@v2
+  with:
+    app-id: ${{ secrets.APP_ID }}
+    private-key: ${{ secrets.APP_PRIVATE_KEY }}
+
+- uses: anthropics/claude-code-action@beta
+  with:
+    model: "anthropic.claude-3-7-sonnet-20250219-beta:0"
+    use_bedrock: "true"
+    # ... other inputs
+
+  permissions:
+    id-token: write # Required for OIDC
+```
+
+```yaml
+# For GCP Vertex AI with OIDC
+- name: Authenticate to Google Cloud
+  uses: google-github-actions/auth@v2
+  with:
+    workload_identity_provider: ${{ secrets.GCP_WORKLOAD_IDENTITY_PROVIDER }}
+    service_account: ${{ secrets.GCP_SERVICE_ACCOUNT }}
+
+- name: Generate GitHub App token
+  id: app-token
+  uses: actions/create-github-app-token@v2
+  with:
+    app-id: ${{ secrets.APP_ID }}
+    private-key: ${{ secrets.APP_PRIVATE_KEY }}
+
+- uses: anthropics/claude-code-action@beta
+  with:
+    model: "claude-3-7-sonnet@20250219"
+    use_vertex: "true"
+    # ... other inputs
+
+  permissions:
+    id-token: write # Required for OIDC
+```
+
+## Security
+
+### Access Control
+
+- **Repository Access**: The action can only be triggered by users with write access to the repository
+- **No Bot Triggers**: GitHub Apps and bots cannot trigger this action
+- **Token Permissions**: The GitHub app receives only a short-lived token scoped specifically to the repository it's operating in
+- **No Cross-Repository Access**: Each action invocation is limited to the repository where it was triggered
+- **Limited Scope**: The token cannot access other repositories or perform actions beyond the configured permissions
+
+### GitHub App Permissions
+
+The [Claude Code GitHub app](https://github.com/apps/claude) requires these permissions:
+
+- **Pull Requests**: Read and write to create PRs and push changes
+- **Issues**: Read and write to respond to issues
+- **Contents**: Read and write to modify repository files
+
+### Commit Signing
+
+All commits made by Claude through this action are automatically signed with commit signatures. This ensures the authenticity and integrity of commits, providing a verifiable trail of changes made by the action.
+
+### ⚠️ Authentication Protection
+
+**CRITICAL: Never hardcode your Anthropic API key or OAuth token in workflow files!**
+
+Your authentication credentials must always be stored in GitHub secrets to prevent unauthorized access:
+
+```yaml
+# CORRECT ✅
+anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+# OR
+claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+# NEVER DO THIS ❌
+anthropic_api_key: "sk-ant-api03-..." # Exposed and vulnerable!
+claude_code_oauth_token: "oauth_token_..." # Exposed and vulnerable!
+```
+
+### Setting Up GitHub Secrets
+
+1. Go to your repository's Settings
+2. Click on "Secrets and variables" → "Actions"
+3. Click "New repository secret"
+4. For authentication, choose one:
+   - API Key: Name: `ANTHROPIC_API_KEY`, Value: Your Anthropic API key (starting with `sk-ant-`)
+   - OAuth Token: Name: `CLAUDE_CODE_OAUTH_TOKEN`, Value: Your Claude Code OAuth token (Pro and Max users can generate this by running `claude setup-token` locally)
+5. Click "Add secret"
+
+### Best Practices for Authentication
+
+1. ✅ Always use `${{ secrets.ANTHROPIC_API_KEY }}` or `${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}` in workflows
+2. ✅ Never commit API keys or tokens to version control
+3. ✅ Regularly rotate your API keys and tokens
+4. ✅ Use environment secrets for organization-wide access
+5. ❌ Never share API keys or tokens in pull requests or issues
+6. ❌ Avoid logging workflow variables that might contain keys
+
+## Security Best Practices
+
+**⚠️ IMPORTANT: Never commit API keys directly to your repository! Always use GitHub Actions secrets.**
+
+To securely use your Anthropic API key:
+
+1. Add your API key as a repository secret:
+
+   - Go to your repository's Settings
+   - Navigate to "Secrets and variables" → "Actions"
+   - Click "New repository secret"
+   - Name it `ANTHROPIC_API_KEY`
+   - Paste your API key as the value
+
+2. Reference the secret in your workflow:
+   ```yaml
+   anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+   ```
+
+**Never do this:**
+
+```yaml
+# ❌ WRONG - Exposes your API key
+anthropic_api_key: "sk-ant-..."
+```
+
+**Always do this:**
+
+```yaml
+# ✅ CORRECT - Uses GitHub secrets
+anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+This applies to all sensitive values including API keys, access tokens, and credentials.
+We also recommend that you always use short-lived tokens when possible

 ## License

--- a/action.yml
+++ b/action.yml
@@ -172,7 +172,7 @@ runs:
        echo "Base-action dependencies installed"
        cd -
        # Install Claude Code globally
-        bun install -g @anthropic-ai/claude-code@1.0.67
+        bun install -g @anthropic-ai/claude-code@1.0.66

    - name: Setup Network Restrictions
      if: steps.prepare.outputs.contains_trigger == 'true' && inputs.experimental_allowed_domains != ''
@@ -201,11 +201,10 @@ runs:
        INPUT_MCP_CONFIG: ${{ steps.prepare.outputs.mcp_config }}
        INPUT_SETTINGS: ${{ inputs.settings }}
        INPUT_SYSTEM_PROMPT: ""
-        INPUT_APPEND_SYSTEM_PROMPT: ${{ env.APPEND_SYSTEM_PROMPT }}
+        INPUT_APPEND_SYSTEM_PROMPT: ""
        INPUT_TIMEOUT_MINUTES: ${{ inputs.timeout_minutes }}
        INPUT_CLAUDE_ENV: ${{ inputs.claude_env }}
        INPUT_FALLBACK_MODEL: ${{ inputs.fallback_model }}
-        INPUT_EXPERIMENTAL_SLASH_COMMANDS_DIR: ${{ github.action_path }}/slash-commands

        # Model configuration
        ANTHROPIC_MODEL: ${{ inputs.model || inputs.anthropic_model }}
--- a/base-action/action.yml
+++ b/base-action/action.yml
@@ -61,9 +61,6 @@ inputs:
    description: "Timeout in minutes for Claude Code execution"
    required: false
    default: "10"
-  experimental_slash_commands_dir:
-    description: "Experimental: Directory containing slash command files to install"
-    required: false

  # Authentication settings
  anthropic_api_key:
@@ -118,7 +115,7 @@ runs:

    - name: Install Claude Code
      shell: bash
-      run: bun install -g @anthropic-ai/claude-code@1.0.67
+      run: bun install -g @anthropic-ai/claude-code@1.0.66

    - name: Run Claude Code Action
      shell: bash
@@ -146,7 +143,6 @@ runs:
        INPUT_TIMEOUT_MINUTES: ${{ inputs.timeout_minutes }}
        INPUT_CLAUDE_ENV: ${{ inputs.claude_env }}
        INPUT_FALLBACK_MODEL: ${{ inputs.fallback_model }}
-        INPUT_EXPERIMENTAL_SLASH_COMMANDS_DIR: ${{ inputs.experimental_slash_commands_dir }}

        # Provider configuration
        ANTHROPIC_API_KEY: ${{ inputs.anthropic_api_key }}
--- a/base-action/src/index.ts
+++ b/base-action/src/index.ts
@@ -10,11 +10,7 @@ async function run() {
  try {
    validateEnvironmentVariables();

-    await setupClaudeCodeSettings(
-      process.env.INPUT_SETTINGS,
-      undefined, // homeDir
-      process.env.INPUT_EXPERIMENTAL_SLASH_COMMANDS_DIR,
-    );
+    await setupClaudeCodeSettings(process.env.INPUT_SETTINGS);

    const promptConfig = await preparePrompt({
      prompt: process.env.INPUT_PROMPT || "",
--- a/base-action/src/setup-claude-code-settings.ts
+++ b/base-action/src/setup-claude-code-settings.ts
@@ -5,7 +5,6 @@ import { readFile } from "fs/promises";
 export async function setupClaudeCodeSettings(
  settingsInput?: string,
  homeDir?: string,
-  slashCommandsDir?: string,
 ) {
  const home = homeDir ?? homedir();
  const settingsPath = `${home}/.claude/settings.json`;
@@ -66,17 +65,4 @@ export async function setupClaudeCodeSettings(

  await $`echo ${JSON.stringify(settings, null, 2)} > ${settingsPath}`.quiet();
  console.log(`Settings saved successfully`);
-
-  if (slashCommandsDir) {
-    console.log(
-      `Copying slash commands from ${slashCommandsDir} to ${home}/.claude/`,
-    );
-    try {
-      await $`test -d ${slashCommandsDir}`.quiet();
-      await $`cp ${slashCommandsDir}/*.md ${home}/.claude/ 2>/dev/null || true`.quiet();
-      console.log(`Slash commands copied successfully`);
-    } catch (e) {
-      console.log(`Slash commands directory not found or error copying: ${e}`);
-    }
-  }
 }
--- a/base-action/test/setup-claude-code-settings.test.ts
+++ b/base-action/test/setup-claude-code-settings.test.ts
@@ -3,7 +3,7 @@
 import { describe, test, expect, beforeEach, afterEach } from "bun:test";
 import { setupClaudeCodeSettings } from "../src/setup-claude-code-settings";
 import { tmpdir } from "os";
-import { mkdir, writeFile, readFile, rm, readdir } from "fs/promises";
+import { mkdir, writeFile, readFile, rm } from "fs/promises";
 import { join } from "path";

 const testHomeDir = join(
@@ -147,72 +147,4 @@ describe("setupClaudeCodeSettings", () => {
    expect(settings.newKey).toBe("newValue");
    expect(settings.model).toBe("claude-opus-4-20250514");
  });
-
-  test("should copy slash commands to .claude directory when path provided", async () => {
-    const testSlashCommandsDir = join(testHomeDir, "test-slash-commands");
-    await mkdir(testSlashCommandsDir, { recursive: true });
-    await writeFile(
-      join(testSlashCommandsDir, "test-command.md"),
-      "---\ndescription: Test command\n---\nTest content",
-    );
-
-    await setupClaudeCodeSettings(undefined, testHomeDir, testSlashCommandsDir);
-
-    const testCommandPath = join(testHomeDir, ".claude", "test-command.md");
-    const content = await readFile(testCommandPath, "utf-8");
-    expect(content).toContain("Test content");
-  });
-
-  test("should skip slash commands when no directory provided", async () => {
-    await setupClaudeCodeSettings(undefined, testHomeDir);
-
-    const settingsContent = await readFile(settingsPath, "utf-8");
-    const settings = JSON.parse(settingsContent);
-    expect(settings.enableAllProjectMcpServers).toBe(true);
-  });
-
-  test("should handle missing slash commands directory gracefully", async () => {
-    const nonExistentDir = join(testHomeDir, "non-existent");
-
-    await setupClaudeCodeSettings(undefined, testHomeDir, nonExistentDir);
-
-    const settingsContent = await readFile(settingsPath, "utf-8");
-    expect(JSON.parse(settingsContent).enableAllProjectMcpServers).toBe(true);
-  });
-
-  test("should skip non-.md files in slash commands directory", async () => {
-    const testSlashCommandsDir = join(testHomeDir, "test-slash-commands");
-    await mkdir(testSlashCommandsDir, { recursive: true });
-    await writeFile(join(testSlashCommandsDir, "not-markdown.txt"), "ignored");
-    await writeFile(join(testSlashCommandsDir, "valid.md"), "copied");
-    await writeFile(join(testSlashCommandsDir, "another.md"), "also copied");
-
-    await setupClaudeCodeSettings(undefined, testHomeDir, testSlashCommandsDir);
-
-    const copiedFiles = await readdir(join(testHomeDir, ".claude"));
-    expect(copiedFiles).toContain("valid.md");
-    expect(copiedFiles).toContain("another.md");
-    expect(copiedFiles).not.toContain("not-markdown.txt");
-    expect(copiedFiles).toContain("settings.json"); // Settings should also exist
-  });
-
-  test("should handle slash commands path that is a file not directory", async () => {
-    const testFile = join(testHomeDir, "not-a-directory.txt");
-    await writeFile(testFile, "This is a file, not a directory");
-
-    await setupClaudeCodeSettings(undefined, testHomeDir, testFile);
-
-    const settingsContent = await readFile(settingsPath, "utf-8");
-    expect(JSON.parse(settingsContent).enableAllProjectMcpServers).toBe(true);
-  });
-
-  test("should handle empty slash commands directory", async () => {
-    const emptyDir = join(testHomeDir, "empty-slash-commands");
-    await mkdir(emptyDir, { recursive: true });
-
-    await setupClaudeCodeSettings(undefined, testHomeDir, emptyDir);
-
-    const settingsContent = await readFile(settingsPath, "utf-8");
-    expect(JSON.parse(settingsContent).enableAllProjectMcpServers).toBe(true);
-  });
 });
--- a/docs/capabilities-and-limitations.md
+++ b/docs/capabilities-and-limitations.md
@@ -1,33 +0,0 @@
-# Capabilities and Limitations
-
-## What Claude Can Do
-
- **Respond in a Single Comment**: Claude operates by updating a single initial comment with progress and results
- **Answer Questions**: Analyze code and provide explanations
- **Implement Code Changes**: Make simple to moderate code changes based on requests
- **Prepare Pull Requests**: Creates commits on a branch and links back to a prefilled PR creation page
- **Perform Code Reviews**: Analyze PR changes and provide detailed feedback
- **Smart Branch Handling**:
-  - When triggered on an **issue**: Always creates a new branch for the work
-  - When triggered on an **open PR**: Always pushes directly to the existing PR branch
-  - When triggered on a **closed PR**: Creates a new branch since the original is no longer active
- **View GitHub Actions Results**: Can access workflow runs, job logs, and test results on the PR where it's tagged when `actions: read` permission is configured (see [Additional Permissions for CI/CD Integration](./configuration.md#additional-permissions-for-cicd-integration))
-
-## What Claude Cannot Do
-
- **Submit PR Reviews**: Claude cannot submit formal GitHub PR reviews
- **Approve PRs**: For security reasons, Claude cannot approve pull requests
- **Post Multiple Comments**: Claude only acts by updating its initial comment
- **Execute Commands Outside Its Context**: Claude only has access to the repository and PR/issue context it's triggered in
- **Run Arbitrary Bash Commands**: By default, Claude cannot execute Bash commands unless explicitly allowed using the `allowed_tools` configuration
- **Perform Branch Operations**: Cannot merge branches, rebase, or perform other git operations beyond pushing commits
-
-## How It Works
-
-1. **Trigger Detection**: Listens for comments containing the trigger phrase (default: `@claude`) or issue assignment to a specific user
-2. **Context Gathering**: Analyzes the PR/issue, comments, code changes
-3. **Smart Responses**: Either answers questions or implements changes
-4. **Branch Management**: Creates new PRs for human authors, pushes directly for Claude's own PRs
-5. **Communication**: Posts updates at every step to keep you informed
-
-This action is built on top of [`anthropics/claude-code-base-action`](https://github.com/anthropics/claude-code-base-action).
--- a/docs/cloud-providers.md
+++ b/docs/cloud-providers.md
@@ -1,95 +0,0 @@
-# Cloud Providers
-
-You can authenticate with Claude using any of these three methods:
-
-1. Direct Anthropic API (default)
-2. Amazon Bedrock with OIDC authentication
-3. Google Vertex AI with OIDC authentication
-
-For detailed setup instructions for AWS Bedrock and Google Vertex AI, see the [official documentation](https://docs.anthropic.com/en/docs/claude-code/github-actions#using-with-aws-bedrock-%26-google-vertex-ai).
-
-**Note**:
-
- Bedrock and Vertex use OIDC authentication exclusively
- AWS Bedrock automatically uses cross-region inference profiles for certain models
- For cross-region inference profile models, you need to request and be granted access to the Claude models in all regions that the inference profile uses
-
-## Model Configuration
-
-Use provider-specific model names based on your chosen provider:
-
-```yaml
-# For direct Anthropic API (default)
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    # ... other inputs
-
-# For Amazon Bedrock with OIDC
- uses: anthropics/claude-code-action@beta
-  with:
-    model: "anthropic.claude-3-7-sonnet-20250219-beta:0" # Cross-region inference
-    use_bedrock: "true"
-    # ... other inputs
-
-# For Google Vertex AI with OIDC
- uses: anthropics/claude-code-action@beta
-  with:
-    model: "claude-3-7-sonnet@20250219"
-    use_vertex: "true"
-    # ... other inputs
-```
-
-## OIDC Authentication for Bedrock and Vertex
-
-Both AWS Bedrock and GCP Vertex AI require OIDC authentication.
-
-```yaml
-# For AWS Bedrock with OIDC
- name: Configure AWS Credentials (OIDC)
-  uses: aws-actions/configure-aws-credentials@v4
-  with:
-    role-to-assume: ${{ secrets.AWS_ROLE_TO_ASSUME }}
-    aws-region: us-west-2
-
- name: Generate GitHub App token
-  id: app-token
-  uses: actions/create-github-app-token@v2
-  with:
-    app-id: ${{ secrets.APP_ID }}
-    private-key: ${{ secrets.APP_PRIVATE_KEY }}
-
- uses: anthropics/claude-code-action@beta
-  with:
-    model: "anthropic.claude-3-7-sonnet-20250219-beta:0"
-    use_bedrock: "true"
-    # ... other inputs
-
-  permissions:
-    id-token: write # Required for OIDC
-```
-
-```yaml
-# For GCP Vertex AI with OIDC
- name: Authenticate to Google Cloud
-  uses: google-github-actions/auth@v2
-  with:
-    workload_identity_provider: ${{ secrets.GCP_WORKLOAD_IDENTITY_PROVIDER }}
-    service_account: ${{ secrets.GCP_SERVICE_ACCOUNT }}
-
- name: Generate GitHub App token
-  id: app-token
-  uses: actions/create-github-app-token@v2
-  with:
-    app-id: ${{ secrets.APP_ID }}
-    private-key: ${{ secrets.APP_PRIVATE_KEY }}
-
- uses: anthropics/claude-code-action@beta
-  with:
-    model: "claude-3-7-sonnet@20250219"
-    use_vertex: "true"
-    # ... other inputs
-
-  permissions:
-    id-token: write # Required for OIDC
-```
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -1,292 +0,0 @@
-# Advanced Configuration
-
-## Using Custom MCP Configuration
-
-The `mcp_config` input allows you to add custom MCP (Model Context Protocol) servers to extend Claude's capabilities. These servers merge with the built-in GitHub MCP servers.
-
-### Basic Example: Adding a Sequential Thinking Server
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    mcp_config: |
-      {
-        "mcpServers": {
-          "sequential-thinking": {
-            "command": "npx",
-            "args": [
-              "-y",
-              "@modelcontextprotocol/server-sequential-thinking"
-            ]
-          }
-        }
-      }
-    allowed_tools: "mcp__sequential-thinking__sequentialthinking" # Important: Each MCP tool from your server must be listed here, comma-separated
-    # ... other inputs
-```
-
-### Passing Secrets to MCP Servers
-
-For MCP servers that require sensitive information like API keys or tokens, use GitHub Secrets in the environment variables:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    mcp_config: |
-      {
-        "mcpServers": {
-          "custom-api-server": {
-            "command": "npx",
-            "args": ["-y", "@example/api-server"],
-            "env": {
-              "API_KEY": "${{ secrets.CUSTOM_API_KEY }}",
-              "BASE_URL": "https://api.example.com"
-            }
-          }
-        }
-      }
-    # ... other inputs
-```
-
-### Using Python MCP Servers with uv
-
-For Python-based MCP servers managed with `uv`, you need to specify the directory containing your server:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    mcp_config: |
-      {
-        "mcpServers": {
-          "my-python-server": {
-            "type": "stdio",
-            "command": "uv",
-            "args": [
-              "--directory",
-              "${{ github.workspace }}/path/to/server/",
-              "run",
-              "server_file.py"
-            ]
-          }
-        }
-      }
-    allowed_tools: "my-python-server__<tool_name>" # Replace <tool_name> with your server's tool names
-    # ... other inputs
-```
-
-For example, if your Python MCP server is at `mcp_servers/weather.py`, you would use:
-
-```yaml
-"args":
-  ["--directory", "${{ github.workspace }}/mcp_servers/", "run", "weather.py"]
-```
-
-**Important**:
-
- Always use GitHub Secrets (`${{ secrets.SECRET_NAME }}`) for sensitive values like API keys, tokens, or passwords. Never hardcode secrets directly in the workflow file.
- Your custom servers will override any built-in servers with the same name.
-
-## Additional Permissions for CI/CD Integration
-
-The `additional_permissions` input allows Claude to access GitHub Actions workflow information when you grant the necessary permissions. This is particularly useful for analyzing CI/CD failures and debugging workflow issues.
-
-### Enabling GitHub Actions Access
-
-To allow Claude to view workflow run results, job logs, and CI status:
-
-1. **Grant the necessary permission to your GitHub token**:
-
-   - When using the default `GITHUB_TOKEN`, add the `actions: read` permission to your workflow:
-
-   ```yaml
-   permissions:
-     contents: write
-     pull-requests: write
-     issues: write
-     actions: read # Add this line
-   ```
-
-2. **Configure the action with additional permissions**:
-
-   ```yaml
-   - uses: anthropics/claude-code-action@beta
-     with:
-       anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-       additional_permissions: |
-         actions: read
-       # ... other inputs
-   ```
-
-3. **Claude will automatically get access to CI/CD tools**:
-   When you enable `actions: read`, Claude can use the following MCP tools:
-   - `mcp__github_ci__get_ci_status` - View workflow run statuses
-   - `mcp__github_ci__get_workflow_run_details` - Get detailed workflow information
-   - `mcp__github_ci__download_job_log` - Download and analyze job logs
-
-### Example: Debugging Failed CI Runs
-
-```yaml
-name: Claude CI Helper
-on:
-  issue_comment:
-    types: [created]
-
-permissions:
-  contents: write
-  pull-requests: write
-  issues: write
-  actions: read # Required for CI access
-
-jobs:
-  claude-ci-helper:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: anthropics/claude-code-action@beta
-        with:
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          additional_permissions: |
-            actions: read
-          # Now Claude can respond to "@claude why did the CI fail?"
-```
-
-**Important Notes**:
-
- The GitHub token must have the `actions: read` permission in your workflow
- If the permission is missing, Claude will warn you and suggest adding it
- Currently, only `actions: read` is supported, but the format allows for future extensions
-
-## Custom Environment Variables
-
-You can pass custom environment variables to Claude Code execution using the `claude_env` input. This is useful for CI/test setups that require specific environment variables:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    claude_env: |
-      NODE_ENV: test
-      CI: true
-      DATABASE_URL: postgres://test:test@localhost:5432/test_db
-    # ... other inputs
-```
-
-The `claude_env` input accepts YAML format where each line defines a key-value pair. These environment variables will be available to Claude Code during execution, allowing it to run tests, build processes, or other commands that depend on specific environment configurations.
-
-## Limiting Conversation Turns
-
-You can use the `max_turns` parameter to limit the number of back-and-forth exchanges Claude can have during task execution. This is useful for:
-
- Controlling costs by preventing runaway conversations
- Setting time boundaries for automated workflows
- Ensuring predictable behavior in CI/CD pipelines
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    max_turns: "5" # Limit to 5 conversation turns
-    # ... other inputs
-```
-
-When the turn limit is reached, Claude will stop execution gracefully. Choose a value that gives Claude enough turns to complete typical tasks while preventing excessive usage.
-
-## Custom Tools
-
-By default, Claude only has access to:
-
- File operations (reading, committing, editing files, read-only git commands)
- Comment management (creating/updating comments)
- Basic GitHub operations
-
-Claude does **not** have access to execute arbitrary Bash commands by default. If you want Claude to run specific commands (e.g., npm install, npm test), you must explicitly allow them using the `allowed_tools` configuration:
-
-**Note**: If your repository has a `.mcp.json` file in the root directory, Claude will automatically detect and use the MCP server tools defined there. However, these tools still need to be explicitly allowed via the `allowed_tools` configuration.
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    allowed_tools: |
-      Bash(npm install)
-      Bash(npm run test)
-      Edit
-      Replace
-      NotebookEditCell
-    disallowed_tools: |
-      TaskOutput
-      KillTask
-    # ... other inputs
-```
-
-**Note**: The base GitHub tools are always included. Use `allowed_tools` to add additional tools (including specific Bash commands), and `disallowed_tools` to prevent specific tools from being used.
-
-## Custom Model
-
-Use a specific Claude model:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    # model: "claude-3-5-sonnet-20241022"  # Optional: specify a different model
-    # ... other inputs
-```
-
-## Claude Code Settings
-
-You can provide Claude Code settings to customize behavior such as model selection, environment variables, permissions, and hooks. Settings can be provided either as a JSON string or a path to a settings file.
-
-### Option 1: Settings File
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    settings: "path/to/settings.json"
-    # ... other inputs
-```
-
-### Option 2: Inline Settings
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    settings: |
-      {
-        "model": "claude-opus-4-20250514",
-        "env": {
-          "DEBUG": "true",
-          "API_URL": "https://api.example.com"
-        },
-        "permissions": {
-          "allow": ["Bash", "Read"],
-          "deny": ["WebFetch"]
-        },
-        "hooks": {
-          "PreToolUse": [{
-            "matcher": "Bash",
-            "hooks": [{
-              "type": "command",
-              "command": "echo Running bash command..."
-            }]
-          }]
-        }
-      }
-    # ... other inputs
-```
-
-The settings support all Claude Code settings options including:
-
- `model`: Override the default model
- `env`: Environment variables for the session
- `permissions`: Tool usage permissions
- `hooks`: Pre/post tool execution hooks
- And more...
-
-For a complete list of available settings and their descriptions, see the [Claude Code settings documentation](https://docs.anthropic.com/en/docs/claude-code/settings).
-
-**Notes**:
-
- The `enableAllProjectMcpServers` setting is always set to `true` by this action to ensure MCP servers work correctly.
- If both the `model` input parameter and a `model` in settings are provided, the `model` input parameter takes precedence.
- The `allowed_tools` and `disallowed_tools` input parameters take precedence over `permissions` in settings.
- In a future version, we may deprecate individual input parameters in favor of using the settings file for all configuration.
--- a/docs/custom-automations.md
+++ b/docs/custom-automations.md
@@ -1,91 +0,0 @@
-# Custom Automations
-
-These examples show how to configure Claude to act automatically based on GitHub events, without requiring manual @mentions.
-
-## Supported GitHub Events
-
-This action supports the following GitHub events ([learn more GitHub event triggers](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)):
-
- `pull_request` - When PRs are opened or synchronized
- `issue_comment` - When comments are created on issues or PRs
- `pull_request_comment` - When comments are made on PR diffs
- `issues` - When issues are opened or assigned
- `pull_request_review` - When PR reviews are submitted
- `pull_request_review_comment` - When comments are made on PR reviews
- `repository_dispatch` - Custom events triggered via API (coming soon)
- `workflow_dispatch` - Manual workflow triggers (coming soon)
-
-## Automated Documentation Updates
-
-Automatically update documentation when specific files change (see [`examples/claude-pr-path-specific.yml`](../examples/claude-pr-path-specific.yml)):
-
-```yaml
-on:
-  pull_request:
-    paths:
-      - "src/api/**/*.ts"
-
-steps:
-  - uses: anthropics/claude-code-action@beta
-    with:
-      direct_prompt: |
-        Update the API documentation in README.md to reflect
-        the changes made to the API endpoints in this PR.
-```
-
-When API files are modified, Claude automatically updates your README with the latest endpoint documentation and pushes the changes back to the PR, keeping your docs in sync with your code.
-
-## Author-Specific Code Reviews
-
-Automatically review PRs from specific authors or external contributors (see [`examples/claude-review-from-author.yml`](../examples/claude-review-from-author.yml)):
-
-```yaml
-on:
-  pull_request:
-    types: [opened, synchronize]
-
-jobs:
-  review-by-author:
-    if: |
-      github.event.pull_request.user.login == 'developer1' ||
-      github.event.pull_request.user.login == 'external-contributor'
-    steps:
-      - uses: anthropics/claude-code-action@beta
-        with:
-          direct_prompt: |
-            Please provide a thorough review of this pull request.
-            Pay extra attention to coding standards, security practices,
-            and test coverage since this is from an external contributor.
-```
-
-Perfect for automatically reviewing PRs from new team members, external contributors, or specific developers who need extra guidance.
-
-## Custom Prompt Templates
-
-Use `override_prompt` for complete control over Claude's behavior with variable substitution:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    override_prompt: |
-      Analyze PR #$PR_NUMBER in $REPOSITORY for security vulnerabilities.
-
-      Changed files:
-      $CHANGED_FILES
-
-      Focus on:
-      - SQL injection risks
-      - XSS vulnerabilities
-      - Authentication bypasses
-      - Exposed secrets or credentials
-
-      Provide severity ratings (Critical/High/Medium/Low) for any issues found.
-```
-
-The `override_prompt` feature supports these variables:
-
- `$REPOSITORY`, `$PR_NUMBER`, `$ISSUE_NUMBER`
- `$PR_TITLE`, `$ISSUE_TITLE`, `$PR_BODY`, `$ISSUE_BODY`
- `$PR_COMMENTS`, `$ISSUE_COMMENTS`, `$REVIEW_COMMENTS`
- `$CHANGED_FILES`, `$TRIGGER_COMMENT`, `$TRIGGER_USERNAME`
- `$BRANCH_NAME`, `$BASE_BRANCH`, `$EVENT_TYPE`, `$IS_PR`
--- a/docs/experimental.md
+++ b/docs/experimental.md
@@ -1,127 +0,0 @@
-# Experimental Features
-
-**Note:** Experimental features are considered unstable and not supported for production use. They may change or be removed at any time.
-
-## Execution Modes
-
-The action supports three execution modes, each optimized for different use cases:
-
-### Tag Mode (Default)
-
-The traditional implementation mode that responds to @claude mentions, issue assignments, or labels.
-
- **Triggers**: `@claude` mentions, issue assignment, label application
- **Features**: Creates tracking comments with progress checkboxes, full implementation capabilities
- **Use case**: General-purpose code implementation and Q&A
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    # mode: tag is the default
-```
-
-### Agent Mode
-
-**Note: Agent mode is currently in active development and may undergo breaking changes.**
-
-For automation with workflow_dispatch and scheduled events only.
-
- **Triggers**: Only works with `workflow_dispatch` and `schedule` events - does NOT work with PR/issue events
- **Features**: Perfect for scheduled tasks, works with `override_prompt`
- **Use case**: Maintenance tasks, automated reporting, scheduled checks
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    mode: agent
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    override_prompt: |
-      Check for outdated dependencies and create an issue if any are found.
-```
-
-### Experimental Review Mode
-
-**Warning: This is an experimental feature that may change or be removed at any time.**
-
-For automated code reviews on pull requests.
-
- **Triggers**: Pull request events (`opened`, `synchronize`) or `@claude review` comments
- **Features**: Provides detailed code reviews with inline comments and suggestions
- **Use case**: Automated PR reviews, code quality checks
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    mode: experimental-review
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    custom_instructions: |
-      Focus on code quality, security, and best practices.
-```
-
-See [`examples/claude-modes.yml`](../examples/claude-modes.yml) and [`examples/claude-experimental-review-mode.yml`](../examples/claude-experimental-review-mode.yml) for complete examples of each mode.
-
-## Network Restrictions
-
-For enhanced security, you can restrict Claude's network access to specific domains only. This feature is particularly useful for:
-
- Enterprise environments with strict security policies
- Preventing access to external services
- Limiting Claude to only your internal APIs and services
-
-When `experimental_allowed_domains` is set, Claude can only access the domains you explicitly list. You'll need to include the appropriate provider domains based on your authentication method.
-
-### Provider-Specific Examples
-
-#### If using Anthropic API or subscription
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    # Or: claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-    experimental_allowed_domains: |
-      .anthropic.com
-```
-
-#### If using AWS Bedrock
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    use_bedrock: "true"
-    experimental_allowed_domains: |
-      bedrock.*.amazonaws.com
-      bedrock-runtime.*.amazonaws.com
-```
-
-#### If using Google Vertex AI
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    use_vertex: "true"
-    experimental_allowed_domains: |
-      *.googleapis.com
-      vertexai.googleapis.com
-```
-
-### Common GitHub Domains
-
-In addition to your provider domains, you may need to include GitHub-related domains. For GitHub.com users, common domains include:
-
-```yaml
- uses: anthropics/claude-code-action@beta
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    experimental_allowed_domains: |
-      .anthropic.com  # For Anthropic API
-      .github.com
-      .githubusercontent.com
-      ghcr.io
-      .blob.core.windows.net
-```
-
-For GitHub Enterprise users, replace the GitHub.com domains above with your enterprise domains (e.g., `.github.company.com`, `packages.company.com`, etc.).
-
-To determine which domains your workflow needs, you can temporarily run without restrictions and monitor the network requests, or check your GitHub Enterprise configuration for the specific services you use.
--- a/docs/security.md
+++ b/docs/security.md
@@ -1,38 +0,0 @@
-# Security
-
-## Access Control
-
- **Repository Access**: The action can only be triggered by users with write access to the repository
- **No Bot Triggers**: GitHub Apps and bots cannot trigger this action
- **Token Permissions**: The GitHub app receives only a short-lived token scoped specifically to the repository it's operating in
- **No Cross-Repository Access**: Each action invocation is limited to the repository where it was triggered
- **Limited Scope**: The token cannot access other repositories or perform actions beyond the configured permissions
-
-## GitHub App Permissions
-
-The [Claude Code GitHub app](https://github.com/apps/claude) requires these permissions:
-
- **Pull Requests**: Read and write to create PRs and push changes
- **Issues**: Read and write to respond to issues
- **Contents**: Read and write to modify repository files
-
-## Commit Signing
-
-All commits made by Claude through this action are automatically signed with commit signatures. This ensures the authenticity and integrity of commits, providing a verifiable trail of changes made by the action.
-
-## ⚠️ Authentication Protection
-
-**CRITICAL: Never hardcode your Anthropic API key or OAuth token in workflow files!**
-
-Your authentication credentials must always be stored in GitHub secrets to prevent unauthorized access:
-
-```yaml
-# CORRECT ✅
-anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-# OR
-claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-
-# NEVER DO THIS ❌
-anthropic_api_key: "sk-ant-api03-..." # Exposed and vulnerable!
-claude_code_oauth_token: "oauth_token_..." # Exposed and vulnerable!
-```
--- a/docs/setup.md
+++ b/docs/setup.md
@@ -1,146 +0,0 @@
-# Setup Guide
-
-## Manual Setup (Direct API)
-
-**Requirements**: You must be a repository admin to complete these steps.
-
-1. Install the Claude GitHub app to your repository: https://github.com/apps/claude
-2. Add authentication to your repository secrets ([Learn how to use secrets in GitHub Actions](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions)):
-   - Either `ANTHROPIC_API_KEY` for API key authentication
-   - Or `CLAUDE_CODE_OAUTH_TOKEN` for OAuth token authentication (Pro and Max users can generate this by running `claude setup-token` locally)
-3. Copy the workflow file from [`examples/claude.yml`](../examples/claude.yml) into your repository's `.github/workflows/`
-
-## Using a Custom GitHub App
-
-If you prefer not to install the official Claude app, you can create your own GitHub App to use with this action. This gives you complete control over permissions and access.
-
-**When you may want to use a custom GitHub App:**
-
- You need more restrictive permissions than the official app
- Organization policies prevent installing third-party apps
- You're using AWS Bedrock or Google Vertex AI
-
-**Steps to create and use a custom GitHub App:**
-
-1. **Create a new GitHub App:**
-
-   - Go to https://github.com/settings/apps (for personal apps) or your organization's settings
-   - Click "New GitHub App"
-   - Configure the app with these minimum permissions:
-     - **Repository permissions:**
-       - Contents: Read & Write
-       - Issues: Read & Write
-       - Pull requests: Read & Write
-     - **Account permissions:** None required
-   - Set "Where can this GitHub App be installed?" to your preference
-   - Create the app
-
-2. **Generate and download a private key:**
-
-   - After creating the app, scroll down to "Private keys"
-   - Click "Generate a private key"
-   - Download the `.pem` file (keep this secure!)
-
-3. **Install the app on your repository:**
-
-   - Go to the app's settings page
-   - Click "Install App"
-   - Select the repositories where you want to use Claude
-
-4. **Add the app credentials to your repository secrets:**
-
-   - Go to your repository's Settings → Secrets and variables → Actions
-   - Add these secrets:
-     - `APP_ID`: Your GitHub App's ID (found in the app settings)
-     - `APP_PRIVATE_KEY`: The contents of the downloaded `.pem` file
-
-5. **Update your workflow to use the custom app:**
-
-   ```yaml
-   name: Claude with Custom App
-   on:
-     issue_comment:
-       types: [created]
-     # ... other triggers
-
-   jobs:
-     claude-response:
-       runs-on: ubuntu-latest
-       steps:
-         # Generate a token from your custom app
-         - name: Generate GitHub App token
-           id: app-token
-           uses: actions/create-github-app-token@v1
-           with:
-             app-id: ${{ secrets.APP_ID }}
-             private-key: ${{ secrets.APP_PRIVATE_KEY }}
-
-         # Use Claude with your custom app's token
-         - uses: anthropics/claude-code-action@beta
-           with:
-             anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-             github_token: ${{ steps.app-token.outputs.token }}
-             # ... other configuration
-   ```
-
-**Important notes:**
-
- The custom app must have read/write permissions for Issues, Pull Requests, and Contents
- Your app's token will have the exact permissions you configured, nothing more
-
-For more information on creating GitHub Apps, see the [GitHub documentation](https://docs.github.com/en/apps/creating-github-apps).
-
-## Security Best Practices
-
-**⚠️ IMPORTANT: Never commit API keys directly to your repository! Always use GitHub Actions secrets.**
-
-To securely use your Anthropic API key:
-
-1. Add your API key as a repository secret:
-
-   - Go to your repository's Settings
-   - Navigate to "Secrets and variables" → "Actions"
-   - Click "New repository secret"
-   - Name it `ANTHROPIC_API_KEY`
-   - Paste your API key as the value
-
-2. Reference the secret in your workflow:
-   ```yaml
-   anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-   ```
-
-**Never do this:**
-
-```yaml
-# ❌ WRONG - Exposes your API key
-anthropic_api_key: "sk-ant-..."
-```
-
-**Always do this:**
-
-```yaml
-# ✅ CORRECT - Uses GitHub secrets
-anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-This applies to all sensitive values including API keys, access tokens, and credentials.
-We also recommend that you always use short-lived tokens when possible
-
-## Setting Up GitHub Secrets
-
-1. Go to your repository's Settings
-2. Click on "Secrets and variables" → "Actions"
-3. Click "New repository secret"
-4. For authentication, choose one:
-   - API Key: Name: `ANTHROPIC_API_KEY`, Value: Your Anthropic API key (starting with `sk-ant-`)
-   - OAuth Token: Name: `CLAUDE_CODE_OAUTH_TOKEN`, Value: Your Claude Code OAuth token (Pro and Max users can generate this by running `claude setup-token` locally)
-5. Click "Add secret"
-
-### Best Practices for Authentication
-
-1. ✅ Always use `${{ secrets.ANTHROPIC_API_KEY }}` or `${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}` in workflows
-2. ✅ Never commit API keys or tokens to version control
-3. ✅ Regularly rotate your API keys and tokens
-4. ✅ Use environment secrets for organization-wide access
-5. ❌ Never share API keys or tokens in pull requests or issues
-6. ❌ Avoid logging workflow variables that might contain keys
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -1,126 +0,0 @@
-# Usage
-
-Add a workflow file to your repository (e.g., `.github/workflows/claude.yml`):
-
-```yaml
-name: Claude Assistant
-on:
-  issue_comment:
-    types: [created]
-  pull_request_review_comment:
-    types: [created]
-  issues:
-    types: [opened, assigned, labeled]
-  pull_request_review:
-    types: [submitted]
-
-jobs:
-  claude-response:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: anthropics/claude-code-action@beta
-        with:
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          # Or use OAuth token instead:
-          # claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          # Optional: set execution mode (default: tag)
-          # mode: "tag"
-          # Optional: add custom trigger phrase (default: @claude)
-          # trigger_phrase: "/claude"
-          # Optional: add assignee trigger for issues
-          # assignee_trigger: "claude"
-          # Optional: add label trigger for issues
-          # label_trigger: "claude"
-          # Optional: add custom environment variables (YAML format)
-          # claude_env: |
-          #   NODE_ENV: test
-          #   DEBUG: true
-          #   API_URL: https://api.example.com
-          # Optional: limit the number of conversation turns
-          # max_turns: "5"
-          # Optional: grant additional permissions (requires corresponding GitHub token permissions)
-          # additional_permissions: |
-          #   actions: read
-```
-
-## Inputs
-
-| Input                          | Description                                                                                                                           | Required | Default   |
-| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | -------- | --------- |
-| `mode`                         | Execution mode: 'tag' (default - triggered by mentions/assignments), 'agent' (for automation), 'experimental-review' (for PR reviews) | No       | `tag`     |
-| `anthropic_api_key`            | Anthropic API key (required for direct API, not needed for Bedrock/Vertex)                                                            | No\*     | -         |
-| `claude_code_oauth_token`      | Claude Code OAuth token (alternative to anthropic_api_key)                                                                            | No\*     | -         |
-| `direct_prompt`                | Direct prompt for Claude to execute automatically without needing a trigger (for automated workflows)                                 | No       | -         |
-| `override_prompt`              | Complete replacement of Claude's prompt with custom template (supports variable substitution)                                         | No       | -         |
-| `base_branch`                  | The base branch to use for creating new branches (e.g., 'main', 'develop')                                                            | No       | -         |
-| `max_turns`                    | Maximum number of conversation turns Claude can take (limits back-and-forth exchanges)                                                | No       | -         |
-| `timeout_minutes`              | Timeout in minutes for execution                                                                                                      | No       | `30`      |
-| `use_sticky_comment`           | Use just one comment to deliver PR comments (only applies for pull_request event workflows)                                           | No       | `false`   |
-| `github_token`                 | GitHub token for Claude to operate with. **Only include this if you're connecting a custom GitHub app of your own!**                  | No       | -         |
-| `model`                        | Model to use (provider-specific format required for Bedrock/Vertex)                                                                   | No       | -         |
-| `fallback_model`               | Enable automatic fallback to specified model when primary model is unavailable                                                        | No       | -         |
-| `anthropic_model`              | **DEPRECATED**: Use `model` instead. Kept for backward compatibility.                                                                 | No       | -         |
-| `use_bedrock`                  | Use Amazon Bedrock with OIDC authentication instead of direct Anthropic API                                                           | No       | `false`   |
-| `use_vertex`                   | Use Google Vertex AI with OIDC authentication instead of direct Anthropic API                                                         | No       | `false`   |
-| `allowed_tools`                | Additional tools for Claude to use (the base GitHub tools will always be included)                                                    | No       | ""        |
-| `disallowed_tools`             | Tools that Claude should never use                                                                                                    | No       | ""        |
-| `custom_instructions`          | Additional custom instructions to include in the prompt for Claude                                                                    | No       | ""        |
-| `mcp_config`                   | Additional MCP configuration (JSON string) that merges with the built-in GitHub MCP servers                                           | No       | ""        |
-| `assignee_trigger`             | The assignee username that triggers the action (e.g. @claude). Only used for issue assignment                                         | No       | -         |
-| `label_trigger`                | The label name that triggers the action when applied to an issue (e.g. "claude")                                                      | No       | -         |
-| `trigger_phrase`               | The trigger phrase to look for in comments, issue/PR bodies, and issue titles                                                         | No       | `@claude` |
-| `branch_prefix`                | The prefix to use for Claude branches (defaults to 'claude/', use 'claude-' for dash format)                                          | No       | `claude/` |
-| `claude_env`                   | Custom environment variables to pass to Claude Code execution (YAML format)                                                           | No       | ""        |
-| `settings`                     | Claude Code settings as JSON string or path to settings JSON file                                                                     | No       | ""        |
-| `additional_permissions`       | Additional permissions to enable. Currently supports 'actions: read' for viewing workflow results                                     | No       | ""        |
-| `experimental_allowed_domains` | Restrict network access to these domains only (newline-separated).                                                                    | No       | ""        |
-| `use_commit_signing`           | Enable commit signing using GitHub's commit signature verification. When false, Claude uses standard git commands                     | No       | `false`   |
-
-\*Required when using direct Anthropic API (default and when not using Bedrock or Vertex)
-
-> **Note**: This action is currently in beta. Features and APIs may change as we continue to improve the integration.
-
-## Ways to Tag @claude
-
-These examples show how to interact with Claude using comments in PRs and issues. By default, Claude will be triggered anytime you mention `@claude`, but you can customize the exact trigger phrase using the `trigger_phrase` input in the workflow.
-
-Claude will see the full PR context, including any comments.
-
-### Ask Questions
-
-Add a comment to a PR or issue:
-
-```
-@claude What does this function do and how could we improve it?
-```
-
-Claude will analyze the code and provide a detailed explanation with suggestions.
-
-### Request Fixes
-
-Ask Claude to implement specific changes:
-
-```
-@claude Can you add error handling to this function?
-```
-
-### Code Review
-
-Get a thorough review:
-
-```
-@claude Please review this PR and suggest improvements
-```
-
-Claude will analyze the changes and provide feedback.
-
-### Fix Bugs from Screenshots
-
-Upload a screenshot of a bug and ask Claude to fix it:
-
-```
-@claude Here's a screenshot of a bug I'm seeing [upload screenshot]. Can you fix it?
-```
-
-Claude can see and analyze images, making it easy to fix visual bugs or UI issues.
--- a/examples/claude-modes.yml
+++ b/examples/claude-modes.yml
@@ -1,17 +1,13 @@
 name: Claude Mode Examples

 on:
-  # Events for tag mode
+  # Common events for both modes
  issue_comment:
    types: [created]
  issues:
    types: [opened, labeled]
  pull_request:
    types: [opened]
-  # Events for agent mode (only these work with agent mode)
-  workflow_dispatch:
-  schedule:
-    - cron: "0 0 * * 0" # Weekly on Sunday

 jobs:
  # Tag Mode (Default) - Traditional implementation
@@ -32,12 +28,13 @@ jobs:
          # - Creates tracking comments with progress checkboxes
          # - Perfect for: Interactive Q&A, on-demand code changes

-  # Agent Mode - Automation for workflow_dispatch and schedule events
-  agent-mode-scheduled-task:
-    # Only works with workflow_dispatch or schedule events
+  # Agent Mode - Automation without triggers
+  agent-mode-auto-review:
+    # Automatically review every new PR
+    if: github.event_name == 'pull_request' && github.event.action == 'opened'
    runs-on: ubuntu-latest
    permissions:
-      contents: write
+      contents: read
      pull-requests: write
      issues: write
      id-token: write
@@ -47,10 +44,13 @@ jobs:
          mode: agent
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
          override_prompt: |
-            Check for outdated dependencies and security vulnerabilities.
-            Create an issue if any critical problems are found.
+            Review this PR for code quality. Focus on:
+            - Potential bugs or logic errors
+            - Security concerns
+            - Performance issues
+
+            Provide specific, actionable feedback.
          # Agent mode behavior:
-          # - ONLY works with workflow_dispatch and schedule events
-          # - Does NOT work with pull_request, issues, or issue_comment events
-          # - No @claude mention needed for supported events
-          # - Perfect for: scheduled maintenance, manual automation runs
+          # - NO @claude mention needed - runs immediately
+          # - Enables true automation (impossible with tag mode)
+          # - Perfect for: CI/CD integration, automatic reviews, label-based workflows
--- a/src/entrypoints/prepare.ts
+++ b/src/entrypoints/prepare.ts
@@ -81,19 +81,6 @@ async function run() {

    // Set the MCP config output
    core.setOutput("mcp_config", result.mcpConfig);
-
-    // Step 6: Get system prompt from mode if available
-    if (mode.getSystemPrompt) {
-      const modeContext = mode.prepareContext(context, {
-        commentId: result.commentId,
-        baseBranch: result.branchInfo.baseBranch,
-        claudeBranch: result.branchInfo.claudeBranch,
-      });
-      const systemPrompt = mode.getSystemPrompt(modeContext);
-      if (systemPrompt) {
-        core.exportVariable("APPEND_SYSTEM_PROMPT", systemPrompt);
-      }
-    }
  } catch (error) {
    const errorMessage = error instanceof Error ? error.message : String(error);
    core.setFailed(`Prepare step failed with error: ${errorMessage}`);
--- a/src/mcp/install-mcp-server.ts
+++ b/src/mcp/install-mcp-server.ts
@@ -1,6 +1,7 @@
 import * as core from "@actions/core";
 import { GITHUB_API_URL, GITHUB_SERVER_URL } from "../github/api/config";
-import type { ParsedGitHubContext } from "../github/context";
+import type { GitHubContext } from "../github/context";
+import { isEntityContext } from "../github/context";
 import { Octokit } from "@octokit/rest";

 type PrepareConfigParams = {
@@ -12,7 +13,7 @@ type PrepareConfigParams = {
  additionalMcpConfig?: string;
  claudeCommentId?: string;
  allowedTools: string[];
-  context: ParsedGitHubContext;
+  context: GitHubContext;
 };

 async function checkActionsReadPermission(
@@ -115,10 +116,10 @@ export async function prepareMcpConfig(
    const hasActionsReadPermission =
      context.inputs.additionalPermissions.get("actions") === "read";

-    if (context.isPR && hasActionsReadPermission) {
+    if (isEntityContext(context) && context.isPR && hasActionsReadPermission) {
      // Verify the token actually has actions:read permission
      const actuallyHasPermission = await checkActionsReadPermission(
-        process.env.DEFAULT_WORKFLOW_TOKEN || "",
+        process.env.ACTIONS_TOKEN || "",
        owner,
        repo,
      );
@@ -138,10 +139,12 @@ export async function prepareMcpConfig(
        ],
        env: {
          // Use workflow github token, not app token
-          GITHUB_TOKEN: process.env.DEFAULT_WORKFLOW_TOKEN,
+          GITHUB_TOKEN: process.env.ACTIONS_TOKEN,
          REPO_OWNER: owner,
          REPO_NAME: repo,
-          PR_NUMBER: context.entityNumber?.toString() || "",
+          PR_NUMBER: isEntityContext(context)
+            ? context.entityNumber?.toString() || ""
+            : "",
          RUNNER_TEMP: process.env.RUNNER_TEMP || "/tmp",
        },
      };
--- a/src/modes/agent/index.ts
+++ b/src/modes/agent/index.ts
@@ -2,6 +2,7 @@ import * as core from "@actions/core";
 import type { Mode, ModeOptions, ModeResult } from "../types";
 import { isAutomationContext } from "../../github/context";
 import type { PreparedContext } from "../../create-prompt/types";
+import { prepareMcpConfig } from "../../mcp/install-mcp-server";

 /**
 * Agent mode implementation.
@@ -39,7 +40,7 @@ export const agentMode: Mode = {
    return false;
  },

-  async prepare({ context }: ModeOptions): Promise<ModeResult> {
+  async prepare({ context, githubToken }: ModeOptions): Promise<ModeResult> {
    // Agent mode handles automation events (workflow_dispatch, schedule) only

    // Agent mode doesn't need to create prompt files here - handled by createPrompt
@@ -67,26 +68,21 @@ export const agentMode: Mode = {
    core.exportVariable("INPUT_ALLOWED_TOOLS", allowedTools.join(","));
    core.exportVariable("INPUT_DISALLOWED_TOOLS", disallowedTools.join(","));

-    // Agent mode uses a minimal MCP configuration
-    // We don't need comment servers or PR-specific tools for automation
-    const mcpConfig: any = {
-      mcpServers: {},
-    };
-
-    // Add user-provided additional MCP config if any
+    // Get MCP configuration using the same setup as other modes
    const additionalMcpConfig = process.env.MCP_CONFIG || "";
-    if (additionalMcpConfig.trim()) {
-      try {
-        const additional = JSON.parse(additionalMcpConfig);
-        if (additional && typeof additional === "object") {
-          Object.assign(mcpConfig, additional);
-        }
-      } catch (error) {
-        core.warning(`Failed to parse additional MCP config: ${error}`);
-      }
-    }
+    const mcpConfig = await prepareMcpConfig({
+      githubToken,
+      owner: context.repository.owner,
+      repo: context.repository.repo,
+      branch: "", // Agent mode doesn't use branches
+      baseBranch: "",
+      additionalMcpConfig,
+      claudeCommentId: undefined, // Agent mode doesn't track comments
+      allowedTools: [...baseTools, ...context.inputs.allowedTools],
+      context,
+    });

-    core.setOutput("mcp_config", JSON.stringify(mcpConfig));
+    core.setOutput("mcp_config", mcpConfig);

    return {
      commentId: undefined,
@@ -95,7 +91,7 @@ export const agentMode: Mode = {
        currentBranch: "",
        claudeBranch: undefined,
      },
-      mcpConfig: JSON.stringify(mcpConfig),
+      mcpConfig: mcpConfig,
    };
  },

@@ -112,9 +108,4 @@ export const agentMode: Mode = {
    // Minimal fallback - repository is a string in PreparedContext
    return `Repository: ${context.repository}`;
  },
-
-  getSystemPrompt() {
-    // Agent mode doesn't need additional system prompts
-    return undefined;
-  },
 };
--- a/src/modes/review/index.ts
+++ b/src/modes/review/index.ts
@@ -349,10 +349,4 @@ This ensures users get value from the review even before checking individual inl
      mcpConfig,
    };
  },
-
-  getSystemPrompt() {
-    // Review mode doesn't need additional system prompts
-    // The review-specific instructions are included in the main prompt
-    return undefined;
-  },
 };
--- a/src/modes/tag/index.ts
+++ b/src/modes/tag/index.ts
@@ -130,9 +130,4 @@ export const tagMode: Mode = {
  ): string {
    return generateDefaultPrompt(context, githubData, useCommitSigning);
  },
-
-  getSystemPrompt() {
-    // Tag mode doesn't need additional system prompts
-    return undefined;
-  },
 };
--- a/src/modes/types.ts
+++ b/src/modes/types.ts
@@ -73,13 +73,6 @@ export type Mode = {
   * @returns PrepareResult with commentId, branchInfo, and mcpConfig
   */
  prepare(options: ModeOptions): Promise<ModeResult>;
-
-  /**
-   * Returns an optional system prompt to append to Claude's base system prompt.
-   * This allows modes to add mode-specific instructions.
-   * @returns The system prompt string or undefined if no additional prompt is needed
-   */
-  getSystemPrompt?(context: ModeContext): string | undefined;
 };

 // Define types for mode prepare method
--- a/test/install-mcp-server.test.ts
+++ b/test/install-mcp-server.test.ts
@@ -547,8 +547,8 @@ describe("prepareMcpConfig", () => {
  });

  test("should include github_ci server when context.isPR is true and actions:read permission is granted", async () => {
-    const oldEnv = process.env.DEFAULT_WORKFLOW_TOKEN;
-    process.env.DEFAULT_WORKFLOW_TOKEN = "workflow-token";
+    const oldEnv = process.env.ACTIONS_TOKEN;
+    process.env.ACTIONS_TOKEN = "workflow-token";

    const contextWithPermissions = {
      ...mockPRContext,
@@ -575,7 +575,7 @@ describe("prepareMcpConfig", () => {
    expect(parsed.mcpServers.github_ci.env.PR_NUMBER).toBe("456");
    expect(parsed.mcpServers.github_file_ops).toBeDefined();

-    process.env.DEFAULT_WORKFLOW_TOKEN = oldEnv;
+    process.env.ACTIONS_TOKEN = oldEnv;
  });

  test("should not include github_ci server when context.isPR is false", async () => {
@@ -595,8 +595,8 @@ describe("prepareMcpConfig", () => {
  });

  test("should not include github_ci server when actions:read permission is not granted", async () => {
-    const oldTokenEnv = process.env.DEFAULT_WORKFLOW_TOKEN;
-    process.env.DEFAULT_WORKFLOW_TOKEN = "workflow-token";
+    const oldTokenEnv = process.env.ACTIONS_TOKEN;
+    process.env.ACTIONS_TOKEN = "workflow-token";

    const result = await prepareMcpConfig({
      githubToken: "test-token",
@@ -612,12 +612,12 @@ describe("prepareMcpConfig", () => {
    expect(parsed.mcpServers.github_ci).not.toBeDefined();
    expect(parsed.mcpServers.github_file_ops).toBeDefined();

-    process.env.DEFAULT_WORKFLOW_TOKEN = oldTokenEnv;
+    process.env.ACTIONS_TOKEN = oldTokenEnv;
  });

  test("should parse additional_permissions with multiple lines correctly", async () => {
-    const oldTokenEnv = process.env.DEFAULT_WORKFLOW_TOKEN;
-    process.env.DEFAULT_WORKFLOW_TOKEN = "workflow-token";
+    const oldTokenEnv = process.env.ACTIONS_TOKEN;
+    process.env.ACTIONS_TOKEN = "workflow-token";

    const contextWithPermissions = {
      ...mockPRContext,
@@ -644,12 +644,12 @@ describe("prepareMcpConfig", () => {
    expect(parsed.mcpServers.github_ci).toBeDefined();
    expect(parsed.mcpServers.github_ci.env.GITHUB_TOKEN).toBe("workflow-token");

-    process.env.DEFAULT_WORKFLOW_TOKEN = oldTokenEnv;
+    process.env.ACTIONS_TOKEN = oldTokenEnv;
  });

  test("should warn when actions:read is requested but token lacks permission", async () => {
-    const oldTokenEnv = process.env.DEFAULT_WORKFLOW_TOKEN;
-    process.env.DEFAULT_WORKFLOW_TOKEN = "invalid-token";
+    const oldTokenEnv = process.env.ACTIONS_TOKEN;
+    process.env.ACTIONS_TOKEN = "invalid-token";

    const contextWithPermissions = {
      ...mockPRContext,
@@ -677,6 +677,6 @@ describe("prepareMcpConfig", () => {
      ),
    );

-    process.env.DEFAULT_WORKFLOW_TOKEN = oldTokenEnv;
+    process.env.ACTIONS_TOKEN = oldTokenEnv;
  });
 });
Author	SHA1	Message	Date
km-anthropic	340104d9cf	fix: use proper type guards instead of manual property checks Address review feedback by using isEntityContext() type guard instead of checking 'isPR' in context manually. This provides better type safety and uses the existing type guard infrastructure.	2025-08-01 15:43:07 -07:00
km-anthropic	9abdfa8a3a	Merge branch 'main' into km/add-mcp-to-agent Resolved conflict by keeping both MCP server changes and generatePrompt method	2025-08-01 15:38:20 -07:00
km-anthropic	6c5d11c8c3	fix: remove generatePrompt method to match Mode interface Remove the generatePrompt method from agent mode since it's not part of the Mode interface in the current main branch. Also remove unused PreparedContext import.	2025-08-01 14:35:42 -07:00
km-anthropic	106183c4c0	bun format	2025-08-01 14:26:31 -07:00
km-anthropic	7cc3cff20b	feat: add MCP servers to agent mode - Update agent mode to use prepareMcpConfig instead of empty config - Update prepareMcpConfig to accept both ParsedGitHubContext and AutomationContext - Add type guards for context-specific properties (isPR, entityNumber) - This enables bot actors to use full MCP capabilities via workflow_dispatch	2025-08-01 14:26:15 -07:00