GitHub

GitHub links your own GitHub account to MaxSuite. You and your agents can then read your repositories, sort their issues and pull requests, and, with your approval, push work to them as branches, commits and pull requests (module github).

In the sidebar under Connections → GitHub. The connection is yours: it acts as you on GitHub, and nobody else in the workspace can use it, an administrator included.

GitHub

• No account linked yet: "No GitHub account linked", with Connect with GitHub if you may manage GitHub.
• Your account: your GitHub login, how it was connected, its status and the date you linked it. Opening the page asks GitHub, live, whether the connection still works.
• Repositories: the repositories your account can reach, most recently pushed first, marked private or public. Repositories are read live from GitHub every time, never copied into MaxSuite.
• Set up Connect with GitHub: a card an admin sees until it is done.

Open a repository to see its Issues and pull requests. Filter by Kind (issues, pull requests or both), State (open, closed or both), label, Author and Changed since. A repository page also says whether your connection can change issues there, and which permission to add if it cannot.

Triage report

A Triage report lists suggestions for a repository's open items, built by fixed rules, not by a model: what looks stale, a possible duplicate, answered, short of information, ready to merge or worth closing. Each comes with its reason, the threshold it used and evidence you can open. It reads at most the number of open items set in Settings (300 by default), longest-silent first, and says how many it did not. A report only suggests. It never merges, reads code or follows a link in an issue. Reports are kept 90 days so the next one can say what is new, changed or gone.

Settings holds the thresholds: Stale after (days), A question waits (days), Looks answered after (days), Items examined per report, Duplicate similarity, Shortest bug report (characters), Bug labels, Keep-open labels, Ready to merge needs passing checks, and Note on comments an agent posts. Only a workspace admin can turn that note off.

Weekly triage schedules one of your agents to check the repository each week and send you a short digest with a link to the full report. A week with nothing new sends nothing.

What you can do

Connect your account

1. Open Connections → GitHub and press Connect with GitHub.
2. GitHub shows its own page listing what Max asks for (repo, workflow and read:org). Approve it.
3. You come back here connected. If you cancel on GitHub, nothing changes.

The token GitHub gives is stored encrypted, and no screen or tool returns it. Reconnect is the same button.

Use a token instead is a backup: paste a personal access token. To push and to create repositories it needs the repo scope (classic token), or Contents and Administration read and write (fine-grained token). To change issues it needs Issues and Pull requests read and write. MaxSuite asks GitHub who the token belongs to before saving it.

Set up Connect with GitHub

Done once by an admin for the whole workspace.

1. On GitHub, register an OAuth App called Max with the callback address the card shows.
2. Paste its Client ID and Client secret on the card.
3. Press Test. Remove forgets them. People already connected stay connected.

Until this is done, people can still connect with a token.

Label, comment on or close items

From a report or the item list, choose Label, Comment or Close. A preview shows exactly what will go out under your GitHub name. Confirming it is the approval. Labels must already exist in the repository. A close needs a comment saying why, unless you tick Close without a comment, and is Not planned or Completed. One approval covers up to 25 items. An item that changed since the report is skipped. Undo reopens what the batch closed and removes the labels it added. A comment already posted stays.

Disconnect

Press Disconnect and confirm. The token is deleted from MaxSuite and Max's access is withdrawn on GitHub.

Record which repository a project uses

To record where a project's code lives, link the repository from the project in Projects. Agents do it with projects.connectRepo.

Who can do what

Permission	Label	Lets you
github:read	View github	Open the page, see your own account's status, repositories, issues and pull requests, and make triage reports.
github:write	Manage github	Connect, reconnect and disconnect your own account, change triage settings, and label, comment on and close items. For agents, also create branches, commit, delete files, open pull requests and create repositories.
github:admin	Set up Connect with GitHub for the workspace	Save, test and remove the workspace's OAuth App.

Every action uses the caller's own linked account. Holding github:write never lets anyone use a colleague's connection. See People, roles and permissions.

What happens on its own

Job	When	What it does
prune-reports	Every day at 03:30 UTC	Deletes triage reports older than 90 days.
prune-connect-states	Every day at 03:40 UTC	Clears unfinished Connect with GitHub attempts.

Needs

Nothing has to be switched on first.

What agents can do

An agent works on GitHub as the person it acts for, through that person's own connection. Reads run straight away. Every change waits for a person's approval by default. Changing several issues at once always asks, every time. A commit or a pull request is published under your GitHub name the moment it lands. The approval card names the repository, the branch, the message and every file path. See Agents and approvals.

Connection: github.status, github.appSetup, github.testAppSetup (read only); github.connectLink gives the person a link to approve on GitHub; github.removeAppSetup, github.disconnect (change)

Repositories, read only: github.repos, github.commits

Code, need approval: github.createBranch, github.putFile, github.commitFiles, github.deleteFile, github.openPullRequest, github.createRepo

Issues and triage, read only: github.issues, github.item, github.labels, github.triage, github.triageReport, github.triageDue, github.triageSettings

Issues, change: github.labelItems, github.applyItemActions (always asks), github.undo, github.dismiss, github.setTriageSettings

What to know about them:

• github.status checks the connection with GitHub every time. When it was revoked or expired, it says why and how to fix it.
• github.createBranch refuses if the branch already exists, rather than moving it.
• github.commitFiles writes many files as one commit: at most 100 files and 2 MB in all. It refuses .env files (except .env.example), *.pem, id_rsa and anything that looks like a credential. Keep secrets in Named secrets instead.
• github.createRepo asks which owner to make the repository under, and makes it private unless told otherwise.
• github.dismiss keeps an item open: it is not suggested again until it changes.
• github.disconnect only ever removes the caller's own account.

Over MCP the same tools are named github__status, github__commitFiles and so on. See API keys and MCP access.

Related

• Projects: link a repository to a project
• Doc sync: binds a project's documentation to a repository
• Integrations (provider accounts): GitHub can also be connected there, as an account whose repositories are inventoried
• Agents and approvals