App Reliability, Project Management, and UI Issues

Open
#37,034 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
desktop

Research direction

The report names no repository file, test, or reproducible step beyond a feedback ID. Start by identifying which Codex app components own projects, usage limits, memory, and branding, then split the report into focused issues with expected behavior and reproduction steps. Done would require an agreed scope and a focused failing case.

Written by the indexing model from the issue text.

Description

app bug memory rate-limits session skills
What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.730.61639

What subscription do you have?

Business

What platform is your computer?

No response

What issue are you seeing?

The app currently feels unstable and inconsistent. I frequently have issues with plugins, skills, and projects. Projects often do not load properly in ChatGPT Work or even in regular ChatGPT, and I cannot move older chats into or out of projects.

The usage overview is useful, but it should provide clearer information about limits, remaining usage, and reset times. Memory management is also missing, since I cannot view or manage saved memories in the app.

The renaming itself was not a bad idea, but the branding is inconsistent. ChatGPT still refers to the app as “Codex,” and the feedback menu says “Feedback improves Codex.” This is confusing and makes the app feel unfinished.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019fd072-95dd-7e12-9c92-185a7b4bfe3e

What is the expected behavior?

No response

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.