
Link a GitHub repository and Productlane reads it once to write an agent-only article for every screen your customers can reach, naming its buttons, fields, and settings. The Productlane Agent answers customers from those articles. Pull requests and source files also become context for AI drafts, so drafts reflect what you actually shipped.
Settings > Integrations > GitHub.
Go to Settings > Integrations > GitHub.
Click Install GitHub App and complete the installation on your GitHub organization. If your org requires admin approval, the request goes to an admin and the page connects on its own once approved.
Pick a repository under Linked repository. When the install granted access to a single repository, it is linked for you.
The linked repository saves as soon as you pick it.
Once a repository is linked, click Map now to have Productlane read your front end and write the agent-only articles. Run it again later with Re-map after you ship changes; the settings page shows when the product was last mapped.
A map costs AI spend, so it never runs automatically after the first time. Re-map when your customer-facing screens change enough that the agent's answers would be out of date.
The agent your customers talk to has no connection to GitHub. It cannot read a file, search your repository, or open a pull request. It answers from help center articles, and from nothing else.
Productlane reads, never writes. Every call it makes to your repository is a read.
One repository, the one you pick. Nothing else in your organization is reachable.
Customer-facing screens only. Admin panels, internal dashboards, and staff tooling stay out of the map.
A screen holding credentials, keys, or another customer's data is skipped, never summarized.
One repository at a time.
The agent-only articles sit outside your public docs site, in Product reference. Customers never see the page an answer came from.
Uninstalling revokes the App's access to every repository, not only the linked one. To come back, install the App again.