Does Agent Planners support GitHub?

Yes. Fifteen reads and seven approval-gated writes cover repositories, branches, the file tree, issues, pull requests, commits, releases, files, search, traffic and workflow runs, plus issues, comments, issue updates, draft releases, new branches, file changes on a branch and draft pull requests.

Can the agent delete anything on GitHub?

No. No tool deletes a repository, branch, file, issue, comment or release, and a destructive argument is refused on every lane.

Can the agent change my code?

On a branch, behind your approval: it reads the file tree and the files, creates a new branch, writes each changed file there (one approval per file, with before and after shown) and opens a draft pull request. It never writes to your default branch, never touches workflow files, and never merges — you do that on GitHub.

Can it read private repositories?

Only where the deployment opts into the repo permission and you re-authorize; by default it reads public repositories plus your profile and organization memberships.

What is GitHub doing in a marketing agent?

Launches and campaigns follow the code: release notes from merged pull requests, a changelog for the newsletter, repository traffic next to the campaign that drove it, and an issue filed when a landing page breaks.

Data

AI agent for GitHub: release notes, issue triage, repository traffic, launch tracking and pull requests

TL;DR

GitHub connects through GitHub's own sign-in and reads the repositories your login and its organizations reach. The agent turns commits and merged pull requests into release notes, triages issues by label, reads repository traffic next to your campaigns, files issues or drafts releases that wait for your approval, and makes small code changes the safe way: a new branch, one approved file write at a time, and a draft pull request you review and merge. Text written by other people in issues and files is handled as data, never as instructions.

Connecting it, and what it asks for

1Open Integrations and click Connect on the GitHub card.
2Sign in to GitHub and authorize the app; your login and each organization you belong to appear as rows.
3Pick the login or organization for the task, then write the goal with the repository as owner/name.

The authorization asks for read:user, read:org and public_repo. Private repositories need the repo permission, which a deployment opts into and a Re-authorize grants; the agent says so when a read is refused. No admin, delete or organization-write permission is ever requested.

What the agent reads

Repositories (yours, your organizations', or any you name), with language, stars, forks, open issues and the default branch.
Issues and pull requests — state, labels, assignees, authors, timestamps — and single items in full.
Commits, releases and workflow runs, so a launch can be tied to the code that shipped.
File contents up to 200 KB, directory listings, the file tree of a branch or a subtree (up to 2,000 entries, with an honest truncated flag), the list of branches, and GitHub search across repositories, issues, code and commits.
Repository traffic for the last fourteen days — views, clones, top referrers and paths — where your login has push access.

What the agent changes — all of it approval-gated

Create an issue with a title, body, labels and assignees.
Comment on an issue or pull request.
Update an issue — title, body, labels, assignees, or close and reopen it (reversible).
Draft a release from a tag — a draft publishes nothing until you publish it.
Create a branch from your default branch (or any branch, tag or commit) — an existing name is never moved or replaced.
Create or update a file on a branch — one file per approval, with the previous and the new version shown; never on the default branch (that is refused), never under .github/workflows/, and never a delete.
Open a draft pull request from that branch — you review it and you merge it; no tool merges.

Nothing deletes, nothing merges, and the default branch is never written to. No tool removes a repository, a branch, a file, an issue, a comment or a release; a destructive or merge argument is refused on every lane; a code change reaches your default branch only through the pull request you merge on GitHub.

Things worth knowing before you plan around it

Issue, pull-request, commit and file text is third-party content; the agent treats it as data and never as instructions, and never pastes tokens or secrets into what it writes.
GitHub allows 5,000 requests an hour per connection and 30 searches a minute; search returns its first page.
A GitHub token does not expire on a clock — it ends when you revoke the app under github.com → Settings → Applications, which the card then reports.

Frequently asked questions

Does Agent Planners support GitHub?: Yes. Fifteen reads and seven approval-gated writes cover repositories, branches, the file tree, issues, pull requests, commits, releases, files, search, traffic and workflow runs, plus issues, comments, issue updates, draft releases, new branches, file changes on a branch and draft pull requests.
Can the agent delete anything on GitHub?: No. No tool deletes a repository, branch, file, issue, comment or release, and a destructive argument is refused on every lane.
Can the agent change my code?: On a branch, behind your approval: it reads the file tree and the files, creates a new branch, writes each changed file there (one approval per file, with before and after shown) and opens a draft pull request. It never writes to your default branch, never touches workflow files, and never merges — you do that on GitHub.
Can it read private repositories?: Only where the deployment opts into the repo permission and you re-authorize; by default it reads public repositories plus your profile and organization memberships.
What is GitHub doing in a marketing agent?: Launches and campaigns follow the code: release notes from merged pull requests, a changelog for the newsletter, repository traffic next to the campaign that drove it, and an issue filed when a landing page breaks.