I would love to see a non idle sessions group on the main navigation left panel.
- 主要言語
- 言語のデータがありません
- スター
- 2.1k
- フォーク
- 153
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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 |
コントリビューションガイド
調査の方向性
Start at the /chat entry point and review how the main navigation lists and filters sessions across repositories. Define the scope before implementation: the requested non-idle group, session states, and optional path and VS Code actions are separate ideas; done should include an agreed filtering or grouping behavior that makes active sessions discoverable without scrolling.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github
- 領域
- desktop
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 静か
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 35/100