GitHub automation with an AI agent on your own box.
Cronable reacts to what happens in a repository and acts on it: open an issue, leave a comment, kick off an Actions workflow. Because it runs on your machine, the step in between can be Claude Code or Codex working in a real checkout of your code.
A GitHub workflow on the canvas
Each card is one job. A wire means the next job runs when the one before it succeeds, or when it fails.
Open an issue
GitHub·Idle
After Diagnose the failure (succeeded)
Diagnose the failure
Claude (CLI)·Running
After CI run finished (succeeded)
2m 40s
CI run finished
GitHub webhook·Succeeded
On GitHub event
3 min ago
CI run finished
GitHub webhook·Succeeded
On GitHub event
3 min ago
Diagnose the failure
Claude (CLI)·Running
After CI run finished (succeeded)
2m 40s
Open an issue
GitHub·Idle
After Diagnose the failure (succeeded)
“When a GitHub Actions run fails on main, have Claude fetch the run’s logs with gh, find the likely cause in my checkout and open an issue with the fix.”
Every GitHub step Cronable ships
Actions
Steps a workflow can take in GitHub.List issues
Return a repository’s open, closed or all issues, paged.
Get an issue
Read one issue by number.
Create an issue
Open an issue with a title and body written by an earlier step.
Add a comment
Post a comment on an issue.
Dispatch a workflow
Start a GitHub Actions workflow on a branch or tag.
Check the token
Read the account the token belongs to.
Custom request
Any other GitHub REST endpoint, with your own method, path and body.
Triggers
What starts a GitHub workflow.Repository webhook events
Set the owner and repository and Cronable registers the webhook for you: pushes, pull requests, issues, releases and Actions workflow runs. The event type and full payload reach the next step, and every delivery’s signature is verified.
GitHub workflows worth automating first
CI failure triage
When an Actions run fails, a Claude Code agent fetches the run’s logs (for example with gh), works out the likely cause in your local checkout and opens an issue with what it found.
Morning issue digest
List yesterday’s new issues each morning and let an AI step group them by area before your standup.
Release announcements
A published release fires the trigger, an AI step writes friendly notes from the payload, and Discord or Slack posts them.
Scheduled workflow runs
Dispatch an Actions workflow from a Cronable schedule or after a local job succeeds, such as a nightly data export that has to land before the build.
How you connect
Connecting GitHub
GitHub connects with a personal access token you paste. No GitHub App to install.
- 1Create a personal access token with access to the repositories the workflow uses, and store it as a bearer token credential.
- 2For the trigger, the token also needs permission to manage repository webhooks, so Cronable can register and later remove the hook.
- 3Webhooks reach your machine through Cronable’s relay, with no port opened, from the Basic plan up. Plain git work, such as commit and push, uses the built-in Git job type and the git credentials already on your machine.
Your GitHub automation, on your own machine
Runs on your own machine
Install Cronable as a Mac or Windows app, or on a server you own. Your GitHub jobs, secrets and run history stay on that machine by default.
Built from one sentence
Describe the workflow in plain English and the built-in assistant builds the jobs, the schedule and the failure handling for you to review on the canvas. On every plan, including Free.
Unlimited runs
Plans count the jobs you define, not how often they fire. A job that touches GitHub every hour costs the same as one that runs once a month.
Credentials encrypted locally
Keys and tokens are AES-256-GCM encrypted in a local database, referenced from jobs by name and masked out of logs and run output.
GitHub automation, answered
Can Cronable react to GitHub pushes and pull requests?
Yes. The GitHub trigger registers a repository webhook for pushes, pull requests, issues, releases and workflow runs, and starts a run for each event with the payload available to the next step.
Can an AI agent work on my repository?
Yes. Claude Code and Codex run as job types on your own machine, inside the working directory you choose, so they can read the code, run commands and report back. Claude Code runs with the access of the user Cronable runs as, and Codex runs in the sandbox mode you pick, so give them work you would trust a shell with.
What token does GitHub need?
A personal access token with access to your repositories. To let the trigger register its own webhook, the token also needs permission to manage repository hooks.
Where is the GitHub token stored?
Encrypted in the credential store on your machine. The webhook’s signing secret is generated and stored there too, and both are masked in logs.
Can it start a GitHub Actions workflow?
Yes. Dispatch a workflow takes the workflow file or ID and the branch or tag to run it on.
Anything you do twice in GitHub is cronable.
The CI log you read every morning before coffee can read itself.