GitHub
How to install Kwern's GitHub App, which files it reads at a commit, and why every fix it proposes arrives as a pull request.
What you need
A repository you can install a GitHub App on. The repository should be the one that actually serves the site, because that is where a site fix has to land.
Connect it
Open Settings · Add an account and press Connect GitHub. GitHub asks you to install Kwern's App and to pick the repositories it may see. Kwern stores the installation id and nothing else: every call mints a fresh token from it, and you revoke the whole thing from your GitHub settings in one click.
A personal access token would have carried everything you can see. The App carries what you picked.
Then open the product's Apps page, press Choose what Kwern reads and choose the GitHub repository. You can add a root path inside it, so one repository can back several products.
What Kwern reads
A repo snapshot pinned to one commit of the default branch:
- the files that describe the product: README, docs, changelog, store metadata, translations and pricing
- the open issues
- the latest releases
Secrets and binaries are never read. The paths are a curated list, not the whole tree.
What Kwern can change
One thing: a pull request. A branch cut from the head of the default branch, one commit carrying the change, and a pull request left open for you.
Merges happen on GitHub, never in Kwern. A proposal's pull request is never merged automatically; you read it, change it and merge it like any other.
Two things arrive that way: a site fix from an SEO or GEO recommendation, and a listing change that belongs in a file of the repository rather than in the App Store itself.
The agents that use it
The SEO agent and the GEO agent both need it. Both fix pages, and a page is fixed by a pull request on the repository that serves it: without one they audit and have nothing to propose.
When it breaks
Uninstalling the App marks the account as needing attention and pauses the agents that depend on it. Recommendations only exist while a repository backs the product, and go with it.