[Feedback]: Confusing relationship between projects, chats, and sessions — terminology and sync between TUI/CLI and Desktop
@aliarain ci sta già lavorando.
Dal 13/8/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What problem are you trying to solve?
Summary
I'm confused about how projects, chats, sessions, and transcripts relate in the Desktop app, and how they map to (or fail to map to) CLI/TUI concepts. The naming and behavior feel inconsistent between surfaces, and sessions started in one place don't show up in the other.
Observations
- A project seems to be tied to a directory, and new chats appear underneath it.
- Opening a folder I've used before with the TUI/CLI shows no chats — chats appear to be tracked only from within Desktop and do not pull in prior TUI sessions for that directory.
- When I create a project for an existing directory, the prior chats are hidden under "History."
- Search shows "chats," but only project-associated chats appear — general/standalone chat items don't show up. Not sure if that's expected or stale data from very early Desktop versions.
- In 1.9 there's a terminal window. Launching
cmdinside it lets me interact with the same project/directory shown in the GUI, but sessions started (prompting/chatting) in that terminal don't appear in the project sidebar as chats.
Questions
- Is "project" a Desktop-only concept? Is there a CLI equivalent?
- Can I have a chat that isn't associated with a project? What's the use case?
- When does a new chat become "history"? Is a session "historic" just because its transcript predates the Desktop project — i.e. anything before project creation is history, and anything new is a "new chat"?
- Are the general chat items from older TUI sessions, or stray data from early Desktop versions?
What would improve it?
Expectations / friction
- Creating a project for an existing directory should find the sessions for that directory, giving comprehensive history.
- A session started in the in-app terminal (1.9) should show up in the project sidebar as a chat, since it's the same directory/project.
- Consistent terminology (project / directory / chat / session / transcript) and behavior across Desktop, TUI, headless, and future UI formats would make it much easier to move between surfaces.
What do you do today?
Use the CLI/TUI
BTW - Even here in "Project Area" for GH issues it refers to "projects and sessions" not "chats" so some terminology inconsistency demonstrated.
Product area
Projects and sessions
- Lingua principale
- Shell
- Stelle
- 110
- Fork
- 9
- Merge medio
- 12m
- PR unite (30g)
- 1
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CommandCodeAI/desktop
-
[Bug]: v0.1.61 fails to initialize preload script due to system memory information error on LinuxApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
CommandCodeAI/desktop#167 ·
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 56/100
CommandCodeAI/desktop#166 ·
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
CommandCodeAI/desktop#164 ·
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
CommandCodeAI/desktop#163 · 1 reazione ·
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
CommandCodeAI/desktop#162 ·
Tutte le issue di CommandCodeAI/desktop
Issue simili
-
S3: friction & debt ws:testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
MedakaLang/medaka#5184 ·
I maintainer di solito rispondono entro 1 giorno
-
Link Checker ReportApertaautomated issue report
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
a2aproject/A2A#2445 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
MadiroGlobalHealth/UVL-EMR#580 ·
I maintainer di solito rispondono entro 1 giorno
-
Storage with Nitro Sandboxes: clarify which CSI volumes are supported (third-party NFS volumes fail)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
awsdocs/amazon-eks-user-guide#1259 ·