Latch Console

Console · GitHub is the backend

Configure the loop in your own repo.

Latch's tunables live in your repository's own Actions variables — not in a Latch account, and not in a workflow file you have to edit. This page reads and writes them straight through the GitHub API from your browser, so it is a convenience over the Settings tab, never a dependency.

Nothing here is required. A fresh install works with no variables set at all — the defaults are the product. And a saved value takes effect on the next workflow run: no commit, no redeploy.

01

Connect

Sign in to GitHub and pick the repository. The token stays in this browser.

Not signed in

Use a fine-grained token instead

Paste a personal access token scoped to the one repository you want to configure. It goes to api.github.com and nowhere else.

How do I get a token?

Fine-grained · recommended

  1. Open github.com/settings/personal-access-tokens/new. The button below is meant to open it with the name and every permission in the table filled in (and the owner too, once you pick a repo below) — double-check them on the form before you generate.
  2. Name it Latch Console and pick an Expiration. When it expires the console simply asks for a new one.
  3. Set Resource owner to the account or organization that owns the repository.
  4. Under Repository access choose Only select repositories and pick the single repo you are configuring.
  5. Under Repository permissions set exactly these. Trim any you would rather not grant — the console will tell you which check stopped working instead of failing silently.
    Create fine-grained token ↗

    One honest gap on this path: a fine-grained token cannot list your GitHub App installations, so the readiness check's reviewer-app row reads “could not check” and points you at github.com/apps/claude to confirm by eye. Every other check works.

    Classic · fastest

    Two scopes: repo and workflow. The second one is not optional — a classic token cannot push a file under .github/workflows/ without it, the same split as the fine-grained Contents/Workflows pair.

    Create classic token ↗

    Confirm repo and workflow are ticked before you generate: treat the preselection as a convenience to check rather than a guarantee, the same as the fine-grained link above. The tradeoff is the reason fine-grained is listed first — a classic token reaches every repository your account can reach, while a fine-grained one is confined to the repositories you picked.

    The token never leaves this browser: it is sent only to api.github.com and stored only in this browser's localStorage. There is no Latch server in this path. Sign out wipes it.

    02

    Install

    Put the two workflows and a starter policy in the repo. Two ways; pick either.

    Unknown

    Open the integration PR

    Creates the latch/install branch, commits the three files fetched fresh from this repo's canonical templates, and opens a pull request. Latch does not merge it — you do.

      Committing under .github/workflows/ needs a token with workflow write access. If yours cannot, use the agent instructions instead — same result, done locally.

      Agent instructions

      Hand this to your own coding agent (or run it yourself). It covers the steps this page cannot do for you: the GitHub App install and the provider secret.

      Sign in and choose a repository to generate the instructions.
      03

      Readiness

      Everything that has to be true for the loop to actually turn — checked, not assumed.

      Not run

      04

      Config

      The loop's tunables, as they are stored: this repo's Actions variables.

      Not loaded