Jerry Liu: Each Tab Lacks Features That Would Be Nice in a Unified Interface
TL;DR · AI Summary
Jerry Liu points out that tools like Cowork lack thread fork and Code lacks Projects, advocating for integrated interfaces; Codex offers better UX as a reference.
Key Takeaways
- Cowork lacks thread fork, limiting collaborative editing
- Code lacks Projects concept, causing structural confusion
- Codex has better interface integration, serving as an optimization model
Outline
Jump quickly between sections.
Jerry Liu notes current tools like Cowork and Code operate in isolation, lacking cross-functional integration and causing user friction.
Cowork lacks thread fork; Code lacks Projects — both hinder project organization and collaboration.
Codex provides superior interface integration and unified experience, cited by the author as a benchmark for improvement.
Mindmap
See how the topics connect at a glance.
查看大纲文本（无障碍 / 无 JS 友好）
- 多工具功能整合缺失问题
- 当前工具缺陷
- Cowork 缺乏 fork 功能
- Code 缺乏 Projects 概念
- 用户诉求
- 希望界面整合减少切换成本
- 期待统一协作与项目管理体验
- 参考方案
- Codex 的整合设计更优
Highlights
Key sentences worth saving and sharing.
Why doesn't Cowork have a `fork` feature on threads? — this limits collaborative editing and versioning in shared contexts.
Code lacks a 'Projects' concept like Cowork — making it harder to organize codebases, collaborators, and workflows in a unified way.
I've been loyal to Claude but it would be really nice to have these tabs be consolidated — Codex is a lot nicer in that regard.
- why doesn't Cowork have a
forkfeature on threads? - why doesn't Code have a concept of "Projects" like Cowork?" / X
One annoyance is each tab is missing features that would be really nice to have in a combined interface - why doesn't Cowork have a fork feature on threads? - why doesn't Code have a concept of "Projects" like Cowork?
Quote
Jerry Liu
@jerryjliu0
May 30
I've been loyal to Claude but it would be really nice to have these tabs be consolidated Codex is a lot nicer in that regard
