Before submitting
Area
apps/desktop
Problem or use case
I want to use e.g. pnpm run dev when I start working on the project, and I still want to be able to find it quickly when I am working in multiple chats. Currently I would have to open a dedicated terminal app or try to find the chat where I created the "persistent" terminal.
Proposed solution
Like the new chat button next to the project, there would be a new terminal button.
This button will open a new terminal tab, and the new terminal button switches to an open terminal for given project.
Why this matters
Those who do not want to open another terminal app, just to have a long running terminal session for a project.
The user can have short lived (chat based) terminal sessions and long lived project terminal sessions
Smallest useful scope
use the existing chat based terminal tab.
If the user is currently in a chat for the project, then open the tab and point it to the terminal session for the project.
If the user is currently in a chat in another project, open a new chat for the targeted project and open the terminal session for the project.
Add a small title or other indication to show the user that it is a project and nor chat based terminal session
Alternatives considered
Currently I need to find the chat terminal session, where I started the long running npm run dev command. Which is doable bu a hassle.
I can also open a terminal app and create the session in there instead.
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/desktop
Problem or use case
I want to use e.g.
pnpm run devwhen I start working on the project, and I still want to be able to find it quickly when I am working in multiple chats. Currently I would have to open a dedicated terminal app or try to find the chat where I created the "persistent" terminal.Proposed solution
Like the new chat button next to the project, there would be a new terminal button.
This button will open a new terminal tab, and the new terminal button switches to an open terminal for given project.
Why this matters
Those who do not want to open another terminal app, just to have a long running terminal session for a project.
The user can have short lived (chat based) terminal sessions and long lived project terminal sessions
Smallest useful scope
use the existing chat based terminal tab.
If the user is currently in a chat for the project, then open the tab and point it to the terminal session for the project.
If the user is currently in a chat in another project, open a new chat for the targeted project and open the terminal session for the project.
Add a small title or other indication to show the user that it is a project and nor chat based terminal session
Alternatives considered
Currently I need to find the chat terminal session, where I started the long running
npm run devcommand. Which is doable bu a hassle.I can also open a terminal app and create the session in there instead.
Risks or tradeoffs
No response
Examples or references
No response
Contribution