Cannot submit a prompt depending on its context

Resolved 💬 7 comments Opened Nov 25, 2025 by aehlke Closed Mar 16, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.63.0

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

_No response_

What issue are you seeing?

I copy/pasted a line from my Xcode logs and tried to submit it, but it just says "loading..." beneath it and then if I backspace one char it says "no matches" and if I press enter again it says "loading..." again...

The line: [ERROR] [JS] Error: Can't find variable: perfStart @ ebook://ebook/load/local/Books/%E7%BE%85%E7%94%9F%E9%96%80%20-%20%E8%8A%A5%E5%B7%9D%E9%BE%8D%E4%B9%8B%E4%BB%8B.epub:-1:-1 — error: @ebook://ebook/load/viewer-assets/foliate-js/paginator.js:2776:34

Maybe the @ trips it up? Especially since I pasted the entire line without typing it out, it seems particularly bad to treat the @ as an autocompletion query

What steps can reproduce the bug?

Paste this into Codex CLI and then try to press enter - you will see it say "loading..." and it won't let you submit:
[ERROR] [JS] Error: Can't find variable: perfStart @ ebook://ebook/load/local/Books/%E7%BE%85%E7%94%9F%E9%96%80%20-%20%E8%8A%A5%E5%B7%9D%E9%BE%8D%E4%B9%8B%E4%BB%8B.epub:-1:-1 — error: @ebook://ebook/load/viewer-assets/foliate-js/paginator.js:2776:34

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 7 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#5839
#6915

Powered by Codex Action

aehlke · 7 months ago

🧩 Bug report: @ mention in Codex CLI always returns “no matches” #5839 Codex CLI reference file completions remove @ sign and make completion more convenient #6915

These are not dupes

Priya-753 contributor · 7 months ago

You are right, the @ symbol gets interpreted as a file-lookup/autocomplete trigger, which causes the UI to hang on “loading…”.

If you type one extra space after pasting, it breaks the token and prevents the system from treating the @ as part of a path it should resolve. After that, the message submits normally.

So there may not be anything to fix here.

aehlke · 7 months ago

Thanks. Yes I was able to find a workaround. But it is not obvious what is broken - I didn't even notice immediately that the pasted text contains a "@", and the message beneath is simply "loading..." which never ends. There are certainly ways to improve this experience (which I think should not be triggered anyway if the text is pasted in - or in this case, the @ has a space after it too, which normally stops the autocomplete from triggering, so it is suspicious that it treated this as an autocomplete)

Priya-753 contributor · 7 months ago

The second @ doesn't have a space after it

etraut-openai contributor · 4 months ago

This bug hasn't received any additional posts in four months, and the Codex CLI has changed significantly since then. Is it still an issue?

aehlke · 4 months ago

seems fixed