Codex needs better long-session project continuity and context transition UX

Welcome to the forum!

Oscar2020:

The problem is project continuity

FYI

I have been using ChatGPT Pulse to reivew the commits for Codex and give me daily updates. The reasong being I have been watching the Codex commits manually for many months and there are too many to read, so I have ChatGPT analyze them and report back.

Todays report, similer to many for the last few weeks notes

The direction increasingly suggests:

• isolated runtime identities,
• dynamic workspace mounting,
• multi-root execution,
• safer agent orchestration,
• and enterprise/team-oriented execution models.

and then notes many additial focus areas, one being

Shared execution/runtime infrastructure keeps consolidating

The ToolExecutor consolidation still looks strategically important.

Key commits:

• feat: extract shared tool executor interface (#22359)
• Refactor extension tools onto shared ToolExecutor (#22369)

This likely means:

• standardized execution lifecycles,
• centralized orchestration semantics,
• and reduced duplication across:
  • app-server,
  • plugins,
  • MCP tooling,
  • desktop integrations,
  • and remote/mobile execution surfaces.

The repository increasingly resembles:

• a generalized developer-agent runtime platform.

Notice: centralized orchestration semantics

HTH