Codex CLI 0.171: the TUI workspace is now on by default.
Ctrl X then t opens the sidebar:
• side chats (/side): multiple tabs, saved with the session, back after `codex resume`
• click any path:line Codex mentions → source opens on that line
• Markdown preview with / search, images rendered inline
• live subagent status
Try it and send me your feedback and sharp edges.
if you find yourself wanting to prompt subagents directly, try using thread tools laterally instead. in both research and product philosophy our stance is that codex subagents are purely a utility for the agent.
when releasing codex CLI we don't use semver:
0.X.Y[-alpha.Z]
0 = always 0 so far
X = increments tues/thurs (new schedule)
Y = increments per hotfix/backport to 0.X.0
Z = increments arbitrarily as we move to stable 0.X.0 (alphas)
are people okay with this? does it make sense?
@Caust1c i like the simplicity! does this mean we'd be naming releases for the day we expect them to reach stable? (for us, one week after its alpha is cut)
also if a stable release get delayed, does that cause confusion with version numbers becoming offset until the pipeline clears?
good system design can prevent a thousand papercuts. but the cost of fixing papercuts is going to zero, so the incentive for good design is too.
the papercuts still cause user grief. are we missing an incentive to prevent them? or is this the new way