Configuration

Everything you can tune from the dashboard — which repos Senix watches, the tokens your IDEs use, and how to remove Senix entirely.

Managing connected repos

Every repository connected through the GitHub App has a toggle on your dashboard. Switching a repo off pauses analysis for it without uninstalling the app — useful for repos full of generated code or noisy fixtures. Switching it back on resumes analysis on the next pull request.

Managing MCP tokens

Go to Dashboard → MCP tokens to manage the tokens your IDEs use.

1. View — every token shows its name, creation date, and last-used date.
2. Revoke — revoking a token immediately stops it from authenticating with the MCP server. The row is kept as an audit record.
3. Regenerate — there is no in-place rotate. Generate a new token, update your IDE config, then revoke the old one.

See MCP for IDEs for the config snippets.

Notification settings

Coming soon. Slack and email digests for high-risk PRs are on the roadmap. For now, reviews appear as a comment on the PR and in your dashboard.

Risk threshold customization

Coming soon. Custom risk-flag configuration — tuning which flags raise the overall risk level — is planned for the Pro tier. The default thresholds work for most teams today.

Uninstalling Senix

Removing Senix has two independent parts. Do whichever applies to you:

1. GitHub App — uninstall Senix-bot from github.com/settings/installations. This stops all PR analysis.
2. Account deletion — to remove your Senix account and data entirely, use the Feedback button in the dashboard to request deletion. This also revokes all MCP tokens.