Authenticate the installation
A GitHub App installation provides a clearer repository boundary than a pasted personal token. Runovio connects one installation per private workspace and stores durable, non-secret installation metadata. Short-lived installation tokens are created server-side, narrowed when supported, used in memory, and never persisted.
Repository selection and installation removal are managed on GitHub. Runovio synchronizes a safe projection of accessible repositories; removing access marks a repository inaccessible without rewriting historical agent versions or runs.
Bind scope server-side
The model must not choose owner names, repositories, credentials, arbitrary URLs, pull request head SHAs, or workflow job IDs. A published agent version pins one integration, one accessible repository, and specific allowlisted tool IDs. PR and CI identifiers come from validated run input and trusted execution context.
Every tool has a strict schema, GET-only transport, timeout, item limits, and byte budgets. PR Risk Reviewer may receive bounded, redacted patch excerpts already present in GitHub's list-files response. CI Failure Analyst can use at most one bounded failed-job log excerpt under strict redirect validation, and that raw text remains ephemeral.
Repository text is untrusted evidence. Prompt instructions reinforce that boundary, while code independently enforces tool identity, repository scope, permissions, call counts, and output size.
Read-only means no actions
Runovio requests read access to Metadata, Contents, Pull requests, Actions, Checks, and Commit statuses. It cannot comment on a pull request, submit a review, merge, change a file, dispatch or rerun a workflow, or modify repository settings. Engineering Daily, PR Risk Reviewer, and CI Failure Analyst produce information for a person to review.
This narrower contract makes claims testable. “Read-only” is not merely a user-interface promise; it is reflected in GitHub App permissions, the internal registry, HTTP method constraints, and the absence of write tools.
Follow the GitHub App guide, explore the GitHub feature, or review the PR Risk Reviewer template.