Artifacts on the screen, screen redraw partially fixes it

Open 💬 4 comments Opened Feb 11, 2026 by kucharskim

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

What version of Codex CLI is running?

codex-cli 0.94.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.2-codex

What platform is your computer?

OpenBSD 7.8-current (GENERIC.MP) #234: Wed Feb 4 13:18:55 MST 2026, amd64

What terminal emulator and version are you using (if applicable)?

XTerm/OpenBSD(403)

What issue are you seeing?

Random artifacts, leftover random letters on screen. I was looking for equivalent of CTRL+L to redraw the screen. See attached screenshot.

Here is copy paste, plain text:

    194  if __name__ == "__main__":
        ⋮
    197      cfg = load_config(args.config)
    198 +    fetcher = MockFetcher(args.current) if args.current else None
    199 +
    200      if args.hostdisiNone:
        ⋮
    203              print_host_info(hostname,pall_info[hostname])
  [… 66 lines] ctrl + a view all

What steps can reproduce the bug?

It shows up randomly over time, when I work with it. I don't have specific reproduction step.

What is the expected behavior?

No artifacts on the screen.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 6 months ago

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

#11438
#11425

Powered by Codex Action

etraut-openai contributor · 6 months ago

My guess is that this behavior is specific to XTerm on OpenBSD. We don't have many users with this configuration. As such, this is likely going to be a low priority for us to investigate. If you'd like to clone the repo and do your own debugging and diagnosis, we'd welcome any findings.

dagelf · 5 months ago

Depending on the exact cause, this might be part of the solution https://github.com/openai/codex/issues/5259

etraut-openai contributor · 4 months ago

Are you still seeing this issue with the latest release (0.118.0)? We've rewritten large parts of the TUI since this was reported, so it's quite possible this bug no longer repros.