SENTARYN Free on GitHub

Install and configure Sentaryn Free

1. Install the Sentaryn GitHub App using Install Sentaryn.
2. Select repository access through GitHub for the repository you want Sentaryn to observe.
3. Complete Sentaryn setup: verify the GitHub installation if prompted, choose an available repository, review Sentaryn Free, and select Activate Sentaryn Free.
4. Continue using your normal AI coding workflow.
5. Review the Shadow decision in your GitHub workflow.

Select the repository

GitHub repository access and Sentaryn repository configuration are separate steps. In Sentaryn setup, choose from the repositories supplied by the verified GitHub installation context, then activate Sentaryn Free for the selected repository.

• If prompted, use Verify GitHub installation before choosing a repository.
• If GitHub verification fails or no installation session is available, return to the GitHub App installation/setup flow.
• If activation fails, review the setup error before retrying.

Set up Sentaryn Free →

What Sentaryn Free evaluates

Requested → Authorized → Actual → Evidence → Decision

• Requested: What did the task ask?
• Authorized: What was the agent allowed to change?
• Actual: What actually changed?
• Evidence: What evidence is available for the evaluation?
• Decision: What did Shadow find?

These concepts are related but distinct. A request describes the task; authorization defines what may change. The actual diff may exceed that scope. Available evidence supports the evaluation, and the decision reports its findings.

Where to review the result

For each configured repository, Sentaryn Free evaluates AI-generated changes against task authority. Review the Shadow decision in your GitHub workflow, considering the requested task, authorized scope, actual change, and available evidence.

Sentaryn Free publishes informational GitHub checks. Sentaryn does not configure branch protection or make its check required. If you choose to require the Sentaryn check in GitHub, a missing result can affect merge eligibility. Shadow decisions are not enforced and do not replace code review, tests, or security scanners.

Passing tests can show that code works. They do not prove that an AI agent was authorized to make every change in the diff.

If Shadow reports scope expansion, compare the flagged change with the task’s authority before deciding how to proceed through your existing review process.

Fix authentication timeout

This example illustrates the authority question; it is not a customer result.

• Requested: Fix authentication timeout.
• Authorized: src/auth/** and tests/auth/**.
• Actual: src/auth/session.py, tests/auth/test_session.py, and .github/workflows/deploy.yml.
• Evidence: Tests may pass while the diff still exceeds its authorized scope.
• Decision: Shadow can report scope expansion without enforcing the decision; the GitHub check conclusion is neutral.

The deployment workflow file is outside this task’s authorized scope. Passing tests do not authorize that extra change.

Current Sentaryn Free boundaries

• Observation/evaluation only.
• Sentaryn does not configure merge protection.
• No decision enforcement.
• Keep existing code review, CI, tests, and security checks.
• Treat Sentaryn Free as an additional authority signal.

Review security boundaries →

Installation, setup, and contact

• Install Sentaryn — GitHub App installation.
• Setup — repository configuration.
• Security — security boundaries.
• Pricing — offer information.
• Contact Sentaryn — existing early-access form.

If you need help, describe the setup step or Shadow result you are trying to understand through the existing contact form. Do not include credentials or secrets.

Uninstall the GitHub App

You can remove Sentaryn’s GitHub access by uninstalling the GitHub App from the relevant GitHub installation.

Use GitHub’s App installation settings to manage the installation. Removing GitHub access is separate from questions about retained data; review the Privacy Policy for privacy contact information.