Chats
A project has its own conversation history.
Project chats are loaded from the project scope, sorted by recent activity, and kept out of the rest of your account unless you choose otherwise.
Projects
Give serious work its own room.
Projects turn just4o.chat from a loose stream of chats into a real workspace. Each project gets its own chats, files, memory layer, goal, custom instructions, icon, and color so the work stays coherent when you leave and when you come back.
Chats stay scoped to the projectFiles attach to the same workspaceProject memory stays separate from global memoryGoal and custom instructions live with the work
SR
Launch site refresh
Files, chats, and memory scoped together.
12Chats
8Memories
4Files
Project chats
Homepage hero rewrite
GPT-5.4 mini · Persona on · Updated 12m ago
Pricing comparison cleanup
Claude Sonnet · 3 files attached
Launch FAQ draft
Gemini · Memory in scope
Goal
Ship the public refresh without losing approved language.
Files
site-map.md, pricing-notes.docx, launch-brief.pdf, feature-copy.txt
Project memory
Warm tone. No filler. Keep model choice explicit. Preserve approved copy.
Scoped by design
Everything that should stay together, stays together.
Projects are not cosmetic folders. They have their own storage, their own chat list, and their own memory scope, which is why long-running work feels stable instead of smeared across your whole account.
Files
Files belong to the workspace, not to one lucky message.
Upload files into the project, browse them from the project view, and keep the source material attached to the same body of work.
Memory
Memory stays local when the job needs local context.
Project memories sit beside the project instead of blending into your account-wide memory, so a launch plan does not leak into unrelated work.
Workspace shape
A project is configured like a real working surface.
The creation flow is intentionally simple, but it has enough structure to keep a project legible later: name, description, goal, custom instructions, icon, and color all exist before you even start attaching chats and files.
NameLaunch site refresh
DescriptionHomepage, pricing, docs, and feature-page rewrite for spring launch.
GoalShip the public refresh without losing approved language or file context.
InstructionsKeep copy grounded, premium, and true to the product. No generic SaaS filler.
IdentityCustom icon and color help the workspace stay legible in the chat UI.
Project capacity by plan
Per-project file cap tops out at 10; memory stays scoped per project.Explorer
1 projects0 files15 memories
Builder
5 projects5 files30 memories
Studio
10 projects10 files75 memories
Aurora
25 projects10 files100 memories
Pro
100 projects10 files200 memories
Why it holds up
Projects reduce reassembly work.
The point is not organization for its own sake. The point is coming back to a job and finding the conversations, attached material, and memory already in the same place they were when the work was moving.
- 1
Create the workspace once.
A project can hold a name, description, goal, custom instructions, icon, and color before the first real chat even starts.
- 2
Keep the work inside that scope.
Chats, files, and project memory all live together, so every return visit starts with the right material already nearby.
- 3
Pick up where you left off.
The project view surfaces recent chats, project files, and project memories together instead of making you reconstruct the workspace from scratch.
Start the work in the workspace it deserves.
Open chat, spin up a project, and keep the next long-running job from dissolving into a pile of loose threads.