Sign in with GitHub
Choose Connect on the GitHub connection page and sign in to GitHub to approve the ApexGenius Connect app. Then choose Choose repos on GitHub and install the app on the repositories your AI may read; GitHub brings you back to ApexGenius. The app reaches only the repositories it is installed on, and its sign-in renews itself. For a repository owned by an organization, an owner may need to approve the app. An organization can require approval for the app. If a repository is missing, check the app installation, then the organization’s policy.Connect and read your first repository
Before you start- A GitHub account that can read the repositories you want your AI to use.
- For a repository owned by an organization, an owner who can approve the ApexGenius Connect app.
Open GitHub in Connections

Open Connections and find GitHub. Until you connect it, its row shows Connect.
Sign in to GitHub

GitHub asks which account to use. Choose Continue on the one you want. Account names are blurred in this capture.
Choose your repositories

Back in ApexGenius, open the status control and choose Choose repos on GitHub to install the app on your repositories.

Pick your account or an organization to install the ApexGenius Connect app on.

Choose Only select repositories, pick the ones your AI may use, then Install. ApexGenius keeps the connection read-only until you turn on writes.
Check the connected account

After you connect, Overview shows Connected and lists your repositories. The repository name is blurred in this capture.
Turn on writes for selected repositories
Writes are off until you turn them on, one connection at a time. Each person does this on their own connection. Turning writes on for yourself does not turn them on for a teammate.Switch on the repositories

The Repositories list on Overview. Each repository has its own switch. The repository name is blurred.
Open Settings on the Tools tab

Settings is on the Tools tab, to the right of Tool permissions.
Choose Read and write

Mode, under GitHub access. This capture shows a connection after writes are on, so the badge reads Writes on and the button reads Save access.
Tick Run workflows, if you need it

Run workflows appears once Read and write is on. Tick a repository, then select Save access. The repository name is blurred.
Check that writes are on
create_branch and push_files. That is your check that writes
are on.repo: filters for your repositories, and
repository search is turned off. Switch back to Read only at any time; the
change takes effect on the next call. Every write is recorded in the connection’s
activity.
Every setting, and where it lives
GitHub has more settings than most apps. Each one belongs to a single connection, so every person sets their own. The status menu is the Connected control under the page title.
Most settings live here: the Tools tab, then Settings. This capture shows a connection with writes on. The repository name is blurred.
Tools and the GitHub skill
Open Skills on the connection to read GitHub, or read that MCP prompt in a compatible AI client. It explains the first safe read, how to connect, the two modes and the tools below. Three ApexGenius tools route GitHub’s live catalog:expectedHeadSha so GitHub
refuses the merge if new code was pushed in the meantime. A merge can trigger
workflows and deployments even when manual workflow runs are off in ApexGenius.
Read back the merged state and commit before reporting completion. Reverting
the code does not undo deployments or other effects the merge triggered.
Your AI discovers the tools with apex_search_tools, runs reads with
apex_call_read_tool and writes with apex_call_write_tool. Approval works
the same way on every ApexGenius connector: Writes run immediately.
Blocked hides a tool from agents.
What is not exposed
delete_file, create_repository, delete_repository
and fork_repository are refused on every connection, whatever GitHub
allows, and are hidden from discovery. Do those on github.com, along with deleting
workflow run logs. Dependabot, code scanning, discussions, gists,
notifications and projects are not reached by this connection.
Troubleshooting
- A repository is missing. A signed-in connection reaches only the repositories the app is installed on: choose Choose repos on GitHub and add it, or ask an organization owner to approve the app.
- Your AI says GitHub is read-only, or it cannot push. The connection is still read-only. GitHub lists no write tools on a read-only connection, so your AI finds nothing to call. Turn on writes above, then ask your AI to discover GitHub tools again.
- It works for you and not for a teammate. Writes are set on each person’s connection. Ask them to turn on writes on theirs.
- A write was refused. The connection is read-only, the repository is not on its list, or the tool is one of the blocked four. The refusal names which. For a write GitHub itself rejects, check that the app is installed on that repository.