How does a project use GitHub?

You attach the connection to the project that works with it. That project's agreements decide what the agent does there.

Who decides what the agent can do?

You do. It only gets the permissions the job needs, and you can follow and steer the work from the conversation.

How does GitHub fit our workflow?

Tell us what work you do with GitHub. In the demo we look at what is possible and how it fits your project.

Engineering & data · OAuth

GitHub.
Connected to your work.

Bring GitHub in with the rest of the work. You choose which project the connection joins, and the agent works there with your agreements.

See what it can do

GitHubEngineering & data

This is what you ask itGitHubShow me what this connection can doGitHubPut GitHub in the project where we use itGitHubTurn the way we work into an instruction

Auttendo drafts, you approve. Nothing sends without you.

What your agent can do with GitHub.

You choose the capabilities for the assignment and the access you give them.

In plain language

Actions

Triggers

Create and update issues
Comment on an issue
Create and merge pull requests
Leave a review on a pull request
Create and update branches
Create or update files
Search issues and pull requests
Start and follow GitHub Actions

What is available depends on the access and permissions of your connection. This list shows what the connection itself offers.

Your tools connected. Your team in control.

You choose the tools for the job. Follow what your agent uses in the conversation and see where your input is needed.

Connect the tools you use.
Connect your account and bring your existing workspace with you.
Give your project the right context.
Make knowledge and tools available for the work your agent takes on.
Follow the work in the conversation.
See which actions were completed and decide when the work calls for it.