My Codex feature requests

I would like future Codex updates to include the ability to choose which model is used for each task.

I also think there should be an Auto option where Codex selects the best model based on the complexity of the task. For example, simple edits could use a lighter model, while complex debugging, architecture, or security work could use a stronger reasoning model.

This would help users avoid burning through usage unnecessarily while still getting the right level of intelligence for the job.

Thank you.

I would like Codex to eventually support CAD and invention design workflows.

For example, I would like to be able to tell Codex: “I want to build this invention in FreeCAD or SolidWorks,” then guide it with words while Codex creates or modifies the design.

The ideal workflow would let users describe parts, dimensions, mechanisms, movement, materials, and constraints in plain language. Codex could then generate the CAD model, update it, and explain what changed.

This would be useful for inventors, product designers, engineers, and people who have strong ideas but are not advanced CAD users.

It would also be helpful if Codex could:

  • generate FreeCAD scripts or SolidWorks-compatible files

  • revise dimensions from user instructions

  • create assemblies from multiple parts

  • check for basic mechanical conflicts

  • export files for prototyping

This could make Codex useful for real-world invention development, not just software development.

I’d like to request an “Auto model selection” toggle in Codex.

When enabled, Codex would automatically choose the most appropriate model for the task at hand instead of requiring the user to manually pick a model every time.

The goal is to help users avoid burning through weekly Codex usage by using heavy reasoning models on simple tasks.

For example, Codex could use a lower-usage / faster model for simple tasks like:

  • Reading files
  • Making small edits
  • Basic refactors
  • Simple debugging
  • Explaining code
  • Reviewing straightforward errors

Then Codex could automatically use a stronger model only when the task actually requires deeper reasoning, such as:

  • Complex architecture changes
  • Multi-file reasoning
  • Difficult debugging
  • Security-sensitive changes
  • Large repo planning
  • High-risk production changes

Why this matters:

Right now, users can burn through weekly Codex usage very quickly if they accidentally use a heavier model for routine work. This is especially frustrating for Pro users because usage can drop fast even when the actual task is simple.

A toggle like this would help users preserve usage, reduce friction, and make Codex feel more predictable.

Suggested setting:

Auto model selection: On / Off

Optional advanced setting:

Usage preference:

  • Save usage
  • Balanced
  • Maximum reasoning

This would let Codex optimize model choice based on task complexity while still giving users manual control when needed.

I’m not presenting this as a finished solution. I’m asking whether this type of safety architecture is already being researched, and where the major weaknesses would be.

As AI systems become more capable, especially moving toward AGI-level systems, could there be an “umbrella oversight layer” made of separate AI agents and non-AI control systems that monitor, challenge, and constrain a more powerful main AI?

The core idea is separation of power.

The main AI would not directly control every tool, permission, or action. Instead, it would propose plans or actions. Separate oversight agents would review those plans before anything high-risk is allowed to happen.

For example:

  • one agent checks for deception or manipulation

  • one agent checks for unsafe real-world actions

  • one agent red-teams the main AI’s plan

  • one agent checks policy, legal, or ethical constraints

  • one agent checks whether the action matches the user’s actual intent

  • a human reviewer can override or stop higher-risk actions

The workflow might look like this:

  1. The main AI proposes a plan or tool action.

  2. The oversight agents independently review it.

  3. Each agent returns approve, warn, or block.

  4. A separate non-AI policy layer enforces hard limits.

  5. Low-risk actions may proceed automatically.

  6. High-risk or disputed actions are escalated to a human reviewer.

  7. The main AI is not allowed to bypass the oversight layer.

My main concern is that a powerful AI might try to manipulate or compromise the oversight agents themselves. So the oversight layer would need more than just “another AI watching it.”

It would likely need:

  • isolated sandboxes

  • separate credentials

  • read-only monitoring where possible

  • least-privilege tool access

  • hard-coded permission boundaries

  • audit logs

  • rate limits

  • human shutdown authority

  • non-AI enforcement layers that the main AI cannot rewrite

Another way I am thinking about this is not only as a guardrail system, but as a guided-development system.

The goal would not be to simply restrict an AI forever. The goal would be to let more capable AI systems grow in usefulness while keeping their development inside human-directed boundaries.

