codex - 💡(How to fix) Fix GitHub connector exposes create_pull_request but not create_issue [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17513Fetched 2026-04-12 13:27:18
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Author
Timeline (top)
commented ×3labeled ×3closed ×1unlabeled ×1

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.

Root Cause

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

RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The GitHub connector needs to be updated to include a create_issue action to support issue creation, similar to the existing create_pull_request action.

Guidance

  • Review the GitHub connector's code and documentation to determine if issue creation is intentionally unsupported or an oversight.
  • Compare the implementation of github_create_pull_request with the missing github_create_issue action to identify potential similarities and differences.
  • Consider adding a feature request or proposal to the GitHub connector's development pipeline to include the create_issue action.
  • Evaluate the feasibility of creating a custom or temporary workaround, such as using the github_fetch_issue and github_add_comment_to_issue actions in combination to simulate issue creation.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require updates to the GitHub connector's codebase, documentation, or configuration, and may involve collaboration with the connector's development team.

Recommendation

Apply workaround: While waiting for the create_issue action to be implemented, use browser automation or manual user intervention as a temporary workaround to file GitHub issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix GitHub connector exposes create_pull_request but not create_issue [3 comments, 3 participants]