How-to guides

Manage your projects

The Projects page lists every project as a nested tree with counts and last-opened dates. Create, pin, open and tidy from there; each project's settings page holds its instructions, files, defaults and sharing.

Projects are the folders your conversations live in, and the Projects page is where you look after them. Home's left panel shows a short list of them (pinned first); click "All projects" at the end of that list, or open the Projects page directly, to see the whole set.

What the Projects page shows

Every project you can open, as a nested tree. Each row carries the project's name, when it was last opened, and its conversation and branch counts. Sub-projects sit under their parents, and a pinned project floats to the top.

The first row is "Not in a project". That is where a conversation lands when you start one without picking a project, so it is the honest answer to "where did that quick question go". It is not a project of its own: it has no instructions, no files and no settings, just a count and a way in.

Each row has four actions:

  • New conversation starts a conversation inside that project, already briefed by its instructions and files.
  • Open shows the project's conversations and their branches.
  • Pin project (or Unpin project) moves it to the top of the list, here and in Home's left panel. Pin the two or three you are living in this week.
  • Project settings (the gear) opens the project's settings page.

Two buttons sit at the top of the page. "New project" creates one, and "Clean up conversations" opens Landscaper, which finds empty conversations and stale branches and removes nothing until you confirm.

Creating a project

"New project" is in three places: the top of the Projects page, the menu behind the arrow next to "New conversation" (on Home and in the left rail), and the project switcher in a conversation's header. All three open the same dialog: a name (required), a description, and an optional "Parent Project". Pick a parent and the new project nests inside it, which is how a client engagement holds a project per workstream. Name it after the work, not the tool.

The settings page

Project settings open as a page of their own, with the project's name in the address, so you can bookmark it or send a teammate straight to a tab. The tabs:

  • General: the name, description and parent project, the standing instructions the AI follows inside this project, and a default model and default persona for new conversations here. Changing the parent moves the project, conversations and all; the one rule is that a project cannot move under one of its own children. Save applies the General tab.
  • Files: the reference files the AI can use when replying in this project. Files save per action, and a file with a newer version elsewhere in your knowledge shows that under "Possible newer versions", with a version history when there is one.
  • Sharing (Team plan): make the project visible to everyone on your Team, or share it with specific people as viewers or editors. Viewers read; editors can send messages and branch. Everyone works from their own account and their own credits.
  • Danger zone: delete the project. This is the only place that button lives, and it asks first.

A Review tab appears on plans that include knowledge review, for choosing whether GPTree reads facts from the project's files and keeps its decisions and merges in your knowledge.

Moving a conversation between projects

Inside a conversation, the header shows the project it belongs to. Click it to switch to another project's conversations, or use the move option beside it to send the conversation, with all its branches, into a different project or out to "Not in a project". Nothing about the conversation changes except which folder it sits in and which instructions brief it from now on.

On a phone

The menu button opens a drawer with the same rail destinations across the top and Home's panel underneath, projects included. The Projects page itself works at phone width; the middle Open arrow is hidden there because tapping the row does the same thing.

Related reading