Manually selecting a project

What you'll learn

In this article, you'll learn how to manually scope a chat in Assist to a specific project. We'll cover what scoping means, why you'd do it, and how to set, change, or remove a project on any chat.

This is useful when you want to take control of where your outputs land and which project's knowledge the assistant uses — instead of relying on auto-detection.

What "manually selecting a project" means

Manually selecting a project means you explicitly tell Assist which project the current chat belongs to. Once a chat is scoped to a project:

Any outputs created in the chat are saved into that project automatically.
The project's knowledge is loaded into context, so the assistant can reference it when answering.
The chat itself is tied to that project for easy organisation later.

Assist will usually try to auto-detect the right project based on what you're discussing. Manually selecting overrides this — useful when auto-detection picks the wrong project, picks nothing, or when you just want to be deliberate from the start.

Why you'd manually select a project

Common reasons to scope a chat yourself:

You're starting work that clearly belongs to a specific project.
You want any outputs you create to land in that project without having to move them later.
You want the project's knowledge available to the assistant from the first message.
Auto-detection chose the wrong project, or didn't choose one.

Where to do it

You'll find the project selector in the chat — typically near the chat input or in the chat header. It shows the currently scoped project, or a placeholder if no project is selected yet.

Open the selector to see a list of projects you have access to, with a search box for finding one quickly.

What happens when you scope a chat

As soon as you select a project:

New outputs created from that point on are saved into the selected project.
The project's knowledge is loaded into the chat's context.
Earlier outputs in the same chat are moved into the selected project. Assist will let you know how many outputs were moved.

Changing or removing the project

You can change the scope at any time:

To switch projects: open the project selector again and pick a different one.
To remove the scope: open the selector and clear the selection. The chat will no longer be tied to any project.

If you change the project mid-conversation, earlier outputs in the chat move into the new project too.

Step-by-step: scoping a chat to a project

Open the chat you want to scope.
Click the project selector near the chat input or in the chat header.
Search or browse for the project you want to use.
Select the project. The chat is now scoped to it.
Confirm by checking that the project name now appears on the chat.

That's it — from this point, new outputs will land in that project, and its knowledge is available to the assistant. If there were already outputs in this chat, Assist will move them into the selected project and tell you how many were moved.

Tip: ask the assistant to do it for you

You don't have to use the selector. You can also just tell the assistant in natural language, for example:

"Let's work on Project X."

Assist will scope the chat to that project for you.

Tips and common pitfalls

Can't see the project you want? Check that you have access to it and that it exists in your current workspace. Projects from other workspaces won't appear in the selector.
Scoping doesn't restrict the chat. You can still talk about anything you like — selecting a project just sets the context and the default home for outputs.
Mid-conversation scoping moves earlier outputs. If you scope a chat after already creating outputs, those earlier outputs will be moved into the new project. Later outputs go there too.
Switching projects moves outputs again. If you change to a different project later, the outputs in the chat follow along.
Prefer auto-detection? You don't have to manually scope every chat. Manual selection is there for when you want to override or guide the assistant — for everyday work, auto-detection usually does the job.