Skip to content
Cloud

Integrations · AI coding agents

The same pack writes Copilot’s repository hooks and instructions. Pull requests from the Copilot coding agent are governed changes like any other.

Control levels

  1. 1Observe

    We watch, record and flag.

    Copilot agent pull requests and their sessions, tied to the person who assigned the work.

  2. 2Gate

    The tool waits for an approval.

    preToolUse hooks generated from the pack; agent pull requests need a human approval.

  3. 3Hold

    Only Aspian holds the credentials.

    The agent holds no production credentials.

Set it up

  1. 1Generate .github/hooks and instructions from your policy pack.
  2. 2Commit them to each governed repo.
  3. 3Assign agent work as usual; Aspian records who asked for it.

Limits worth knowing

  • Copilot hooks fail open on timeout, so the server-side gate is what makes the rule hold.

More ai coding agents

See what shipped without approval in your last 90 days.

Install the GitHub App and the scan arrives in minutes: every repo scored, every unreviewed merge and unapproved deploy named. Nothing is blocked until you choose.

Ship like a startup. Prove it like a bank.