Axon Shaft docs

FAQ

Short answers to common questions about Axon Shaft, each linking to the page with the details.

Which AI does it use?

Claude, through the Claude Agent SDK on your runner. You save either a Claude Pro or Max plan's token from claude setup-token, or a Claude Console API key. See Claude tokens.

What does it cost?

Axon Shaft is free on a personal account, and organizations are on a free trial with no price yet. Each run still uses your Claude plan or API credits, and minutes on your GitHub Actions runners. See Plans.

Does my code go to Axon Shaft's servers?

No. The action reads the code on your runner and sends what the model reads only to Anthropic, with your token. The Axon Shaft API gets the pull request's number, title, branch and author, and back from the run what the review posted, the model and the tokens. See Data flow.

How long is my data kept?

Runs for 7 days. The daily usage totals and the audit log for 3 months, and each project's lifetime totals until you remove the project. See How long it's kept.

Does the repo need any secrets?

No. The workflow asks for id-token: write, and the action signs in to the Axon Shaft API with the OIDC token GitHub gives the run. See The workflow file.

Can the action run code from your server?

No. The API sends data: settings, prompt text and checklists. Everything the action runs is in its tagged release. See What runs in CI.

Does it run the pull request's code?

A review and /ask never do. /fix and /axonshaft run the repo's own install, test, lint and build commands in a sandbox, and the push starts the repo's own CI. See /fix.

Are pull requests from forks reviewed?

Yes, on pull_request_target, as the dashboard's workflow runs. The forks setting can make them wait for a maintainer's /review instead. See Forks.

Who can see my Claude token?

No response, error or log shows it, and the dashboard shows only its last four characters. Anyone who can push a workflow to a project's repo can get the token that project uses, so give a project its own token to keep it to that repo. See Claude tokens.

Who can change a project's settings?

The account's admin, and anyone with the Admin or Maintain role on the repo. Write access isn't enough. Other members see the Overview and Runs. See Who can do what.

What happens when I push again?

The review runs again and edits the same summary comment. A finding that already has an inline comment isn't posted twice, and when a push fixes one, its thread is resolved. See How a review runs.

Can I block merging on the review?

Yes. Require Axon Shaft / gates or a checklist's check run, such as Axon Shaft / security, in the branch's protection rule or ruleset. See Check runs.

Can I keep settings in a file in the repo?

No. Settings live on the dashboard. The review does read the repo's guide files, such as CLAUDE.md and CONTRIBUTING.md, from the base branch. See Repo guide files.

Does it work on self-hosted runners?

Reviews and /ask do. /fix and /axonshaft run only on GitHub-hosted runners. See self_hosted_unsupported.

Does it approve or merge pull requests?

No. It posts a comment review and check runs. Merging stays with you and your branch protection rules.

Last updated on