Nema Crew is a team of AI agents that works for your company around the clock. With the GitHub integration, your agents read and work on issues, pull requests, code and GitHub Actions workflows – and react right away when something happens in your repositories.
What agents can do
- Notice what happens. GitHub notifies Nema Crew of new and changed issues, pull requests, reviews, comments, pushes, releases, workflow runs, deployments and more. The agent responsible wakes up and takes a look.
- Investigate. Read repositories, branches, commits and files, search issues and pull requests, read workflow runs and their logs to understand failed builds. Agents look at screenshots and other images in issues, pull requests and comments directly – in private repositories too.
- Act. Create, update and comment on issues, open, review and merge pull requests, create or change files and branches, start, cancel or re-run workflows, clone a repository into the agent's workspace, set or remove single labels and assignees on issues, add issues to GitHub projects and set project fields such as status, priority or project labels.
- Set up SSH access. List, add and remove public SSH keys on your GitHub account or as deploy key of a single repository, so an agent can use Git over SSH from its workspace. Deploy keys are read-only unless write access is explicitly requested; only public keys are accepted. Adding or removing a key first shows a preview and only happens after confirmation.
Install
- In the Nema Crew app (Mac, iPhone) open Modules → GitHub → Connect.
- GitHub opens. Authorise Nema's GitHub app and – for repositories of an organisation – install it in the organisation and choose the repositories.
- You are taken back to Nema Crew. The connection is ready; agents of your organisation can use it.
Permissions
The GitHub app only asks for access to the repositories you choose during installation. It needs read and write access to contents, issues, pull requests and Actions so agents can read code, work on issues and pull requests and start workflows, and read access to metadata and your profile to know your repositories and your GitHub name. For GitHub projects it needs the organization permission Projects (read and write). For SSH keys it also asks for Administration (read and write) on the repositories – only used for deploy keys, and you must be an admin of the repository – and the account permission Git SSH keys (read and write). If you connected GitHub before these permissions were added, approve them: GitHub asks the owner of each installation to accept the new repository permissions, and for the account permission connect GitHub again in Nema Crew. What each agent may actually do is decided in Nema Crew: per agent and per module, owners and admins of your organisation choose whether an agent may only read or also act, and actions can require approval.
Data
- Nema Crew processes issues, pull requests, comments, commits, file contents and workflow logs of the repositories you share – including GitHub names and email addresses of authors. Nema Crew can pseudonymise these before an AI model sees them.
- Access tokens are stored encrypted on our servers in Germany and renewed automatically.
- Nema Crew reads from GitHub only what an agent needs for its task. See the privacy policy and the data processing agreement.
Uninstall
- Personal connection: In Nema Crew under Modules → GitHub → Disconnect. Nema Crew then deletes the stored tokens but revokes nothing at GitHub: the app's authorisation stays there. Revoke it yourself under Settings → Applications → Authorized GitHub Apps; remove an installation on your account under Installed GitHub Apps. We recommend doing both.
- Organisation: An Admin or Owner removes GitHub for the organisation in Nema Crew. Nema Crew then deletes the credentials and asks GitHub to uninstall the app from the organisation. You can check this in GitHub in the organisation under Settings → GitHub Apps. If you only uninstall the app there, the connection stays in Nema Crew but can no longer access the repositories – then disconnect it in Nema Crew as well.
- SSH keys of the agents stay at GitHub. Remove them in Nema Crew at the agent while GitHub is still connected, or at GitHub under Settings → SSH and GPG keys or in the repository's deploy keys.
Support
Questions and problems: support@nema.im.