Projects

A project is the box round one initiative's work: one client, one product, one house move. Say "make me a project for Halton" and Player One creates it, gives it its own working file area, switches you into it and opens a fresh chat already assigned to it.

From then on, what you do while Halton is selected belongs to Halton. Your chats, agents, files and automations narrow to it, and the assistant works with Halton's knowledge in front of it rather than everybody's.

What belongs to one

Every chat sits in exactly one project, and whatever an agent makes in that chat lands there too. A project holds:

• Chats, and the folders you group them into.
• Agents. One agent can belong to several projects at once, and adding it to a project brings its own memory and files with it. Your main assistant and the system agents are in every project already.
• Workspaces. Each project gets its own working file area from the moment it is created, which is where a job puts its files unless it is told otherwise.
• Memory Spaces connected as knowledge, so an agent searching for background finds this client's and not the others'.
• Jobs, flows and scheduled tasks. A job or a scheduled task lives in one project at a time, so putting one somewhere else moves it.
• Contact lists, though the contacts inside them stay shared.
• Skills owned by the project, which beat a site-wide skill of the same name for anyone working inside it.
• Standing instructions, one file that every agent and chat in the project reads.

Your AI accounts, your models, the vault, your account settings and your site-wide skills and instructions belong to the whole installation. Choosing a project never changes which AI you are talking to, and passwords in the vault keep their own access rules wherever the work goes. Anything unfiled lives in Default Project.

A project organises; it is not a security wall. Organising with projects covers when to make one and what that distinction means in practice.

The selector at the top

The project you are in sits at the top left of every page: an avatar, and beside it the name with a chevron. The avatar opens the Dashboard (/dashboard). The name and chevron open the picker, where you search your projects, pin the ones you use daily, open the current one, or create a new one from the footer.

The first option is All projects, a browsing mode rather than a project. Every list widens to the whole installation. Nothing has a project while you are in it, so New chat and the Project menu row are hidden, and anything that would have to be filed somewhere is unavailable until you pick a project again. The control turns dark red so the wider scope is unmistakable.

The Manage Project page

Manage > Project (/project) manages whichever project is currently selected. There is no address for a particular project and no list page: you switch in the header, then manage the one you are in. It has seven tabs.

• Overview (/project) is the project itself: name, description and avatar edited in place, headline counts, recent chats and a list of everything it holds. The avatar takes your own logo, a searchable icon or plain initials.
• Agents (/project/agents) adds and removes agents.
• Automations (/project/automations) carries jobs, flows (/project/automations/flows) and scheduled tasks (/project/automations/scheduled-tasks), with Move here for the two that belong to one project at a time.
• Resources (/project/manage) holds contact lists, and the project's own skills at /project/manage/skills.
• Knowledge (/project/knowledge) is what the project may search: shared Memory Spaces here, workspaces at /project/knowledge/workspaces, each connected as Use as knowledge or Use and update.
• Instructions (/project/instructions) is the standing instruction file for this project, read on every turn by every agent in it.
• Advanced (/project/advanced) is deletion. It shows what would be affected, asks where the work should go instead, and hands the rest to a logged review that waits for your confirmation before writing anything.

For the steps, see Organise work with projects. For what the pieces themselves are, see Agents, Workspaces and files and Memory.