For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/atlas/chat-scope.md.
Docs

Chat scope and context

Every conversation has a scope: either a specific project or the platform as a whole. The scope controls which data the assistant queries and, when it acts, which sandbox and credentials it uses.

Setting the scope

Opening the assistant while browsing any page within a project starts the conversation in that project's scope. The panel header shows the project name.

To change the scope, press the @ button in the composer. A picker appears with a Search projects... field and your projects listed below. Select a project to switch, or choose the Platform option (no project) to remove the project and ask across all projects. Pressing Remove project context on the chip above the input does the same thing.

The button's label tells you the current state: Add project context when no project is pinned, Change project context when one is.

Switching scope restarts the conversation. The previous transcript is saved and appears in the history menu under the old scope.

Pinned resource

When you open the assistant from an artifact, work item, or code file page, that resource is pinned as a chip above the composer. The chip shows the display identifier (for example PRD-001 or WI-042) and the title if available. The assistant treats the pinned resource as what you mean by "this" or "here" in your first message.

Press Remove project context on the chip to drop the resource from context without changing the project scope.

On a list or overview page, no resource is pinned. The project shown in the panel header is the full context.

How scope auto-resolves

When you have not pinned a scope explicitly, the assistant follows the current route. Navigating into a project page starts a project conversation; navigating back to a platform page reverts to platform scope. Pinning a scope by picking from the @ menu locks it for the rest of the conversation, regardless of navigation.

Closing the panel resets the pinned scope, so the next conversation starts fresh from wherever you are.

FAQ

Can I attach a project to a conversation I started in platform scope?

Yes. Press @ at any point and pick a project. The conversation restarts in that project's scope; the prior transcript is saved in history.

What happens if I navigate to a different project while the panel is open?

If you have not pinned a scope, the conversation scope follows the route. Navigating to a different project page switches the scope to that project on the next message. Pinning keeps the scope fixed regardless of where you navigate.