Replies: 1 comment
|
Closing as a duplicate of #6869, which tracks chats / sessions without a project (Codex-style “No project” / quick chat). #6891 was already folded into that thread. Please +1 / fold any extra acceptance criteria (neutral workspace, no project AGENTS.md inheritance, clear this-device destination) into #6869. Related implementation in progress: #10702 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
feat(sessions): start a session without a project folder
Summary
Add a simple “No project” option when starting a T3 Code session, so users can begin unrelated work without selecting a folder or inheriting the previously selected project's context.
Problem to solve
In my current workflow, opening an existing thread and pressing Shift+Command+N starts a new session in the same project folder. That is convenient for related work, but I often want a fresh session for something unrelated. The selected thread may also belong to a project on another Mac, making its folder and device an inappropriate starting point.
The workaround is to go through “New project” → “This device” → “Local folder”, then choose a folder I know does not contain project-specific agent instructions. This requires unnecessary navigation and makes me maintain or remember a neutral folder just to start a general-purpose conversation.
Proposed behavior
Provide a readily accessible “No project” or “Don't work in a project” choice in the new-session flow. For example, users could clear the selected project with an × control or choose “No project” from the project picker. These are possible UI treatments for the same capability; both are not required.
Once selected, the new session should be visibly independent of the previous project. Starting it should not require creating a project, browsing for a directory, or manually finding a folder without project instructions. If the provider requires a working directory, T3 Code can manage a neutral workspace behind the scenes.
The session must not inherit the previously selected project's folder-specific agent instructions, such as AGENTS.md or instructions associated with its .agents directory. A neutral workspace must also avoid inadvertently loading unrelated project instructions through its location. Normal user-wide or provider-wide instructions can still apply.
When the previous thread belongs to another device, make the destination device clear and allow starting the no-project session on this device without navigating through project creation.
Acceptance criteria
Affected area
New-session creation, project selection, and device selection.
Non-goals
Changing existing threads' project associations, disabling user-wide agent instructions, or prescribing how providers store no-project sessions internally.
Alternatives considered
Manually selecting a neutral folder works, but retains the project-creation and directory-selection steps that this feature should remove.
Supporting context
The supplied Codex screenshot shows a “Don't work in a project” entry in its project picker. A similarly direct choice in T3 Code would address this workflow. The T3 Code behavior above is based on the reported user experience, rather than independent reproduction against a specific build.
All reactions