Session-first instead of project-first

[kozak-codes]

Right now I spent a lot of time switching between machines, projects, workspaces to find sessions that need my attention. I often lose track of sessions because of this.

I think a better UX would be to list sessions first instead of projects | workspaces | sessions breadcrumbs

This would look like: A full list of all your sessions happening across all your projects, workspaces, and even machines. Show which ones are running, unread, etc. Allow pinning sessions. Underneath each session name show the machine | workspace | project

When you want to create a new session, click the plus button which allows you to select the project/workspace you want to do it in. Or add a "create session here" under the three dots to the right of the workspace for a faster new session flow.

We could also add filters to filter sessions by recent, machine, project, workspace, etc.

The only problem I see is accessing workspace terminals/tasks without a session. IMO this is solved by requiring a session in that workspace to access terminals.

In slack or any chat communication app we do not have this many "layers" of UX. Ideally, you want to limit it to at MOST 2 layers, otherwise the context gets too high. Currently we are at 3-4 (machine, project, workspace, session). Session would make it just one layer.

Thoughts? Would you be interested in seeing a prototype?