I would love to see a non idle sessions group on the main navigation left panel.
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 2.1k
- Forks
- 153
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
I would love to see a non idle sessions group on the main navigation left panel. This sholud be filterable same way as sessions but should noly show awaiting input / recently idle / finished sessions / WIP. this could also be a preset for or filterable thing for the normal sessions section. I guess the main goal I want to express here, I need a way to see my interesting and point of interest sessions somehow without needding to scroll through my 20 projects until i find a session that is currently WIP or waiting for input. like make it usable, i dont want to always move arround repos or want to archive everything always. Give us a way to sort or split or properly filter sessions. Like this is one of the main resopnsibilities now and in the future for this product: "How do we enable many many paralel agents to be managed effectivly" and this is clearly not solved, here. Anyhow love to use the app, even as deeply technical persion i find this the perfect harness for deeply diving into sub-sub agents etc.
Other things to optimize for the tech heavy analysis tasks:
Provide a way to show session data folder similar to file canvas.
Provide all path based tool renderings with the option to copy the path or open in vscode / insiders...
Like make it even more usable in the real real world scenarios i would love to adopt this fully.
---
| Field | Value |
| --- | --- |
| App version | 1.1.2 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 4 |
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le point d’entrée /chat et examinez comment la navigation principale répertorie et filtre les sessions entre les dépôts. Définissez le périmètre avant l’implémentation : le groupe demandé de sessions non inactives, les états des sessions et les actions facultatives de chemin et de VS Code sont des idées distinctes ; le travail devrait être considéré comme terminé lorsqu’il inclut un comportement de filtrage ou de regroupement convenu permettant de trouver les sessions actives sans faire défiler.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- github
- Domaine
- desktop
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100