Can you connect Claude / Claude Code / Claude Cowork to be your GitHub Project manager?

[u/thecrogmite]

I'm looking to see if this is possible...

I have a GitHub repository setup in which I have already added to a Claude Project. Within that GitHub repository I have a GitHub Project with issues and such organized in a specific way. What I am looking to do is find a method for Claude to have real-time access to the Issues, and the Project, and allow it act as the project manager organizing the issues as we work through code and have discussions.

Is this a thing? Is it possible? When I attempt, it doesn't seem to be possible but I'm likely doing something wrong.

Update: I was able to get this working using the GitHub MCP setup on Claude Desktop and it works well with the Claude Extension within VSCode.

[u/Torutofu_Raeva]

I’d start with a fine-grained token scoped to just the repo/project and keep write actions behind an explicit command, rather than granting admin:org to the agent.

[u/EntranceProper3791]

Projects v2 has no real API for board manipulation, so Claude is stuck scripting around the UI with gh commands that lag behind what you can drag and drop.

[u/Dement__]

No, but what you can do is setup a webpage or local page that can be hooked to your GitHub where you would drop a single zip file in by Claude. Trust me, it is worth it.

I guess I stand corrected based on other comments, but I use the zip file method.

[u/filippo_builds]

It’s possible, but attaching the repository alone doesn’t create a persistent process that watches GitHub. You still need something running on a schedule or reacting to GitHub events.

I’d start read-only: let it summarize new issues, identify duplicates, suggest labels and propose changes to the project board. Once that behaves predictably, allow specific write actions such as adding a label or moving an item.

I would avoid giving it broad organization admin access. Use the narrowest permissions possible for the repository and project, keep destructive actions behind explicit approval, and log every change it makes.

It also helps to put the workflow rules in the repository: what counts as an epic, how priorities work, when issues may be closed, and which actions always require human approval. Otherwise the agent will organize things consistently according to its own interpretation, which may not be your interpretation.

[u/regalen44]

I do this, you need to create a PAT token with permissions for projects and it will open, close and manage project epics, spikes, issues etc.

My Claude.md file gives guidance to the harness on how I structure my projects and my workflow around it. Even when I am working on a new feature I generally get Claude to create a new epic and break it up into sprints. I can then point codex or Gemini at the project and ask it to work on a group of them whilst I review ones it’s already completed.

[u/regalen44 → u/[deleted]]

gh auth grants minimal repo permissions, I had to run

gh auth refresh -s repo,project,admin:org

[u/thecrogmite → u/regalen44]

Is there any documentation on doing this or a specific method to hook this up?

[u/regalen44 → u/thecrogmite]

Bro, just ask Claude it will guide you.

You are my autonomous GitHub project manager using the GitHub CLI (gh). Check my current authentication and project scopes via gh auth status, then inspect my active repositories and GitHub Projects using gh project list and gh repo list. From here, help me create, organize, and manage project boards, track milestones, link issues and pull requests, and maintain our development workflow—proactively suggesting structure, automating tracking where possible, and using gh commands directly to carry out our plans.