What's missing. In the desktop app a chat can't be moved into a project after it was created, and there's no way to group chats in the sidebar from a tool. Other agent hosts allow both. An agent can create a new chat in a project (create_project + create_session + navigate_to), but it can't attach the chat it's running in. The folder can be changed from an extension (setWorkingDirectory, see #3035), but the sidebar doesn't follow: the chat stays under "Chats".
Why it matters. Long-running work often only finds out which folder or project it belongs to after the first messages. Starting a new chat loses the conversation; leaving it in place means the sidebar doesn't match where the work actually happens.
Request.
- A user action to move a chat into an existing project.
- A model-callable tool, e.g.
move_session_to_project(project_id), with the same consent rules as create_project.
- Optionally, a tool for the custom sidebar sections that currently seem to sit behind an experiment flag.
Seen in app 1.1.28 (Windows), CLI 1.0.94-3.
What's missing. In the desktop app a chat can't be moved into a project after it was created, and there's no way to group chats in the sidebar from a tool. Other agent hosts allow both. An agent can create a new chat in a project (
create_project+create_session+navigate_to), but it can't attach the chat it's running in. The folder can be changed from an extension (setWorkingDirectory, see #3035), but the sidebar doesn't follow: the chat stays under "Chats".Why it matters. Long-running work often only finds out which folder or project it belongs to after the first messages. Starting a new chat loses the conversation; leaving it in place means the sidebar doesn't match where the work actually happens.
Request.
move_session_to_project(project_id), with the same consent rules ascreate_project.Seen in app 1.1.28 (Windows), CLI 1.0.94-3.