GitHub Actions running Claude Code

A hosted service that is always on. A schedule event can be delayed at busy times, most of all at the start of each hour, and under very high load some queued scheduled jobs are dropped, so schedule off the hour and give scheduled triggers a generous wait. The shortest schedule is every five minutes, and a public repository's schedules are turned off after 60 days without activity. https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule

The workflow file's steps run as code on the runner, the same way every time. A step that runs claude-code-action is where an agent decides. https://docs.github.com/en/actions/concepts/runners/github-hosted-runners https://code.claude.com/docs/en/github-actions

Claude Code runs on the runner with the checked-out repository and whatever secrets the job hands it. On Amazon Bedrock or Google Cloud instead of the Claude API, list that company here. https://code.claude.com/docs/en/github-actions https://code.claude.com/docs/en/github-actions-cloud-providers

Each job gets a new virtual machine with ordinary internet access, so the workflow's own code can call any model company's API with a key from the repository's secrets. https://docs.github.com/en/actions/concepts/runners/github-hosted-runners

The runner holds the repository the job checks out, and keeps changes only by committing and pushing them. So it holds notes only when the notes are kept in that repository. https://docs.github.com/en/actions/concepts/runners/github-hosted-runners