TINY(1)General Commands ManualTINY(1)

Facts checked Nov 11, 2026 · all comparisons

tiny vs the Claude Code GitHub Action

The Claude Code GitHub Action runs Claude Code inside a workflow job. Mention @claude on an issue or pull request, or trigger it from any GitHub event, and Claude works in the job, pushes commits and replies in a comment. It's official, and setup takes a few minutes with /install-github-app.

tiny's GitHub loop does the same job from a different place: label an issue tiny, a session on your Kubernetes cluster picks it up, and a pull request comes back.

Side by side

Claude Code GitHub Action tiny
trigger @claude mention, or any GitHub event with a prompt a labelled issue, or anything that pipes text into tiny deliver
where it runs a workflow job, on GitHub-hosted runners by default a pod on your Kubernetes; an in-cluster runner only delivers the issue
lifetime one job per request, bounded by your workflow timeout a long-lived session that keeps its workspace and transcript
GitHub access during the run the job holds a token with contents, issues and pull-request write access the agent pod holds no GitHub token
how work lands Claude pushes commits from the job the agent writes a git bundle; a separate short-lived job pushes it and opens the PR
when it needs a decision it replies on the issue the question lands as an issue comment with the tiny answer command, run with your credentials
watching it work the comment it updates, and the job log attach to the real terminal mid-task
agents Claude Code Claude Code and Codex
what you pay Actions minutes plus tokens or your subscription your cluster plus tokens or your subscription

Where the Action is the better choice

Where tiny fits

The two aren't exclusive. Plenty of teams would use the Action for quick reviews and tiny for the work that takes an afternoon.

Sources: Anthropic's GitHub Actions documentation, checked on the date above. Tell us on GitHub if a row has gone stale.