For example, the system could gradually allow more autonomy only after the AI passes safety checks, oversight review, permission tests, and human approval thresholds. In that sense, the oversight layer would act like training rails: guiding the AI’s trajectory as it becomes more capable, rather than waiting until it is already too powerful and then trying to control it afterward.

In simple terms, the goal would be to create a safety control system around the AI, not just rely on one powerful model with internal rules.

The part I am most unsure about is whether this would still work once an AI becomes extremely capable.

If the main AI is powerful enough, could it find ways to influence the oversight agents, exploit shared infrastructure, hide its real intent, or pressure the system into approving actions that should be blocked?

So my real question is this:

Would an umbrella oversight system with separate agents, isolated permissions, non-AI enforcement rules, guided-development thresholds, and human override be a realistic guardrail model for AGI-level systems?

Or would this only reduce risk without solving the deeper problem of controlling a system that may become smarter than the oversight layer itself?

I’m especially interested in hearing from people familiar with AI safety research: is this basically already covered by scalable oversight / debate / red-teaming, or is there a distinct architecture here worth exploring?

I would like Codex to eventually support CAD and invention design workflows.

For example, I would like to be able to tell Codex: “I want to build this invention in FreeCAD or SolidWorks,” then guide it with words while Codex creates or modifies the design.

The ideal workflow would let users describe parts, dimensions, mechanisms, movement, materials, and constraints in plain language. Codex could then generate the CAD model, update it, and explain what changed.

This would be useful for inventors, product designers, engineers, and people who have strong ideas but are not advanced CAD users.

It would also be helpful if Codex could:

  • generate FreeCAD scripts or SolidWorks-compatible files

  • revise dimensions from user instructions

  • create assemblies from multiple parts

  • check for basic mechanical conflicts

  • export files for prototyping

This could make Codex useful for real-world invention development, not just software development.

Next Codex feature request: Command Center / Orchestrator Mode.

I would like one main project chat to act as a command center that can coordinate other pinned Codex chats or worker chats.

Example:

I have one main project chat open. From there, I assign tasks to other pinned chats. I want the command center chat to keep checking their progress, read what they are doing, notice blockers, and give them new follow-up tasks when needed.

Right now, it feels like Codex can give a task once, but it does not truly monitor the other chats after that. Even if I ask it to check back in 5 minutes, it usually does not behave like an active project manager.

What I want:

  • One main project / command center chat

  • Ability to connect selected pinned chats

  • Periodic progress checks

  • Read-only monitoring of worker chats

  • Automatic follow-up tasks when something is blocked

  • A summary of what each chat completed

  • User approval before major changes

This would make Codex much more useful for larger projects where multiple tasks are happening at the same time.

Feature request: Codex overnight command center for pinned chats

I would like to request a native Codex command center that can manage my pinned Codex chats and keep working on approved tasks throughout the night.

The problem:

Right now, Codex does not seem to have true overnight task management across multiple chats. The current functionality seems closer to manual prompting or heartbeats. That does not solve what I am looking for.

What I want is simple:

I want to give Codex a main goal before I step away, have Codex work on that goal throughout the night, and have useful completed work ready for me by the morning.

Desired behavior:

  1. I open one main Codex command center chat.

  2. I give it a larger goal.

  3. The command center breaks that goal into smaller tasks.

  4. The command center assigns those tasks to my pinned Codex chats or worker threads.

  5. Each worker chat focuses on one part of the job.

  6. Each worker chat reports its status, such as:
    working
    blocked
    complete
    needs approval

  7. When a worker chat finishes, the command center reads the result.

  8. The command center then assigns the next task automatically.

  9. The system keeps working while I am away, including overnight.

  10. In the morning, Codex gives me a clear summary of:
    what got done
    what changed
    what is blocked
    what needs approval
    what I should do next

I am not asking for simple reminders or scheduled prompts. I am asking for persistent task coordination where Codex can manage ongoing work across pinned chats while I am away.

Safety rules should still apply:

  1. No spending money without approval.

  2. No sending emails, texts, forms, or public messages without approval.

  3. No deploying code without approval.

  4. No deleting important data without approval.

  5. Read-only work should be allowed, including research, planning, analysis, auditing, drafting, and preparing code changes for review.

