Scopes of Data
Scope of data decides which saved context is used for a chat. Every message you send is routed into either global scope or project scope, and that choice determines which memories and files the system can see. This keeps everyday chats, project chats, and persona chats cleanly separated so replies stay relevant and nothing leaks across boundaries you didn't intend.
Understanding scopes helps you organize your work: put sensitive or project-specific context in a project, keep general preferences in global, and use personas when you want consistent voice across both without merging the underlying data.
Global
Global scope is used when you chat outside any project. It draws from your account-level memories and account-level files—the context you've chosen to share across all everyday conversations.
Global scope does not pull in project-only details. If you have a project for work notes or a side venture, those memories and files stay out of your regular chats. This helps keep everyday conversations separate from focused project work, so you can switch contexts without worrying about cross-talk.
Project
Project scope is used when you chat inside a specific project. It uses that project's memories and files only—nothing from other projects or from your global account.
Each project stays isolated. Details from one project do not spill into other projects or into regular global chats. That isolation is intentional: you can have a project for a client, another for personal research, and another for a hobby, and each one keeps its own context clean.
Persona
Persona is a style layer that can be used in both global and project chats. It keeps voice, tone, and behavior consistent across spaces without merging the underlying memory or file stores.
Persona can travel across chats, while global and project memory spaces remain separate. You get continuity in tone—the same personality whether you're in a global chat or a project chat—without mixing private context. It's the best of both: consistent voice, strict data boundaries.
Files
Files follow the same scope rules as memories. Global files are available in global chats; project files are available only when you're chatting inside that project. There is no shared file pool that crosses scope boundaries.
Upload files where they belong: account-level docs for everyday use, project-specific docs inside the project. The system retrieves only the files that match the current scope when you send a message.
Customization And Scope Interaction
Customization settings are account-level and can be managed from Account in the Customization and Memories sections. The same options are also available in the chat account modal.
In regular chats, customization settings guide reply style—how the assistant structures responses, how formal or casual it sounds, and other preferences. When a persona is active, persona guidance takes priority so tone stays consistent for that persona across every chat.
Global chats continue to use global memory space, and project chats continue to use project memory space. Persona can move across both without merging those spaces. You get a single, coherent voice without blurring the lines between work and personal context.