Paste one Tripwire setup link into an agent running in a repository checkout. The agent identifies the GitHub repository, opens the existing Tripwire browser authorization flow when it needs a session, and resumes setup after approval.
In-development guide · Boat reference
- Reuse the installed MCP client's authorization or the CLI device grant. The agent checks the signed-in account and exact repository before making changes.
- Treat GitHub App installation as a separate browser step when the repository is missing. Verify that the intended repository becomes visible after approval.
- Preserve existing rules, propose a starting set, and wait for confirmation before saving rules or enabling the gate.
- Handle expired or denied approval and wrong-account recovery. Resume from verified state after interruptions.
- Exercise a clean checkout through browser approval and resumed setup against an isolated preview. Cover the signed-in path and interruption recovery before publishing the link.
Staging verified the first-run CLI browser approval and same-session resume. After approval, the agent verified the account and org, matched the checkout to Boring-Software-Inc/scratch, and read its installed rules and the catalog. A fresh GitHub App installation and rule or gate writes remain acceptance cases for a disposable repository.