Skip to main content

​
Chats

The Studio's full window. The sidebar has a Search chats box, Mine, Shared and Bookmarks tabs, a Projects list with one project expanded to its chats, a New project button, and a long All chats list below it, ending in the account row and credit balance. Two pinned topics sit above the thread. The thread itself shows two AI-generated photos of a ceramic cup on a sunlit concrete ledge, the first captioned with the model that made it; the thread continues past the bottom of the screen. The composer at the bottom carries an Agent and Manual switch, a model selector, attachment and web-search buttons, and an estimated cost.

A chat: the thread in the middle, your chats and projects on the left, and the model, mode and running cost along the composer

A chat is a threaded conversation with a model. Every message you send creates or extends one. Each chat has:
  • An auto-generated title (from the first user message)
  • A model (can change mid-conversation)
  • Optional system prompt
  • A sharing scope (private · workspace · users)
  • A creator (you, unless forked from someone else’s chat)
Chats live in the sidebar under the Mine tab by default. Switch to Shared to see chats others have shared with you, or Bookmarks for pinned messages.

​
Actions on a chat

  • Fork — copy a chat at a specific message. Useful for branching off “what-if” directions without losing the original.
  • Move to project — pick a project from the chat’s ⋯ menu (Move to…) to file it there, or Remove from project to send it back to All chats.
  • Rename / delete — on the chat menu (owner only)
  • Make temporary — won’t appear in history (useful for throwaway experiments)

​
Projects

A project is a folder for related chats. Projects carry default settings:
  • Default system prompt — applied to every new chat (chat can override)
  • Sharing scope — chats inherit unless they set their own
Create a project via the New project button below your project list in the sidebar. Give it a name like “Marketing Copy”, “Research Q4”, “Production bug triage”.

​
Cascading sharing

Sharing is set per-project, and chats inherit:
  • Project scope = workspace → every chat inside is visible to the workspace (unless the chat overrides to private)
  • Project scope = users [A, B] → only members A, B see the project and its chats
  • Chat overrides parent scope if set
See Sharing for the full matrix. Type in the Search chats box at the top of the sidebar. Search matches both the words you type and what your chats are about, so “rate limiting” also finds a chat that only ever said “throttling”. Results respect sharing — you only see chats you have access to.

​
Memory scope

Each project carries a memory scope deciding whether it draws on the rest of your chats, and whether they can draw on it. Set it from the project menu. See Memory and context for what each option means in both directions.

​
Temporary chats

Toggle Temporary on a chat to keep it out of history. Messages still count toward credits, but the chat disappears from the sidebar the moment you leave it. Good for experiments you don’t want cluttering the list.