Skip to main content
Manage in the Settings page. GitHub organization admins can manage billing and workspace administration. Settings can be configured on workspace, repo, and personal level.

​
Workspace settings

​
Excluded commit authors

With Status enabled, admins can exclude authors from commit metering, summaries, and productivity metrics. Match by GitHub username or Git author name in Excluded Commit Authors.

​
Personal settings

Personal review preferences apply to PRs you author and can follow the repository default: Personal MCP connections are available only to you.

​
Repo settings

In Repos, edit one repository or select several for a batch change. Defaults seeds newly linked repositories; changes there do not update existing repositories.

​
Features

Correctness, Check Run Agents, and Approvability each offer three choices:
  • Always run: runs automatically on eligible pull requests.
  • Manual invocation only: runs when requested with @macroscope-app or an Always Review PR Label. Labels remain subject to spend limits; only an @macroscope-app review comment bypasses the correctness caps.
  • Never run: never runs; mentions, labels, and personal preferences cannot override it.
Status is an on/off toggle. It generates executive summaries, productivity statistics, and commit summaries. A feature appears only if the workspace has it. Set features per repository, in a batch, or under Defaults for newly linked repositories. Correctness, Check Run Agents, and Status require repository write access; only a GitHub Admin can change Approvability.

​
Pull request settings

Correctness documents triggers, severity, draft/fork eligibility, author/label/branch filters, run-count caps, and file-size limits. Detection mode covers coverage, validation, and cost. Check Run Agent triggers explains how those controls apply to custom checks. Additional settings include Summarize PRs on GitHub and Auto-assign Reviewer for PRs opened without a reviewer.

​
Approvability settings

GitHub admins choose the run mode under Features and configure Preview Mode separately. Preview Mode shows which PRs Macroscope would approve without submitting approvals. It is off by default and can be set per repository, in a batch, or under Defaults for newly linked repositories. Choose Minimum Blocking Severity, Check Run Conclusion, and Approvability Mode in the same Approvability settings. GitHub admins control these settings. Commit .macroscope/approvability.md for custom eligibility rules. A mode key in that file’s front matter overrides Approvability Mode for the repository.

​
Policy inheritance

Choose a Policy Repo to share its .macroscope/ configuration with other repositories. Only a GitHub Admin can change it. See Policy Inheritance.

​
Repo stages

The default branch comes from GitHub. Release Ref Patterns identifies release branches and tags for summaries and agent queries. Patterns support globs such as release/*, release/**, and production.

​
Connections and exports

  • Connected tools: credentials and permissions for connected tools.
  • Webhooks: inbound query triggers and allowed external delivery URLs.
  • S3 exports: export check runs, review analytics, and user activity.
  • API: create, rotate, and revoke read-only keys for the Macroscope REST API. Only workspace admins can create keys.

​
Support

Settings → Support can open a shared Slack support channel or resynchronize workspace data with GitHub. For billing controls, see pricing and spend controls.