GitHub
The repository is where a site fix has to land. Kwern reads the files that describe the product and opens a pull request for every fix, which you read, change and merge on GitHub like any other.
What Kwern reads
What Kwern can change, once you approve
How the connection is made
What Kwern never does
Questions
The SEO and GEO agents. 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.
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 curated set of paths at one commit: README, docs, changelog, store metadata, translations and pricing. Secrets and binaries are never read.
A GitHub App install is scoped to the repositories you pick and is revoked from your GitHub settings in one click. A personal token would have carried everything you can see.
Yes. Bind the repository with a root path and each product reads its own folder.
The agents that use it
These agents cannot run without it. Without the connection each one says what to connect and does not run.
Someone is asking for what you built today.
On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.