Setup
Connections and limits.
View-only. On the working desk, this page holds the safety switches, the Claude connection test and the GitHub token. Here they are shown as they stand, and nothing can be changed.
What Patch may do
Claude
On the working desk, Patch and Pitch call the Claude Code program signed in on its owner's computer. So they use that Claude plan and never an API key. They stop calling Claude once plan usage reaches 40% of the 5-hour or the weekly limit, and they do not call at all when the usage cannot be read.
Each call is stripped down: no tools, no project files, a short system prompt. In the first live test on the owner's machine, on 4 October 2026, reading the usage cost nothing and a stripped-down call took 1,712 tokens.
The scheduled check that keeps this site up to date never calls Claude. It uses rules and templates only, so what it suggests is limited to what those can write: licenses, .gitignore files, CI workflows and the plain version of a post.
GitHub
What a token allows on the working desk
The owner can give Patch a fine-grained token, starting with read-only access. It is kept in a file on the owner's machine, never sent to a browser and never sent to Claude.
| Tier | Repository permissions | Patch can |
|---|---|---|
1. Read Start here | Contents, Issues, Pull requests, Actions: Read-only | Audit and draft everything, private repositories included |
2. Pull requests When you trust it | Contents and Pull requests: Read and write. Workflows: Read and write, to add CI files | Open housekeeping pull requests for you to merge |
3. Repository details Optional | Administration: Read and write | Set descriptions, website links and topics |
Whatever the token allows, nothing is written without the owner's approval, and dry-run rehearses a change instead of making it.