A web page takes up a 16:9 area, with chat and a session list beside it. This is a concrete vision of a working interface—and enough to make someone consider a 5K ultrawide display.
The need came from using the browser built into Codex: web pages still need enough width, and the conversation needs to stay in view. When the browser and the agent share one window, the space that used to belong mostly to web pages has to be renegotiated.
A wider screen really can show all these areas at once. But whether the workspace feels right also depends on where windows appear, and how the pages in front of you relate to what you are doing.
Web pages and conversation start competing for space
Using a browser on its own, a page can occupy most of the window. Add a chat area and a session list, and keeping the page at its original width means widening the layout on both sides—or, if the total width stays fixed, compressing one of the areas.
In that layout, a wide screen has a clear purpose: view a page on one side, converse with the agent on the other, and switch back and forth less. That explains why a change in how software is used leads to thoughts of buying a new display.
Keeping every area open at all times, though, makes the interface feel crowded. Feedback on this kind of usage includes both wishes for more screen width and complaints about areas taking up room and windows being split and merged repeatedly. They reflect the same interface under different ways of working.
For work that needs a page and a conversation visible together, more horizontal space may help; if the window arrangement changes often during work, width is only one factor.
Where a window appears needs to be predictable
More disruptive than a shortage of space is clicking a link and not knowing where the page will show up.
Two situations came up in this experience: a page sometimes opened in the side browser, sometimes in a separate window. The merged-versus-split state changed too. The user had to deal with the page’s content while also relocating windows and re-understanding their relation to the current session.
Such problems do not disappear when the screen gets wider. An ultrawide display can hold more areas; window behavior still has to be stable. Only when the outcome of each action can be expected does the extra space become easy to use.
So evaluating an interface like this means looking beyond whether pages and chat fit side by side: can work continue smoothly when you open a link or switch pages?
Which task should a tab follow?
Once the browser enters the agent, the relationship between tabs and projects deserves reconsideration too.
If a piece of work already has its own project and sessions, its web pages still live in a separate tab list, and the user has to maintain the connection between the two. Putting the browser inside the same application only brings the surfaces closer together.
The deeper idea is letting tabs link to projects: switch to a piece of work, and its conversations and pages can be found as one group. The project provides the organization, the tabs hold the actual pages, and together they form the context of that work.
What is discussed here is a workspace design, not a complete capability that shipped at the time. Its value lies in reducing the split between two management systems, letting pages be organized by task instead of merely occupying another visible area.
This can happen alongside a wider screen. Width makes more content visible at once; project linkage makes that content relate to each other. With both space and organization in place, the browser and the agent start to form a coherent experience.
From browsing pages to organizing pages around tasks
Adding an AI assistant to a browser and adding a browser to an agent start from different points.
The former builds on existing browsing habits, adding an entry point to ask questions or get help beside a page. The latter starts from tasks and conversations, treating pages as things to open, view, and operate while getting work done.
Both routes may end up putting pages and chat together, but the organizational center of gravity differs. For task-centered usage, whether projects, sessions, and tabs can work together matters more than adding another chat panel.
Standalone browsers still have their place. Watching videos, scrolling feeds, and reading articles do not all require setting up a task first. In-task page operations and everyday content consumption can keep separate entry points.
The urge to buy an ultrawide display therefore offers a concrete angle of observation: as agent capabilities enter daily use, even what belongs on screen—and where—starts to change. Pages, conversations, and tasks can share one screen; the next product question is how to make them all belong to the same piece of work.