›_ Codex Issues
Codex Issues / #7011

Codex bug report link is broken over two lines so one must edit it to make it work

Resolved 💬 2 comments Opened Nov 20, 2025 by joesh Closed Aug 4, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.60.1

What subscription do you have?

Pro

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

Darwin 23.6.0 arm64 arm

What issue are you seeing?

• Feedback uploaded. Please open an issue using the following URL:

https://github.com/openai/codex/issues/new?template=2-bug-
report.yml&steps=Uploaded%20thread:%20019a9b37-6ff6-7160-adee-4b0f8bb64173

The link is split across bug- and report. Pasting this link won't work without hand-tweaking it. This is a bummer for you guys!

What steps can reproduce the bug?

Uploaded thread: 019a9b37-6ff6-7160-adee-4b0f8bb64173

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

middleDuckAi · 5 months ago

I checked this on current main instead of assuming the historical report still matched the live code.

Repro

  • The original issue body shows a broken URL built around template=2-bug-report.yml that wrapped as 2-bug- / report.yml.
  • On current main, the external bug-report path now uses https://github.com/openai/codex/issues/new?template=3-cli.yml.
  • I could not reproduce the historical broken-link state from the current code path.

Current Main Verdict

  • The exact helper that builds the external bug URL already returns the full 3-cli.yml URL in both TUI surfaces.
  • That suggests this issue is already fixed upstream rather than needing another patch today.

Validation

  • CARGO_TARGET_DIR=/tmp/codex-target-7011 cargo test -p codex-tui issue_url_available_for_bug_bad_result_safety_check_and_other -- --nocapture
  • CARGO_TARGET_DIR=/tmp/codex-target-7011 cargo test -p codex-tui-app-server issue_url_available_for_bug_bad_result_safety_check_and_other -- --nocapture

Risk

  • Low confidence that a fresh code change would help here, because the current helper/test contract already covers the broken-link scenario described in the issue.
  • If someone can still reproduce this on a recent build, the next useful artifact would be a fresh screenshot or exact terminal output from that newer path.
etraut-openai contributor · 5 months ago

@middleDuckAi, please stop spamming this issue tracker with AI-generated slop.