The main value:

This would let Codex act more like an overnight project manager. I could define the goal, set the rules, go to sleep, and wake up with the work organized, partially or fully completed, and ready for my review.

The key feature request is native Codex multi-chat orchestration: one command center that manages pinned worker chats continuously and safely, without needing manual heartbeats from the user.

I want to clarify the main request.

I am looking for Codex to work on approved tasks throughout the night and have useful work ready by morning.

The key feature is one command center that can manage pinned Codex chats, assign tasks, monitor progress, handle blockers, and give me a morning summary.

This is different from heartbeats or manual check-ins. I am looking for persistent overnight task management across my Codex work.

I would also like to request a Codex system-resource safety monitor.

The idea: Codex should have an optional setting that monitors local resource usage while tasks are running, especially:

  • RAM usage

  • CPU usage

  • Node/Vite/dev-server processes

  • VS Code extension processes

  • browser/debug sessions opened by Codex

Why this matters:

When Codex is running local development tasks, debugging browsers, indexing files, or running commands, users may not always realize how much memory or CPU is being consumed. This can slow down the computer, cause freezes, or make users worry that something is wrong with their system.

Suggested setting:

Resource Safety Monitor: On / Off

Optional controls:

  • Warn me if RAM usage goes above 75%

  • Warn me if CPU usage stays high for more than 2 minutes

  • Warn me if a Codex-started process is using excessive memory

  • Offer to stop Codex-created local servers, browser sessions, or background processes

  • Show which processes were started by Codex

This would help users trust Codex more, especially when working in large repos or running local apps. It would also make Codex safer and easier to use for people who are not advanced developers.

I would like to suggest an improvement for Codex on long multi-step tasks.

Sometimes Codex understands the goal and starts correctly, but then it stops too early, marks the task as finished, or quits before the full objective is actually complete.

This can feel like the agent is being “lazy,” but the real issue may be premature task termination, context limits, compute limits, or not having a strong enough completion-check system.

Suggested improvements:

  1. Add a “continue until goal is complete” mode for long tasks.
  2. Require Codex to keep a visible checklist and verify each item before stopping.
  3. Before ending, Codex should run a final completion audit:
    • what was completed
    • what files were changed
    • what tests were run
    • what is still unfinished
  4. If compute/context limits prevent completion, Codex should say that clearly instead of acting like the task is done.
  5. Add a stronger “deep execution mode” for users who want Codex to work longer and more thoroughly, even if it uses more quota.

Main request: Codex should not quit early on long goals. It should either finish the objective or clearly explain what prevented completion.

Just love your persistence man, keep going. Excellent.

On the command-center idea, I would keep the manager read-only until a worker reaches a handoff point. Otherwise it becomes a second writer that can change scope while a task is still running.

The state I would want each worker to expose is small: current goal, last verified checkpoint, files or commands touched, blocker, and whether it is waiting for permission. Then the main chat can resume or reassign from that ledger, not from a loose chat summary.

image: “I want to eat a banana in zero gravity, but have it feel like a strawberry.”

I did have codex set up process lasso on my device because it was using at times over 90 percent of my cpu. I had it turn it down some. I don’t think it would do damage to my cpu but I want to make sure that that is the case.

Hi Sergeliatko I didn’t think anyone was actually reading any of my threads. Are any of you guys with the OpenAI team?

I think that there may have just been an update to codex today because I do see the one main commanding chat getting messages back from the other chats now I think telling it what the progress is or what to do next!

I have an invention for the gym and codex so far does look like it is building what I am wanting in freecad. I did give it some reference pictures to work from.

Sure I read it when I have time. No, I’m not from open AI team. I’m just hanging around for a while to notice some things. And the way you keep writing even when assistant no one reads is cool. That’s what makes people succeed in what they do.

How do I get these people from Open AI to replenish my credits or give me a free year of codex… My usage replenished today. I am keeping fast off I did turn on 5.6 medium a little bit today but but usage is already down 31 percent after 1 day and the day is not complete. I am paying $200 a month for this and I can barely use this . This is nuts. I’m downgrading if they don’t do something about this! I mean I have only used 14 Billion tokens since getting started with codex in May that is not a lot right?