[FEATURE] Claud Code Web: Better orgnaization

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Right now the ui is to select the repo and make each chat individually in one list of all session chats. But Github repositories are akin to projects in the Claude ui. We should be able to add a repository to work on first just like adding a project and then add multiple chats under that repository for better organization. This principle is already followed in the standard Claude UI so it shouldn't be that hard to implement.

Proposed Solution

Change ui to first select a repository project and then add chats that are grouped within that repository.
Add a plus button next to the repository so we can add chats under that specific repository project. Every new chat should still start a new session in a new feature branch

Alternative Solutions

Alternative UI: when selecting a repository, new chats are grouped under each repository automatically. Either UI would achieve the same organizational structure as projects where chats are properly grouped. The only issue with this is its not as easy to context switch.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

I want to manage chats across multiple projects simultaneously.

Current problem: since all new chats are connected to the last selected repository, when there are multiple repositories that need work, the user may accidentally start a chat for one repository that was meant for another because they forgot to change the repository designation.

If all chats are grouped, this becomes much less likely as users could have ui to specifically add a chat under a repository the way projects work

Additional Context

Just apply the logic behind projects to github repository projects