[Feature]: Add standalone terminal sessions not tied to a project

[isaachorowitz]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the request.

Area

apps/desktop

Problem or use case

I want to use a terminal in T3 Code without first opening or selecting a project. This would be a general-purpose shell session, similar to opening a terminal app, rather than a terminal whose working directory and lifecycle are tied to a project or thread.

Expected behavior

Allow users to create a standalone terminal session with:

• A user-selected or default working directory.
• A normal shell process and environment.
• No required project association.
• The ability to open additional standalone terminal tabs and close them independently.

The existing project terminal behavior should remain unchanged.

Smallest useful scope

Add a “New standalone terminal” action from the terminal UI or command palette. Let the user choose the initial working directory, defaulting to the home directory if no directory is selected.

Why this matters

Many shell tasks are not project-specific: navigating the filesystem, managing multiple repositories, running system commands, or doing quick checks. Requiring a project context adds unnecessary friction.

Contribution

• I would be open to helping implement this.