How to Run Claude Code from GitHub Actions with an Ace Data Cloud Proxy

How to Run Claude Code from GitHub Actions with an Ace Data Cloud Proxy

Code review bots are useful only when they can actually see the repository, respond in the right GitHub thread, and run with the same constraints as the rest of your CI pipeline. The Claude Code GitHub Actions setup gives you that workflow: mention @claude in an Issue, pull request, review, or comment, and a GitHub Actions job can run Claude Code against the repository.

This guide walks through the practical wiring described in the Ace Data Cloud documentation: a GitHub secret named ANTHROPIC_AUTH_TOKEN, a local proxy on the runner at 127.0.0.1:8788, and anthropics/claude-code-action@v1 configured with real claude_args.

What you can do

With this workflow in place, repository collaborators can ask Claude Code to work from normal GitHub surfaces instead of switching to a separate terminal session. The documented triggers cover:

  • issue_comment events when a new comment contains @claude.
  • pull_request_review_comment events when a PR review comment contains @claude.
  • pull_request_review submissions where the review body contains @claude.
  • issues events where either the issue title or body contains @claude.

The same job can then read code, write changes, comment, or submit pull-request updates through the GitHub bot context, depending on the permissions and arguments you give the action.

How it works

The important detail is authentication. The Ace Data Cloud gateway expects requests authenticated as Authorization: Bearer <token>. The official anthropics/claude-code-action@v1, however, uses the Anthropic SDK path where requests are sent with x-api-key. The documented solution is to start a small local HTTP proxy inside the GitHub runner.

The data path is straightforward: GitHub sees @claude, starts the workflow, sets ANTHROPIC_BASE_URL to http://127.0.0.1:8788, and runs Claude Code. Requests hit the local proxy first. The proxy drops x-api-key, adds Authorization: Bearer <token>, and forwards the request to https://api.acedata.cloud.

1. Store the Ace Data Cloud token as a GitHub secret

In your repository, open Settings → Secrets and variables → Actions, create a new repository secret, and name it exactly ANTHROPIC_AUTH_TOKEN. The workflow reads this value through ${ secrets.ANTHROPIC_AUTH_TOKEN }.

If you prefer the GitHub CLI, the documentation recommends setting the value directly with --body rather than piping from stdin incorrectly:

gh secret set ANTHROPIC_AUTH_TOKEN --repo <org>/<repo> --body '<your-real-token>'

Do not print the token itself in logs. If you need to verify that the secret exists during troubleshooting, print only a derived property such as its length.

2. Add the workflow

Create .github/workflows/claude.yml. The core fields to preserve are the event list, the if: guard that checks for @claude, the write permissions, ANTHROPIC_BASE_URL, and the non-empty placeholder anthropic_api_key.

name: Claude Code

on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  issues:
    types: [opened, assigned]
  pull_request_review:
    types: [submitted]

jobs:
  claude:
    if: |
      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
    runs-on: ubuntu-latest
    permissions:
      contents: write
      pull-requests: write
      issues: write
      id-token: write
    env:
      ANTHROPIC_BASE_URL: http://127.0.0.1:8788
      CLAUDE_CODE_AUTO_COMPACT_WINDOW: '850000'
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Start AceData Cloud proxy (x-api-key to Bearer)
        env:
          UPSTREAM: https://api.acedata.cloud
          ACEDATA_TOKEN: ${{ secrets.ANTHROPIC_AUTH_TOKEN }}
        run: |
          # Start the documented local proxy on 127.0.0.1:8788.
          # It removes x-api-key and forwards with Authorization: Bearer <token>.
          python3 /tmp/proxy.py &

      - name: Run Claude Code via AceData Cloud
        uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: dummy-not-used
          github_token: ${{ secrets.GITHUB_TOKEN }}
          claude_args: |
            --model claude-opus-4-8
          show_full_output: 'true'

The placeholder value dummy-not-used is intentional. The action requires a non-empty anthropic_api_key or equivalent credential before it starts, but the actual upstream authentication is performed by the local proxy using ANTHROPIC_AUTH_TOKEN.

3. Bridge x-api-key to Authorization: Bearer

The proxy step is the only translation layer. It listens at 127.0.0.1:8788, receives the Anthropic SDK-style request, removes x-api-key, and forwards to https://api.acedata.cloud with Authorization: Bearer <token>. Keep the proxy local to the runner and source the token from ${ secrets.ANTHROPIC_AUTH_TOKEN }.

