Focus issue in Codex
Bhavya shah
I am using NVDA with Codex by OpenAI. When vibecoding, after the session is long enough, I begin experiencing a major focus issue. Specifically, when I try to go from the edit box to the most recent response via up arrow, Ctrl+up arrow, or Shift+p (previous text paragraph), I land on a message way earlier in the chat history. I need to manually navigate down to the most recent response, wading through a ton of chat history to do so each time. Sometimes, there is a scroll to bottom button but pressing it through Space, Enter, NVDA+Enter, or a simulated left mouse click seems to have no effect.
Have you experienced this issue? How do you work around it?
Grateful for your advice,
Bhavya Shah
M.S. AI & B.S. Math/CS, Stanford University
Sarah Alawami
you should just be able to get to the heading level 4 which will be gpt's response. I use the app on windows.
I hope that helps.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CACHadJ0aS9b-uQ%3DmtpHRP5si7%2B%2B%2BzMx4KikCy_%3DZKS1PLS3TEA%40mail.gmail.com.
Mister Kayne
Also another trick is use the find feature of NVDA in browse mode. However, believe you can get to the responses using heading navigation. Same like how you would navigate the responses on Be My Eyes on Windows
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e9f72fc5-e39b-4171-9354-ba103f7fe3fc%40gmail.com.
Derek Riemer
* open wsl.
* install codex
* cd to the directory I need.
* you can even open vscode there if needed.
* install tmux.
* attach to tmux.
* you can review output with control+b then left bracket, "[" and
press "q" to get back to typing. control+j for new line.
--
Derek Riemer
Improving the world one byte at a time! ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
• Accessibility enthusiast.
• Proud user of the NVDA screen reader.
• Open source enthusiast.
• Skier.
• Personal website: https://derekriemer.com