Assigning Claude issue

[michael-kozyrev-kigroup]

Select Topic Area

Question

Body

I’m trying to assign Claude to a GitHub issue through the GitHub API in an organization repo, but it fails with an assignee/access error. Is there some org-level restriction I’m missing?

[michael-kozyrev-kigroup]

For the context, this is a follow-up from this conversation: https://github.com/orgs/community/discussions/189984

[Smikalo]

Following up on the answer to the old conversation mentioned, you can do the assignment through the GitHub API

[Smikalo]

There usually are two separate gates here.

First, GitHub only lets you assign issues to accounts that are actually assignable in that repo, and only people with write access can make the assignment. In org repos, assignable users include people with write access, org members with read access, and some participants like commenters, but not arbitrary accounts that don’t have repo access. GitHub’s assignees docs are here: https://docs.github.com/en/rest/issues/assignees and https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users

Second, if you mean GitHub’s native Claude coding agent, the org has to enable partner agents/coding agents first. GitHub’s org policy docs say Anthropic Claude must be enabled in the organization before you can assign work to it: https://docs.github.com/copilot/managing-github-copilot-in-your-organization/managing-policies-and-features-for-copilot-in-your-organization and https://docs.github.com/en/copilot/concepts/agents/anthropic-claude

If you mean Anthropic’s Claude Code GitHub Action instead of GitHub’s built-in agent assignment, that is a different setup. Anthropic’s action can trigger from issue assignment, but it uses your workflow config (assignee_trigger) and GitHub Actions permissions, not some magic GitHub API ability to assign an inaccessible bot account: https://code.claude.com/docs/en/github-actions and https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md

One more org wrinkle: if your org restricts outside collaborators or app/integration installs, that can also block the setup path even before assignment works: https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators

So the practical answer is: if Claude is not showing as assignable, check whether the org has enabled coding agents/partner agents for that repo. If you are using Anthropic’s action instead, don’t rely on assigning a random bot through the Issues API: use the documented workflow triggers instead

[michael-kozyrev-kigroup]

All right, sounds doable

[michael-kozyrev-kigroup]

And thank you for the docs links!