This is why ANTHROPIC_BASE_URL points to http://127.0.0.1:8788 instead of the upstream directly: Claude Code talks to the local adapter, while the adapter talks to Ace Data Cloud.

4. Choose a model and constrain the run

The documented example uses --model claude-opus-4-8. The same claude_args block can also pass supported Claude Code options such as --max-turns, --allowed-tools, and --mcp-config.

claude_args: |
  --model claude-sonnet-4-5
  --max-turns 8
  --allowed-tools Bash,Read,Edit
  --mcp-config .claude/mcp.json

CLAUDE_CODE_AUTO_COMPACT_WINDOW: '850000' sets the automatic compression trigger window to about 850,000 tokens. Keep it quoted in YAML so the environment variable is treated as a string. This value reserves space for tool results and final responses; it does not change the model context limit.

Triggering and debugging

To test the setup, open a new issue and include a short instruction such as @claude Reply with: OK.. If everything is connected, the Claude Code workflow appears under the repository Actions tab and the github-actions bot replies in the thread.

If nothing happens, first check that the event type is covered by the workflow if: condition. Then confirm that .github/workflows/claude.yml exists on the branch where Actions run, repository Actions are enabled, and the proxy step started successfully. For a 401, inspect whether the secret was set to the wrong value, especially the accidental literal - case described in the documentation.

Wrap-up

This pattern is small but useful: GitHub keeps the collaboration surface, Claude Code keeps the agent workflow, and the runner-local proxy adapts the authentication header expected by Ace Data Cloud. Once the workflow is committed, the day-to-day interface is just a normal GitHub mention.

Read the full source documentation here: Claude Code GitHub Actions Integration Guide.

Comments

Post a Comment

Popular posts from this blog

Artistic QR Code API Integration Guidance

Image
Artistic QR code is an innovative technological product that combines QR codes with beautiful background images, creating practical and visually appealing works. They not only possess the functionality of traditional QR codes, allowing quick scanning and recognition by smart devices, but also incorporate artistic elements to enhance visual appeal and brand recognition. Some artistic QR codes are even generated by artificial intelligence, fully leveraging modern technology to demonstrate unparalleled innovation and uniqueness. This makes artistic QR codes widely applicable in areas such as brand marketing and advertising. In simple terms, artistic QR codes are the perfect combination of QR code scanning and artistic aesthetics. They not only provide the function of information transmission, but also enhance the user's visual experience, making each scan a delightful artistic enjoyment. Overview of Artworks Let's take a look at a few QR code works: How are they? These are ar...
Read more
Image
Nexior is an open-source project on GitHub that allows us to deploy our AI application site with one click, including AI Q&A, Midjourney drawing, knowledge base Q&A, artistic QR codes, and more. There is no need to develop AI systems, purchase AI accounts, worry about API support, or configure payment systems. It comes with zero startup costs and allows you to earn income through AI without risk. This article will introduce the deployment process of the Nexior project on Vercel. Without any programming skills, you can deploy your AI site in a few minutes and easily generate revenue. Preparation First, open the Nexior GitHub repository at: https://github.com/AceDataCloud/Nexior , then register or log in to your GitHub account. Click Fork to clone the code to your local repository, as shown below: After completing the Fork, we will get our personal repository, as shown below: In this example, the account is Germey, so we can see that we have Forked to the Germey user, wit...
Read more

How to Configure Claude Code with CC Switch and Ace Data Cloud

Image
If you use Claude Code across a terminal, VS Code, or remote development setup, the awkward part is often not the model itself but the configuration: where should requests go, where should the token live, and how do you switch providers without editing files by hand? This guide walks through a practical setup using CC Switch as the graphical configuration manager and Ace Data Cloud as the Anthropic-compatible base URL. The goal is simple: configure Claude Code once, verify the active endpoint, and keep the setup easy to change later. What you can do With the setup described in the Ace Data Cloud documentation, you can: Manage Claude Code provider configuration through a desktop UI instead of manually editing settings.json . Store an Ace Data Cloud provider with ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN . Switch the active Claude Code provider from CC Switch without rewriting your configuration every time. Use the same provider configuration from the terminal an...
Read more