Skip to content
curiositech.

Agent systems / Coming soon

GitHub Custodian

Give AI agents scoped GitHub permissions through explicit policies and signed receipts, without sharing personal GitHub credentials.

Made for

For teams introducing agents into repository workflows who want a clearer answer to three questions: what was allowed, who had authority, and what record remains afterward.

Scoped GitHub permissions

Authority is tied to an explicit policy, giving repository operations a more deliberate boundary than an unrestricted credential.

Start here

Start with a policy describing the GitHub action and its scope. Make the boundary specific enough to assess before the operation happens.

GitHub Custodian is coming soon. Talk with us about scoped agent permissions and signed action receipts for your team’s GitHub workflow.

GitHub Custodian preview

Availability

Coming soon

How it works and what’s inside

Made for

For teams introducing agents into repository workflows who want a clearer answer to three questions: what was allowed, who had authority, and what record remains afterward.

Giving an agent useful GitHub access should not mean giving it your personal credentials and hoping for the best. GitHub Custodian separates the work an agent wants to do from the authority it needs, with explicit policy and signed receipts for the actions it handles.

How it works

Workflow

  1. Define the allowed work

    Start with a policy describing the GitHub action and its scope. Make the boundary specific enough to assess before the operation happens.

  2. Keep authority separate

    Let the agent request work through the custodian's permission model, rather than sharing a person's general-purpose GitHub credentials with the agent.

  3. Keep the receipt

    Retain a signed record of the handled action so a later review has something concrete to inspect beyond the agent's own account.

Inside GitHub Custodian

Features

Scoped GitHub permissions

Authority is tied to an explicit policy, giving repository operations a more deliberate boundary than an unrestricted credential.

Signed action receipts

Receipts make the permission story inspectable after the fact. They give a later review a concrete record of the permissioned action to examine.

Agent and person separation

The product is built around preserving the distinction between agent authority and personal access, a useful foundation for teams adopting automated workflows.

GitHub Custodian is coming soon. Talk with us about scoped agent permissions and signed action receipts for your team’s GitHub workflow.

Like what you see? Hire Curiositech

Back to products