Sanaf AI
Start free
Developer Tools

GitHub, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your GitHub account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 97 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What GitHub is

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

You sign in with your own GitHub account, the same way you already do. We never see or hold your password.

It can also be told by GitHub when something happens, rather than only doing things when you ask.

How a run works

One message in, the work done in GitHub.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in GitHub. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own GitHub account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

97 tools it already has

What it can do in GitHub

These are the ready-made tools your AI employee already has in GitHub. It is not limited to them, but it never has to be taught these.

  • Accept a repository invitationAccepts a pending repository invitation that has been issued to the authenticated user.
  • Add a repository collaboratorAdds a github user as a repository collaborator, or updates their permission if already a collaborator; permission applies to organization-owned repositories (personal ones default
  • Add a repository to an app installationAdds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
  • Add a selected repository to a user secretGrants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.
  • Add app access restrictionsReplaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' w
  • Add assignees to an issueAdds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
  • Add email for auth userAdds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for ano
  • Add labels to an issueAdds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
  • Add or update team membership for a userAdds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no ch
  • Add or update team project permissionsGrants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
  • Add or update team repository permissionsSets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
  • Add org runner labelsAdds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
  • Add project collaboratorAdds a specified github user as a collaborator to an existing organization project with a given permission level.
  • Add repo to org secret with selected accessAdds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.
  • Add runner labelsAdds and appends custom labels to a self-hosted repository runner, which must be registered and active.
  • Add selected repo to org secretGrants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if ac
  • Add selected repository to an organization secretAdds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
  • Add selected repository to an organization variableGrants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.
  • Add social accounts for the authenticated userAdds one or more social media links (which must be valid, full urls for platforms supported by github) to the authenticated user's public github profile.
  • Add status check contextsAdds status check contexts (provided in the request body, e.g., {"contexts": ["new-context"]}) to a protected branch, requiring these contexts to have been previously reported.
  • Add team access restrictionsOverwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.
  • Add user access restrictionsSets/replaces list of users allowed to push to a protected branch; usernames (e.g., ["user1"]) must be a json array in request body (not schema parameters), an empty array [] remov
  • Add users to codespaces access for an organizationSets or replaces the list of organization members granted codespaces access billed to the organization; ensure the organization's billing settings allow access for selected members
  • Approve a workflow run for a fork pull requestApproves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
  • Assign an organization role to a teamAssigns an existing organization-level role (identified by role id) to a team (identified by team slug) within a github organization (org), provided the organization, team, and rol
  • Assign an organization role to a userAssigns a specific organization role to a user who is a member or an outside collaborator in a github organization, using a valid role id.
  • AuthuserdockerconflictpackageslistLists docker packages for the authenticated user that encountered conflicts during the docker migration process.
  • Block a userBlocks an existing individual github user (not an organization or your own account), preventing them from interacting with your account and repositories.
  • Block a user from an organizationBlocks an existing github user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.
  • Cancel a GitHub Pages deploymentCancels an existing, ongoing or queued github pages deployment for a repository using its pages deployment id.
  • Cancel a workflow runCancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').
  • Check a tokenChecks if a github app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.
  • Check if a gist is starredChecks if a gist, identified by gist id, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.
  • Check if a user can be assignedVerifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the resp
  • Check if a user can be assigned to an issueChecks if a specified github user can be assigned to a given issue within a repository.
  • Check if a user follows another userChecks if a github user username follows target user; returns a 204 http status if true, 404 if not or if users are invalid.
  • Check if a user is a repository collaboratorChecks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
  • Check if a user is blocked by an organizationChecks if a github user is blocked by an organization; a successful response (204 no content) indicates the user is blocked, while a 404 not found error indicates the user is not b
  • Check if a user is blocked by the authenticated userChecks if the specified github user is blocked by the authenticated user; a 204 no content response indicates the user is blocked, while a 404 not found indicates they are not.
  • Check if person is followed by authenticated userChecks if the authenticated github user follows a target github user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not followed
  • Check if pull request mergedChecks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
  • Check if repo starred by auth userUse to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data
  • Check private vulnerability reporting statusChecks if private vulnerability reporting is enabled for the specified repository.
  • Check team permissions for a projectChecks if a team has 'read', 'write', or 'admin' permissions for an organization's specific classic project, returning the project's details if access is confirmed.
  • Check team permissions for a repositoryChecks a team's permissions for a specific repository within an organization, including permissions inherited from parent teams.
  • Clear repository cache by keyDeletes github actions caches from a repository matching a specific key and an optional git ref, used to manage storage or clear outdated/corrupted caches; the action succeeds even
  • Clear self-hosted runner org labelsRemoves all custom labels from a self-hosted runner for an organization; default labels (e.g., 'self-hosted', 'linux', 'x64') will remain.
  • Compare two commitsCompares two commit points (commits, branches, tags, or shas) within a repository or across forks, using base...head or owner:ref...owner:ref format for the basehead parameter.
  • Configure JIT runner for an orgGenerates a jit configuration for a github organization's new self-hosted runner to run a single job then unregister; the runner group id must exist.
  • Configure OIDC subject claim templateSets or updates the oidc subject claim customization template for an existing github organization by specifying which claims (e.g., 'repo', 'actor') form the oidc token's subject (
  • Convert an organization member to outside collaboratorConverts an existing organization member, who is not an owner, to an outside collaborator, restricting their access to explicitly granted repositories.
  • Create a blobCreates a git blob in a repository, requiring content and encoding ('utf-8' or 'base64').
  • Create a check runCreates a new check run for a specific commit in a repository, used by external services to report status, detailed feedback, annotations, and images directly within the github ui.
  • Create a check suiteCreates a new check suite for a specific commit (head sha) in an original repository (not a fork); github dispatches a check suite webhook event with the requested action upon succ
  • Create a codespace for the authenticated userCreates a github codespace for the authenticated user, requiring a json request body with either repository id (integer) or a pull request object (containing pull request number (i
  • Create a codespace from a pull requestCreates a github codespace for an open pull request in a codespaces-enabled repository, with options to customize its configuration.
  • Create a codespace in a repositoryCreates a github codespace for the authenticated user in a specified repository, which must be accessible and use a valid devcontainer.json if devcontainer path is specified.
  • Create a commitCreates a new commit in a github repository; the tree sha and any parents shas must already exist in the repository.
  • Create a commit commentCreates a comment on a specific commit, or on a specific line if path and position are provided.
  • Create a commit statusSets a commit's status (e.g., error, failure, pending, success from ci/cd) for a given sha; max 1000 statuses per sha/context.
  • Create a custom organization roleCreates a custom role with defined permissions within a github organization.
  • Create a deploy keyCreates a deploy key for a repository; the repository must exist and be accessible, and the provided key must be a valid public ssh key.
  • Create a deploymentCreates a github deployment for an existing repository, targeting a specific ref (branch, tag, or sha) that must also exist within the repository.
  • Create a deployment branch policyCreates a deployment branch or tag policy for an existing environment in a github repository, using a ruby file.fnmatch pattern (where doesn't match /) to specify which branches or
  • Create a deployment statusCreates a status for an existing deployment, updating its operational state, associated urls, and description.
  • Create a discussionCreates a new discussion post on a specific team's page within an organization.
  • Create a discussion commentCreates a new comment on an existing team discussion within a github organization.
  • Create a forkCreates a fork of an accessible repository, optionally into a specific organization, with a new name, or copying only the default branch.
  • Create a gistCreates a new gist on github with provided files, an optional description, and public/secret visibility.
  • Create a gist commentCreates a new comment on a specified github gist.
  • Create a GitHub App from a manifestUse this action to finalize a github app's creation by exchanging the temporary code (received as a url parameter during the app manifest setup redirection) for the app's full conf
  • Create a github pages deploymentCreates a github pages deployment for a repository using a specified artifact and oidc token, provided github pages is enabled and the artifact (containing static assets) is access
  • Create a github pages siteConfigures or updates github pages for a repository, setting build type and source; ensure a pages workflow exists for 'workflow' build type, or source branch exists for 'legacy' o
  • Create a labelCreates a new label in a specified github repository, provided the repository exists and the user has write permissions.
  • Create a milestoneCreates a milestone in a github repository for tracking progress on issues or pull requests; requires repository existence and user write permissions.
  • Create a project cardCreates a project card in a github project column; the request body must contain either a note for a note-only card, or both content id (id of an issue or pull request) and content
  • Create a project columnCreates a new column in a github project (classic).
  • Create a pull requestCreates a pull request in a github repository, requiring existing base and head branches; title or issue must be provided.
  • Create a referenceCreates a git reference (e.g., a branch or tag) in a repository; the repository must not be empty prior to this operation.
  • Create a registration token for a repositoryGenerates a time-limited token required to register a new self-hosted runner with a specific repository.
  • Create a registration token for an organizationGenerates a temporary (one-hour) registration token to add a new self-hosted runner to an organization for github actions.
  • Create a releaseCreates a release in a github repository for a specified tag; the tag must be unique for published releases, and if a discussion category name is given, it must already exist.
  • Create a remove token for a repositoryGenerates a temporary (one-hour validity) token required to unregister and remove a self-hosted runner from a repository.
  • Create a remove token for an organizationGenerates a token, valid for one hour, to authenticate removing a self-hosted runner from an organization.
  • Create a reply for a review commentPosts a reply to a specific review comment on a github pull request, requiring the repository, pull request, and original comment to exist, and a non-empty reply body.
  • Create a repository dispatch eventTriggers a github actions workflow or a webhook on a repository by creating a repository dispatch event, allowing programmatic triggering of workflows based on events outside of gi
  • Create a repository for the authenticated userCreates a new repository for the authenticated user, optionally within an organization if team id is specified.
  • Create a repository from an unpublished codespacePublishes the specified codespace to a new repository, using the codespace's current state as the initial commit.
  • Create a repository projectCreates a new classic project board within a specified repository; classic projects must be enabled for the target repository.
  • Create an autolink reference for a repositoryCreates a repository autolink to automatically convert text references (e.g., 'ticket-123') into hyperlinks, using a unique key prefix and a url template that includes <num.
  • Create an environment variableCreates an encrypted environment variable for a pre-existing environment within a github repository; will fail if the variable name already exists.
  • Create an issueCreates a new issue in a github repository, requiring the repository to exist and have issues enabled; specific fields like assignees, milestone, or labels may require push access.
  • Create an issue commentCreates a new comment on an existing github issue or pull request within the specified repository.
  • Create an organization projectCreates a new classic project board within a specified github organization.
  • Create an organization repositoryCreates a new repository within a specified github organization, with options for detailed configuration including visibility, features, merge strategies, initial commit, and templ
  • Create an organization variableCreates a new, uniquely named github actions variable for an organization, with configurable repository access visibility (all, private, or selected).
  • Create an organization webhookCreates a webhook for a github organization to deliver event notifications to a configured url.
46 things it can watch for

What GitHub can tell it about

It does not only wait to be asked. These are the things GitHub can tell your AI employee about the moment they happen, so it can act without anyone noticing first.

  • Branch ChangedA GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unpro
  • Check Run Status / Conclusion ChangedA specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, inprogress, completed, etc.), conclusion (su
  • Check Suite Status / Conclusion ChangedA GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for chan
  • Commit EventA new commit is pushed to a repository.
  • Follower ChangesNew followers are detected on your GitHub account.
  • GitHub Deployment State ChangedA specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - environment -- the target environment name - originalenvironmen
  • GitHub Issue Comment ChangedA specific GitHub issue comment changes. Monitors the following fields for changes: - body -- the text content of the comment (detects edits) - updatedat -- the last-
  • GitHub Issue Labels ChangedThe labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored iss
  • GitHub Pull Request Reviewers ChangedThe list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the
  • GitHub Release State ChangedA specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/co
  • GitHub Repository README ChangedThe README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current RE
  • GitHub Workflow Run State ChangedA GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued t
  • Issue Added EventA new issue is added to the repository.
  • Issue State / Properties ChangedA specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), statereason, title, body, assignees, labels, milestone, lock
  • Issue UpdatedAn existing issue is updated in a GitHub repository. Monitors issues for any changes such as title edits, body edits, label changes, assignee changes, state transitio
  • Label Added EventA new label is added to a pull request.
  • New Artifact Added to Workflow RunA new artifact is uploaded to a specific GitHub Actions workflow run. Monitors a single workflow run for newly added artifacts such as build outputs, test results, or
  • New Branch CreatedA new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
  • New Code Scanning Alert CreatedA new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be f
  • New Commit Added to Pull RequestA new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers forc
  • New Deployment CreatedA new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally
  • New Deployment Status CreatedA new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses
  • New Git Reference CreatedA new Git reference (branch or tag) matching a specified prefix is created in a repository. Fires an event for each newly created branch or tag whose name matches the
  • New GitHub Actions Workflow AddedA new GitHub Actions workflow is added to a repository. Monitors a repository's GitHub Actions workflows and fires an event for each newly added workflow. The payload
  • New GitHub Issue CommentA new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload in
  • New GitHub Release Asset AddedA new asset is added to a specific GitHub release. Monitors a single release (identified by release ID) for newly uploaded assets such as binaries, archives, or check
  • New Issue Assigned to MeA new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatica
  • New Issue CreatedA new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assigne
  • New Issue EventA new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, mil
  • New Pull Request CreatedA new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repositor
  • New Pull Request Review CommentA new inline review comment is added to a specific GitHub pull request. Monitors all review comments across all reviews on the specified pull request and emits an eve
  • New Repository Collaborator AddedA new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The
  • New Repository Tag CreatedA new tag is created in a GitHub repository. Monitors the repository's tags and fires an event for each newly created tag. The payload includes the tag name, the comm
  • New Secret Scanning Alert DetectedA new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filter
  • New Stargazer AddedA new user stars a GitHub repository. Emits an event for each new stargazer detected on the monitored repository.
  • New Workflow Artifact CreatedA new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restri
  • New Workflow Job AddedA new job appears in a specific GitHub Actions workflow run. This is useful for detecting matrix-expanded jobs that are added after the initial workflow run creation,
  • New Workflow Run CreatedA new workflow run is created in a GitHub repository. Monitors the repository for any new workflow runs and fires an event for each one. Optional filters allow narrow
  • Pull Request EventA pull request is opened, closed, or synchronized.
  • Pull Request Review SubmittedA new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED
  • Pull Request State / Properties ChangedA specific GitHub pull request changes any of these tracked properties: state (open/closed), title, body, draft status, lock status, merge status, assignees, labels,
  • Pull Request UpdatedAn existing pull request is updated in a GitHub repository. Updates include title edits, description changes, label changes, assignee changes, reviewer requests, draf
  • Repository Content ChangedThe content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires co
  • Repository Notification ReceivedA new or newly updated notification thread appears for a specific GitHub repository. Monitors notifications for issues, pull requests, commits, releases, check suites
  • Star Added EventA new star is added to the repository.
  • Workflow Job State ChangedThe status, conclusion, timestamps, runner assignment, or step details of a specific GitHub Actions workflow job change between polls. The payload includes the full c
Access, and who is in charge of it

You stay the boss of your GitHub account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own GitHub account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in GitHub is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in GitHub and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about GitHub

Can an AI employee really work inside GitHub?
Yes. It signs in to your own GitHub account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of GitHub?
No. Nothing moves and nothing is replaced. Your records stay in GitHub, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my GitHub account?
You sign in with your own GitHub account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in GitHub?
It has 97 ready-made tools in GitHub today, among them Accept a repository invitation, Add a repository collaborator and Add a repository to an app installation. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use GitHub and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in GitHub and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in GitHub?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in GitHub is written down with what it did and when.