Working with multiple projects
Projects are how Magister keeps contexts clean. Each one has its own agent memory, files, connections, and workflows — nothing crosses the boundary.
Use a separate project when:
- You're managing distinct brands (different names, different voices, different audiences)
- You're running work for different clients and need to keep their data apart
- You want to run different products or landing sites with different analytics and CMSs
- You want to test the agent on something without contaminating a live brand's memory
Keep it in one project when:
- It's the same brand, same tools, same audience — even if it's multiple campaigns
- The agent will benefit from the shared context (past chats, uploaded files, prior drafts)
Switching — use the project switcher in the app header. Switching changes which agent you're talking to, which chat history you see, which files you have access to, and which integrations the agent can use.
Billing impact — your team plan includes one project. Each additional project adds to your monthly price and credit allowance. See Plans and Adding projects.