src ▸ task opened 0

Automate GitHub

Turn the repetitive GitHub work you do by hand (open a repo, read issues and PRs) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate GitHub See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
GitHub workflow
  1. 1
    open a repo
  2. 2
    read issues and PRs
  3. 3
    export a list
  4. 4
    run a UI-only admin action

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing GitHub by hand

The GitHub tasks you repeat (open a repo, read issues and PRs, export a list) are exactly the kind of work a computer should do. But GitHub only exposes part of it through an API, and the flow runs behind a login and dynamic pages. GitHub has a strong API, but some org settings, Insights views, and enterprise admin screens are only reachable through the browser UI.

Writ closes that gap. Record the GitHub task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

GitHub tasks Writ can run for you

Each of these is a real GitHub action, captured into a workflow and run on your own account.

{ }open a repo
{ }read issues and PRs
{ }export a list
{ }run a UI-only admin action

Workflows extract structured fields such as repo metadata, stars, open issues, PR status along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your GitHub automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the GitHub task once in a real browser (open a repo, then read issues and PRs) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on GitHub in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch GitHub's own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on GitHub

The reason GitHub is tedious to automate is the same reason most tools can't. Writ handles it.

Writ signs into your own GitHub account through a Persona with 2FA for UI-only actions, or reads public repos with no login.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the GitHub automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the GitHub task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch GitHub for new release or new issue matching a label and fire the automation the instant it happens.
  1. 1
    Build the GitHub workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when GitHub changes. It runs on your own GitHub account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/github/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the GitHub automation too.

watch ▸ changes tracked 06
06
watch

Trigger the GitHub automation on a change

Monitor GitHub for new release, new issue matching a label, star threshold and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your GitHub automation in seconds. Monitor GitHub ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach GitHub even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same GitHub automation is an API and an MCP tool

Automating GitHub for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/github/run and a matching MCP tool, so your code or an AI agent can trigger the GitHub task too.

GitHub API GitHub MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with GitHub

GitHub APICall GitHub as a REST endpoint from your own software.Website to API GitHub MCP toolsExpose GitHub as MCP tools your agent can call.For AI agents Monitor GitHubWatch GitHub and act the instant it changes.Change detection WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating GitHub: questions

How do I automate GitHub?
Record the GitHub task once in the recorder (open a repo, read issues and PRs, export a list) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own GitHub account. It usually takes minutes, not a backend project.
Is it allowed to automate GitHub this way?
Use Writ on your own GitHub account and on public repos you have the right to access. Respect its Terms of Service. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does GitHub automation work behind login and 2FA?
Writ signs into your own GitHub account through a Persona with 2FA for UI-only actions, or reads public repos with no login. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated GitHub session.
Can I run the GitHub automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when GitHub is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate GitHub in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started