GitHub connector exposes create_pull_request but not create_issue

Resolved 💬 3 comments Opened Apr 12, 2026 by fireshort Closed Apr 12, 2026

Summary

The curated GitHub connector bundled with Codex exposes issue read/search/comment actions and pull request creation, but it does not expose a create_issue action.

Evidence

In the current GitHub connector tool list, I can see actions such as:

  • github_fetch_issue
  • github_fetch_issue_comments
  • github_search_issues
  • github_add_comment_to_issue
  • github_create_pull_request

But there is no github_create_issue.

Actual behavior

When a user asks Codex to file a GitHub issue, the agent cannot do it through the GitHub connector and must fall back to browser automation or ask the user to file it manually.

Expected behavior

Please add a create_issue capability to the GitHub connector, similar to create_pull_request, or document clearly that issue creation is intentionally unsupported.

Why this matters

Creating issues is a common GitHub workflow. Supporting PR creation but not issue creation creates a noticeable gap in the connector's write capabilities.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